"Thomas B. Rücker" wrote (ao):
Bad news: Something horribly breaks the network behaviour of this board. It does NOT acquire a routed IPv6 prefix through stateless auto configuration. It doesn't even see the route advertisements (checked by installing 'radvd' and running 'radvdump'). Other devices on the network use those without issue. The IPv6 link local address is NOT reachable over ICMPv6. It becomes reachable by _one_ node at a time by pinging that node _from_ the device. Actually the same behaviour can be observed for legacy IPv4 too. You can't ping the device until the Dragonboard has pinged that particular machine and its address first.
I'm not going to bother explaining how broken such network behaviour is, it's rather obvious. Time to get a USB ethernet adaptor from my drawer.
Is there anything I can do to the wifi driver to fix this? Like disabling all optimizations and power saving? I highly suspect this is one of those optimized until useless for anything than an Android phone in its basic use case drivers.
FWIW, there is a post on the forum regarding this issue:
https://www.96boards.org/forums/topic/410c-linux-and-incoming-tcpip-connecti...
Patryk writes: "Today we noticed that in when the 410C is configured in hotspot mode using hostapd (so that you can directly connect to it without going through a Wifi network), this problem does not occur."
Sander