On Mon, 2014-08-25 at 11:09 +0200, Harald Dunkel wrote:
PS: For testing I have explicitly enabled method=auto for IPv4 in
the "eth0" connection and clicked on [save]. Now there is a config
file /etc/NetworkManager/system-connections/eth0, but IPv4 is still
ignored (now and on reboot).
[ethernet]
duplex=full
mac-address=28:D2:44:3D:xx:xx
[connection]
id=eth0
uuid=e3e1c512-84fa-47d8-9945-fce001441d0c
interface-name=eth0
type=ethernet
autoconnect=false
timestamp=1408950085
[ipv6]
method=auto
dns=2a00:xx:xx::3;
dns-search=red.example.com.;
ip6-privacy=0
[ipv4]
method=auto
The static configuration without n-m still works as expected.
BTW, how comes that information provided by stateless DHCP6
gets hardwired in the generated config file?
Regards
Harri
when you start NetworkManager... ..., and the interface has already some IP configuration, NM tries to take over that configuration non-destructively (1). In that case, NM looks for a matching connection and pretends that the connection is already active on your device -- without actually changing the device. If no matching connection can be found, it creates a connection. That connection is in-memory only, until you delete it or until you save/modify it. That was "eth0" you see, and it contains dhcp data, because NM does not know that some parts came via DHCP6. OTOH, when you start NM and there is no IP configuration, then it *might* create an in-memory, autoconnect connection and autoactivates it. It does this only for ethernet device. That is the "Wired Connection" you saw. It does not create this connection, when you have already connection for the device. Otherwise, it will look for a applicable connection that is autoconnect, and connect it. Otherwise, it will not connect any connection at startup. You can avoid (1) by not configuring the interface externally. Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part