[nzlug] IPCop Stalling

[Nevyn]

On 2/7/07, Howard <howard-nzlug at fox.co.nz> wrote:
> on 7/02/2007 1:59 p.m. Nevyn wrote:
> > Just about every night my ADSL router appears to drop the connection
> > and then connect almost immediately (normal behavior I would've
> > thought).
> >
> > However IPCop seems to have a problem with it.
> >>> SNIP<<
>
> Hi Nevyn,
>
> What sort of ADSL device? Internal/External?  (I assume external if you
> refer to a router...)How is it connected to your IPCop box? IPSec
> bridged?  NAT? How does IPCop then get it's IP address?  Static?  DHCP?
>
> Do you know if you are being assigned a new IP address from your ISP
> when this occurs?  (You can check the IPCop box or the router's webpage
> config if it is another NAT connection to the IPCop box)
>
> Version of IPCop?  Latest with all updates? (v1.4.13)  Any unofficial
> addons that may conflict with the newest kernel added this month?
>
> Also, why would you think that the router dropping the connection would
> be normal behaviour?
>
> cheers
> H

Whoa there big boy!

It's an external ADSL modem - it's a dinosaur which I picked up off
trade me ages ago and had to update it with a similar but by no means
meant for this particular modem updated firmware to fix a problem with
bridging.

So in answer to your next question, the red device gets it's IP
address from the ADSL modem - so it has the external IP addy meaning
that all the modem is doing is routing information from the phone
lines into a more usable Ethernet connection and the IP Cop box is
taking care of things from there. The green device is static.

I'm assuming that Slingshot is renewing the IP address when this
happens as it seems to be fairly constant. I.e. it happens around 4am
in the morning. I did have the IP Cop box rebooting at around 5 in the
morning but kept on getting woken up by the beeps when it starts up
and sometimes it either didn't need the reboot or the disconnect would
happen much earlier.

Yep, definitely version 1.4.13 and definitely on addon's. Basically it
has to just behave as a embedded device - I like what it does and I
don't care how it does it.

What I'm looking for is some kind of time out - If it's been trying to
connect for say.... more than 5 minutes, disconnect and try again.