Question: UDP Extension, can it support more than one IP interface or phys interface? - TCL

dkushne...@yahoo.com wrote:
> Can I utilize more than one physical or IP interface like I can with
> the TCL TCP "socket" implementation.

It current uses "any/all interfaces".

> The TCP socket command supports a
> -myaddr option to specify a source IP address to use. I really need
> this option for what I am writing. I hope it's not a lost cause!
>
> Is there any way to do this with UDP extension?

Not with the tcludp extension as it currently stands; I've just
checked the source code, and that currently hard-codes the local host
address to be 0 (== any) which isn't what you need. Looks like time to
write a small Feature Request...

Donal.

<dkushner99@yahoo.com> wrote in message
news:1183504163.580121.192120@e16g2000pri.googlegroups.com...
> Hello,
> I have a question concerning UDP Extension.
>
> Can I utilize more than one physical or IP interface like I can with
> the TCL TCP "socket" implementation. The TCP socket command supports a
> -myaddr option to specify a source IP address to use. I really need
> this option for what I am writing. I hope it's not a lost cause!
>

Dan, tell us what network functionality you are trying to emulate and maybe
we can suggest an alternative. What are you trying to do?

On Jul 3, 10:35 pm, "Tom Conner" <tcon...@olopha.net> wrote:
> <dkushne...@yahoo.com> wrote in message
>
> news:1183504163.580121.192120@e16g2000pri.googlegroups.com...
>
> > Hello,
> > I have a question concerning UDP Extension.
>
> > Can I utilize more than one physical or IP interface like I can with
> > the TCL TCP "socket" implementation. The TCP socket command supports a
> > -myaddr option to specify a source IP address to use. I really need
> > this option for what I am writing. I hope it's not a lost cause!
>
> Dan, tell us what network functionality you are trying to emulate and maybe
> we can suggest an alternative. What are you trying to do?

