[opensuse] NetworkManager issues: can't disable (a) wpa_ ... wifi and (b) dhcp_client
I've had no end of problems with NetworkManager but seem to be converging on a solution. I have a config file /etc/system-connections/ethernet that seems reasonable, built with the CLI level "nm" tools. Nowhere in any of the config do I have anything that indicates I am running wifi or have wifi hardware on this desktop. That file described a static configuration But when I run nmcli con up ethernet and I get a network connection, the wpa-supplicant starts and a dhcp client starts and I get a dhcp address (.66) and some weird but valid entries in /etc/resolv.conf that are not the ones I specify in the config file (aka 8.8.8.8 & 8.8.4.4) I'm manually killing the wpa and dhcp processes and manually resetting the address and route and resolver entries after boot. I *think* I can solve the issue of static addresses if I can figure a way to make this NOT start wpa and dhcp in the first place. Maybe. Any advice on how to do that other than by use nmcli each time? # cat /etc/os-release AME="openSUSE Leap" VERSION="42.1" VERSION_ID="42.1" PRETTY_NAME="openSUSE Leap 42.1 (x86_64)" # zypper info NetworkManager Information for package NetworkManager: --------------------------------------- Repository: openSUSE-Leap-42.1-Update Name: NetworkManager Version: 1.0.6-10.1 Arch: x86_64 Vendor: openSUSE Installed: Yes Status: up-to-date # more /etc/NetworkManager/system-connections/ethernet-1 [connection] id=ethernet-1 uuid=96b2bb28-208a-482f-a45f-d60b59e7fe99 type=ethernet permissions= secondaries= [ethernet] mac-address=00:1E:4F:BF:B7:E8 mac-address-blacklist= mtu=1500 [ipv4] address1=192.168.2.14/32,192.168.2.1 dns=8.8.8.8;8.8.4.4; dns-search=HOME......; may-fail=false method=auto [ipv6] dns-search= method=ignore -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/04/17 08:21 AM, Andrei Borzenkov wrote:
01.04.2017 15:12, Anton Aylward пишет: ...
[ipv4] ... method=auto
You told it to use DHCP, I am not sure why you complain now.
So "auto" means DHCP? That's as clear as mud! The alternatives are * disabled, which is obviously not what I want * link-local, which isn't useful * manual, which isn't getting me anything I haven't got this long way round doing it manually so why bother * shared - which means what? Shared with what? As I said, "clear as mud". if I'm giving it a static address then why isn't it smart enough to recognise that mad make use of it 'automatically'? Is it (or the designer/implementer) really that dumb? Why give a static address if you're going to use anything except a static address? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
01.04.2017 16:24, Anton Aylward пишет:
if I'm giving it a static address then why isn't it smart enough to recognise that mad make use of it 'automatically'?
Apart from the obvious fact that "it" is neither smart nor dumb - "it" does exactly what "it" was programmed to do - having static addresses in addition to dynamic is valid and sometimes useful configuration. So in this case "it" does exactly what "it" was told to do. I have some reasons to suspect that /32 address is simply being dropped because it's validity is questionable on Ethernet. At least, when I add static addresses with more traditional netmask they are applied in addition to DHCP. NetworkManager logs may tell you more. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/04/17 02:22 PM, Andrei Borzenkov wrote:
01.04.2017 16:24, Anton Aylward пишет:
if I'm giving it a static address then why isn't it smart enough to recognise that mad make use of it 'automatically'?
Apart from the obvious fact that "it" is neither smart nor dumb - "it" does exactly what "it" was programmed to do - having static addresses in addition to dynamic is valid and sometimes useful configuration. So in this case "it" does exactly what "it" was told to do.
"It" was programmed by a human being and that human being determined the decision algorithm and prioritization (even if that happens to be "stop after the first thing and don't consider any others") in the event of multiple entries.
I have some reasons to suspect that /32 address is simply being dropped because it's validity is questionable on Ethernet. At least, when I add static addresses with more traditional netmask they are applied in addition to DHCP. NetworkManager logs may tell you more.
Just to make it absolutely clear: I *DID NOT* tell it "/32". I simply have it an address. "It" decided to add the "/32" all but it's algorithmic self. I will take a look a the logs tomorrow. Good night :-) Sweet dreams :-) -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/01/2017 07:22 PM, Anton Aylward wrote:
Good night :-) Sweet dreams :-)
Before you turn in, drop by /etc/sysconfig/network and make sure on of the interface scripts isn't part of the problem. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
02.04.2017 03:22, Anton Aylward пишет:
Just to make it absolutely clear: I *DID NOT* tell it "/32". I simply have it an address. "It" decided to add the "/32" all but it's algorithmic self.
Then start with explaining what you did. You started with showing us raw NM configuration file, in which case it is logical to assume that you created this file. I cannot even add additional address using nm-connection-editor if Auto is chosen for IPv4 activation method. And I can *NOT* save connection in nm-connection-editor unless I explicitly set mask for address if Manual method is selected. And if I create connection with Manual method and then change to Auto, any extra address is removed. So please explain what was "it" which "decided" for /32 mask and what were steps to talk "it" into doing it. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/04/17 02:19 AM, Andrei Borzenkov wrote:
02.04.2017 03:22, Anton Aylward пишет:
Just to make it absolutely clear: I *DID NOT* tell it "/32". I simply have it an address. "It" decided to add the "/32" all but it's algorithmic self.
Then start with explaining what you did. You started with showing us raw NM configuration file, in which case it is logical to assume that you created this file.
I cannot even add additional address using nm-connection-editor if Auto is chosen for IPv4 activation method. And I can *NOT* save connection in nm-connection-editor unless I explicitly set mask for address if Manual method is selected. And if I create connection with Manual method and then change to Auto, any extra address is removed.
So please explain what was "it" which "decided" for /32 mask and what were steps to talk "it" into doing it.
I'm sure I mentioned somewhere along the line that I used "nmtui" and the ability of nmcli to set explicit values. There was a lot of 'pushing and shoving' and tweaking and "I wonder what this does' along the way. Nmcli is awesome! The 'Swiss Army Knife" of NetworkManager! Per seems to have clarified that my not explicitly specifying a mask in nmtui meant that it "assumed" /32. In that specific iteration of the Drunkard's Walk 'nmtui' was the "it". I have Carlos to thank for showing me a different semantic interpretation of "manual" and "automatic" to the one I was assuming. "manual" ==> do everything automatically (aka '*without* _manual_ intervention such as 'nmcli connection up') at boot time as per the config files "automatic" ==> use DHCP and ignore the config files -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
02.04.2017 15:34, Anton Aylward пишет:
On 02/04/17 02:19 AM, Andrei Borzenkov wrote:
02.04.2017 03:22, Anton Aylward пишет:
Just to make it absolutely clear: I *DID NOT* tell it "/32". I simply have it an address. "It" decided to add the "/32" all but it's algorithmic self.
Then start with explaining what you did. You started with showing us raw NM configuration file, in which case it is logical to assume that you created this file.
I cannot even add additional address using nm-connection-editor if Auto is chosen for IPv4 activation method. And I can *NOT* save connection in nm-connection-editor unless I explicitly set mask for address if Manual method is selected. And if I create connection with Manual method and then change to Auto, any extra address is removed.
So please explain what was "it" which "decided" for /32 mask and what were steps to talk "it" into doing it.
I'm sure I mentioned somewhere along the line that I used "nmtui" and the ability of nmcli to set explicit values. There was a lot of 'pushing and shoving' and tweaking and "I wonder what this does' along the way. Nmcli is awesome! The 'Swiss Army Knife" of NetworkManager!
Per seems to have clarified that my not explicitly specifying a mask in nmtui meant that it "assumed" /32. In that specific iteration of the Drunkard's Walk 'nmtui' was the "it".
Yes, indeed. Still, when I test it, NM does assign /32 address in addition to any automatic from DHCP. Does it do it in your case? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/04/17 08:45 AM, Andrei Borzenkov wrote:
Yes, indeed. Still, when I test it, NM does assign /32 address in addition to any automatic from DHCP. Does it do it in your case?
Thanks to Per and Carlos I've got something that works if I start NetworkManager with systemctl and I'm going to test that with boot later today after all housekeeping and errands. Or maybe during the week ... I did go back to nmtui and specify a mask :-) -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Anton Aylward wrote:
I've had no end of problems with NetworkManager but seem to be converging on a solution.
I have a config file /etc/system-connections/ethernet that seems reasonable, built with the CLI level "nm" tools.
Nowhere in any of the config do I have anything that indicates I am running wifi or have wifi hardware on this desktop. That file described a static configuration
Not completely clear - don't you have wifi hardware, or is it just not mentioned? If the latter, you might try the no-auto-default key in NetworkManager.conf. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/04/17 12:40 PM, pit wrote:
Anton Aylward wrote:
I've had no end of problems with NetworkManager but seem to be converging on a solution.
I have a config file /etc/system-connections/ethernet that seems reasonable, built with the CLI level "nm" tools.
Nowhere in any of the config do I have anything that indicates I am running wifi or have wifi hardware on this desktop. That file described a static configuration
Not completely clear - don't you have wifi hardware, or is it just not mentioned? If the latter, you might try the no-auto-default key in NetworkManager.conf.
I don't have wifi configured because I don't have wifi hardware. This is a desktop; regular readers might recall it is a Dell Optiplex 755. The wifi is in my Thompson router/switch/cable-model. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2017-04-01 a las 08:12 -0400, Anton Aylward escribió:
[ipv4] address1=192.168.2.14/32,192.168.2.1 dns=8.8.8.8;8.8.4.4; dns-search=HOME......; may-fail=false method=auto
Something like this works for me: [ipv4] method=manual dns=127.1.1.1; dns-search=valinor; address1=192.168.1.129/24,192.168.1.1 may-fail=false - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAljgJN0ACgkQja8UbcUWM1zCogEAhqbvgvCns/iycLZO47pqZ99i Aw0X3rPBi9BfuemdrvwA/RQF+OtpHLKLtVjMO/NRx2BjmuFmKGSuRHyJ3snyyV3N =NNfl -----END PGP SIGNATURE-----
On 01/04/17 06:08 PM, Carlos E. R. wrote:
Something like this works for me:
[ipv4] method=manual
^^^^^^ And what does "manual" mean? Does it start "auto"-matically after boot or does it require that you log in (?as root?) and start it "manual"-ly with something like nmcli con up eth0
dns=127.1.1.1; dns-search=valinor; address1=192.168.1.129/24,192.168.1.1 ^^^
Did you enter that "/24" or did you just enter the address and the program figured out the "/24"? I ask because I used the "nmtui" and entered the address with no mask and it decided on "/32" for me without asking or consulting me in any way.
may-fail=false
-- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2017-04-02 02:37, Anton Aylward wrote:
On 01/04/17 06:08 PM, Carlos E. R. wrote:
Something like this works for me:
[ipv4] method=manual
^^^^^^
And what does "manual" mean? Does it start "auto"-matically after boot or does it require that you log in (?as root?) and start it "manual"-ly with something like
Of course it works "automatically". The human decided to enter _manually_ an IP address, instead of having it find one _automatically_ from the router via dhcp or whatever. Not my business how. I'm just a plain user :-P You think way to much ;-P
nmcli con up eth0
In my case, it is configured via applet in XFCE, but being a system connection it starts sometime during the boot sequence
dns=127.1.1.1; dns-search=valinor; address1=192.168.1.129/24,192.168.1.1 ^^^
Did you enter that "/24" or did you just enter the address and the program figured out the "/24"?
I entered a mask, 255.255.255.0
I ask because I used the "nmtui" and entered the address with no mask and it decided on "/32" for me without asking or consulting me in any way.
Must be the default for "no entry". -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
Carlos E. R. wrote:
dns=127.1.1.1; dns-search=valinor; address1=192.168.1.129/24,192.168.1.1 ^^^
Did you enter that "/24" or did you just enter the address and the program figured out the "/24"?
I entered a mask, 255.255.255.0
I ask because I used the "nmtui" and entered the address with no mask and it decided on "/32" for me without asking or consulting me in any way.
Must be the default for "no entry".
Yes, that is the CIDR notation convention - if you omit the /mask, it is assumed to be /32 for IPv4 and /128 for IPv6. -- Per Jessen, Zürich (12.0°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/04/17 09:43 PM, Carlos E. R. wrote:
Of course it works "automatically". The human decided to enter _manually_ an IP address, instead of having it find one _automatically_ from the router via dhcp or whatever.
Now that's an interpretation of 'manual' and 'automatic' that didn't occur to me. Perhaps I was thinking in automotive terms. That the function had to be engaged manually after starting, possibly by running nmcli con up eth0 as opposed to starting automatically like every other service. Not "thinking too much", just thinking with different semantics. never the ess, I've come to learn a lot about nmcli :-) -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2017-04-02 a las 08:20 -0400, Anton Aylward escribió:
On 01/04/17 09:43 PM, Carlos E. R. wrote:
Of course it works "automatically". The human decided to enter _manually_ an IP address, instead of having it find one _automatically_ from the router via dhcp or whatever.
Now that's an interpretation of 'manual' and 'automatic' that didn't occur to me. Perhaps I was thinking in automotive terms.
It is the same wording as in Windows, LOL :-)) - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAljhkSkACgkQja8UbcUWM1zieQEAikgNebUT2Wfq9Ur2iqMTw7L3 U2BDid3yJ1aysmnOdLkA/0gPrsqsqC4E1lcS1jZAzauDN4iK6HtfeXg7hLz/eGFe =THIh -----END PGP SIGNATURE-----
On 02/04/17 08:02 PM, Carlos E. R. wrote:
It is the same wording as in Windows, LOL :-))
Which isn't relevant to me as I've not had occasion to use a Windows system for ... I think over a decade and half. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (6)
-
Andrei Borzenkov -
Anton Aylward -
Carlos E. R. -
David C. Rankin -
Per Jessen -
pit