SPAM: Re: FW: [SLE] Need help switching from connecting through router to direct connecting



On 11/10/06 20:59, Greg Wallace wrote:
On Wednesday, October 11, 2006 @ 3:28 PM, Darryl Gregorash wrote:


On 11/10/06 12:28, Greg Wallace wrote:

On Wednesday, October 11, 2006 @ 7:25 AM, Darryl Gregorash wrote:


<snip>

First you need to make sure your ISP is actually sending the name server
information in its DHCP replies (it should).


Did you verify that you are actually receiving the name servers in the
DHCP response? If not, then you may have to add a "require
domain-name-server" option to the dhcp options list.

There are two variables in the network config that might prevent
/etc/resolv.conf from being modified. The first of these is
MODIFY_RESOLV_CONF_DYNAMICALLY. If this is "no", then nothing will
change the file. With DHCP, the other is DHCLIENT_MODIFY_RESOLV_CONF.



Well, I checked and both of those variables were set to Yes, so that's not
the problem. Thanks anyway.

If those are set to "yes", and you are getting the name server list from
the provider, then something else is screwing up the works..


That's the problem. I'm NOT getting the name server list from the provider,
even though it's now set to use DHCP (i. e., the box is checked next to


You really do not know this. All you know is that your resolv.conf file
is not being modified. As root, do the following:

1. In the Yast sysconfig editor, Network/DHCP/DHCP client, check the
variable DHCLIENT_BIN to see if you are using dhcpcd or dhclient. Unless
something has changed since 9.3, there are no other choices in SuSE. The
default is dhcpcd, but dhclient is much easier to use if you are
configuring a single interface with DHCP.

2. Find out if it is actually running:
ps aux| grep dhc

3. If it is dhcpcd, then run this:
grep DNS /var/lib/dhcpcd/*

With this client, if you are receiving name server information from your
service provider, you will see a line similar to this:
/var/lib/dhcpcd/dhcpcd-eth1.info:DNS=204.83.142.2,204.83.142.4


If it is dhclient, run this instead:
grep name-server /var/lib/dhcp/*

With this client, you should see several lines looking similar to this
(dhclient has a habit of keeping a few old dhcp leases in its files):
option domain-name-servers 204.83.142.2,204.83.142.4;

4. If you see the appropriate line, then you are receiving the name
server information from the provider. In this case, since your config
variables are properly set to have the system modify resolv.conf,
something else is preventing that file from being modified properly.
IMO, that something can only be Networkmanager. If this is the case,
then dump Networkmanager (unless you have an absolute compelling reason
to keep it running), and let the system init scripts perform the task
for you. They do work, I assure you.

If you do not see the appropriate line, then you are not receiving
the information at all, and this becomes an issue of properly
configuring your dhcp client program. I doubt if this will be the case,
as both dhcpcd and dhclient, as they are installed out of the box, will
request name server information in a dhcp request.

5. If all else fails, take the name server information you got in step 3
(or call your service provider to get it) and modify resolv.conf
yourself. This is not the ideal situation, but it will at least give you
functioning name servers while you look for the problem elsewhere.

--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx



Relevant Pages

  • Re: wireless, Broadcom & jaunty
    ... IF you don't get a dhcp address ... dhclient, but if dhclient doesn't work from the command line anyway, the ... wireless-key XXXXXXXXXXXXXXXXXXXX ... laptop soesn't have a switch to turn wireless off which I have on ...
    (Ubuntu)
  • Re: DNS problem on local network
    ... Remove domain-name-servers from that list and dhcp wont supply it. ... My problem is that the DHCP and DNS server running dnsmasq is actually the gateway server and has a second NIC connected to a modem, from which it gets its ip via DHCP, hence the reason why this box is running dnsmasq for one NIC and dhclient3 for the other. ... I now have to figure out what is happening on the dhclient front on my workstations, or at least my linux workstation since that has no concept of its domain name still. ...
    (Debian-User)
  • Re: Marvell 88E80856 switching from static to dhcp configuration all on its own
    ... 3Com handles dhcp and dns requests. ... have both interfaces using static ip, dhclient shouldn't even be ... Isn't there some process watching the settings in /etc/network/interfaces to stop just such a thing from happening, or doesn't the driver and device itself record its state so that dhclient wouldn't even attempt this unless there is some type of user override, ...
    (Debian-User)
  • Re: Problems with OpenBSD dhclient
    ... > been having some issues with managing my network connection. ... DHCP is not playing, yet. ... > When I go to a meeting, I want to switch to the wireless network. ... > Now life is not so nice with the OpenBSD dhclient. ...
    (freebsd-current)
  • Re: VOIP Static Device
    ... I also have a Linksys PAP2-NA v1 VOIP adapter which I am ... DHCP option to 'No'. ... I've spoken with the VOIP provider about this. ... I have a pap2 with 2 providers as well, and I need to turn provisioning ...
    (comp.dcom.sys.cisco)