I'm a SW test engineer. I test protocols for routers. I've developed
BGP simulation tool using TCL TCP sockets. I've done IGMPv1,2,3 using
TCL and packetsource libs (but that doesn't support win).

I need to develop an LDP simulation tool this time. LDP utilizes UDP
(minimally) and TCP for LDP protocol. I could do a lot more with the
tool (high level simulations) if I could utilize multple interfaces
for the sim tool.


- Daniel

On Jul 3, 10:35 pm, "Tom Conner" <tcon...@olopha.net> wrote:
> <dkushne...@yahoo.com> wrote in message
>
> news:1183504163.580121.192120@e16g2000pri.googlegroups.com...
>
> > Hello,
> > I have a question concerning UDP Extension.
>
> > Can I utilize more than one physical or IP interface like I can with
> > the TCL TCP "socket" implementation. The TCP socket command supports a
> > -myaddr option to specify a source IP address to use. I really need
> > this option for what I am writing. I hope it's not a lost cause!
>
> Dan, tell us what network functionality you are trying to emulate and maybe
> we can suggest an alternative. What are you trying to do?

Question: What does "any" mean? Does this mean it will send out all
interfaces or just the primary interface? I might be able to work-
around it if it sends out all interfaces (maybe). Most of what I need
is TCP anyway but I need UDP for the LDP UDP-HELLO messages.

I might try to modify the source code myself but I have very little
experience with C. I looked at the source too and it seems pretty
simple. I like the implementation of the UDP Extension from what I've
seen (except for the interface limitation).
- Daniel
- Daniel

dkushner99@yahoo.com writes:

>>
>> Dan, tell us what network functionality you are trying to emulate and maybe
>> we can suggest an alternative. What are you trying to do?
>
>Question: What does "any" mean? Does this mean it will send out all
>interfaces or just the primary interface? I might be able to work-
>around it if it sends out all interfaces (maybe). Most of what I need
>is TCP anyway but I need UDP for the LDP UDP-HELLO messages.
>
>I might try to modify the source code myself but I have very little
>experience with C. I looked at the source too and it seems pretty
>simple. I like the implementation of the UDP Extension from what I've
>seen (except for the interface limitation).

Adding a -myaddr is on the list to be done.
What you are doing -- sounds like you might find hping3 useful.
See http://wiki.hping.org/94

--
Pat Thoyts http://www.patthoyts.tk/
To reply, rot13 the return address or read the X-Address header.
PGP fingerprint 2C 6E 98 07 2C 59 C8 97 10 CE 11 E6 04 E0 B9 DD

On Jul 4, 2:08 pm, Pat Thoyts <cnggub...@hfref.fbheprsbetr.arg> wrote:
> dkushne...@yahoo.com writes:
>
> >> Dan, tell us what network functionality you are trying to emulate and maybe
> >> we can suggest an alternative. What are you trying to do?
>
> >Question: What does "any" mean? Does this mean it will send out all
> >interfaces or just the primary interface? I might be able to work-
> >around it if it sends out all interfaces (maybe). Most of what I need
> >is TCP anyway but I need UDP for the LDP UDP-HELLO messages.
>
> >I might try to modify the source code myself but I have very little
> >experience with C. I looked at the source too and it seems pretty
> >simple. I like the implementation of the UDP Extension from what I've
> >seen (except for the interface limitation).
>
> Adding a -myaddr is on the list to be done.
> What you are doing -- sounds like you might find hping3 useful.
> Seehttp://wiki.hping.org/94
>
> --
> Pat Thoyts http://www.patthoyts.tk/
> To reply, rot13 the return address or read the X-Address header.
> PGP fingerprint 2C 6E 98 07 2C 59 C8 97 10 CE 11 E6 04 E0 B9 DD


Hi Pat,
Thanks for your response. I looked at hping briefly. I have not tried
it yet. I was impressed with the number of options it supports but
there are also some limitations that make it less that optimal for my
applications.

It's really slick in that it supports so many options for TCP and UDP
and also RAW IP (I like that a lot). Does it support RAW packets (L2,
not IP). I really need all of this kind of flexibility for what I do.
There are some things that I do not like though ... one thing is that
it is a compiled executable like an OS command so to use it from TCL I
need to call the .exe. Another thing that I do not like is that (I
have not tried it yet), but it looks like I cannot use data in the
script to use for the data portion of the packet. It appears (I may be
wrong) as though it only takes data (packet payload) from a file.

I think that for my application at least, it would be better if the
package was a loadable extension to TCL and it included the
flexibility of specifying the data portion f the packet from a TCL
variable. that would be perfect. I( wonder how much work it would be
to make it that way? There is another package that I used that I like
a lot but there is no Windows support for it. Also, I do not think
it's avalable anymore ... some copmpany bought the code. It was called
packetsource. That was a slick package but it didn't have all of the
options thast hping has (close though). The developer of the
packetsource also included lots of protocols to use with the tool
implemented in TCL. Pretty cool!!
- Daniel

dkushner99@yahoo.com wrote:
> Thanks for your response. I looked at hping briefly. I have not
> tried it yet. I was impressed with the number of options it
> supports but there are also some limitations that make it less
> that optimal for my applications.
>
If you are working on *NIX, you may be interested in ceptcl
(http://wiki.tcl.tk/11140). It allows you to specify the source IP
address when sending UDP packets.


Schelte.
--
set Reply-To [string map {nospam schelte} $header(From)]

On Jul 5, 12:43 pm, Schelte Bron <nos...@wanadoo.nl> wrote:
> dkushne...@yahoo.com wrote:
> > Thanks for your response. I looked at hping briefly. I have not
> > tried it yet. I was impressed with the number of options it
> > supports but there are also some limitations that make it less
> > that optimal for my applications.
>
> If you are working on *NIX, you may be interested in ceptcl
> (http://wiki.tcl.tk/11140). It allows you to specify the source IP
> address when sending UDP packets.
>
> Schelte.
> --
> set Reply-To [string map {nospam schelte} $header(From)]

That looks like it might do the trick. No Windows though .. I'd rather
use Linux or Unix myself, but here where I work most of the people are
using windows. I tried to get the package and I downloaded a .tar file
but have not yet been able to open it. I'll keep trying.

- Daniel