Re: IPv6 Prefix Delegation through Network Manager
Hi, in the log [1538019154.6638] policy: ipv6-pd: enp5s0 needs a subnet [1538019154.6638] policy: ipv6-pd: no device to obtain a subnet to share on enp5s0 from ... [1538019154.6719] policy: ipv6-pd: none of 0 prefixes of enp2s0 can be shared on enp5s0 [1538019154.6719] device (enp2s0): ipv6-pd: device doesn't use DHCPv6, can't request prefixes ... [1538019158.9088] ndisc[0x561734e850e0,"enp2s0"]: neighbor discovery configuration changed [dGR]: [1538019158.9088] ndisc[0x561734e850e0,"enp2s0"]: dhcp-level managed ... [1538019158.9359] dhcp6 (enp2s0): dhclient started with pid 6501 ... It seems there is a bug. At the moment when enp5s0 required a prefix, it wasn't available. And later on, when enp2s0 did DHCPv6, it wrongly wasn't retried to share a prefix. What to do about that, and how to fix is, that is a good question... best, Thomas signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: No new PIN request to the user if PIN stored in settings is wrong
On Thu, 2018-09-27 at 11:51 +0200, Aleksander Morgado wrote: > Hey, > > I'm trying to understand whether this behavior is on purpose or not. > > I have some "gsm" settings for a broadband connection, and the > settings have a PIN stored. I then try to use those settings on a > modem device but the expected PIN in the modem is a different one, so > the connection attempt fails with a "sim-pin-incorrect" reason. At > this point NetworkManager doesn't request the user new secrets for > this connection after finding that the stored ones are wrong; i.e. i > don't see any popup window in the shell asking to enter PIN. The > connection attempt just fails and we do get reported in the UI about > the failed attempt. > > Is this behavior (asking the user for PIN after a "sim-pin-incorrect" > failure) not implemented or am I missing some reason that would > prevent doing that? The behavior is different e.g. with WiFi; if I > change the key in my router and I request NM to connect to the WiFi > network, the authentication failure triggers a new request for > secrets > to the user. > > Cheers! Hi, sounds like a bug. If a secret/pin is wrong, NM should re-ask for it. Do you have a level=TRACE log? best, Thomas signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
No new PIN request to the user if PIN stored in settings is wrong
Hey, I'm trying to understand whether this behavior is on purpose or not. I have some "gsm" settings for a broadband connection, and the settings have a PIN stored. I then try to use those settings on a modem device but the expected PIN in the modem is a different one, so the connection attempt fails with a "sim-pin-incorrect" reason. At this point NetworkManager doesn't request the user new secrets for this connection after finding that the stored ones are wrong; i.e. i don't see any popup window in the shell asking to enter PIN. The connection attempt just fails and we do get reported in the UI about the failed attempt. Is this behavior (asking the user for PIN after a "sim-pin-incorrect" failure) not implemented or am I missing some reason that would prevent doing that? The behavior is different e.g. with WiFi; if I change the key in my router and I request NM to connect to the WiFi network, the authentication failure triggers a new request for secrets to the user. Cheers! -- Aleksander https://aleksander.es ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
