--=-cnJXVFXvH11GbXkExWfV
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Well, I'm pretty sure the power outage idea doesn't hold because 1)
where I live, about .5mi from the Kyrene generating station, we have
pretty good electricity and 2) furthermore, it's on the same UPS the
router's on (makes sense, eh?). The router is the only computer with
direct access to the modem and doesn't forward dhcp requests to it (like
I'm going to pay 5 flippin' dollars more per computer to Cox? ha!) so I
don't think it has to do with flushing the modem's cache. My theory was
just one based on the fact that once in a long while, it would go down
(lose signal? no idea, modem's 50ft away in another room) and I would
just ssh into the router and grab another dhcp lease, same address as
usual.
As for the configuration, that's not really possible. I'm running
smoothwall on the router and it uses dhcpcd and it tends to overwrite
the config.
Thanks anyways,
Bryce
On Sun, 2003-09-21 at 12:08, Brian Cluff wrote:
> Bryce C wrote:
> > The nearly static IP has been my experience too. In fact, I just set up
> > my fw to use this static IP and every once in a long while (weekly I
> > think), I run my version of a dhcp client just to let them know I'm
> > still alive as they do stop service somewhere along the way if you
> > haven't "pinged" them.
>=20
> I don't think thats what is happening. More likely you have a small=20
> power outage that reset your cable modem.
> What happens is that your cable modem allows the first card that is gets=20
> a DHCP request from to access the internet. Without the DHCP request=20
> you can set it static and you'll never get though, even though you were=20
> just using it 30 seconds before your cable modem was power cycled.
> Thats also the reason you have to powercycle your cable modem if you=20
> change ethernet cards. It needs to flush the old MAC address that it=20
> was bound to.
>=20
> > FYI, the reason I use a static IP setup is so I can use the DNS servers
> > I want and not have them overwritten by the DHCP server's values. *&^*@
> > DNS servers, never updating and whatnot.
>=20
> You can configure your dhcp client to hand back whatever you want. In=20
> dhclient just add a line like:
> supersede domain-name "yourdomain.com anotherdomain.com";
> supersede domain-name-servers 111.112.113.114;
>=20
> or in my case, I would like to get cox's domain servers but I would=20
> perfer that it checked my local DNS first, so I put:
> prepend domain-name-servers 127.0.0.1;
>=20
> in my /etc/dhcp3/dhclient.conf
> there's a TON of other stuff you can do in there too. It's really worth=20
> a look.
>=20
> You can do similar things with dhcpcd, althought they don't seem to be=20
> as powerful, but would meet your needs. Just checkout the config file=20
> in /etc/dhcpc/config You just need to comment out a line like:
> SET_DNS=3D'Yes'
> and that will keep your DNS entries.
>=20
> My paths are from a debian box, your machine might be different.
>=20
> Brian Cluff
>=20
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
--=20
Bryce C <
Plug@BryceCo.Net>
CoBryce Communications
--=-cnJXVFXvH11GbXkExWfV
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQA/bf/9/wbq/C6yyPcRAqMhAKCG/IAQ9eh70cap5rZN+DjydyC03gCeKJXH
KemDdTIXDqxBTST1hFVR5sg=
=e7Vn
-----END PGP SIGNATURE-----
--=-cnJXVFXvH11GbXkExWfV--
(text/plain)