Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: Bookworm won't route ipv6 requests
221 views
Skip to first unread message
Tom Furie
Dec 11, 2022, 12:10:06 PM12/11/22
to
On Sun, Dec 11, 2022 at 11:59:55PM +1100, Jason Bigelow wrote:
> $ host 04:92:26:d1:fa:77
That isn't an IP address, it's a MAC address.
> $ ip addr
> 2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
> UP group default qlen 1000
> link/ether 04:92:26:d1:fa:77 brd ff:ff:ff:ff:ff:ff
^^^^^^^^^^^^^^^^^
This is a MAC address
> inet 10.0.0.96/24 brd 10.0.0.255 scope global dynamic noprefixroute
^^^^^^^^^
This is an IPv4 address
> inet6 2001:8003:234d:a600:d010:41cc:f0bc:48f3/64 scope global temporary
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is an IPv6 address
> inet6 2001:8003:234d:a600:692:26ff:fed1:fa77/64 scope global dynamic
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is an IPv6 address
What do "ip route" and "ip -6 route" give for output?
--
Marxist Law of Distribution of Wealth:
Shortages will be divided equally among the peasants.
> $ host 04:92:26:d1:fa:77
That isn't an IP address, it's a MAC address.
> $ ip addr
> 2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state
> UP group default qlen 1000
> link/ether 04:92:26:d1:fa:77 brd ff:ff:ff:ff:ff:ff
^^^^^^^^^^^^^^^^^
This is a MAC address
> inet 10.0.0.96/24 brd 10.0.0.255 scope global dynamic noprefixroute
^^^^^^^^^
This is an IPv4 address
> inet6 2001:8003:234d:a600:d010:41cc:f0bc:48f3/64 scope global temporary
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is an IPv6 address
> inet6 2001:8003:234d:a600:692:26ff:fed1:fa77/64 scope global dynamic
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is an IPv6 address
What do "ip route" and "ip -6 route" give for output?
--
Marxist Law of Distribution of Wealth:
Shortages will be divided equally among the peasants.
Georgi Naplatanov
Dec 11, 2022, 12:40:05 PM12/11/22
to
On 12/11/22 14:59, Jason Bigelow wrote:
> Hello,
>
> I've recently started having network issues on Bookworm. I re-installed
> Debian
> and re-upgraded to Bookworm while preserving my /home and /boot
> partitions which
> solved the issue of being totally unable to connect, but I have since
> noticed
> that I am unable to connected to anything across IPv6, which may be the
> same
> issue resurfacing, just not as badly because the installation has had
> time to
> establish IPv4 connections..?
>
> I have what should be a standard IP setup for a system upgraded from
> Bullseye
> netinst media to bookworm: no firewalls, no proxies. Just a desktop on an
> ordinary residential LAN, connected by ethernet port. I have a WLAN card
> but
> don't use it, I haven't configured it.
>
> I haven't experienced similar issues on Windows and Android devices on the
> same LAN, so I'm thinking it's an issue with my Debian Machine.
>
>
> I can't get any DNS, ICMP or other protocol requests to reach even
> localhost,
> let alone my router. I have pretty limited knowledge about networking.
> How can I fix the IPv6 configuration on my machine?
> $ host -6 04:92:26:d1:fa:77
> ;; communications error to ::1#53: connection refused
> ;; communications error to ::1#53: connection refused
> ;; no servers could be reached
>
> $ host -6 foo
> ;; communications error to ::1#53: connection refused
> ;; communications error to ::1#53: connection refused
> ;; no servers could be reached
>
> $ dig -6 localhost
> ;; communications error to ::1#53: connection refused
> ;; communications error to ::1#53: connection refused
> ;; communications error to ::1#53: connection refused
Hi Jason,
how did you configure your Ethernet card - with Network Manager or?
Please provide configuration.
The above errors means that your system is configured to use DNS server
on localhost (IPv6 - ::1) and connection was refused. So this is first
thing to check - your DNS configuration. You have the following choices:
- install DNS server on your local computer (BIND for example)
- you can use DNS on your router
- you can use DNS provided by your ISP.
Kind regards
Georgi
> Inspecting the network with WireShark while running DNS queries with
> `dig -6`
> shows nothing whatsoever.
>
> $ ip addr
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen 1000
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> valid_lft 50579sec preferred_lft 50579sec
> valid_lft 4127sec preferred_lft 4127sec
> valid_lft 4127sec preferred_lft 4127sec
> inet6 fe80::692:26ff:fed1:fa77/64 scope link noprefixroute
> valid_lft forever preferred_lft forever
> 3: wlp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
> DOWN group default qlen 1000
> link/ether a2:e1:fa:5c:61:3f brd ff:ff:ff:ff:ff:ff permaddr
> d0:37:45:91:cf:4d
>
> $ cat /etc/hosts
> 127.0.0.1 localhost
> 127.0.1.1 <redacted>
> # The following lines are desirable for IPv6 capable hosts
> ::1 localhost ip6-localhost ip6-loopback
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
>
> Select output of lspci:
> 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
> 07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192EE
> PCIe Wireless Network Adapter
>
>
> Select entries from dpkg-query -l:
> ii avahi-daemon 0.8-6+b1 amd64 Avahi
> mDNS/DNS-SD daemon
> ii bind9-host 1:9.18.8-1 amd64 DNS Lookup
> Utility
> ii bind9-libs:amd64 1:9.18.8-1 amd64 Shared
> Libraries used by BIND 9
> ii dns-root-data 2021011101 all DNS
> root data including root zone and DNSSEC key
> ii dnsmasq-base 2.87-1.1 amd64 Small
> caching DNS proxy and DHCP/TFTP server
> ii glib-networking:amd64 2.74.0-1 amd64
> network-related giomodules for GLib
> ii glib-networking:i386 2.74.0-1 i386
> network-related giomodules for GLib
> ii glib-networking-common 2.74.0-1 all network-related
> giomodules for GLib - data files
> ii glib-networking-services 2.74.0-1 amd64 network-related
> giomodules for GLib - D-Bus services
> ii iputils-ping 3:20221126-1 amd64 Tools to
> test the reachability of network hosts
> ii ifupdown 0.8.39+b1 amd64 high level
> tools to configure network interfaces
> ii iproute2 6.0.0-1+b1 amd64 networking
> and traffic control tools
> ii libavahi-core7:amd64 0.8-6+b1 amd64 Avahi's
> embeddable mDNS/DNS-SD library
> ii libdns-export1110 1:9.11.19+dfsg-2.1 amd64 Exported
> DNS Shared Library
> ii libip4tc2:amd64 1.8.8-1 amd64 netfilter
> libip4tc library
> ii libip6tc2:amd64 1.8.8-1 amd64 netfilter
> libip6tc library
> ii libgeoip1:amd64 1.6.12-9 amd64 non-DNS
> IP-to-country resolver library
> ii libkf5kiocore5:amd64 5.100.0-2 amd64
> resource and network access abstraction (KIO core library)
> ii libkf5kiofilewidgets5:amd64 5.100.0-2 amd64 resource and
> network access abstraction (KIO file widgets library)
> ii libkf5kiogui5:amd64 5.100.0-2 amd64 resource
> and network access abstraction (KIO gui library)
> ii libkf5kiontlm5:amd64 5.100.0-2 amd64
> resource and network access abstraction (KIO NTLM library)
> ii libkf5kiowidgets5:amd64 5.100.0-2 amd64 resource and network
> access abstraction (KIO widgets library)
> ii libnet-dbus-perl 1.2.0-1+b3 amd64 Perl
> extension for the DBus bindings
> ii libnet-http-perl 6.22-1 all module
> providing low-level HTTP connection client
> ii libnet-smtp-ssl-perl 1.04-2 all Perl
> module providing SSL support to Net::SMTP
> ii libnet-ssleay-perl:amd64 1.92-2+b1 amd64 Perl module for
> Secure Sockets Layer (SSL)
> ii libnetfilter-conntrack3:amd64 1.0.9-2 amd64 Netfilter
> netlink-conntrack library
> ii libnetpbm11:amd64 2:10.97.00-2 amd64 Graphics
> conversion tools shared libraries
> ii libnettle8:amd64 3.8.1-2 amd64 low
> level cryptographic library (symmetric and one-way cryptos)
> ii libnettle8:i386 3.8.1-2 i386 low
> level cryptographic library (symmetric and one-way cryptos)
> ii libnfnetlink0:amd64 1.0.2-2 amd64
> Netfilter netlink library
> ii libnl-3-200:amd64 3.7.0-0.2+b1 amd64 library
> for dealing with netlink sockets
> ii libnl-genl-3-200:amd64 3.7.0-0.2+b1 amd64 library for dealing
> with netlink sockets - generic netlink
> ii libnl-route-3-200:amd64 3.7.0-0.2+b1 amd64 library for
> dealing with netlink sockets - route interface
> ii libnss-mdns:amd64 0.15.1-3 amd64 NSS
> module for Multicast DNS name resolution
> ii libproxy1-plugin-networkmanager:amd64
> 0.4.18-1 amd64 automatic proxy
> configuration management library (Network Manager plugin)
> ii libqt5network5:amd64 5.15.6+dfsg-5 amd64 Qt 5
> network module
> ii libwireshark-data 4.0.1-1 all network
> packet dissection library -- data files
> ii libwireshark16:amd64 4.0.1-1 amd64 network
> packet dissection library -- shared library
> ii libwiretap13:amd64 4.0.1-1 amd64 network
> packet capture library -- shared library
> ii libwsutil14:amd64 4.0.1-1 amd64 network
> packet dissection utilities library -- shared library
> ii libxtables12:amd64 1.8.8-1 amd64 netfilter
> xtables library
> ii netbase 6.4 all Basic TCP/IP
> networking system
> ii netcat-traditional 1.10-47 amd64 TCP/IP
> swiss army knife
> ii netpbm 2:10.97.00-2 amd64 Graphics
> conversion tools between image formats
> ii network-manager 1.40.6-1 amd64 network
> management framework (daemon and userspace tools)
> ii tcpdump 4.99.1-4+b1 amd64 command-line
> network traffic analyzer
> ii traceroute 1:2.1.0-3 amd64 Traces the
> route taken by packets over an IPv4/IPv6 network
> ii update-inetd 4.51 all inetd
> configuration file updater
> ii wireshark 4.0.1-1 amd64 network
> traffic analyzer - meta-package
> ii wireshark-common 4.0.1-1 amd64 network
> traffic analyzer - common files
> ii wireshark-qt 4.0.1-1 amd64 network
> traffic analyzer - Qt version
>
> Hello,
>
> I've recently started having network issues on Bookworm. I re-installed
> Debian
> and re-upgraded to Bookworm while preserving my /home and /boot
> partitions which
> solved the issue of being totally unable to connect, but I have since
> noticed
> that I am unable to connected to anything across IPv6, which may be the
> same
> issue resurfacing, just not as badly because the installation has had
> time to
> establish IPv4 connections..?
>
> I have what should be a standard IP setup for a system upgraded from
> Bullseye
> netinst media to bookworm: no firewalls, no proxies. Just a desktop on an
> ordinary residential LAN, connected by ethernet port. I have a WLAN card
> but
> don't use it, I haven't configured it.
>
> I haven't experienced similar issues on Windows and Android devices on the
> same LAN, so I'm thinking it's an issue with my Debian Machine.
>
>
> I can't get any DNS, ICMP or other protocol requests to reach even
> localhost,
> let alone my router. I have pretty limited knowledge about networking.
> How can I fix the IPv6 configuration on my machine?
>
> $ host 04:92:26:d1:fa:77
> Host 04:92:26:d1:fa:77 not found: 3(NXDOMAIN)
> $ host 04:92:26:d1:fa:77
> $ host -6 04:92:26:d1:fa:77
> ;; communications error to ::1#53: connection refused
> ;; communications error to ::1#53: connection refused
> ;; no servers could be reached
>
> $ host -6 foo
> ;; communications error to ::1#53: connection refused
> ;; communications error to ::1#53: connection refused
> ;; no servers could be reached
>
> $ dig -6 localhost
> ;; communications error to ::1#53: connection refused
> ;; communications error to ::1#53: connection refused
> ;; communications error to ::1#53: connection refused
Hi Jason,
how did you configure your Ethernet card - with Network Manager or?
Please provide configuration.
The above errors means that your system is configured to use DNS server
on localhost (IPv6 - ::1) and connection was refused. So this is first
thing to check - your DNS configuration. You have the following choices:
- install DNS server on your local computer (BIND for example)
- you can use DNS on your router
- you can use DNS provided by your ISP.
Kind regards
Georgi
> Inspecting the network with WireShark while running DNS queries with
> `dig -6`
> shows nothing whatsoever.
>
> $ ip addr
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen 1000
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
> state UP group default qlen 1000
> link/ether 04:92:26:d1:fa:77 brd ff:ff:ff:ff:ff:ff
> state UP group default qlen 1000
> link/ether 04:92:26:d1:fa:77 brd ff:ff:ff:ff:ff:ff
> inet 10.0.0.96/24 brd 10.0.0.255 scope global dynamic noprefixroute
> enp6s0
> valid_lft 50579sec preferred_lft 50579sec
> inet6 2001:8003:234d:a600:d010:41cc:f0bc:48f3/64 scope global
> temporary dynamic
> valid_lft 4127sec preferred_lft 4127sec
> inet6 2001:8003:234d:a600:692:26ff:fed1:fa77/64 scope global
> dynamic mngtmpaddr noprefixroute
> valid_lft 4127sec preferred_lft 4127sec
> inet6 fe80::692:26ff:fed1:fa77/64 scope link noprefixroute
> valid_lft forever preferred_lft forever
> 3: wlp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state
> DOWN group default qlen 1000
> link/ether a2:e1:fa:5c:61:3f brd ff:ff:ff:ff:ff:ff permaddr
> d0:37:45:91:cf:4d
>
> $ cat /etc/hosts
> 127.0.0.1 localhost
> 127.0.1.1 <redacted>
> # The following lines are desirable for IPv6 capable hosts
> ::1 localhost ip6-localhost ip6-loopback
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
>
> Select output of lspci:
> 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
> 07:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192EE
> PCIe Wireless Network Adapter
>
>
> Select entries from dpkg-query -l:
> ii avahi-daemon 0.8-6+b1 amd64 Avahi
> mDNS/DNS-SD daemon
> ii bind9-host 1:9.18.8-1 amd64 DNS Lookup
> Utility
> ii bind9-libs:amd64 1:9.18.8-1 amd64 Shared
> Libraries used by BIND 9
> ii dns-root-data 2021011101 all DNS
> root data including root zone and DNSSEC key
> ii dnsmasq-base 2.87-1.1 amd64 Small
> caching DNS proxy and DHCP/TFTP server
> ii glib-networking:amd64 2.74.0-1 amd64
> network-related giomodules for GLib
> ii glib-networking:i386 2.74.0-1 i386
> network-related giomodules for GLib
> ii glib-networking-common 2.74.0-1 all network-related
> giomodules for GLib - data files
> ii glib-networking-services 2.74.0-1 amd64 network-related
> giomodules for GLib - D-Bus services
> ii iputils-ping 3:20221126-1 amd64 Tools to
> test the reachability of network hosts
> ii ifupdown 0.8.39+b1 amd64 high level
> tools to configure network interfaces
> ii iproute2 6.0.0-1+b1 amd64 networking
> and traffic control tools
> ii libavahi-core7:amd64 0.8-6+b1 amd64 Avahi's
> embeddable mDNS/DNS-SD library
> ii libdns-export1110 1:9.11.19+dfsg-2.1 amd64 Exported
> DNS Shared Library
> ii libip4tc2:amd64 1.8.8-1 amd64 netfilter
> libip4tc library
> ii libip6tc2:amd64 1.8.8-1 amd64 netfilter
> libip6tc library
> ii libgeoip1:amd64 1.6.12-9 amd64 non-DNS
> IP-to-country resolver library
> ii libkf5kiocore5:amd64 5.100.0-2 amd64
> resource and network access abstraction (KIO core library)
> ii libkf5kiofilewidgets5:amd64 5.100.0-2 amd64 resource and
> network access abstraction (KIO file widgets library)
> ii libkf5kiogui5:amd64 5.100.0-2 amd64 resource
> and network access abstraction (KIO gui library)
> ii libkf5kiontlm5:amd64 5.100.0-2 amd64
> resource and network access abstraction (KIO NTLM library)
> ii libkf5kiowidgets5:amd64 5.100.0-2 amd64 resource and network
> access abstraction (KIO widgets library)
> ii libnet-dbus-perl 1.2.0-1+b3 amd64 Perl
> extension for the DBus bindings
> ii libnet-http-perl 6.22-1 all module
> providing low-level HTTP connection client
> ii libnet-smtp-ssl-perl 1.04-2 all Perl
> module providing SSL support to Net::SMTP
> ii libnet-ssleay-perl:amd64 1.92-2+b1 amd64 Perl module for
> Secure Sockets Layer (SSL)
> ii libnetfilter-conntrack3:amd64 1.0.9-2 amd64 Netfilter
> netlink-conntrack library
> ii libnetpbm11:amd64 2:10.97.00-2 amd64 Graphics
> conversion tools shared libraries
> ii libnettle8:amd64 3.8.1-2 amd64 low
> level cryptographic library (symmetric and one-way cryptos)
> ii libnettle8:i386 3.8.1-2 i386 low
> level cryptographic library (symmetric and one-way cryptos)
> ii libnfnetlink0:amd64 1.0.2-2 amd64
> Netfilter netlink library
> ii libnl-3-200:amd64 3.7.0-0.2+b1 amd64 library
> for dealing with netlink sockets
> ii libnl-genl-3-200:amd64 3.7.0-0.2+b1 amd64 library for dealing
> with netlink sockets - generic netlink
> ii libnl-route-3-200:amd64 3.7.0-0.2+b1 amd64 library for
> dealing with netlink sockets - route interface
> ii libnss-mdns:amd64 0.15.1-3 amd64 NSS
> module for Multicast DNS name resolution
> ii libproxy1-plugin-networkmanager:amd64
> 0.4.18-1 amd64 automatic proxy
> configuration management library (Network Manager plugin)
> ii libqt5network5:amd64 5.15.6+dfsg-5 amd64 Qt 5
> network module
> ii libwireshark-data 4.0.1-1 all network
> packet dissection library -- data files
> ii libwireshark16:amd64 4.0.1-1 amd64 network
> packet dissection library -- shared library
> ii libwiretap13:amd64 4.0.1-1 amd64 network
> packet capture library -- shared library
> ii libwsutil14:amd64 4.0.1-1 amd64 network
> packet dissection utilities library -- shared library
> ii libxtables12:amd64 1.8.8-1 amd64 netfilter
> xtables library
> ii netbase 6.4 all Basic TCP/IP
> networking system
> ii netcat-traditional 1.10-47 amd64 TCP/IP
> swiss army knife
> ii netpbm 2:10.97.00-2 amd64 Graphics
> conversion tools between image formats
> ii network-manager 1.40.6-1 amd64 network
> management framework (daemon and userspace tools)
> ii tcpdump 4.99.1-4+b1 amd64 command-line
> network traffic analyzer
> ii traceroute 1:2.1.0-3 amd64 Traces the
> route taken by packets over an IPv4/IPv6 network
> ii update-inetd 4.51 all inetd
> configuration file updater
> ii wireshark 4.0.1-1 amd64 network
> traffic analyzer - meta-package
> ii wireshark-common 4.0.1-1 amd64 network
> traffic analyzer - common files
> ii wireshark-qt 4.0.1-1 amd64 network
> traffic analyzer - Qt version
>
Georgi Naplatanov
Dec 11, 2022, 2:30:05 PM12/11/22
to
On 12/11/22 20:12, Jason Bigelow wrote:
>
> I am using Network Manager without any input/manual configuration,
> running under
> the assumption it would 'just work'. This also means I am using WPA
> supplicant
> Since my home network needs no special configuration, I had assumed my
> router or
> ISP would act as DNS. Why would DNS on IPv4 work under this
> configuration but
> not IPv6?
>
> It's hard to provide configuration when I'm not sure what I'm looking
> for. I
> installed a bare netinst installation, accidentally with GNOME, but then
> removed
> it and installed sway and i3 in its place. I haven't touched any
> configuration
> text files and have no GUI for it either. /etc/network contains just
> some shell
> files, nothing in /etc/network/interfaces.d:
>
> /etc/network$ ls -R
>
> if-down.d if-post-down.d if-pre-up.d if-up.d interfaces interfaces.d
>
> ./if-down.d:
> resolved wpasupplicant
>
> ./if-post-down.d:
> wpasupplicant
>
> ./if-pre-up.d:
> wpasupplicant
>
> ./if-up.d:
> resolved wpasupplicant
>
> ./interfaces.d:
>
> I've never needed to change this state of affairs i.e. autoconfiguration
> as much
> as possible, until recently when issues started cropping up.
>
> Aware I was using NetworkManager, I tried configuring it by starting
> nm-applet
> and adding a configuration with nm-connection-editor.
>
>
> I added a DNS server for IPv6, OpenDNS' ipv6 address. I then looked under
> into NetworkManager's configuration directory for the connection info:
>
> /etc/NetworkManager/system-connections$ sudo cat 'Wired connection 1'
> [connection]
> id=Wired connection 1
> uuid=aa3b5fa9-a0e8-4ed0-98d5-cae938d836cb
> type=ethernet
> timestamp=1670726772
>
> [ethernet]
>
> [ipv4]
> method=auto
>
> [ipv6]
> addr-gen-mode=stable-privacy
> dns=2620:0:ccc::2;
> ip6-privacy=2
> method=auto
>
> [proxy]
>
Try to comment or delete the following line:
ip6-privacy=2
Kind regards
Georgi
>
> On 2022-12-12 04:32, Georgi Naplatanov wrote:
>> Hi Jason,
>>
>> how did you configure your Ethernet card - with Network Manager or?
>>
>> Please provide configuration.
>>
>> The above errors means that your system is configured to use DNS
>> server on localhost (IPv6 - ::1) and connection was refused. So this
>> is first thing to check - your DNS configuration. You have the
>> following choices:
>>
>> - install DNS server on your local computer (BIND for example)
>> - you can use DNS on your router
>> - you can use DNS provided by your ISP.
>>
>> Kind regards
>> Georgi
>
>
> Hi Georgi,
> On 2022-12-12 04:32, Georgi Naplatanov wrote:
>> Hi Jason,
>>
>> how did you configure your Ethernet card - with Network Manager or?
>>
>> Please provide configuration.
>>
>> The above errors means that your system is configured to use DNS
>> server on localhost (IPv6 - ::1) and connection was refused. So this
>> is first thing to check - your DNS configuration. You have the
>> following choices:
>>
>> - install DNS server on your local computer (BIND for example)
>> - you can use DNS on your router
>> - you can use DNS provided by your ISP.
>>
>> Kind regards
>> Georgi
>
>
>
> I am using Network Manager without any input/manual configuration,
> running under
> the assumption it would 'just work'. This also means I am using WPA
> supplicant
> Since my home network needs no special configuration, I had assumed my
> router or
> ISP would act as DNS. Why would DNS on IPv4 work under this
> configuration but
> not IPv6?
>
> It's hard to provide configuration when I'm not sure what I'm looking
> for. I
> installed a bare netinst installation, accidentally with GNOME, but then
> removed
> it and installed sway and i3 in its place. I haven't touched any
> configuration
> text files and have no GUI for it either. /etc/network contains just
> some shell
> files, nothing in /etc/network/interfaces.d:
>
> /etc/network$ ls -R
>
> if-down.d if-post-down.d if-pre-up.d if-up.d interfaces interfaces.d
>
> ./if-down.d:
> resolved wpasupplicant
>
> ./if-post-down.d:
> wpasupplicant
>
> ./if-pre-up.d:
> wpasupplicant
>
> ./if-up.d:
> resolved wpasupplicant
>
> ./interfaces.d:
>
> I've never needed to change this state of affairs i.e. autoconfiguration
> as much
> as possible, until recently when issues started cropping up.
>
> Aware I was using NetworkManager, I tried configuring it by starting
> nm-applet
> and adding a configuration with nm-connection-editor.
>
>
> I added a DNS server for IPv6, OpenDNS' ipv6 address. I then looked under
> into NetworkManager's configuration directory for the connection info:
>
> /etc/NetworkManager/system-connections$ sudo cat 'Wired connection 1'
> [connection]
> id=Wired connection 1
> uuid=aa3b5fa9-a0e8-4ed0-98d5-cae938d836cb
> type=ethernet
> timestamp=1670726772
>
> [ethernet]
>
> [ipv4]
> method=auto
>
> [ipv6]
> addr-gen-mode=stable-privacy
> dns=2620:0:ccc::2;
> ip6-privacy=2
> method=auto
>
> [proxy]
>
Try to comment or delete the following line:
ip6-privacy=2
Kind regards
Georgi
0 new messages