Menu
▾
▴
Re: [Contiki-developers] Jackdaw CDC-ECM Support
|
From: Bernd W. <be...@ci...> - 2010-08-29 14:35:25
|
On Wed, Aug 25, 2010 at 09:40:33AM +0200, Wouter Horré wrote:
> Hi Robert,
>
> It seems to work now. I get an ethernet interface that I can configure and run radvd on top. However, my contiki 2.4 node is not answering to any of the neigbor sollications. Is this code incompatible with contiki 2.4? If it is, I'll have to stick with my linux VM solution for now, since updating to contiki CVS is not an option for the short term...
I still see problems with neighbor solitation.
16:09:05.539775 02:11:22:33:44:55 > 33:33:ff:33:44:55, ethertype Unknown (0x809a), length 63:
0x0000: 01ca a8ff ffff ffcd ab55 4433 feff 2211 .........UD3..".
0x0010: 0203 d8c8 3aa4 0285 00ae f200 0000 0001 ....:...........
0x0020: 0202 1122 fffe 3344 5500 0000 0000 00ae ..."..3DU.......
0x0030: 73 s
16:09:05.540513 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 16) fe80::11:22ff:fe33:4455 > ff02::2: [icmp6 sum ok] ICMP6, router solicitation, length 16
source link-address option (1), length 8 (1): 02:11:22:33:44:55
0x0000: 0211 2233 4455
16:09:05.541938 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 56) fe80::28fe:94ff:fe2f:100 > ff02::1: [icmp6 sum ok] ICMP6, router advertisement, length 56
hop limit 64, Flags [none], pref medium, router lifetime 1800s, reachable time 0s, retrans time 0s
source link-address option (1), length 8 (1): 2a:fe:94:2f:01:00
0x0000: 2afe 942f 0100
prefix info option (3), length 32 (4): 2002:559f:e31:2::/64, Flags [onlink, auto], valid time 2592000s, pref. time 604800s
0x0000: 40c0 0027 8d00 0009 3a80 0000 0000 2002
0x0010: 559f 0e31 0002 0000 0000 0000 0000
16:09:05.559263 02:12:13:14:15:16 > 33:33:00:00:00:01, ethertype Unknown (0x809a), length 111:
0x0000: 81c8 c8ff ffff ffcd ab16 1514 feff 1312 ................
0x0010: 0203 d848 3a28 fe94 fffe 2f01 00a4 0186 ...H:(..../.....
0x0020: 005a 6940 0007 0800 0000 0000 0000 0001 .Zi@............
0x0030: 022a fe94 fffe 2f01 0040 c000 278d 0003 .*..../..@..'...
0x0040: 0440 c000 278d 0000 093a 8000 0000 0020 .@..'....:......
0x0050: 0255 9f0e 3100 0200 0000 0000 0000 0000 .U..1...........
0x0060: 02 .
16:09:06.752048 02:11:22:33:44:55 > 33:33:00:00:00:01, ethertype Unknown (0x809a), length 93:
0x0000: 01ca a9ff ffff ffcd ab55 4433 feff 2211 .........UD3..".
0x0010: 0203 d800 3a00 0000 0000 0000 0000 0000 ....:...........
0x0020: 0000 0000 00ff 0200 0000 0000 0000 0000 ................
0x0030: 01ff 3344 5587 004c b200 0000 0020 0255 ..3DU..L.......U
0x0040: 9f0e 3100 0200 1122 fffe 3344 5511 06 ..1...."..3DU..
16:09:06.752551 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 24) :: > ff02::1:ff33:4455: [icmp6 sum ok] ICMP6, neighbor solicitation, length 24, who has 2002:559f:e31:2:11:22ff:fe33:4455
Up to here everything looks Ok.
The raven board (running 2.4 prebuild binary) does a router solicitation, gets
a response and finaly does a neighbor solicitation for it's sythesized IP,
so its obvious that the router advertisement was received.
But I can't ping the board because it won't answer the neighbor solicitation
packets from the host.
Probably it never finishes it's IP configuration?
16:09:23.251836 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) 2002:559f:e31:2::15 > ff02::1:ff33:4455: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has 2002:559f:e31:2:11:22ff:fe33:4455
source link-address option (1), length 8 (1): 2a:fe:94:2f:01:00
0x0000: 2afe 942f 0100
16:09:23.266894 02:12:13:14:15:16 > 33:33:ff:33:44:55, ethertype Unknown (0x809a), length 109:
0x0000: 81c8 c9ff ffff ffcd ab16 1514 feff 1312 ................
0x0010: 0203 d800 3a20 0255 9f0e 3100 0200 0000 ....:..U..1.....
0x0020: 0000 0000 15ff 0200 0000 0000 0000 0000 ................
0x0030: 01ff 3344 5587 003a a100 0000 0020 0255 ..3DU..:.......U
0x0040: 9f0e 3100 0200 1122 fffe 3344 5501 022a ..1...."..3DU..*
0x0050: fe94 fffe 2f01 0040 c000 278d 0000 00 ..../..@..'....
16:09:24.252462 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) 2002:559f:e31:2::15 > ff02::1:ff33:4455: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has 2002:559f:e31:2:11:22ff:fe33:4455
source link-address option (1), length 8 (1): 2a:fe:94:2f:01:00
0x0000: 2afe 942f 0100
16:09:24.266822 02:12:13:14:15:16 > 33:33:ff:33:44:55, ethertype Unknown (0x809a), length 109:
0x0000: 81c8 caff ffff ffcd ab16 1514 feff 1312 ................
0x0010: 0203 d800 3a20 0255 9f0e 3100 0200 0000 ....:..U..1.....
0x0020: 0000 0000 15ff 0200 0000 0000 0000 0000 ................
0x0030: 01ff 3344 5587 003a a100 0000 0020 0255 ..3DU..:.......U
0x0040: 9f0e 3100 0200 1122 fffe 3344 5501 022a ..1...."..3DU..*
0x0050: fe94 fffe 2f01 0040 c000 278d 0000 00 ..../..@..'....
16:09:25.253078 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) 2002:559f:e31:2::15 > ff02::1:ff33:4455: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has 2002:559f:e31:2:11:22ff:fe33:4455
source link-address option (1), length 8 (1): 2a:fe:94:2f:01:00
0x0000: 2afe 942f 0100
16:09:25.266727 02:12:13:14:15:16 > 33:33:ff:33:44:55, ethertype Unknown (0x809a), length 109:
0x0000: 81c8 cbff ffff ffcd ab16 1514 feff 1312 ................
0x0010: 0203 d800 3a20 0255 9f0e 3100 0200 0000 ....:..U..1.....
0x0020: 0000 0000 15ff 0200 0000 0000 0000 0000 ................
0x0030: 01ff 3344 5587 003a a100 0000 0020 0255 ..3DU..:.......U
0x0040: 9f0e 3100 0200 1122 fffe 3344 5501 022a ..1...."..3DU..*
0x0050: fe94 fffe 2f01 0040 c000 278d 0000 00 ..../..@..'....
--
B.Walter <be...@bw...> http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
|