Leopold Palomo-Avellaneda wrtoe: > > > Hi Mathias, > > > > > > I got some differences. The route table seems better: > > > > > > Host Routing Table > > > Hash Destination HW Address Device > > > 00 0.0.0.0 00:00:00:00:00:00 rtlo > > > 01 10.0.1.1 00:1B:21:05:0C:B6 rteth0 > > > 01 10.0.0.1 00:1B:21:05:0C:FC rteth1 > > > 01 127.0.0.1 00:00:00:00:00:00 rtlo > > > 02 10.0.1.2 00:1B:21:05:0C:B6 rteth1 > > > 02 10.0.0.2 00:17:F2:26:BC:1C rteth0 > > > 03 10.0.0.3 00:17:F2:26:BC:1C rteth0 > > > 3F 10.0.1.255 FF:FF:FF:FF:FF:FF rteth1 > > > 3F 10.0.0.255 FF:FF:FF:FF:FF:FF rteth0 > > > > > > > > > no entry from 10.0.0.1 to the loopback device. > > > > That's because of your rtroute solicit loop: You are requesting also > > 10.0.0.1 to be resolved over rteth0, thus the entry for rtlo gets > > deleted while no one answers on your IP on the cable. > > ok, but the wait of 3 seconds has been important because the table route > is > different. Now is "correct" I think.
I didn't followed this thread until now, but I think you are using e1000 and you need an delay to get it working?! Then check this out: http://www.xenomai.org/index.php/RTnet:rt_e1000 > > > However I'm figthing to some bizarre problem. > > > Scenario > > > - one box with rtnet, one imac box and one robot controller > > > - rtnet 10.0.0.1; imac 10.0.0.3; robot 10.0.0.2 > > > - connect the cable from rtnet to imac and can ping > > > ping 10.0.0.1 --> 10.0.0.3 no problem > > > > > > - connect the cable from the robot to the imac and can ping > > > ping 10.0.0.3 --> 10.0.0.2 no problem > > > > > > - connect the cable from the robot to the rtnet and no ping > > > ping 10.0.0.1 --> 10.0.0.2 problem, NO ping > > > > Again, use a packet sniffer to find out what is on the wire and what is > > missing. > > packet sniffer .... Jan, I have one cable from one box to the other > directly > (crosscable .... is possible that this card has something about if and > make > some trouble with the controller card?). > Are you saying that I unplug the cable and put it in a hub, and another > cable > to the hub with a sniffer to listen the transmission? because if not, I > don't > know how to do it .. Just install wireshark (with RTcap enabled and started) and start sniffing on your boxes. Of course using a hub is also possible, even a better idea, but if you don't have this hardware available, sniffing on both boxes with wireshark would be a good start. Regards, Karl -- von Karl Reichert Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ RTnet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rtnet-users
