Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #184613

Re: Network config

Show all headers | View raw

On Thu, Aug 03, 2017 at 08:49:05PM +0200, Pascal Hambourg wrote:
> Le 03/08/2017 à 15:52, Zenaan Harkness a écrit :
> > On Thu, Aug 03, 2017 at 08:53:27AM -0400, Greg Wooledge wrote:
> > > But the problem is, various Unix DHCP client daemons do *too much*.
> > > All I want them to do is set the IP address, netmask, and gateway.
> > > I *don't* want them to change the system hostname, or the system
> > > resolv.conf (in which I have hand-placed *our* DNS search domain and
> > > *our* DNS resolvers).
> > 
> > Well, making /etc/resolv.conf read-only, owned by root.root
> 
> ... is just useless. resolv.conf is already owned by root, DCHP client daemons run as root and on Linux systems root
> (uid 0) ignores read/write permissions.
> 
> > uninstalling resolvconf should also solve your problem.
> 
> No, it solves nothing. Without resolvonf the DHCP client will write directly in resolv.conf.
> 
> > If you in this last (laptop) scenario need specific addition of your
> > static nameserver, on top of the DHCP nameservers (e.g. one
> > nameserver might resolve some internal names, the others might
> > recursively resolve internet names)
> 
> This does not work.
> The resolver stops as soon as it receives a positive (record exists) or negative (record does not exist) answer. If it
> receives a negative answer from the first name server, it won't query the next name server.
> 
> All name servers declared in resolv.conf must be equal and provide the same answers, or unexpected behaviour will
> happen. Multiple name servers is only for redundancy and load balancing, not to provide different answers.

What about putting your script lines (copying files around etc) into
your /etc/network/interfaces file?

Given the uniqueness of how you seem to want to do your networking,
perhaps that's the best option to make it less abnormal - looks like
it to me.

Good luck,

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Network config ruslan axundov <raxundov@gmail.com> - 2017-08-02 16:10 +0200
  Re: Network config Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-02 16:20 +0200
    Re: Network config Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-08-02 20:20 +0200
      Re: Network config Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-02 21:00 +0200
        Re: Network config Zenaan Harkness <zenaan@freedbms.net> - 2017-08-03 03:20 +0200
          Re: Network config Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-03 15:00 +0200
            Re: Network config Zenaan Harkness <zenaan@freedbms.net> - 2017-08-03 16:00 +0200
              Re: Network config Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-08-03 20:50 +0200
                Re: Network config Zenaan Harkness <zenaan@freedbms.net> - 2017-08-04 03:00 +0200
                Re: Network config Joe <joe@jretrading.com> - 2017-08-04 10:10 +0200
                Re: Network config Zenaan Harkness <zenaan@freedbms.net> - 2017-08-04 17:10 +0200
                Re: Network config <tomas@tuxteam.de> - 2017-08-04 10:20 +0200
                Re: Network config Zenaan Harkness <zenaan@freedbms.net> - 2017-08-04 16:20 +0200
                Re: Network config <tomas@tuxteam.de> - 2017-08-05 10:20 +0200
                Re: Network config Gene Heskett <gheskett@shentel.net> - 2017-08-05 16:40 +0200
                Re: Network config <tomas@tuxteam.de> - 2017-08-05 17:00 +0200
  Re: Network config Zenaan Harkness <zenaan@freedbms.net> - 2017-08-03 03:00 +0200
    Re: Network config Joshua Schaeffer <jschaeffer0922@gmail.com> - 2017-08-03 17:30 +0200
      Re: Network config Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-08-03 21:00 +0200
        Re: Network config Henning Follmann <hfollmann@itcfollmann.com> - 2017-08-03 21:30 +0200

csiph-web