On 09/27/2009 04:45 PM, David Juhl wrote:
It added the route but didn't add anything as far as nameservers are
concerned.... Why?
What works and what doesn't? Can you ping IPs?
ping 74.125.45.100
If yes, you have connectivity and the route works. If it was actually
working even before you added the "routes_eth0" setting in
/etc/conf.d/net, then the route is not the problem and that setting is
not needed in your case.
Can you ping domain names?
ping google.com
If yes, DNS works. If not, the IP in /etc/resolv.conf is wrong.
Specifying it in conf.d/net instead of resolv.conf doesn't help if it's
just the wrong IP. Usually it's the router's IP though. So if it
doesn't work, you might try to use your ISP's DNS directly. You can
either phone them, or search at their homepage for info, or Google
"ISP_Name DNS" and start from there.
David
On Sat, 2009-09-26 at 21:08 -0500, David Juhl wrote:
I feel like a idiot.... my device isn't eth0 it is wlan0 and defined it
as such... No wonder I didn't catch it...
Thanks
David
On Sun, 2009-09-27 at 04:22 +0300, Nikos Chantziaras wrote:
On 09/26/2009 11:11 PM, David Juhl wrote:
What do I put in the /etc/conf.d/net to specify name servers? I can't
seem to modify the /etc/resolv.conf and get it to sick at boot.
Depends on how you connect. If you're behind a router/gateway device
that does NAT (this includes most "DSL modems"), you use the device's IP
as nameserver in /etc/resolv.conf as well as routes_ethN in
/etc/conf.d/net. For example, if your router's IP is 192.168.1.1, you
use this in /etc/resolv.conf:
nameserver 192.168.1.1
And this in /etc/conf.d/net:
routes_eth0="default via 192.168.1.1"
