#3 Allow user to choose interface to bind

[C French]

Hi there:

Excellent package. Great work, and I am very excited to
use the package.

This is a request for the ability to specify which
interface that it is listening on. This is very useful when
running on a multi-homed system.

The reason I would want something like this, is... when
running a DHCP server in TCL, I do not want to listen to
DHCP requests on all networks, only specific ones.

It could be implemented as udp_open with the
parameter -myaddr <addr>, and operate similar to the
way that the socket -server works for TCP sockets.

From the Tcl Manual:

"The following additional option may also be specified
before host:

-myaddr addr

Addr gives the domain-style name or numerical IP
address of the server-side network interface to use for
the connection. This option may be useful if the server
machine has multiple network interfaces. If the option is
omitted then the server socket is bound to the special
address INADDR_ANY so that it can accept connections
from any interface. "

**

I am going to try to submit a patch for approval, but I
just wanted to request it formally in case there was
something already in the works.

[Pat Thoyts]

Logged In: YES
user_id=202636

This WILL be in the next version.

[Daniel Kushner]

Logged In: YES
user_id=1875065
Originator: NO

I'm a test engineer/routing protocols. I'd like to use your tcludp package for building protocol test scripts. At the moment I need to create multicast DA packets (224.0.0.2) UDP port 646 (LDP protocol) on interfaces other than the primary (eth0).

I've done this before for other protocols with other packages, but different packages have diffferent limitations. I was looking at ceptcl package because it supports these options but it doesn't seem to RX multicast, I think it's a bug in it because tcludp does send and receive multicast just fine in that same set up.

I was wondering if I could make an enhancement request. I'd like it if tcludp supported multiple interfaces (and aliases for those interfaces).

There is a very good reason for this. In protocol testing (as in my case), I have a Linux connected to the corp net on my primary interface eth0. I do not want to use that interface to test other protocol implementations because it may affect the corp net. IT would not like that! ;-}

Let me know what you think.

Thanks,
- Daniel

[Daniel Kushner]

Logged In: YES
user_id=1875065
Originator: NO

I'm a test engineer/routing protocols. I'd like to use your tcludp package for building protocol test scripts. At the moment I need to create multicast DA packets (224.0.0.2) UDP port 646 (LDP protocol) on interfaces other than the primary (eth0).

I've done this before for other protocols with other packages, but different packages have diffferent limitations. I was looking at ceptcl package because it supports these options but it doesn't seem to RX multicast, I think it's a bug in it because tcludp does send and receive multicast just fine in that same set up.

I was wondering if I could make an enhancement request. I'd like it if tcludp supported multiple interfaces (and aliases for those interfaces).

There is a very good reason for this. In protocol testing (as in my case), I have a Linux connected to the corp net on my primary interface eth0. I do not want to use that interface to test other protocol implementations because it may affect the corp net. IT would not like that! ;-}

Let me know what you think.

Thanks,
- Daniel