[olug] dhcpcd vs. dhclient

[Jonathan Warren]

Thanks for the lynx reference that is exactly what I wanted.  doestn' matter what I test it with.  dig / browser / ssh the name no longer resolves after about 2-3 minutes of use.  Happens from other Cox machines using Cox's DNS servers and from UP using there DNS servers.  Works fine the next day.  Don't know exactly how long I have to wait to try it again.

On Sun, Mar 31, 2002 at 09:54:38PM -0600, Brian Roberson wrote:
> when you say "the name no longer resolves" what exactly are you testing this
> with? ( nslookup? web browser, what? )
> 
> BTW.... If you have lynx, it would be as simple as
> `lynx -dump -auth=username:password https://users.olug.org/ddns/ `
> 
> 
> ----- Original Message -----
> From: "Jonathan Warren" <jonwarren at cox.net>
> To: <olug at olug.org>
> Sent: Sunday, March 31, 2002 11:56 AM
> Subject: Re: [olug] dhcpcd vs. dhclient
> 
> 
> > I can use thechunk.m.olug.org for about 2 minutes and then the name no
> longer resolves unless I log into users.olug.org.  Has anyone else seen
> this?  Is there a way to fix it?  Has anyone written a script to update
> dyndns?  Something that automatically pinged the server once a day and
> updated my ip would be nice.
> >
> > -Jon
> >
> > On Sat, Mar 30, 2002 at 07:40:06PM -0600, Brian Roberson wrote:
> > > > during the @home -> cox.net cut over.  dyndns.org is a nice way to put
> a
> > > > name to a potentially changing IP also.  I run a python script via
> cron
> > > that
> > > > checks my external IP on the linksys and updates dyndns as needed.
> Very
> > > > smooth.
> > >
> > >
> > > Dont forget olug dyndns service! ( login.m.olug.org )
> > >
> > > >
> > > > Considering that the linksys let's me boot BeOS, *nix and doze with
> out
> > > the
> > > > hassle it was well worth the 129 I paid for the 4 port model.  I've
> seen
> > > the
> > > > single port for $79 recently.  I've been considering upgrading to the
> > > > linksys vpn model.  Anyone else using it?
> > >
> > > I have the 4port router/Wireless AP and it works very well! ( BEFW11S4 )
> > >
> > >
> > > >
> > > > -Jeff
> > > >
> > > > ----- Original Message -----
> > > > From: "Phil Brutsche" <phil at giedi.obix.com>
> > > > To: <olug at olug.org>
> > > > Sent: Saturday, March 30, 2002 12:12 PM
> > > > Subject: Re: [olug] dhcpcd vs. dhclient
> > > >
> > > >
> > > > > A long time ago, in a galaxy far, far way, someone said...
> > > > >
> > > > > > I don't know if anyone else has had trouble with Cox changing your
> ip
> > > > > > address several times a day lately, but I think I've found an
> answer
> > > for
> > > > > > it. This is mostly referring to a Redhat 7.2 system.
> > > > > >
> > > > > > By default Redhat uses dhcpcd, which releases it's IP and requests
> a
> > > new
> > > > > > one when the lease expires.  This may be just coincidemce, but it
> > > looks
> > > > > > like Cox's dhcp server holds an IP for a while after it's been
> > > released
> > > > > > and you get a new one, instead of your old one.  For some reason
> > > dhcpcd
> > > > > > also gets the domain name screwed up too.  It should be
> > > "om.om.cox.net"
> > > > > > (according to reverse DNS lookups), but dhcpcd gets "om.cox.net".
> Oh
> > > > > > well...
> > > > > >
> > > > > > I've tested with ISC's dhclient and it simply sends a renew
> request
> > > for
> > > > > > your current address when the lease expires.  This seems to behave
> > > much
> > > > > > better with Cox.
> > > > >
> > > > > This behavior isn't limited to dhcpcd - several firewall devices
> (like
> > > the
> > > > > Linksys "Cable modem/DSL router") do similar things in their DHCP
> > > clients.
> > > > >
> > > > > --
> > > > >
> > > > > Phil
> > > > >
> > > > >
> > > > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > > > >
> > > > > For help contact olug-help at olug.org - run by ezmlm
> > > > > to unsubscribe, send mail to olug-unsubscribe at olug.org
> > > > > or `mail olug-unsubscribe at olug.org < /dev/null`
> > > > > (c)1998-2002 OLUG http://www.olug.org
> > > > >
> > > > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > > > >
> > > >
> > > >
> > > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > > >
> > > > For help contact olug-help at olug.org - run by ezmlm
> > > > to unsubscribe, send mail to olug-unsubscribe at olug.org
> > > > or `mail olug-unsubscribe at olug.org < /dev/null`
> > > > (c)1998-2002 OLUG http://www.olug.org
> > > >
> > > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > > >
> > >
> > >
> > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> > >
> > > For help contact olug-help at olug.org - run by ezmlm
> > > to unsubscribe, send mail to olug-unsubscribe at olug.org
> > > or `mail olug-unsubscribe at olug.org < /dev/null`
> > > (c)1998-2002 OLUG http://www.olug.org
> > >
> > > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> >
> > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> >
> > For help contact olug-help at olug.org - run by ezmlm
> > to unsubscribe, send mail to olug-unsubscribe at olug.org
> > or `mail olug-unsubscribe at olug.org < /dev/null`
> > (c)1998-2002 OLUG http://www.olug.org
> >
> > -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> >
> 
> 
> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
> 
> For help contact olug-help at olug.org - run by ezmlm
> to unsubscribe, send mail to olug-unsubscribe at olug.org
> or `mail olug-unsubscribe at olug.org < /dev/null`
> (c)1998-2002 OLUG http://www.olug.org
> 
> -_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_

For help contact olug-help at olug.org - run by ezmlm
to unsubscribe, send mail to olug-unsubscribe at olug.org
or `mail olug-unsubscribe at olug.org < /dev/null`
(c)1998-2002 OLUG http://www.olug.org

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_