Am 15.09.2010 15:12, Frederik Bayart wrote: > Hallo, > > I try to use rtnetproxy or rtmac+nomac (without tdma), but I don't > succeed to send non-RT messages. Has anyone experience with this ? > > This is my configuration : > > xenomai : kernel linux-2.6.30.8 + adeos-ipipe-2.6.30.8-x86-2.4-09.patch > rtnet : 0.9.12 > > I have build rtnet with following config flags : > > config_flags=--enable-eepro100 --disable-8139 --disable-e1000 > --disable-e1000-new --enable-rtipv4 --enable-router --enable-net-routing > --enable-rtpacket --enable-tdma --enable-rtcap --enable-rtcfg > --enable-nomac --enable-udp --enable-tcp --enable-rtmac --enable-proxy > --enable-proxy-arp > > > I have 2 network cards : > > - eth0 is an e1000 card > - rteth0 is an e100 card. > > using mac+nomac > =============== > To start rtnet, I execute the commands below : > > rmmod e100 > modprobe rtnet > modprobe rtipv4 > modprobe rtudp > modprobe rttcp > modprobe rtpacket > modprobe rt_eepro100 > modprobe rtmac > modprobe nomac > nomaccfg rteth0 attach > rtifconfig rteth0 up 192.168.0.19 netmask 255.255.255.0 > > rtroute add 192.168.0.254 00:0f:34:cc:1a:77 dev rteth0 rtroute add > 192.168.0.0 netmask 255.255.255.0 gw 192.168.0.254 rtroute add > 255.255.255.0 netmask 255.255.255.0 gw 192.168.0.254 > > To be sure that the correct interface is used, I disable eth0. > ifdown eth0 > ifup vnic0 > > My network configuration (/etc/network/interfaces) is : > > iface vnic0 inet static > address 192.168.0.17 > netmask 255.255.255.0 > gateway 192.168.0.254 > > vnic0 has now ip address 192.168.0.17 and rteth0 has 192.168.0.19. > > My route table is : > > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 192.168.0.0 * 255.255.255.0 U 0 0 0 > vnic0 > default 192.168.0.254 0.0.0.0 UG 0 0 0 > vnic0 > > and my rtroute table is : > > Host Routing Table > Hash Destination HW Address Device > 3E 192.168.0.254 00:0F:34:CC:1A:77 rteth0 > 3F 192.168.0.255 FF:FF:FF:FF:FF:FF rteth0 > > Network Routing Table > Hash Destination Mask Gateway > 00 192.168.0.0 255.255.255.0 192.168.0.254 > 3F 255.255.255.0 255.255.255.0 192.168.0.254 > > > Now I succeed to send RT-messages over UDP to a remote host 192.168.0.8. > However, I am not able to send non-RT messages to 192.168.0.8 : > > - no reply on ping 192.168.0.8 > - both udp and tcp messages sent via netcat don't arrive at 192.168.0.8 >
Do you have nomac running on the other side as well? That's required as it works by encapsulating the non-RT packets into RTmac frames that normal nodes do not understand. > using rtnetproxy > ================ > rmmod e100 > modprobe rtnet > modprobe rtipv4 > modprobe rtudp > modprobe rttcp > modprobe rtpacket > modprobe rt_eepro100 > rtifconfig rteth0 up 192.168.0.19 netmask 255.255.255.0 > > rtroute add 192.168.0.254 00:0f:34:cc:1a:77 dev rteth0 rtroute add > 192.168.0.0 netmask 255.255.255.0 gw 192.168.0.254 rtroute add > 255.255.255.0 netmask 255.255.255.0 gw 192.168.0.254 > > When I execute now > > modprobe rtnetproxy, > > I get the kernel dump below. I have build rtnet on the system where I am > testing, so the drivers are compatible with the kernel > > kernel:Oops: 0000 [#1] SMP > Killed > philippulus:~# > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel:last sysfs file: /sys/class/net/lo/operstate > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel:Process modprobe (pid: 2737, ti=f6530000 task=f68620c0 > task.ti=f6530000) > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel:I-pipe domain Linux > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel:Stack: > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: 00000280 000000d0 000005dc ffffffff f6864480 00000000 f8193940 > c02acf41 > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: 00000000 00000000 ffffffff 00000000 ffffffff 00000010 c03c6240 > ffffffff > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel:Call Trace: > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<c01bb4d1>] ? __kmalloc+0xa8/0x105 > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<c02acf41>] ? rtmsg_ifinfo+0x7c/0xdd > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<c02acfd7>] ? rtnetlink_event+0x35/0x38 > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<c0136416>] ? notifier_call_chain+0x2a/0x47 > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<c013649f>] ? raw_notifier_call_chain+0x9/0xc > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<c02a6efd>] ? register_netdevice+0x332/0x36f > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<c02a360b>] ? __dev_get_by_name+0x16/0x6b > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<c021f920>] ? strlcpy+0x11/0x3d > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<c02a3783>] ? dev_alloc_name+0x123/0x134 > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<c02a6f69>] ? register_netdev+0x2f/0x3b > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<f81960d8>] ? rtnetproxy_init_module+0x9f/0x156 [rtnetproxy] > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<f8196039>] ? rtnetproxy_init_module+0x0/0x156 [rtnetproxy] > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<c010112d>] ? do_one_initcall+0x44/0x140 > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<c014347e>] ? sys_init_module+0x87/0x187 > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel: [<c01028e5>] ? sysenter_do_call+0x12/0x16 > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel:Code: 40 48 ba 0a 00 00 00 89 44 24 28 b9 04 00 00 00 8d 44 24 > 28 50 89 f8 e8 c0 ad f7 ff 5a 85 c0 0f 88 cf 02 00 00 8b 85 c0 01 00 00 > <8b> 40 14 85 c0 74 26 8b 58 10 83 c3 08 89 d8 e8 f6 4e f7 ff ba > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel:EIP: [<c02ac984>] rtnl_fill_ifinfo+0x1b5/0x49e SS:ESP > 0068:f6531e90 > > Message from sysl...@philippulus at Sep 15 14:41:38 ... > kernel:CR2: 0000000000000014 > There were some fixes sent a while back for rtnetproxy, maybe that oops could be healed by them. Unfortunately, the changes are not mergable as-is, and I haven't found the time to do the remaining work. In the meantime, it might be worth trying rtnetproxy on a more recent kernel. Likely the oops is due to a regression introduced while fixing the code for new kernels. Jan
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
