On 6/8/05, ken wrote:

Markus Natter wrote:

...

On 6/8/05, ken wrote:

...

After a wireless internet session using DHCP, my 9.3 Pro system is left without hostname, domainname, /etc/resolv.conf, or default route. I would think that the next time I boot up that at least the previous (default) hostname and domainname would be configured.

Hi,

exactly these values are coming from the DHCP Server and are temporarily written to these files.

You're not understanding the issue. My point is that after a DHCP session is finished, it should restore the default hostname etc. And certainly the default hostname etc. should be configured automatically by the system upon the next bootup (when I'm no longer using DHCP). Clear?

Let me explain again. My laptop is configured with hostname and domain name, perhaps connected to my home network, perhaps not. I take my laptop to a cafe and connect to the internet. My wireless is now using DHCP. Great. Everything is fine. I surf the web. I shut the machine down and go home. I fire up the laptop. Because I always (so far) invoke network connections manually, I'm not connected yet to my home network. At this time there is no hostname and no domain name configured. Just because I'm not connected to a network doesn't mean that the machine shouldn't have a hostname and a domain name. IOW, the machine *should* at this time have a hostname and domain name, the ones which were manually configured in during the original install. IOW, the hostname and domain name shouldn't be blank/empty/nonexistent.

I apologize. I was just not sure if you have configured any of your hostname, default-routes, nic,.. manually at all ( e.g. you could have used a highly configured dhcpd at home ). I'm not really sure what exactly could be broken in your case, but I expect the reason to be in dhcp handling. You could try to tell the dhcp client not to touch these files you don't really need to be changed (and back). At least this could be a workaround. You could check your /etc/sysconfig/network/dhcp for the following options .. # configure your hostname again first and try this setting: DHCLIENT_SET_HOSTNAME="no" # if you have configured your resolv.conf at home and put # valid internet dns server there, your notebook is not depending on # dns servers coming from the dhcpd. DHCLIENT_MODIFY_RESOLV_CONF="no" # this should be set DHCLIENT_SET_DEFAULT_ROUTE="yes"

...

Are you using the wireless connection only, or as a second Networkinterface?

It's the only interface used at this time (in this context).

...

...

Also (separate issue), where is the default route configured for a device. I would have thought that there would be a variable in the ifcfg-* for it, but no.

No, the routes are placed here in this file: /etc/sysconfig/network/routes

Markus, are you saying that DHCP puts routes here...? Or that I should put a default route here? Neither of these interpretations makes sense to me, but I can't see what else you might be meaning. Perhaps you could explain a bit more.

I meant, you could place your default route (for static, home use) there. It wouldn't be used in a dhcp session ( if in /etc/sysconfig/network/dhcp DHCLIENT_SET_DEFAULT_ROUTE="yes" ).

...

Markus

-- A lot of us are working harder than we want, at things we don't like to do. Why? ...In order to afford the sort of existence we don't care to live. -- Bradford Angier

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

hope this helps a bit more.. :-, Markus

Ken Schneider wrote:

On Wed, 2005-06-08 at 10:01 -0400, ken wrote:

...

Markus Natter wrote:

...

On 6/8/05, ken wrote:

...

After a wireless internet session using DHCP, my 9.3 Pro system is left without hostname, domainname, /etc/resolv.conf, or default route. I would think that the next time I boot up that at least the previous (default) hostname and domainname would be configured.

Hi,

exactly these values are coming from the DHCP Server and are temporarily written to these files.

You're not understanding the issue. My point is that after a DHCP session is finished, it should restore the default hostname etc. And certainly the default hostname etc. should be configured automatically by the system upon the next bootup (when I'm no longer using DHCP). Clear?

Let me explain again. My laptop is configured with hostname and domain name, perhaps connected to my home network, perhaps not. I take my laptop to a cafe and connect to the internet. My wireless is now using DHCP. Great. Everything is fine. I surf the web. I shut the machine down and go home. I fire up the laptop. Because I always (so far) invoke network connections manually, I'm not connected yet to my home network. At this time there is no hostname and no domain name configured. Just because I'm not connected to a network doesn't mean that the machine shouldn't have a hostname and a domain name.

Yes it does if you are only using DHCP for this info. Any host name would be what you have in /etc/hosts.

Negative. /etc/HOSTNAME holds the hostname of the machine it resides on. /etc/hosts is something completely different... it can hold the names and IPs of machines which you don't want to rely on DNS for. -- A lot of us are working harder than we want, at things we don't like to do. Why? ...In order to afford the sort of existence we don't care to live. -- Bradford Angier

Ken Schneider wrote:

On Thu, 2005-06-09 at 19:03 -0400, ken wrote:

...

Ken Schneider wrote:

...

Yes it does if you are only using DHCP for this info. Any host name would be what you have in /etc/hosts.

Negative. /etc/HOSTNAME holds the hostname of the machine it resides on. /etc/hosts is something completely different... it can hold the names and IPs of machines which you don't want to rely on DNS for.

And can also be in /etc/hosts which can also be used for name resolution. That's what it was used for before bind was written.

True, but I thought we're talking about suse systems of the current day. I suppose if you wanted, you could ignore /etc/HOSTNAME, use /etc/hosts instead, and your system *might* work fine. But I doubt the suse engineers put /etc/HOSTNAME into the system for no reason. -- A lot of us are working harder than we want, at things we don't like to do. Why? ...In order to afford the sort of existence we don't care to live. -- Bradford Angier

Ken Schneider wrote:

On Fri, 2005-06-10 at 00:07 -0400, ken wrote:

...

Ken Schneider wrote:

...

And can also be in /etc/hosts which can also be used for name resolution. That's what it was used for before bind was written.

True, but I thought we're talking about suse systems of the current day. I suppose if you wanted, you could ignore /etc/HOSTNAME, use /etc/hosts instead, and your system *might* work fine. But I doubt the suse engineers put /etc/HOSTNAME into the system for no reason.

There is no need to ignore it. I simply stated that /etc/hosts can/is still used for name resolution by many people that do not/cannot setup bind/named. If they have a small network their is no need for bind and then /etc/hosts becomes their only means of DNS resolution for PC's their small lan.

I don't have a problem with people revising their own comments, but with this revision your comment is completely irrelevant to the issue under discussion. (See the Subject line.)

Enough of this.

Amen. -- A lot of us are working harder than we want, at things we don't like to do. Why? ...In order to afford the sort of existence we don't care to live. -- Bradford Angier