On Mon, Jan 6, 2014 at 5:51 PM, JJ <jareli.1234...@gmail.com> wrote: > > > maanantai, 6. tammikuuta 2014 14.19.59 UTC+2 Dieter Wirz kirjoitti: >> >> Did you test, if your BBB is still connected to the www while he is >> not accessible? eg with a cronjob, something like: >> * * * * * ping -c 1 google.com >> /some_path_to/ping.log > > > Works fine with 1 minute interval, no errors. > The ping crontab works as the dynamic dns updater, since I am able to ping > and ssh my BBB after the crontab excecution. With 1 minute interval, there > are no connection problems at all. > > This ping crontab may be a temporary solution to the problem, but something > is wrong blatantly. > Here's a summary: if BBB has been connected to somewhere just a moment ago, > I can connect to it. But when BBB's internet connection has been idle for a > few minutes, it won't respond my requests until next dns/ping crontab > execution.
Weird.... ..ooOO IIRC Arch and Debian have conman as default network connection manager. But in a setup you have IMHO conman is *not* the ultimate solution (conman may be great for laptops, etc). Did you have a look at conman's log files? They tend to be *not* in /var/log depending on your system. I would try the following: - Inactivate / Uninstall conman - edit /etc/network/interfaces - start the connections with "ifup eth0" HTH Dieter -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
