🚀 go-pugleaf

On Jun 28, 5:19 pm, Jeff Liebermann <je...@cruzio.com> wrote:
> On Fri, 27 Jun 2008 14:58:53 -0700 (PDT), BigAl...@gmail.com wrote:
>
> (chop...)
>
> >Sound it sounds like things are actually working the way they should,
> >albeit thats not nessecarily the way I want them to work?
>
> Yep.  I had a fast lunch today with a real live genuine expert on
> ethernet and networking.  I managed to squeeze in your problem and got
> the same answer that I supplied.  DHCP clients have no way to know
> that the DHCP server has issued a new lease.  He indicated that I
> should use a keep alive script, similar to what I suggested.
>
> Short form version:  It's not going to get easily fixed.
>
> >Perhaps I should :
> >(a) make my ADSL connection more reliable so it doesnt disconnect
> >(b) Set the 502T to PPPoA mode and turn on DHCP, and make it a DMZ.
>
> Neither.  You should find out WHY your ISP is dropping the lease on
> short notice with only a minimum disconnect.  The ISP should retain
> the old lease for at least an hour or two, which means you should be
> able to disconnect for about an hour and still get the same IP address
> as before.  It's even scribbled into the RFC's somewhere (I'm not
> going to risk my sanity by reading RFC's at this time), that the DHCP
> server should store the leases for some time, and not re-issue an old
> one until the lease expires.  If you're ISP issues 24 hour leases (a
> common number), then you should get back the same IP even after a 23.9
> hr disconnection.  In orther words, it's NOT your problem, it's your
> ISP's problem.  Do some testing and complain if a short disconnect
> results in a immediate change in IP address.
>
> The easiest way to test this is to temporarily remove DD-WRT from the
> picture.  Just plug a computah into the DSL modem and get the IP
> directly from the ISP's server.  Note the lease time.  Now, unplug the
> DSL modem and see what happens.  It should give you back the same IP.
>
> >I would then get the 502T to assign 10.1.1.3 to the DD-WRT and the DMZ
> >would make sure all traffic goes to the DD-WRT? I guess its still a
> >kind of double NAT? I suppose I could make the LAN side of the 502T
> >static IP with 10.1.1.3?
>
> Don't bother.  The problem is at the WAN side and probably at the ISP.
> Double NAT isn't going to help.
>
> Incidentally, make sure your DSL modem doesn't have an "inactivity
> timeout" feature.  If it has a keep alive, turn it on.  Do whatever it
> takes to keep the modem online full time.
>
> >My aim here is to make the DD-WRT do all the work, and just have the
> >502T terminate the connection and pass everything on to the DD-WRT
> >where all the firewalls, acess restrictions and port forwards are
> >setup.
>
> That's the way it's suppose to work.  Disarm all the fancy features in
> the 502T and turn it into a simple DSL->ethernet bridge.
>
> --
> # Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
> # 831-336-2558            je...@comix.santa-cruz.ca.us
> #http://802.11junk.com              je...@cruzio.com
> #http://www.LearnByDestroying.com              AE6KS

I think this keep alive script is what I want:

http://www.dd-wrt.com/wiki/index.php/Useful_Scripts#Automatic_Connection_Repair_.28always_on.sh.29

But it doesnt seem to work...how often is it sending the pings? (I am
not familir with these scripts)

Cheers

-Al