![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
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