Your message dated Thu, 14 Mar 2019 18:24:24 +1100
with message-id <[email protected]>
and subject line 
has caused the Debian Bug report #924534,
regarding network-manager: Regression from 1.14.4-4 in 1.14.6-2, fails to 
connect to IPv6-only network
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
924534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924534
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 1.14.6-2
Severity: important
Tags: ipv6

I am currently using an IPv6-only wireless network, in network-manager
1.14.4-4 this worked fine. After upgrading to 1.14.6-2 it wouldn't
connect. Switching to an IPv4+IPv6 wireless network connected fine in
1.14.6-2, after downgrading to 14.4-4 connecting to an IPv6-only network
works again.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages network-manager depends on:
ii  adduser                3.118
ii  dbus                   1.12.12-1
ii  init-system-helpers    1.56+nmu1
ii  libaudit1              1:2.8.4-2
ii  libbluetooth3          5.50-1
ii  libc6                  2.28-8
ii  libcurl3-gnutls        7.64.0-1
ii  libglib2.0-0           2.58.3-1
ii  libgnutls30            3.6.6-2
ii  libjansson4            2.12-1
ii  libmm-glib0            1.10.0-1
ii  libndp0                1.6-1+b1
ii  libnewt0.52            0.52.20-8
ii  libnm0                 1.14.4-4
ii  libpam-systemd         241-1
ii  libpolkit-agent-1-0    0.105-25
ii  libpolkit-gobject-1-0  0.105-25
ii  libpsl5                0.20.2-2
ii  libreadline7           7.0-5
ii  libselinux1            2.8-1+b1
ii  libsystemd0            241-1
ii  libteamdctl0           1.28-1
ii  libudev1               241-1
ii  libuuid1               2.33.1-0.1
ii  lsb-base               10.2018112800
ii  policykit-1            0.105-25
ii  udev                   241-1
ii  wpasupplicant          2:2.7+git20190128+0c1e29f-2

Versions of packages network-manager recommends:
pn  crda                         <none>
ii  dnsmasq-base [dnsmasq-base]  2.80-1
ii  iptables                     1.8.2-4
ii  isc-dhcp-client              4.4.1-2
ii  modemmanager                 1.10.0-1
ii  ppp                          2.4.7-2+4

Versions of packages network-manager suggests:
pn  libteam-utils  <none>

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
no-auto-default=5c:ff:35:0f:6c:bb,
[ifupdown]
managed=true


-- no debconf information

--- End Message ---
--- Begin Message ---
I wondered if this might be some obsolete piece of config, and cleared
out all the custom config in /etc/NM bar the saved networks.

On re-upgrading I can't reproduce the problem, and after re-adding all
my previous custom config (solely IPv6 stable privacy addressing) still
can't reproduce (& I restarted NM after every change).

Closing this bug.

--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

Reply via email to