unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Thomas Danckaert <post@thomasdanckaert.be>
To: alex.sassmannshausen@gmail.com
Cc: help-guix@gnu.org
Subject: Re: networkmanager hostname woes
Date: Thu, 14 Sep 2017 09:50:45 +0200 (CEST)	[thread overview]
Message-ID: <20170914.095045.1080385090375720557.post@thomasdanckaert.be> (raw)
In-Reply-To: <87h8w6ha74.fsf@gmail.com>

From: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
Subject: Re: networkmanager hostname woes
Date: Wed, 13 Sep 2017 17:47:43 +0200

>> AFAIU, the cause is that networkmanager changes my hostname (after
>> DHCP?), in my case to “new-host2” or something similar, and this
>> seems to break the X session.  When I manually restore the hostname
>> with “sudo hostname <original-hostname>”, the problem is solved.  
>> Is
>> there anyway to disable this behaviour for networkmanager?
> [...]
> This makes me think that it might be a network configuration
> derived issue — but I have not been able to get to the bottom of 
> this
> yet…
>
> I see that you might be based in Belgium — I am too, and my home 
> network
> uses most of the defaults from Proximus' B-Box 2.  If this is the 
> case
> for you too, then perhaps it is a matter of the default settings in 
> that
> router?

Yes, I'm using the same router, and I can agree it's not 
“professional”-grade :-).  Still, I don't think a bad router 
configuration should be able to change my hostname.

Following Christopher Baines' suggestion, I created /etc/hostname by 
adding the following to my system configuration:

(define etc-hostname-service-type
   (service-type (name 'etc-hostname)
                 (extensions
                  (list (service-extension etc-service-type
                                           (lambda (hostname)
                                             (list `("hostname" 
,(plain-file "hostname" hostname)))))))))

and in the (operating-system (services ...)) list:

     (service etc-hostname-service-type host-name)

I don't know if this kind of extension should be added to an existing 
service (networkmanager itself, perhaps?).  Though I have the feeling 
a more proper solution should exist.

 From what I've read, it might also be a DHCP issue: some DHCP 
 clients are configured to take on the hostname offered by the 
 router, perhaps that could/should be changed?  I see that wicd has 
 its own settings for these things (/etc/wicd/wireless-settings.conf 
 contains things like usedhcphostname = 0).  I'm hoping someone with 
 more experience can give some advice here :)

Thomas

  parent reply	other threads:[~2017-09-14  7:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13 10:05 networkmanager hostname woes Thomas Danckaert
2017-09-13 17:01 ` Christopher Baines
2017-09-13 23:27 ` Arun Isaac
2017-09-14  6:38   ` Christopher Baines
2017-09-15 12:14   ` ng0
2017-09-15 12:34     ` ng0
2017-09-16  6:57     ` Thomas Danckaert
2017-09-16  8:11       ` ng0
     [not found] ` <87h8w6ha74.fsf@gmail.com>
2017-09-14  7:50   ` Thomas Danckaert [this message]
2017-09-14  8:17 ` Ludovic Courtès
2017-09-15 10:12   ` Thomas Danckaert
2017-09-15 20:34     ` Ludovic Courtès
2017-09-16 12:03       ` Thomas Danckaert
2017-09-19 12:06         ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170914.095045.1080385090375720557.post@thomasdanckaert.be \
    --to=post@thomasdanckaert.be \
    --cc=alex.sassmannshausen@gmail.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).