Paul, Static IP is not an option, they won't allow it. That ping script might work. I'll try it in the morning as it is now almost 1AM and I'm headed to bed.
Thanks! Andy On Sun, Sep 14, 2014 at 12:34 AM, Paul Boniol <[email protected]> wrote: > I do not have a Raspberry Pi so I can't test anything / have Pi specific > experience. So this is general Linux / computer responses. > > The best option would be if you could request a static (non-DHCP) IP for > it, and put that in instead. You could then avoid the whole DHCP / > response time issue. If your work network too dynamic this would be a > problem, hopefully not. > > You could issue a command to sleep so long that it is guaranteed to be > there (5 minutes?) right before running Chrome. > > Would a script like this work? > http://stackoverflow.com/questions/6118948/bash-loop-ping-successful The > script waits until a ping is successful. > > Paul > > On Sat, Sep 13, 2014 at 11:01 PM, Curt Lundgren <[email protected]> > wrote: > >> I've read (somewhere) that ISC DHCP doesn't work well beyond a class C >> subnet. We run a series of class C networks (as opposed to something >> larger) and have had no issues. >> >> >> On Sat, Sep 13, 2014 at 10:55 PM, Andrew Farnsworth <[email protected]> >> wrote: >> >>> I am running the latest raspbian as of Sept 6 plus full apt-get >>> dist-upgrade so I should be fully up to date. When I run this same Pi at >>> home it works perfectly, it has to do with the fact that the DHCP server at >>> the office takes loads of time to respond with a network configuration for >>> the Pi. I suspect this is because it is running on a full class B subnet >>> but I am not sure. >>> >>> Andy >>> >>> On Sat, Sep 13, 2014 at 11:47 PM, Curt Lundgren <[email protected]> >>> wrote: >>> >>>> What distro are you using? I've played with 3 Raspberry Pi units >>>> running Raspian Wheezy, and they've all been rock-solid. >>>> >>>> Curt >>>> >>>> >>>> On Sat, Sep 13, 2014 at 10:21 PM, Andrew Farnsworth <[email protected]> >>>> wrote: >>>> >>>>> Evening everyone, >>>>> I am experiencing an interesting problem and thought I would reach >>>>> out for some help. I have a raspberry pi that I am using at the office to >>>>> drive a large monitor and display a dashboard. The problem I have is that >>>>> when it boots up it is not immediately receiving a DHCP response (or at >>>>> least not receiving the leased IP) very quickly;. Meanwhile, the boot >>>>> process continues on and loads X windows and chrome / chromium launching >>>>> full screen to a URL that is the basis for the dashboard. The problem is >>>>> that all this loads before the ethernet interface actually receives it's >>>>> IP >>>>> address and initializes so chrome just reports "Cannot load this page". >>>>> Usually after several reboots it manages to time things correctly so the >>>>> dashboard displays. I have tried adding time to the process by sticking >>>>> sleep commands into the xinitrc script but not very successful. I have >>>>> tried adding pings to the xinitrc thinking that would "force" the >>>>> interface >>>>> up but ping just fails immediately too. What I need is a command I can >>>>> run >>>>> that will wait until the network interface is fully initialized and then >>>>> return allowing chrome to load and successfully reach the URL for the >>>>> Dashboard. >>>>> >>>>> I tried writing a simple perl script to loop until it receives a >>>>> successful response to ping, but it doesn't appear to execute during the >>>>> boot process. >>>>> >>>>> Any Suggestions? >>>>> >>>>> More as it happens... >>>>> >>>>> Andy Farnsworth >>>>> >>>>> > -- > -- > You received this message because you are subscribed to the Google Groups > "NLUG" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nlug-talk?hl=en > > --- > You received this message because you are subscribed to the Google Groups > "NLUG" 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/d/optout. > -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" 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/d/optout.
