> I noticed after awhile that dhcp clobbered my /etc/resolv.conf after
> awhile [...] Shawn or someone else familiar with the protocol could
> probably answer this one...
Okay. Remember, though, that asking me to talk about network protocols is
pretty dangerous, especially if you're in a rush... :)
I actually touched on this a *long* time ago on this list, so there's no
reason you'd remember. /etc/resolv.conf is used to identify three
different things: your nameservers, *your* domain, and your search path.
DHCP can send nameservers and a domain for you (e.g., student.yale.edu),
but it doesn't send a search path. The DHCP client accepts the
information and overwrites your /etc/resolv.conf, leading to really boring
/etc/resolv.confs that will cause your resolver (i.e., your DNS client) to
search nothing but its own domain.
DHCP won't overwrite your /etc/resolv.conf automatically; your
/etc/resolv.conf is probably a symlink to /etc/dhcpc/resolv.conf, and
dhcpc (the DHCP client) is just overwriting its own local version of the
file. (The man page is wrong about the location of DHCP's copy of
resolv.conf; ignore it!)
My suggested solution is to kill the symlink and create your own local
version. Ignore the DNS-related info that the DHCP server is sending you
since it's not likely to change much and isn't really all that
interesting.
> And on another note, this manually loading of the 3c509 module is only a
> temporary fix, and I'm searching for a way to fix this so it works upon
> bootup. It still does the same thing upon bootup right now.
>
> insmod: ...3c509.o: invalid parameter io:
As Stefan pointed out in the newsgroup, try not specifying 'io' -- it's
not necessarily a valid parameter.
Shawn