OK Marco,
When the "bad" dongle works "~1 minute"
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 noprefixroute
valid_lft forever preferred_lft forever
9: enp0s20f0u11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000
link/ether be:b2:bf:4f:42:bb brd ff:ff:ff:ff:ff:ff
inet 192.168.8.164/24 brd 192.168.8.255 scope global dynamic noprefixroute
enp0s20f0u11
valid_lft 6992sec preferred_lft 6992sec
inet6 2a04:cec0:10f8:4356:383a:17bc:3b2b:6b6f/64 scope global noprefixroute
valid_lft forever preferred_lft forever
inet6 fe80::f40e:975b:b76a:70cd/64 scope link noprefixroute
valid_lft forever preferred_lft forever
Link 9 (enp0s20f0u11)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS
DNSSEC=no/unsupported
Current DNS Server: 192.168.8.1
DNS Servers: 192.168.8.1 fe80::5044:fdff:fe85:29e3
When the "bad" dongle does not work
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 noprefixroute
valid_lft forever preferred_lft forever
9: enp0s20f0u11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000
link/ether be:b2:bf:4f:42:bb brd ff:ff:ff:ff:ff:ff
inet 192.168.8.164/24 brd 192.168.8.255 scope global dynamic noprefixroute
enp0s20f0u11
valid_lft 6880sec preferred_lft 6880sec
inet6 2a04:cec0:10f8:4356:383a:17bc:3b2b:6b6f/64 scope global noprefixroute
valid_lft forever preferred_lft forever
inet6 fe80::f40e:975b:b76a:70cd/64 scope link noprefixroute
valid_lft forever preferred_lft forever
Link 9 (enp0s20f0u11)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS
DNSSEC=no/unsupported
Current DNS Server: fe80::5044:fdff:fe85:29e3
DNS Servers: 192.168.8.1 fe80::5044:fdff:fe85:29e3
It seems that the current DNS Server changes IPV6 !!!
With the dongle working:
10: enp0s20f0u11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UNKNOWN group default qlen 1000
link/ether aa:88:f1:7e:5c:d0 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.119/24 brd 192.168.1.255 scope global dynamic noprefixroute
enp0s20f0u11
valid_lft 42764sec preferred_lft 42764sec
inet6 fe80::f40e:975b:b76a:70cd/64 scope link noprefixroute
valid_lft forever preferred_lft forever
Link 10 (enp0s20f0u11)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS
DNSSEC=no/unsupported
Current DNS Server: 192.168.1.1
DNS Servers: 192.168.1.1
>
> Am 19.03.2025 um 12:32:28 Uhr schrieb Patrick Dupre via users:
>
> > With the dongle running properly
>
> Use that and post
> ip a
> resolvectl
>
> --
> Gruß
> Marco
>
> Send unsolicited bulk mail to [email protected]
> --
> _______________________________________________
> users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[email protected]
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
