On Thu, 9 Oct 2003, Craig wrote:
> Thanks for the information on fixing my minor problem.
>
> I went back and had a look at the /etc/resolv.conf
> file, it look something like this:
>
> search peregian
> nameserver 192.168.0.1
>
> peregian and ip address is the name I gave to the
> D-Link 624 router wireless access point.
>
> I edited the resolv.conf file to read as such:
>
> nameserver 127.0.0.1
> nameserver 204.194.56.150
>
> With this change I now had access to the internet. I
> could also access the NetComm NB1300 modem/router web
> configuration. But I was unable to access the D-Link
> 624 Wireless router web configuration, was is not a
> major issue.
>
> When I rebooted the debian box, the resolv.conf file
> changed back to the original text of:
>
> search peregian
> nameserver 192.168.0.1
>
>
> What I'm going to do next is change the resolv.conf
> file, apt-get dhcp3-client, configure and see what
> happens.
>
> But I'm open to suggestions.
>
> Craig
Yes basically the problem is DHCP overwriting the resolv.conf file. I've
never tried looking if dhcp has a configuration option to NOT overwrite
this file. The *simple* if not correct fix is to "chmod 444
/etc/resolv.conf" after you fix it. DHCP may complain but who cares ;-)
As for reaching the router's web interface, try entering the IP address
instead of the name. If that's a pain, just add the info to /etc/hosts.
192.168.0.1 peregian
Ummm... apon re-reading the message and my response.. maybe both your
routers have DHCP turned on... not advisable, something to check, I could
be talking shit :-)
--
---<GRiP>---
Electronic Hobyist, Former Arcadia BBS nut, Occasonal nudist,
Linux Guru, SLUG/AUUG/Linux Australia member, Sydney Flashmobber,
BMX rider, Walker, Raver & rave music lover, Big kid that refuses
grow up. I'd make a good family pet, take me home today!
Do people actually read these things?
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
