From: tsorrent <tso...@bb...> - 2009-05-05 14:33:16
|
I had eth0 connected to a network with a DHCP assigned address. On this network the gumstix would be receiving UDP packets. The wlan0 interface had a static IP and was associated to a laptop in ad-hoc mode on a whole other network. I was forwarding UDP packets received by the gumstix on eth0 to the laptop via the gumstix's wlan0 with TCP/IP packets (using socat). I ran into similar problems that coldwarcomms mentioned. The transfer would randomly stop, the blue LED on the netpro-vx would go off and eventually I would get the same NETDEV WATCHDOG error. The only way to restore the network interfaces was to power down the gumstix and then power it back on. I've run into the same issues using other network configurations with both eth0 and wlan0. Another thing that's weird is that it seems to affect the SD card as well. For example, I might be connected through eth0 to a network with a DHCP assigned address. The wlan0 interface has been configured to be an ad-hoc interface but is not associated with another computer so there is no active data being transmitted. Trying to download files through eth0 onto the SD card produces filesystem errors on the SD card. If I comment out the auto wlan0 line in /etc/network/interfaces then I get no filesystem errors when writing to the SD card. So far I haven't been able to find a stable configuration where I can have both network interfaces active. gnmckinney wrote: > > Are they connecting to the same network segment??? > > gm... > > > > > coldwarcomms wrote: >> >> ...The problem is that after a few minutes the wlan0 driver crashes >> somehow. I get the message NETDEV WATCHDOG: wlan0: transmit timed out... >> > > -- View this message in context: http://www.nabble.com/mjpg-streamer-and-netpro-vx-wi-fi-problem-%282.6.21-kernel-default-build%29-tp22517336p23388430.html Sent from the Gumstix mailing list archive at Nabble.com. |