On Thursday, August 29, 2013 2:44:46 PM UTC-4, garyamort wrote:
I had some very....odd network issues with my BBB. Periodically when it > was running on the network, all other pc's on the network would lose their > network connection[a mix of windows8, windows 7, and linux mint 14 - a > ubuntu derivative] > > Unplugging the BBB would result in the network magically start working > again. > Running Angstrom on a BBB that I got just a couple of days ago, I experience the same behavior, primarily with the BBB plugged into a Windows XP Pro machine. > > Checking the logfiles on my BBB I noticed that I had forgotten to set the > date, so all the timestamps where wildly offdate. Since I needed the date > to be realitvely current for other items, I installed the ntpd server[sudo > apt-get install ntp] so that the daemon could keep the system clock up to > date. > I set this up using the method shown by Derek Molloy's post, "Automatically Setting the Beaglebone Black Time Using NTP<http://derekmolloy.ie/automatically-setting-the-beaglebone-black-time-using-ntp/>". And to be sure that the time is set, I have a variant of his ee402/scripts/StartUSBNetwork (modified for the North American instead of the Irish NTP pool: north-america.pool.ntp.org) that I run by hand after logging in. It frequently hangs for a long time, since it can't find the pool (because it can't connect to the name server.) [See Molloy's "Getting Started – USB Network Adapter on the Beaglebone" for details.] These things work only if the BBB is able to see the name servers (e.g. 8.8.8.8) and, especially, the gateway (192.168.1.7), which I've found it frequently cannot, both when connected to a Windows 7 and to a Windows XP computer. FLAKY!! Right now, it's working just fine, but for the previous dozen times earlier today, it failed...even trying reboots of the Windows machine. Yes, very FLAKY!! > > Oddly enough, after doing that all my network issues disappeared. I'm > guessing the problem is somehow related to the dhcp client running into > issues with the timestamps - but that that is just a guess. > > I still have no clue what caused the problem, but at least it has stopped > for me. Figured I'd throw the suggestion out there as it is an easy work > around. > Thanks for sharing your experience. I hope someone can provide some insight about the cause and--even better--a solution. This is getting old. -R -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
