Network Traffic Generation

[Aviv Greenberg]

Seems like you have a routing problem.

Say you have 1 box with 2 interfaces, having IP x and y.
When you try to ping or connect to either x or y, the routing table is
being consulted.
The answer of "what is the route to x" is "Local" - and it is treated
as loopback.
I don't think actual packets will go on the wire.

you can try crafting mind bogling routing rules to fix it, or better
use 2 boxes.

2009/3/13 Daniel Feiglin <dilogsys at inter.net.il>:
> Hello folks!
>
> I'm trying to use a Linux box as a packet traffic generator. It has two
> NICs configured with fixed IP addresses, 192.168.2.100/101. For testing
> purposes, I connected the two NICs to each other with a crossed network
> cable (hardware loopback). For what it's worth, they can both be pinged
> from the host and the ifconfig output looks fine.
>
> Later, the crossed cable will be replaced by a radio link (which relates
> to the purpose of all this).
>
> To carry out the packet generation, I downloaded and built the iperf
> program (http://sourceforge.net/forum/forum.php?forum_id=808751).
>
> I'd like to sent stuff from .100 to .101 using the client and server
> instances of iperf in two console sessions and (later) monitor what's
> happening with tcpdump from a third session.
>
> For various reasons, it's not working. (I have successfully done it
> using two machines on either side of the radio link, which is  the
> "standard" method.)
>
> Has anyone on the list done this (using iperf or something similar)
> using a single box with two NICs?
>
> Regards,
>
>
> Daniel
>
> P.S. I'll supply further background material if there is interest in
> this subject.
>
>
>
>
>
>
> _______________________________________________
> Linux-il mailing list
> Linux-il at cs.huji.ac.il
> http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
>
>



-- 

Joan Collins  - "The problem with beauty is that it's like being born
rich and getting poorer."