Re: iproute, NM and ifupdown (was: My wired connection doesn't work suddenly (Debian sid))
On Sunday 26 August 2018 10:24:35 Pascal Hambourg wrote:
> Le 26/08/2018 à 15:40, Gene Heskett a écrit :
> > Why do I have to read a mailing list to learn how to use these new
> > ip tools.
> "New" ? iproute has been around for more that 20 years !
> > Theres some keywords
> > (mentioned in the man page in obtuse language IIRC) to use in e-n-i
> > to tell N_M to keep its malicious hands off a given interface, but
> > you have to read between the lines with your logical superpowers to
> > detect them.
> No, there is no obscure keyword and nothing between the lines.
Oh? And you wrote that manpage I suppose, and you don't make mistakes...
You may be able to read it, knowing what you "intended" to write. But
others aren't mind readers.
But we can add 2+2 and get a quite precisely defined 4.0000000000.
> By default, NM does not manage any interface configured in
> /etc/network/interfaces. So all you have to do is configure your
> interface with an "iface" stanza in /etc/network/interfaces as usual
> so that it is managed by ifupdown and not by NM.
I have had N-M tear down a well configured staticly defined eth0 on
dozens of occasions, despite using the iface designation in my e-n-i's.
Most recently on a stretch install on a rock64 I had to erect immutable
attributes to resolv.conf after making it a real file, and e-n-i to make
networking Just Work.
It may not do it today, things do get improved but my linux experience
dates to RH5.0 and 1998 and its been something I've had to edit e-n-i
and then quickly make it immutable, ditto for making /etc/resolv.conf a
real file and immutable ever since N-M was made virtually mandatory. My
networking is not portable and with the exception of my ancient lappy
will never be.
Theres a reason my /etc/hosts files are 20+ lines long, and my
resolv.conf has a "search hosts nameserver" line in it, which N-M always
removes if it can. The real file, made immutable fixes that too
N-M is helpless when there is not a dhcp server or a dhcp server that
only recognizes the MAC of one machine for security reasons.
Based on my experience at making N-M work, you might want to get a
Cheers, Gene Heskett
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>