Jan Kiszka wrote: > LEBRETON, Julien wrote: >> I check that there is no packet leaving rteth2 by looking at my NIC >> interface and the destination host. >> When I ping 152.157.1.2 my input NIC's receive data (data led is flashing) >> but the data led of my output NIC (rteth2) isn't flashing.. Ok it is not >> relevant. >> Another way to check is to look at the destination box. I have captured >> packet on his interface. But no packet arrived. >> >> And I have noticed something odd.. >> On my windows box, I can ping any machine even those that do not exist.. >> >> ping 152.157.1.2 => I have a reply >> ping 152.157.1.56 => I have a reply (but no machine with this IP address) >> ping 153.156.25.24 => I have a reply.. this is very odd.. > > Check where those replies come from. Then start over with much less > routing entries on both sides to understand the effect of each rule better.
Some private discussion revealed a potential reason for unwanted replies (and broken IP forwarding): Do you have CONFIG_RTNET_RTIPV4_ROUTER enabled? It is mandatory when RTnet shall forward IP packets. If it is off and a RTnet box receives packets not directed to it, the behavior should be considered as unspecified. Jan
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
