| View previous topic :: View next topic |
| Author |
Message |
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1471
Location: Berlin, Germany
|
 Posted: Wed Jan 26, 2005 2:43 am Post subject: router no longer works as nameserver? |
 |
|
so, i have an SMC 4-port router that's been working fine for several years. but i just switched over to ~x86 (i know, i know, why am i surprised if something on ~ARCH acts funny?), and i've started encountering a problem:
my router, for some reason, assigns itself as the nameserver when it uses dhcp. thus, when dhcpcd is running, my resolv.conf reads
| Code: | | nameserver 192.168.2.1 |
and i get no connection. when i edit that file to read
| Code: | | nameserver {the dsl service nameservers} |
everything works fine. for whatever reason, the SMC dhcp server insists that the router act as the LAN nameserver, and while this used to work, it does no longer.
this would be fine, because i edited my /etc/init.d/net file to run dhcp with the -R flag, except that there's a mac on the network that can't specify only parts of its network config (i.e., get the IP from the router, but specify the nameserver manually)
can anyone suggest why the router no longer is passing nameserver requests on to the WAN nameservers, and consequently cannot work as a nameserver for outgoing requests?
otherwise, i guess i'll just use static IPs for the LAN, which i'm halfway doing anyway.
thanks,
EE |
|
| Back to top |
|
 |
andrewy
l33t
Joined: 07 Apr 2004
Posts: 602
|
| Posted: Wed Jan 26, 2005 2:47 am Post subject: |
|
|
| Can't you just use a static IP for the computer you're having trouble with? Just be sure to set the IP outside of the DHCP range. |
|
| Back to top |
|
|
ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1471
Location: Berlin, Germany
|
| Posted: Wed Jan 26, 2005 2:51 am Post subject: |
|
|
well, yes: that's what i'm doing. i'm just wondering if there's a way around that: because this did used to work fine, i'm guessing that changing some packages (and their associated /etc/config files) might have made something not work properly.
but yes: the simple solution is just to assign static IPs. |
|
| Back to top |
|
|
andrewy
l33t
Joined: 07 Apr 2004
Posts: 602
|
| Posted: Wed Jan 26, 2005 9:07 pm Post subject: |
|
|
I would try installing the previous version of dhcpcd and see if that fixes it.
Also, have you considered just going back to x86 on all of them? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
