As requested by Bodhi on the kernel thread, I'm going to make a separate topic to unclutter that thread.
I recently setup a Seagate DockStar with the 3.16 rootfs and latest Uboot. Everything is working fine on it, but have run into a potential limit of the kernel (or my understanding of the process).
I have setup several "offsite sync" boxes in the past, using a Raspberry Pi and an external USB hard drive. I have them at a few different locations, with rsync jobs and btsync installs keeping my data in it's own kind of "cloud".
The dockstar is a perfect device to do this with since I am out of RPi at the moment. The problem is that I use the N2N project's mesh VPN network to keep all of my devices talking to each other.
http://www.ntop.org/products/n2n/
It's basically a peer-to-peer implementation of what OpenVPN does, creating TUN/TAP devices and linking them with encryption and ARP routing. The difference is that OpenVPN uses a server->client architecture, while N2N has a tracker and nodes (peer to peer).
Regardless, the N2N compile goes fine on the kirkwood, and the binaries run without a problem. I can see on the tracker (supernode) when the kirkwood box comes online, and I can use 'arping' to do ARP pings between the kirkwood device, and any other device on my mesh (and visa versa).
Where it all goes wrong is that is all I can do. I see the registration on the tracker, and I can 'arping', but I can pass no real traffic through the interface. ICMP pings fail, ssh fails, everything. ARP is the only traffic that seems to be able to communicate.
Last night I did a RPi fresh install and a fresh install on the kirkwood, and line for line did the same steps. The RPi joined the mesh and could ping and connect, while the kirkwood could not (only arp traffic).
The tun0 device is being made properly, shows packets sent and received (the ARP stuff i'm assuming), and everything looks identical to the RPi done in tandem. My only thought is that the kernel is missing something, or there is a package in a RPi install of Raspbian that i'm not thinking of that I should add to the Debian kirkwood installl to fix it.
Thoughts?
I recently setup a Seagate DockStar with the 3.16 rootfs and latest Uboot. Everything is working fine on it, but have run into a potential limit of the kernel (or my understanding of the process).
I have setup several "offsite sync" boxes in the past, using a Raspberry Pi and an external USB hard drive. I have them at a few different locations, with rsync jobs and btsync installs keeping my data in it's own kind of "cloud".
The dockstar is a perfect device to do this with since I am out of RPi at the moment. The problem is that I use the N2N project's mesh VPN network to keep all of my devices talking to each other.
http://www.ntop.org/products/n2n/
It's basically a peer-to-peer implementation of what OpenVPN does, creating TUN/TAP devices and linking them with encryption and ARP routing. The difference is that OpenVPN uses a server->client architecture, while N2N has a tracker and nodes (peer to peer).
Regardless, the N2N compile goes fine on the kirkwood, and the binaries run without a problem. I can see on the tracker (supernode) when the kirkwood box comes online, and I can use 'arping' to do ARP pings between the kirkwood device, and any other device on my mesh (and visa versa).
Where it all goes wrong is that is all I can do. I see the registration on the tracker, and I can 'arping', but I can pass no real traffic through the interface. ICMP pings fail, ssh fails, everything. ARP is the only traffic that seems to be able to communicate.
Last night I did a RPi fresh install and a fresh install on the kirkwood, and line for line did the same steps. The RPi joined the mesh and could ping and connect, while the kirkwood could not (only arp traffic).
The tun0 device is being made properly, shows packets sent and received (the ARP stuff i'm assuming), and everything looks identical to the RPi done in tandem. My only thought is that the kernel is missing something, or there is a package in a RPi install of Raspbian that i'm not thinking of that I should add to the Debian kirkwood installl to fix it.
Thoughts?