Yes, also must set UIPCONFIPV6RPL on the USB stick. That address in makefsdata.h is the low 64 bits of the link local address, the upper 64 bits are the link local prefix fe80::/64 until it gets an address from the RPL border router. In the meantime the raven would respond to 6lowpan pings at fe80::11:22ff:fe33:4455 from the original jackdaw or other network interface, but not the RPL jackdaw - RPL does not forward link-local packets. On ubuntu the original rpl border router uses a serial SLIP connection to the /tools/tunslip6 application, and some custom code passes a prefix for the rpl network on startup.
- Patch Net-next 2/4 6lowpan: Set And Use Mac_len For Macbook Pro
- Patch Net-next 2/4 6lowpan: Set And Use Mac_len For Mac Free
- Patch Net-next 2/4 6lowpan Set And Use Mac_len For Mac
However the usbstick uses the RNDIS network interface so there is no method to pass a prefix on startup, it has to be hard coded. The default address is bbbb::200 for the jackdaw stack, use the same prefix for the interface address e.g. You should be able to ping both. # ping6 bbbb::0 PING bbbb::0(bbbb::) 56 data bytes 64 bytes from bbbb::: icmpseq=1 ttl=64 time=0.030 ms 64 bytes from bbbb::: icmpseq=2 ttl=64 time=0.037 ms ^C - bbbb::0 ping statistics - 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.030/0.033/0.037/0.006 ms ping6 bbbb::200 PING bbbb::200(bbbb::200) 56 data bytes 64 bytes from bbbb::200: icmpseq=1 ttl=64 time=23.9 ms 64 bytes from bbbb::200: icmpseq=2 ttl=64 time=10.3 ms 64 bytes from bbbb::200: icmpseq=3 ttl=64 time=14.9 ms But i can't ping the rzraven from ubuntu. How to solve that mismatch?
+ Refresh patch 2002 with new upstream changes. + Refresh patch 2001 with newer libgit2-sys changes. + Add patch 2005 to prevent executing non-existing mdbook command during build. + Move part of typo fix for url crate to patch 1001 to 1002. Url crate is not updated in new cargo release.
Did i forgot something? The RPL network forms on the 6lowpan side of the jackdaw, you will see none of those packets with wireshark on the usb0 interface. The only way to tell if the raven has joined is to dump the jackdaw neighbor and route tables, which you can do from the debug menu on ttyACM0 (or by enabling RS232 and dumping to an external terminal). If the raven doesn't join you will need a separate sniffer to monitor the RF traffic, or enable the RPL debug printfs on one or both sides to see what is going on. If the jackdaw is started first it will put out a bunch of closely spaced RPL announcements, then they will become less frequent so as not to waste battery on the nodes. If the raven is then turned on it could take several minutes to appear in the network.
Jackdaw Menu. Built May 5 2011. m Print current mode. s Set to sniffer mode. n Set to network mode. c Set RF channel. p Set RF power.
6 Toggle 6lowpan. r Toggle raw mode. d Toggle RS232 output. S Enable sneezer mode. N RPL Neighbors.
G RPL Global Repair. e Energy Scan. R Reset (via WDT). h,?
Patch Net-next 2/4 6lowpan: Set And Use Mac_len For Macbook Pro
Patch Net-next 2/4 6lowpan: Set And Use Mac_len For Mac Free
/. For the present the bufferlength calcs in rpl-icmp6.c will need adjustment by the length difference between 6lowpan (0) and ethernet (14) link-layer headers: // bufferlength = uiplen - uipl2l3icmphdrlen; bufferlength = uiplen - uipl2l3icmphdrlen + UIPLLHLEN; //Add jackdaw ethernet header./ This must be done in three places. One of those places is where the route lifetime is decoded; without that patch the route lifetime is zero. Since you have 1200 bytes of unused RAM you could increase the size of the neighbor/route tables to 20 or so.
Patch Net-next 2/4 6lowpan Set And Use Mac_len For Mac
When the tables are full old routes will be dropped as new ones come in.