| 1 |
It added the route but didn't add anything as far as nameservers are |
| 2 |
concerned.... Why? |
| 3 |
|
| 4 |
David |
| 5 |
|
| 6 |
On Sat, 2009-09-26 at 21:08 -0500, David Juhl wrote: |
| 7 |
> I feel like a idiot.... my device isn't eth0 it is wlan0 and defined it |
| 8 |
> as such... No wonder I didn't catch it... |
| 9 |
> |
| 10 |
> Thanks |
| 11 |
> |
| 12 |
> David |
| 13 |
> On Sun, 2009-09-27 at 04:22 +0300, Nikos Chantziaras wrote: |
| 14 |
> > On 09/26/2009 11:11 PM, David Juhl wrote: |
| 15 |
> > > What do I put in the /etc/conf.d/net to specify name servers? I can't |
| 16 |
> > > seem to modify the /etc/resolv.conf and get it to sick at boot. |
| 17 |
> > |
| 18 |
> > Depends on how you connect. If you're behind a router/gateway device |
| 19 |
> > that does NAT (this includes most "DSL modems"), you use the device's IP |
| 20 |
> > as nameserver in /etc/resolv.conf as well as routes_ethN in |
| 21 |
> > /etc/conf.d/net. For example, if your router's IP is 192.168.1.1, you |
| 22 |
> > use this in /etc/resolv.conf: |
| 23 |
> > |
| 24 |
> > nameserver 192.168.1.1 |
| 25 |
> > |
| 26 |
> > And this in /etc/conf.d/net: |
| 27 |
> > |
| 28 |
> > routes_eth0="default via 192.168.1.1" |
| 29 |
> > |
| 30 |
> > |
| 31 |
> |
| 32 |
> |
Archives