Leopold Palomo-Avellaneda wrote: > Hi, > > I know that this issue have been treated before but I'm having a trouble and > I > don't know how to solve. I have a box with a xenomai-2.6.23 with rtnet-trunk. > I have one network card that I want to use in rtnet (rteth0). I don't want to > use tdma. I have this script to load rtnet: > > ---------------------------------------------------------------------- > #!/bin/sh > sudo mknod /dev/rtnet c 10 240; > sudo insmod modules/rtnet.ko; > sudo insmod modules/rtipv4.ko; > sudo insmod modules/rtpacket.ko; > sudo insmod modules/rt_e1000.ko; > sudo insmod modules/rt_loopback.ko; > sudo ./sbin/rtifconfig rtlo up 127.0.0.1 > sudo ./sbin/rtifconfig rteth0 up 10.0.0.1 netmask 255.255.255.0; > for((i=0;i<5;i++)); do > ./sbin/rtroute solicit 10.0.0.$i dev rteth0 > done > sudo ./sbin/rtroute > ---------------------------------------------------------------------- > > I cannot understand why, when I run the rtroute at the end, I got this: > > Host Routing Table > Hash Destination HW Address Device > 00 0.0.0.0 00:00:00:00:00:00 rtlo > 01 10.0.0.1 00:00:00:00:00:00 rtlo > 01 127.0.0.1 00:00:00:00:00:00 rtlo > 3F 10.0.0.255 FF:FF:FF:FF:FF:FF rteth0 > > the second entry.... > > I don't have assigned that 10.0.0.1 to rtlo. I have assigned it to rteth0 and
RTnet's routing is very explicit: Packets sent to your local IP address are, in fact, looped back over rtlo. So you need a routing table entry directing such packets to rtlo. These entries are generated automatically if rtlo is up and some real interface is configured. That's all. Generally, you don't need rtlo at all, and you could switch it off or ignore what is configured here. > the routes attached to it. So, I cannot make a simple ping to 10.0.0.2, I > got: > $ sudo sbin/rtping 10.0.0.2 > Real-time PING 10.0.0.2 56(84) bytes of data. > ioctl: No route to host > > however I must do it explicit: > sudo ./sbin/rtroute add 10.0.0.2 00:1B:21:05:0C:B6 dev rteth0 That's due to RTnet's static ARPing - no routes without explicit ARP, triggered locally or started by the communication partner. > > then > Host Routing Table > Hash Destination HW Address Device > 00 0.0.0.0 00:00:00:00:00:00 rtlo > 01 10.0.0.1 00:00:00:00:00:00 rtlo > 01 127.0.0.1 00:00:00:00:00:00 rtlo > 02 10.0.0.2 00:1B:21:05:0C:B6 rteth0 > 3F 10.0.0.255 FF:FF:FF:FF:FF:FF rteth0 > > en then I can do a rtping ... > > no success because I think that my vxworks controller is missconfigured, but > I > got: > > sudo ./sbin/rtping 10.0.0.2 > Real-time PING 10.0.0.2 56(84) bytes of data. > > and the leds of the card are blinking > > someone can tell me why this behaviour? I have read the readmes but or I > don't > understand then, but I don't find my mistake. Use RTcap + tcpdump or wireshark to debug such issues. Jan
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- 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
