Dongle USB

[Patrick Dupre]

Hello,

4 months ago, I could used my LTE USB Dongle because I could
not connect to 192.168.1.1.
There has no reason for that.
Anyway, I decided to buy a new Dongle. But I am facing the same 
issue.
lsusb is fine.

Could it be an issue with fedora? after an update?
I already tried to use a previous kernel.

Thank.

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
===========================================================================

[Marco Moock]

Am 18.03.2025 um 13:15:31 Uhr schrieb Patrick Dupre via users:
> 4 months ago, I could used my LTE USB Dongle because I could
> not connect to 192.168.1.1.
> There has no reason for that.
> Anyway, I decided to buy a new Dongle. But I am facing the same 
> issue.
> lsusb is fine.
>
> Could it be an issue with fedora? after an update?
> I already tried to use a previous kernel.

Post the output of the following commands:

ip a
ip r s
ip -6 r s

[Patrick Dupre]

> Am 18.03.2025 um 13:15:31 Uhr schrieb Patrick Dupre via users:
> > 4 months ago, I could used my LTE USB Dongle because I could
> > not connect to 192.168.1.1.
> > There has no reason for that.
> > Anyway, I decided to buy a new Dongle. But I am facing the same 
> > issue.
> > lsusb is fine.
> >
> > Could it be an issue with fedora? after an update?
> > I already tried to use a previous kernel.
>
> Post the output of the following commands:
>
> ip a
> ip r s
> ip -6 r s
>
> -- 
> Gruß
> Marco

Thank Marco,

Here some comments.
After tons of tries, my old LTE works !!!
But the new still does not work.

Here are the required outputs

1) ip a The old one (now working!
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
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 50:91:e3:c9:58:ab brd ff:ff:ff:ff:ff:ff
3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 88:d7:f6:c5:a3:9d brd ff:ff:ff:ff:ff:ff
5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:99:2e:c5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
7: enp0s20f0u1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether e6:7d:9d:c6:43:c7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.105/24 brd 192.168.1.255 scope global dynamic noprefixroute enp0s20f0u1
       valid_lft 43140sec preferred_lft 43140sec
    inet6 fe80::18f3:4333:127b:d2a8/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

The new one not working
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
2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 50:91:e3:c9:58:ab brd ff:ff:ff:ff:ff:ff
3: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 88:d7:f6:c5:a3:9d brd ff:ff:ff:ff:ff:ff
5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:99:2e:c5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
6: enp0s20f0u1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 12:5a:80:f3:79:e4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.8.106/24 brd 192.168.8.255 scope global dynamic noprefixroute enp0s20f0u1
       valid_lft 6729sec preferred_lft 6729sec
    inet6 fe80::18f3:4333:127b:d2a8/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

2) ip r s (old working)
default via 192.168.1.1 dev enp0s20f0u1 proto dhcp src 192.168.1.105 metric 100 
192.168.1.0/24 dev enp0s20f0u1 proto kernel scope link src 192.168.1.105 metric 100 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

The new one (not working)
default via 192.168.8.1 dev enp0s20f0u1 proto dhcp src 192.168.8.146 metric 100 
192.168.8.0/24 dev enp0s20f0u1 proto kernel scope link src 192.168.8.146 metric 100 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

3) ip -6 r s (old working)
fe80::/64 dev enp0s20f0u1 proto kernel metric 1024 pref medium

The new one
fe80::/64 dev enp0s20f0u1 proto kernel metric 1024 pref medium

ifconfig (when working)
enp0s20f0u1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.196  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::18f3:4333:127b:d2a8  prefixlen 64  scopeid 0x20<link>
        ether 1a:b2:f6:a4:12:f9  txqueuelen 1000  (Ethernet)
        RX packets 1709  bytes 666894 (651.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1632  bytes 431365 (421.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

when not working
enp0s20f0u1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.8.146  netmask 255.255.255.0  broadcast 192.168.8.255
        inet6 fe80::5084:29d9:8c26:85c1  prefixlen 64  scopeid 0x20<link>
        ether e2:04:0f:81:40:1c  txqueuelen 1000  (Ethernet)
        RX packets 1221  bytes 102725 (100.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1765  bytes 242787 (237.0 KiB)
        TX errors 0  dropped 4 overruns 0  carrier 0  collisions 0

[Marco Moock]

Am 18.03.2025 um 16:53:37 Uhr schrieb Patrick Dupre via users:
> After tons of tries, my old LTE works !!!

What did you change?
> 5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
>     link/ether 52:54:00:99:2e:c5 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
>        valid_lft forever preferred_lft forever

What is that for an interface?

In case it doesn't work:
traceroute 8.8.8.8

[Patrick Dupre]

> Am 18.03.2025 um 16:53:37 Uhr schrieb Patrick Dupre via users:
> > After tons of tries, my old LTE works !!!
>
> What did you change?

Nothings
> > 5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
> >     link/ether 52:54:00:99:2e:c5 brd ff:ff:ff:ff:ff:ff
> >     inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
> >        valid_lft forever preferred_lft forever
>
> What is that for an interface?

I do not think that we have to worry about this interface.
The one to worry is (not working)
enp0s20f0u1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 92:cd:8e:89:d4:a2 brd ff:ff:ff:ff:ff:ff
    inet 192.168.8.146/24 brd 192.168.8.255 scope global dynamic noprefixroute enp0s20f0u1
       valid_lft 7073sec preferred_lft 7073sec
    inet6 fe80::5084:29d9:8c26:85c1/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

When working
enp0s20f0u1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 92:35:b6:34:b9:e0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.160/24 brd 192.168.1.255 scope global dynamic noprefixroute enp0s20f0u1
       valid_lft 42966sec preferred_lft 42966sec
    inet6 fe80::18f3:4333:127b:d2a8/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.671 ms  1.518 ms  1.643 ms
 2  10.110.7.5 (10.110.7.5)  73.399 ms  80.809 ms  80.790 ms
 3  10.110.6.83 (10.110.6.83)  83.676 ms  83.663 ms  83.736 ms
 4  10.110.147.50 (10.110.147.50)  84.023 ms  83.792 ms  83.628 ms
 5  * * *
 6  be41.cbr01-ntr.net.bbox.fr (212.194.171.132)  83.785 ms  80.420 ms  80.422 ms
 7  * * *
 8  142.250.175.198 (142.250.175.198)  31.641 ms  25.472 ms  25.427 ms
 9  108.170.238.45 (108.170.238.45)  28.361 ms  28.348 ms  33.329 ms
10  142.250.234.43 (142.250.234.43)  33.120 ms 142.251.253.37 (142.251.253.37)  31.100 ms 72.14.237.93 (72.14.237.93)  36.679 ms
11  dns.google (8.8.8.8)  37.377 ms  25.800 ms  25.617 ms

When not working

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  _gateway (192.168.8.1)  2.223 ms !N  2.197 ms !N *
> In case it doesn't work:
> traceroute 8.8.8.8
>
> -- 
> Gruß
> Marco
> Send unsolicited bulk mail to [e-mail]
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Barry]

> On 18 Mar 2025, at 15:54, Patrick Dupre via users  wrote:
>
> After tons of tries, my old LTE works !!!
> But the new still does not work.

It has been a very long time since I last looked at this stuff so may be out of date.

Look at the logs for ModemManager and NetworkManager.

Modem manager typically needs to kick the dongal to exit cdrom emulation and become a modem.

You should be able to see what the dongal is doing with verbose lsusb reports.
And the logs should report the modem is detected then kicked.

Barry

[Marco Moock]

Am 18.03.2025 um 18:02:45 Uhr schrieb Patrick Dupre via users:
> traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
>  1  _gateway (192.168.8.1)  2.223 ms !N  2.197 ms !N *

Is the cellular connection established in this situation?

Can you check that in modemmanager-gui?

What does dmesg show?

[Patrick Dupre]

Every thing OK, I just cannot connect to 198.162.1.1

Mar 18 19:41:43 Teucidide NetworkManager[1491]: <info>  [1742323303.4263] audit: op="connection-update" uuid="8c65db7d-46fe-35b3-a83a-3c8ab886c056" name="one_touch" args="connection>
Mar 18 19:41:55 Teucidide NetworkManager[1491]: <info>  [1742323315.7381] audit: op="connection-update" uuid="4cd09bc1-44a5-45a5-9b3a-064982f823dd" name="cat4" args="connection.auto>
Mar 18 19:41:55 Teucidide NetworkManager[1491]: <info>  [1742323315.7568] audit: op="device-reapply" interface="enp0s20f0u1" ifindex=14 args="connection.id,connection.autoconnect-pr>
Mar 18 19:42:11 Teucidide NetworkManager[1491]: <info>  [1742323331.7204] audit: op="connection-update" uuid="4cd09bc1-44a5-45a5-9b3a-064982f823dd" name="cat4" args="connection.time>
Mar 18 19:42:11 Teucidide NetworkManager[1491]: <info>  [1742323331.7446] audit: op="device-reapply" interface="enp0s20f0u1" ifindex=14 args="connection.id,connection.uuid" pid=1509>
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.4996] device (enp0s20f0u1): disconnecting for new activation request.
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.4997] device (enp0s20f0u1): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'm>
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5026] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5028] audit: op="connection-activate" uuid="4cd09bc1-44a5-45a5-9b3a-064982f823dd" name="cat4" pid=15093 uid=1000 >
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5185] device (enp0s20f0u1): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state:>
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5241] dhcp4 (enp0s20f0u1): canceled DHCP transaction
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5241] dhcp4 (enp0s20f0u1): activation: beginning transaction (timeout in 45 seconds)
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5241] dhcp4 (enp0s20f0u1): state changed no lease
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5384] device (enp0s20f0u1): Activation: starting connection 'cat4' (4cd09bc1-44a5-45a5-9b3a-064982f823dd)
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5407] device (enp0s20f0u1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5409] manager: NetworkManager state is now CONNECTING
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5410] device (enp0s20f0u1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5764] device (enp0s20f0u1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5770] dhcp4 (enp0s20f0u1): activation: beginning transaction (timeout in 45 seconds)
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5794] dhcp4 (enp0s20f0u1): state changed no lease
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.5874] dhcp4 (enp0s20f0u1): state changed new lease, address=192.168.8.117, acd pending
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.7213] dhcp4 (enp0s20f0u1): state changed new lease, address=192.168.8.117
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.7216] policy: set 'cat4' (enp0s20f0u1) as default for IPv4 routing and DNS
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.7412] device (enp0s20f0u1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.7442] device (enp0s20f0u1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.7444] device (enp0s20f0u1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.7456] manager: NetworkManager state is now CONNECTED_SITE
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.7457] device (enp0s20f0u1): Activation: successful, device activated.
Mar 18 19:42:14 Teucidide NetworkManager[1491]: <info>  [1742323334.7461] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.5870] device (enp0s20f0u1): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'm>
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.5882] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.5885] device (enp0s20f0u1): disconnecting for new activation request.
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.5886] audit: op="connection-activate" uuid="4cd09bc1-44a5-45a5-9b3a-064982f823dd" name="cat4" pid=15093 uid=1000 >
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.6220] device (enp0s20f0u1): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state:>
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.6278] dhcp4 (enp0s20f0u1): canceled DHCP transaction
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.6279] dhcp4 (enp0s20f0u1): activation: beginning transaction (timeout in 45 seconds)
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.6279] dhcp4 (enp0s20f0u1): state changed no lease
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.6426] device (enp0s20f0u1): Activation: starting connection 'cat4' (4cd09bc1-44a5-45a5-9b3a-064982f823dd)
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.6441] device (enp0s20f0u1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.6461] manager: NetworkManager state is now CONNECTING
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.6462] device (enp0s20f0u1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.6899] device (enp0s20f0u1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.6920] dhcp4 (enp0s20f0u1): activation: beginning transaction (timeout in 45 seconds)
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.7020] dhcp4 (enp0s20f0u1): state changed new lease, address=192.168.8.117, acd pending
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.8384] dhcp4 (enp0s20f0u1): state changed new lease, address=192.168.8.117
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.8387] policy: set 'cat4' (enp0s20f0u1) as default for IPv4 routing and DNS
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.8599] device (enp0s20f0u1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.8635] device (enp0s20f0u1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.8636] device (enp0s20f0u1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.8647] manager: NetworkManager state is now CONNECTED_SITE
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.8648] device (enp0s20f0u1): Activation: successful, device activated.
Mar 18 19:42:43 Teucidide NetworkManager[1491]: <info>  [1742323363.8654] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 18 19:42:46 Teucidide NetworkManager[1491]: <info>  [1742323366.9809] device (enp0s20f0u1): disconnecting for new activation request.
Mar 18 19:42:46 Teucidide NetworkManager[1491]: <info>  [1742323366.9811] device (enp0s20f0u1): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'm>
Mar 18 19:42:46 Teucidide NetworkManager[1491]: <info>  [1742323366.9843] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 18 19:42:46 Teucidide NetworkManager[1491]: <info>  [1742323366.9847] audit: op="connection-activate" uuid="8c65db7d-46fe-35b3-a83a-3c8ab886c056" name="one_touch" pid=15093 uid=>
Mar 18 19:42:46 Teucidide NetworkManager[1491]: <info>  [1742323366.9963] device (enp0s20f0u1): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state:>
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.0065] dhcp4 (enp0s20f0u1): canceled DHCP transaction
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.0066] dhcp4 (enp0s20f0u1): activation: beginning transaction (timeout in 45 seconds)
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.0066] dhcp4 (enp0s20f0u1): state changed no lease
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.0237] device (enp0s20f0u1): Activation: starting connection 'one_touch' (8c65db7d-46fe-35b3-a83a-3c8ab886c056)
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.0285] device (enp0s20f0u1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.0286] manager: NetworkManager state is now CONNECTING
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.0287] device (enp0s20f0u1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.0595] device (enp0s20f0u1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.0645] dhcp4 (enp0s20f0u1): activation: beginning transaction (timeout in 45 seconds)
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.0703] dhcp4 (enp0s20f0u1): state changed new lease, address=192.168.8.117, acd pending
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.2673] dhcp4 (enp0s20f0u1): state changed new lease, address=192.168.8.117
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.2677] policy: set 'one_touch' (enp0s20f0u1) as default for IPv4 routing and DNS
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.2900] device (enp0s20f0u1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.2962] device (enp0s20f0u1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.2965] device (enp0s20f0u1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.2969] manager: NetworkManager state is now CONNECTED_SITE
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.2972] device (enp0s20f0u1): Activation: successful, device activated.
Mar 18 19:42:47 Teucidide NetworkManager[1491]: <info>  [1742323367.2979] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.4974] device (enp0s20f0u1): disconnecting for new activation request.
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.4978] device (enp0s20f0u1): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'm>
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.5008] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.5014] audit: op="connection-activate" uuid="4cd09bc1-44a5-45a5-9b3a-064982f823dd" name="cat4" pid=15093 uid=1000 >
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.5115] device (enp0s20f0u1): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state:>
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.5217] dhcp4 (enp0s20f0u1): canceled DHCP transaction
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.5220] dhcp4 (enp0s20f0u1): activation: beginning transaction (timeout in 45 seconds)
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.5221] dhcp4 (enp0s20f0u1): state changed no lease
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.5437] device (enp0s20f0u1): Activation: starting connection 'cat4' (4cd09bc1-44a5-45a5-9b3a-064982f823dd)
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.5476] device (enp0s20f0u1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.5480] manager: NetworkManager state is now CONNECTING
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.5483] device (enp0s20f0u1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.5770] device (enp0s20f0u1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.5795] dhcp4 (enp0s20f0u1): activation: beginning transaction (timeout in 45 seconds)
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.5874] dhcp4 (enp0s20f0u1): state changed new lease, address=192.168.8.117, acd pending
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.7493] dhcp4 (enp0s20f0u1): state changed new lease, address=192.168.8.117
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.7496] policy: set 'cat4' (enp0s20f0u1) as default for IPv4 routing and DNS
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.7635] device (enp0s20f0u1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.7663] device (enp0s20f0u1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.7665] device (enp0s20f0u1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.7668] manager: NetworkManager state is now CONNECTED_SITE
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.7670] device (enp0s20f0u1): Activation: successful, device activated.
Mar 18 19:42:52 Teucidide NetworkManager[1491]: <info>  [1742323372.7674] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.5622] device (enp0s20f0u1): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'm>
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.5634] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.5638] device (enp0s20f0u1): disconnecting for new activation request.
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.5639] audit: op="connection-activate" uuid="4cd09bc1-44a5-45a5-9b3a-064982f823dd" name="cat4" pid=15093 uid=1000 >
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.5991] device (enp0s20f0u1): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state:>
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.6019] dhcp4 (enp0s20f0u1): canceled DHCP transaction
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.6020] dhcp4 (enp0s20f0u1): activation: beginning transaction (timeout in 45 seconds)
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.6020] dhcp4 (enp0s20f0u1): state changed no lease
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.6255] device (enp0s20f0u1): Activation: starting connection 'cat4' (4cd09bc1-44a5-45a5-9b3a-064982f823dd)
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.6281] device (enp0s20f0u1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.6301] manager: NetworkManager state is now CONNECTING
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.6303] device (enp0s20f0u1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.6604] device (enp0s20f0u1): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.6624] dhcp4 (enp0s20f0u1): activation: beginning transaction (timeout in 45 seconds)
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.6739] dhcp4 (enp0s20f0u1): state changed new lease, address=192.168.8.117, acd pending
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.8143] dhcp4 (enp0s20f0u1): state changed new lease, address=192.168.8.117
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.8146] policy: set 'cat4' (enp0s20f0u1) as default for IPv4 routing and DNS
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.8336] device (enp0s20f0u1): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.8373] device (enp0s20f0u1): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.8374] device (enp0s20f0u1): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.8377] manager: NetworkManager state is now CONNECTED_SITE
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.8378] device (enp0s20f0u1): Activation: successful, device activated.
Mar 18 19:48:12 Teucidide NetworkManager[1491]: <info>  [1742323692.8382] manager: NetworkManager state is now CONNECTED_GLOBAL

Bus 001 Device 026: ID 1bbb:0908 T & A Mobile Phones LinkKey
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            2 Communications
  bDeviceSubClass         0 [unknown]
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x1bbb T & A Mobile Phones
  idProduct          0x0908 LinkKey
  bcdDevice            2.42
  iManufacturer           1 Alcatel
  iProduct                2 LinkKey
  iSerial                 3 1234567890ABCDEF
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x006f
    bNumInterfaces          3
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              500mA
    Interface Association:
      bLength                 8
      bDescriptorType        11
      bFirstInterface         0
      bInterfaceCount         2
      bFunctionClass          2 Communications
      bFunctionSubClass       6 Ethernet Networking
      bFunctionProtocol       0
      iFunction               9
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass         2 Communications
      bInterfaceSubClass      6 Ethernet Networking
      bInterfaceProtocol      0
      iInterface              6
      CDC Header:
        bcdCDC               1.10
      CDC Union:
        bMasterInterface        0
        bSlaveInterface         1
      CDC Ethernet:
        iMacAddress                      7 (??)
        bmEthernetStatistics    0x00000000
        wMaxSegmentSize               1514
        wNumberMCFilters            0x0000
        bNumberPowerFilters              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval               9
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 [unknown]
      bInterfaceProtocol      0
      iInterface              0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       1
      bNumEndpoints           2
      bInterfaceClass        10 CDC Data
      bInterfaceSubClass      0 [unknown]
      bInterfaceProtocol      0
      iInterface              8
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        2
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              4
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval
> > On 18 Mar 2025, at 15:54, Patrick Dupre via users  wrote:
> >
> > After tons of tries, my old LTE works !!!
> > But the new still does not work.
>
> It has been a very long time since I last looked at this stuff so may be out of date.
>
> Look at the logs for ModemManager and NetworkManager.
>
> Modem manager typically needs to kick the dongal to exit cdrom emulation and become a modem.
>
> You should be able to see what the dongal is doing with verbose lsusb reports.
> And the logs should report the modem is detected then kicked.
>
> Barry

[Patrick Dupre]

> Am 18.03.2025 um 18:02:45 Uhr schrieb Patrick Dupre via users:
> > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> >  1  _gateway (192.168.8.1)  2.223 ms !N  2.197 ms !N *
>
> Is the cellular connection established in this situation?
>
> Can you check that in modemmanager-gui?
>
> What does dmesg show?

it seems OK.

I cannot connect to 192.168.1.1
ping 192.168.1.1 does not respond
This is the issue
> -- 
> Gruß
> Marco
> Send unsolicited bulk mail to [e-mail]
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Joe Zeff]

On 03/18/2025 01:03 PM, Patrick Dupre via users wrote:
> I cannot connect to 192.168.1.1
> ping 192.168.1.1 does not respond
> This is the issue

Try using traceroute instead.  If it responds with "no route to host" 
you know what your basic difficulty is right there.

[Marco Moock]

Am 18.03.2025 um 20:00:26 Uhr schrieb Patrick Dupre via users:
> Mar 18 19:42:46 Teucidide NetworkManager[1491]: <info>
> [1742323366.9843] manager: NetworkManager state is now CONNECTED_LOCAL
> Mar 18 19:42:46 Teucidide NetworkManager[1491]: <info>  [1742323366.9847] audit: op="connection-activate" uuid="8c65db7d-46fe-35b3-a83a-3c8ab886c056" name="one_touch" pid=15093 uid=>
> Mar 18 19:42:46 Teucidide NetworkManager[1491]: <info>  [1742323366.9963] device (enp0s20f0u1): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state:>

As you can see, the device reconnects all the time. This is the problem. Check ModemManager logs (maybe you need to increase the log-level).

[Patrick Dupre]

Hello,

I made progresses.

I need to login on  192.168.8.1
(the manual says 192.168.1.1  !!)

But, it seems that the DNS does not work
ping 192.168.8.1  does not answer
while I can connect through the interface http

nmcli connection
NAME       UUID                                  TYPE      DEVICE
cat4       4cd09bc1-44a5-45a5-9b3a-064982f823dd  ethernet  enp0s20f0u1
lo         a69d8d72-fad8-4d7c-9f05-db1ab3caf30a  loopback  lo
virbr0     427a44af-5065-4bf7-a178-c89f2c5bef6a  bridge    virbr0

etstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
default         _gateway        0.0.0.0         UG        0 0          0 enp0s20f0u1
192.168.8.0     0.0.0.0         255.255.255.0   U         0 0          0 enp0s20f0u1
192.168.122.0   0.0.0.0         255.255.255.0   U         0 0          0 virbr0

ifconfig
enp0s20f0u1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.8.107  netmask 255.255.255.0  broadcast 192.168.8.255
        inet6 fe80::5084:29d9:8c26:85c1  prefixlen 64  scopeid 0x20<link>
        inet6 2a04:cec0:10c5:91e9:36df:29dc:2c6a:c815  prefixlen 64  scopeid 0x0<global>
        ether 0e:ad:db:59:13:4f  txqueuelen 1000  (Ethernet)
        RX packets 29643  bytes 14813261 (14.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 33734  bytes 4605751 (4.3 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

resolvectl
Link 16 (enp0s20f0u1)
    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::d0da:44ff:fed6:7916

NetworkManager
Automatic DHCP
Default Route 192.168.8.1
DNS4 192.168.8.1

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
===========================================================================

[Marco Moock]

Am 18.03.2025 um 21:01:11 Uhr schrieb Patrick Dupre via users:
> I need to login on  192.168.8.1
> (the manual says 192.168.1.1  !!)
>
> But, it seems that the DNS does not work
> ping 192.168.8.1  does not answer
> while I can connect through the interface http

Some devices don't reply to ICMP. Rather bad, but a lot of crap exists
in the world. :-)
> ifconfig
> enp0s20f0u1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>         inet 192.168.8.107  netmask 255.255.255.0  broadcast
> 192.168.8.255 inet6 fe80::5084:29d9:8c26:85c1  prefixlen 64  scopeid
> 0x20<link> inet6 2a04:cec0:10c5:91e9:36df:29dc:2c6a:c815  prefixlen
> 64  scopeid 0x0<global> ether 0e:ad:db:59:13:4f  txqueuelen 1000
> (Ethernet) RX packets 29643  bytes 14813261 (14.1 MiB)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 33734  bytes 4605751 (4.3 MiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Looks good.
Test connectivity 
ping 2a00:1450:4001:809::2003 #Google
172.217.18.99

[Joe Zeff]

On 03/18/2025 02:01 PM, Patrick Dupre via users wrote:
> But, it seems that the DNS does not work
> ping 192.168.8.1  does not answer

If you're pinging by IP address, DNS isn't involved.

[Patrick Dupre]

> On 03/18/2025 02:01 PM, Patrick Dupre via users wrote:
> > But, it seems that the DNS does not work
> > ping 192.168.8.1  does not answer
>
> If you're pinging by IP address, DNS isn't involved.

Sure,
But something is wrong in the network config.
why I cannot ping 192.168.8.1 ?
while I can http://192.168.8.1

Is it in /etc/hosts ?
I have
192.168.1.155 Teucidide.localdomain Teucidide

Should I change for
192.168.8.155 Teucidide.localdomain Teucidide

[Marco Moock]

Am 18.03.2025 um 21:21:52 Uhr schrieb Patrick Dupre via users:
> why I cannot ping 192.168.8.1 ?
> while I can http://192.168.8.1

Because the dongle doesn't respond to ICMP, even when required by the
RfCs. Don't stick on that, even when it is nasty.
> Is it in /etc/hosts ?
> I have
> 192.168.1.155 Teucidide.localdomain Teucidide
>
> Should I change for
> 192.168.8.155 Teucidide.localdomain Teucidide

Change the IP to ::1/127.0.0.1

[Patrick Dupre]

> To: [e-mail]
> Subject: Re: Dongle USB
>
> Am 18.03.2025 um 21:21:52 Uhr schrieb Patrick Dupre via users:
> > why I cannot ping 192.168.8.1 ?
> > while I can http://192.168.8.1
>
> Because the dongle doesn't respond to ICMP, even when required by the
> RfCs. Don't stick on that, even when it is nasty.
> > Is it in /etc/hosts ?
> > I have
> > 192.168.1.155 Teucidide.localdomain Teucidide
> >
> > Should I change for
> > 192.168.8.155 Teucidide.localdomain Teucidide
>
> Change the IP to ::1/127.0.0.1

I already have

127.0.0.1   localhost localhost.localdomain
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> -- 
> Gruß
> Marco
> Send unsolicited bulk mail to [e-mail]
>

[Marco Moock]

Am 18.03.2025 um 21:35:50 Uhr schrieb Patrick Dupre via users:
> 127.0.0.1   localhost localhost.localdomain
> ::1         localhost localhost.localdomain localhost6
> localhost6.localdomain6

Add the hostname of your system to that list and remove the entries
with the 192.168 IPs.

[Patrick Dupre]

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
 Laboratoire interdisciplinaire Carnot de Bourgogne
 9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
===========================================================================
> Sent: Tuesday, March 18, 2025 at 9:38 PM
> From: "Marco Moock" 
> To: [e-mail]
> Subject: Re: Dongle USB
>
> Am 18.03.2025 um 21:35:50 Uhr schrieb Patrick Dupre via users:
> > 127.0.0.1   localhost localhost.localdomain
> > ::1         localhost localhost.localdomain localhost6
> > localhost6.localdomain6
>
> Add the hostname of your system to that list and remove the entries
> with the 192.168 IPs.

127.0.0.1   localhost localhost.localdomain
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6 Teucidide teucidide

It does not help the DNS

ping 172.217.18.99 works

I tried the DNS 192.168.1.1 which works with the other dongle, but not with the new one.

[Marco Moock]

Am 18.03.2025 um 22:37:49 Uhr schrieb Patrick Dupre via users:
> ping 172.217.18.99 works

Good, that means IPv4 internet works. Now test 2a00:1450:4001:830::2003
> I tried the DNS 192.168.1.1 which works with the other dongle, but
> not with the new one.

Show ip r s
ip -6 r s
resolvectl

[Tim]

On Tue, 2025-03-18 at 22:37 +0100, Patrick Dupre via users wrote:
> 127.0.0.1   localhost localhost.localdomain
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6 Teucidide teucidide

Adding your own hostname to the loopback address *can* be a problem.

You may not realise networking isn't working, because you're connecting
to yourself internally instead of the interface to the outside world.

Internal things that want the IP of your hostname now get told the
127.0.0.1 IP instead of the IP of your interface to the outside world.

[Tim]

On Tue, 2025-03-18 at 21:01 +0100, Patrick Dupre via users wrote:
> I need to login on  192.168.8.1
> (the manual says 192.168.1.1  !!)
>
> But, it seems that the DNS does not work
> ping 192.168.8.1  does not answer
> while I can connect through the interface http

If the device has changed IPs to what you want of 192.168.8.1 instead
of its original 192.168.1.1, then you should be able to access it from
a PC at 192.168.8.107 if they are directly on the same network.

If you have some *other* network in between, as per your threads last
month, you may strike problems.

If the device is sitting on its original 192.168.1.1 IP and you need to
get into it to change it to the IP you want (192.168.8.1), then change
your PCs IP to one in the same range (e.g. 192.168.1.107), log into the
device, reconfigure it, restart it, then change your PC's IP back to
your desired address.

As others say, some devices don't respond to pings (which can lead to
them being excluded from networks, if other things do ping checks then
cut off unresponsive devices).  Or, you could have a
firewalling/networking issue getting in the way.

[Patrick Dupre]

> Am 18.03.2025 um 22:37:49 Uhr schrieb Patrick Dupre via users:
> > ping 172.217.18.99 works
>
> Good, that means IPv4 internet works. Now test 2a00:1450:4001:830::2003
> > I tried the DNS 192.168.1.1 which works with the other dongle, but
> > not with the new one.
>
> Show ip r s

default via 192.168.8.1 dev enp0s20f0u11 proto dhcp src 192.168.8.162 metric 100
192.168.8.0/24 dev enp0s20f0u11 proto kernel scope link src 192.168.8.162 metric 100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown
> ip -6 r s

2a04:cec0:11ff:e254::/64 dev enp0s20f0u11 proto ra metric 100 pref medium
fe80::/64 dev enp0s20f0u11 proto kernel metric 1024 pref medium
default proto ra metric 100 pref medium
        nexthop via fe80::84d1:a9ff:fee7:c482 dev enp0s20f0u11 weight 1
        nexthop via fe80::dbb:1d65:7605:bbdb dev enp0s20f0u11 weight 1
> resolvectl

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::84d1:a9ff:fee7:c482

In my opinion, still I cannot ping 192.168.8.1
It will not works

Could be a firewall issue with 192.168.8  ?
I do not touch the any thing when a switch from one dongle to the other one.
> -- 
> Gruß
> Marco
> Send unsolicited bulk mail to [e-mail]
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Patrick Dupre]

> On Tue, 2025-03-18 at 21:01 +0100, Patrick Dupre via users wrote:
> > I need to login on  192.168.8.1
> > (the manual says 192.168.1.1  !!)
> >
> > But, it seems that the DNS does not work
> > ping 192.168.8.1  does not answer
> > while I can connect through the interface http
>
> If the device has changed IPs to what you want of 192.168.8.1 instead
> of its original 192.168.1.1, then you should be able to access it from
> a PC at 192.168.8.107 if they are directly on the same network.
>
> If you have some *other* network in between, as per your threads last
> month, you may strike problems.
>
> If the device is sitting on its original 192.168.1.1 IP and you need to
> get into it to change it to the IP you want (192.168.8.1), then change
> your PCs IP to one in the same range (e.g. 192.168.1.107), log into the
> device, reconfigure it, restart it, then change your PC's IP back to
> your desired address.
>
> As others say, some devices don't respond to pings (which can lead to
> them being excluded from networks, if other things do ping checks then
> cut off unresponsive devices).  Or, you could have a
> firewalling/networking issue getting in the way.

PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.096 ms

ping 2a00:1450:4001:830::2003
PING 2a00:1450:4001:830::2003 (2a00:1450:4001:830::2003) 56 data bytes
From fe80::84d1:a9ff:fee7:c482%enp0s20f0u11 icmp_seq=1 Destination unreachable: No route
From fe80::84d1:a9ff:fee7:c482%enp0s20f0u11 icmp_seq=2 Destination unreachable: No route

ifconfig
enp0s20f0u11: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.8.162  netmask 255.255.255.0  broadcast 192.168.8.255
        inet6 fe80::f40e:975b:b76a:70cd  prefixlen 64  scopeid 0x20<link>
        inet6 2a04:cec0:11ff:e254:98b5:f8f:365c:7b91  prefixlen 64  scopeid 0x0<global>
        ether 3a:92:cb:cc:a1:5c  txqueuelen 1000  (Ethernet)
        RX packets 4552  bytes 2671758 (2.5 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5267  bytes 633902 (619.0 KiB)
        TX errors 0  dropped 4 overruns 0  carrier 0  collisions 0
> uname -rsvp
> Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
>
> Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
> I will only get to see the messages that are posted to the mailing list.

[Marco Moock]

Am 19.03.2025 um 10:17:09 Uhr schrieb Patrick Dupre via users:
> > Am 18.03.2025 um 22:37:49 Uhr schrieb Patrick Dupre via users:
> > > ping 172.217.18.99 works
> >
> > Good, that means IPv4 internet works. Now test
> > 2a00:1450:4001:830::2003
> > > I tried the DNS 192.168.1.1 which works with the other dongle, but
> > > not with the new one.
> >
> > Show ip r s
>
> default via 192.168.8.1 dev enp0s20f0u11 proto dhcp src 192.168.8.162
> metric 100 192.168.8.0/24 dev enp0s20f0u11 proto kernel scope link
> src 192.168.8.162 metric 100 192.168.122.0/24 dev virbr0 proto kernel
> scope link src 192.168.122.1 linkdown
> > ip -6 r s
>
> 2a04:cec0:11ff:e254::/64 dev enp0s20f0u11 proto ra metric 100 pref
> medium fe80::/64 dev enp0s20f0u11 proto kernel metric 1024 pref medium
> default proto ra metric 100 pref medium
>         nexthop via fe80::84d1:a9ff:fee7:c482 dev enp0s20f0u11 weight
> 1 nexthop via fe80::dbb:1d65:7605:bbdb dev enp0s20f0u11 weight 1

Looks good.
Now test if IPv6 connectivity works:

ping 2a01:170:118f:1::1
> > resolvectl
> 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::84d1:a9ff:fee7:c482

Looks good. Test DNS:

dig google.com @192.168.8.1
dig google.com @fe80::84d1:a9ff:fee7:c482
> In my opinion, still I cannot ping 192.168.8.1
> It will not works

I assume the server (included in your dongle) will not respond to ICMP.
In my opinion, this is not an issue.

[Marco Moock]

Am 19.03.2025 um 10:19:32 Uhr schrieb Patrick Dupre via users:
> From fe80::84d1:a9ff:fee7:c482%enp0s20f0u11 icmp_seq=1 Destination
> unreachable: No route From fe80::84d1:a9ff:fee7:c482%enp0s20f0u11
> icmp_seq=2 Destination unreachable: No route

Which device is that?

Please reboot your system and only connect one dongle to it.

[Marco Moock]

Am 19.03.2025 um 17:27:33 Uhr schrieb Tim via users:
> If the device is sitting on its original 192.168.1.1 IP and you need
> to get into it to change it to the IP you want (192.168.8.1), then
> change your PCs IP to one in the same range (e.g. 192.168.1.107), log
> into the device, reconfigure it, restart it, then change your PC's IP
> back to your desired address.

I don't see any reason to change that in this case. The "server" can be
reached by http, should be enough from the networking side. :-)

[Patrick Dupre]

Thank Marco,
> Am 19.03.2025 um 10:19:32 Uhr schrieb Patrick Dupre via users:
> > From fe80::84d1:a9ff:fee7:c482%enp0s20f0u11 icmp_seq=1 Destination
> > unreachable: No route From fe80::84d1:a9ff:fee7:c482%enp0s20f0u11
> > icmp_seq=2 Destination unreachable: No route
>
> Which device is that?
>
> Please reboot your system and only connect one dongle to it.

I did.
But no real progress.
Actually,
Things works correctly fine during ~ 1 mn.
And then stop.

This (temporally) behavior can also appear, if I switch from the
working to the nonworking dongle.

This is mysterious.

Another point
 dig google.com @fe80::84d1:a9ff:fee7:c482
gives the same with the working and with the nonworking dongle

[Marco Moock]

Am 19.03.2025 um 11:29:01 Uhr schrieb Patrick Dupre via users:
> Another point
>  dig google.com @fe80::84d1:a9ff:fee7:c482
> gives the same with the working and with the nonworking dongle

What is the output?

[Patrick Dupre]

> > Another point
> >  dig google.com @fe80::84d1:a9ff:fee7:c482
> > gives the same with the working and with the nonworking dongle
>
> What is the output?

;; UDP setup with fe80::84d1:a9ff:fee7:c482#53(fe80::84d1:a9ff:fee7:c482) for google.com failed: invalid file.
;; no servers could be reached

;; UDP setup with fe80::84d1:a9ff:fee7:c482#53(fe80::84d1:a9ff:fee7:c482) for google.com failed: invalid file.
;; no servers could be reached

;; UDP setup with fe80::84d1:a9ff:fee7:c482#53(fe80::84d1:a9ff:fee7:c482) for google.com failed: invalid file.
;; no servers could be reached
> Gruß
> Marco
> Send unsolicited bulk mail to [e-mail]
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Marco Moock]

Am 19.03.2025 um 11:59:03 Uhr schrieb Patrick Dupre via users:
> ;; UDP setup with
> fe80::84d1:a9ff:fee7:c482#53(fe80::84d1:a9ff:fee7:c482) for
> google.com failed: invalid file. ;; no servers could be reached

Try
dig google.de @fe80::84d1:a9ff:fee7:c482%enp0s20f0u11

[Patrick Dupre]

> Am 19.03.2025 um 11:59:03 Uhr schrieb Patrick Dupre via users:
> > ;; UDP setup with
> > fe80::84d1:a9ff:fee7:c482#53(fe80::84d1:a9ff:fee7:c482) for
> > google.com failed: invalid file. ;; no servers could be reached
>
> Try
> dig google.de @fe80::84d1:a9ff:fee7:c482%enp0s20f0u11

dig google.de @fe80::84d1:a9ff:fee7:c482%enp0s20f0u11
;; communications error to fe80::84d1:a9ff:fee7:c482%6#53: timed out
;; communications error to fe80::84d1:a9ff:fee7:c482%6#53: timed out
;; communications error to fe80::84d1:a9ff:fee7:c482%6#53: timed out

; <<>> DiG 9.18.28 <<>> google.de @fe80::84d1:a9ff:fee7:c482%enp0s20f0u11
;; global options: +cmd
;; no servers could be reached

With the dongle running properly

Should I try with the other one ?

[Patrick Dupre]

With the "nonworking" dongle,
During the first "working" mn or after, I get th" same answer

dig google.de @fe80::84d1:a9ff:fee7:c482%enp0s20f0u11
;; communications error to fe80::84d1:a9ff:fee7:c482%7#53: timed out
;; communications error to fe80::84d1:a9ff:fee7:c482%7#53: timed out
;; communications error to fe80::84d1:a9ff:fee7:c482%7#53: timed out

; <<>> DiG 9.18.28 <<>> google.de @fe80::84d1:a9ff:fee7:c482%enp0s20f0u11
;; global options: +cmd
;; no servers could be reached
> Am 19.03.2025 um 11:59:03 Uhr schrieb Patrick Dupre via users:
> > ;; UDP setup with
> > fe80::84d1:a9ff:fee7:c482#53(fe80::84d1:a9ff:fee7:c482) for
> > google.com failed: invalid file. ;; no servers could be reached
>
> Try
> dig google.de @fe80::84d1:a9ff:fee7:c482%enp0s20f0u11
>
> -- 
> Gruß
> Marco
> Send unsolicited bulk mail to [e-mail]
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Marco Moock]

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

[Patrick Dupre]

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 [e-mail]
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Tim]

Tim:
> > If the device is sitting on its original 192.168.1.1 IP and you need
> > to get into it to change it to the IP you want (192.168.8.1), then
> > change your PCs IP to one in the same range (e.g. 192.168.1.107), log
> > into the device, reconfigure it, restart it, then change your PC's IP
> > back to your desired address.

Marco Moock:
> I don't see any reason to change that in this case. The "server" can be
> reached by http, should be enough from the networking side. :-)

It will depend on the networking configuration (or netmasking, in this
case) on both sides.

Sometimes a device on something like 192.168.1.1 *can* talk to
something on 192.168.8.1 directly, sometimes traffic will be blocked.

If the netmasking is 255.255.0.0 on both sides, I'd expect it to work. 
If either side has 255.255.255.0 it may not.  Some devices are strict
about rules, some try to be helpful.  I remember a friend's
modem/router being the very opposite of a firewall, it automatically
tried to route any and all traffic through it.

I've had this palaver before when I've had to connect hardware devices
to a network.  We had some devices that just had to be on 192.168.1,
because the manufacturer was pig-headed.  It forced a renumbering of
the entire LAN.  Then I changed modem/routers and it came preconfigured
for 192.168.0, fortunately it could be changed.  I'm glad I didn't have
other hardware devices that could only work on 192.168.0 at the same
time.

I am seeing a similar thing now, here.  I'm using a mobile phone to
access the internet for my LAN, it insists on a 192.168.42 network (and
I wouldn't be surprised if it only allows throughput from devices it's
assigned IPs to, itself - interlinking DHCP with access control).  It's
certainly a pain in only allowing 10 devices to go through it.  To use
that addressing would mean renumbering my whole LAN, and then making my
LAN unusable when the phone is disconnected.  Or putting a PC in the
middle to manage things.

[Patrick Dupre]

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

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
===========================================================================

[Marco Moock]

Am 19.03.2025 um 15:14:22 Uhr schrieb Patrick Dupre via users:
> When the "bad" dongle works "~1 minute"

This is already a big issue and won't be related to DNS. Does the web
interface show any logs?

Please do a long-time ping test to a destination that works.

[Mike Wright]

On 3/19/25 10:05, Tim via users wrote:

<big-snip/>
> Or putting a PC in the middle to manage things.

In that case you might be able to use NAT instead.

:m

[Patrick Dupre]

I am sorry, but I do not understand.

There is only one PC with a dongle.
The question to get the contraol on the DNS server.
Why when I just start the PC, I have

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

and 1 minute later
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

which does not let me having a connection to the rest of the world while it was OK just before?
It seems to be due to IPV6.

Do I need to switch IPV6 from automatic to
Disable or Automatic DHCP, manual ?
or set the IPV6 DNS

Note that with the working dongle, I have
    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
> On 3/19/25 10:05, Tim via users wrote:
>
> <big-snip/>
> > Or putting a PC in the middle to manage things.
>
> In that case you might be able to use NAT instead.
> :m
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Tim]

On Wed, 2025-03-19 at 23:24 +0100, Patrick Dupre via users wrote:
> There is only one PC with a dongle.
> The question to get the contraol on the DNS server.
> Why when I just start the PC, I have
>
> 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
>
> and 1 minute later
> 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

If you have more than one DNS server (and as far as it's concerned two
different addresses for the same server are two servers), standard
behaviour *was* always to try the first one, then only try the second
one if the first one didn't respond (if it responds, but doesn't have
the answer it has still responded, and the second server is not
consulted).  Every time there's a DNS query, it'll poll the first
server, first.

Other systems (and I don't know if Fedora does this now) may switch
over to the second server if the first one didn't respond, and continue
to use it as first choice.  Only switching back if the *now* first
server doesn't respond.
> which does not let me having a connection to the rest of the world while it was OK just before?
> It seems to be due to IPV6.
>
> Do I need to switch IPV6 from automatic to
> Disable or Automatic DHCP, manual ?
> or set the IPV6 DNS
>
> Note that with the working dongle, I have
>     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

If you want to force a specific server, then set your DHCP client
options to use the DNS server you specify and not get it from DHCP.

The "automatic DHCP addresses only" choice will only get your IP
address from the DHCP server, you will set your DNS server and it won't
change it.

You could be having IPv6 issues that may need you to disable it, or
configure it in a specific way.  I could hazard a guess that your IPv4
connection should have an IPv4 address for a DNS server and your IPv6
connection should have an IPv6 address for its DNS server.  It may be a
simple way that ensures least confusion and your IPv4 queries get IPv4
answers, your IPv6 queries only get IPv6 answers.

I really can't test IPv6 here, the ISPs support for it is erratic.

[Marco Moock]

Am Wed, 19 Mar 2025 23:24:31 +0100
schrieb Patrick Dupre via users :
> Do I need to switch IPV6 from automatic to
> Disable or Automatic DHCP, manual ?
> or set the IPV6 DNS

No, but it needs to be investigated what it doesn't work. You get
addresses assigned.

Please test
traceroute -I 2a01:170:118f:1::1
traceroute -I 8.8.8.8

This doesn't involve DNS at all, so first check the IP connectivity.

[Patrick Dupre]

Thank Marco for your concerns.

With the new LTE dongle not working properly, but when it works

traceroute -I 2a01:170:118f:1::1
traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max, 80 byte packets
 1  ik41.home (2a04:cec0:104d:c3d0:b163:755:4f7b:7d44)  1.140 ms  1.237 ms *
 2  2a04:cec0:104d:c3d0:0:57:ca48:7740 (2a04:cec0:104d:c3d0:0:57:ca48:7740)  33.437 ms  42.443 ms *
 3  * * *
 4  2001:860:b205:5100::1c:1 (2001:860:b205:5100::1c:1)  42.989 ms  43.048 ms  43.075 ms
 5  2001:860:b205:5100::15:2 (2001:860:b205:5100::15:2)  42.722 ms  42.758 ms  42.770 ms
 6  2001:860:b205:5100::11:4 (2001:860:b205:5100::11:4)  43.113 ms * *
 7  2001:860:bbe0:f6::1 (2001:860:bbe0:f6::1)  32.788 ms * *
 8  2001:860:bbee:d9::1 (2001:860:bbee:d9::1)  35.728 ms * *
 9  * * *
10  * * *
11  2003:0:130e:9::2274:1 (2003:0:130e:9::2274:1)  47.779 ms  51.888 ms  47.805 ms
12  2a01:170:118f:1::1 (2a01:170:118f:1::1)  56.947 ms  55.344 ms  55.370 ms

Same dongle after ~ 1 minute
traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max, 80 byte packets
 1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)  2.088 ms !N  2.527 ms !N  2.823 ms !N

With the working LTE
connect: Network is unreachable

traceroute -I 8.8.8.8
Same answer before and after wit hthe new LTE
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

With the the working LTE
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  0.957 ms  1.164 ms  1.363 ms
 2  10.125.68.5 (10.125.68.5)  98.259 ms  106.266 ms  106.334 ms
 3  172.20.24.122 (172.20.24.122)  114.882 ms  114.958 ms  115.144 ms
 4  172.20.24.98 (172.20.24.98)  115.199 ms  115.352 ms  115.603 ms
 5  * * *
 6  212.194.171.69 (212.194.171.69)  115.486 ms * *
 7  * * *
 8  142.250.175.198 (142.250.175.198)  23.918 ms * *
 9  * * *
10  * 142.251.49.131 (142.251.49.131)  27.228 ms  25.073 ms
11  dns.google (8.8.8.8)  23.883 ms  24.983 ms  25.018 ms

When the new LTE dongle, when it is working
I have
default route 192.168.8.1
DNS 192.168.8.1

When it does not work
default route 192.168.8.1
fe80::dcb1:beff!fe30:9ee8
DNS4 192.168.8.1
DNS6 fe80::dcb1:beff!fe30:9ee8

And with the working dongle
default route 192.168.1.1
DNS 192.168.1.1

Please not that I have a single SIM that I switch and switch back from one dongle to the other one.
> Am Wed, 19 Mar 2025 23:24:31 +0100
> schrieb Patrick Dupre via users :
> > Do I need to switch IPV6 from automatic to
> > Disable or Automatic DHCP, manual ?
> > or set the IPV6 DNS
>
> No, but it needs to be investigated what it doesn't work. You get
> addresses assigned.
>
> Please test
> traceroute -I 2a01:170:118f:1::1
> traceroute -I 8.8.8.8
> This doesn't involve DNS at all, so first check the IP connectivity.
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Sent using the mobile mail app

On 3/20/25 at 4:41 AM, Patrick Dupre via users wrote:
> Thank Marco for your concerns.
>
> With the new LTE dongle not working properly, but when it works
>
> traceroute -I 2a01:170:118f:1::1
> traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max, 80 byte packets
>  1  ik41.home (2a04:cec0:104d:c3d0:b163:755:4f7b:7d44)  1.140 ms  1.237 ms *
>  2  2a04:cec0:104d:c3d0:0:57:ca48:7740 (2a04:cec0:104d:c3d0:0:57:ca48:7740)  33.437 ms  42.443 ms *
>  3  * * *
>  4  2001:860:b205:5100::1c:1 (2001:860:b205:5100::1c:1)  42.989 ms  43.048 ms  43.075 ms
>  5  2001:860:b205:5100::15:2 (2001:860:b205:5100::15:2)  42.722 ms  42.758 ms  42.770 ms
>  6  2001:860:b205:5100::11:4 (2001:860:b205:5100::11:4)  43.113 ms * *
>  7  2001:860:bbe0:f6::1 (2001:860:bbe0:f6::1)  32.788 ms * *
>  8  2001:860:bbee:d9::1 (2001:860:bbee:d9::1)  35.728 ms * *
>  9  * * *
> 10  * * *
> 11  2003:0:130e:9::2274:1 (2003:0:130e:9::2274:1)  47.779 ms  51.888 ms  47.805 ms
> 12  2a01:170:118f:1::1 (2a01:170:118f:1::1)  56.947 ms  55.344 ms  55.370 ms
>
> Same dongle after ~ 1 minute
> traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max, 80 byte packets
>  1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)  2.088 ms !N  2.527 ms !N  2.823 ms !N
>
> With the working LTE
> connect: Network is unreachable
>
> traceroute -I 8.8.8.8
> Same answer before and after wit hthe new LTE
> traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
>  1  * * *
>  2  * * *
>  3  * * *
>  4  * * *
>  5  * * *
>  6  * * *
>  7  * * *
>  8  * * *
>  9  * * *
> 10  * * *
> 11  * * *
> 12  * * *
> 13  * * *
> 14  * * *
> 15  * * *
> 16  * * *
> 17  * * *
> 18  * * *
> 19  * * *
> 20  * * *
> 21  * * *
> 22  * * *
> 23  * * *
> 24  * * *
> 25  * * *
> 26  * * *
> 27  * * *
> 28  * * *
> 29  * * *
> 30  * * *
>
> With the the working LTE
> traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
>  1  _gateway (192.168.1.1)  0.957 ms  1.164 ms  1.363 ms
>  2  10.125.68.5 (10.125.68.5)  98.259 ms  106.266 ms  106.334 ms
>  3  172.20.24.122 (172.20.24.122)  114.882 ms  114.958 ms  115.144 ms
>  4  172.20.24.98 (172.20.24.98)  115.199 ms  115.352 ms  115.603 ms
>  5  * * *
>  6  212.194.171.69 (212.194.171.69)  115.486 ms * *
>  7  * * *
>  8  142.250.175.198 (142.250.175.198)  23.918 ms * *
>  9  * * *
> 10  * 142.251.49.131 (142.251.49.131)  27.228 ms  25.073 ms
> 11  dns.google (8.8.8.8)  23.883 ms  24.983 ms  25.018 ms
>
> When the new LTE dongle, when it is working
> I have
> default route 192.168.8.1
> DNS 192.168.8.1
>
> When it does not work
> default route 192.168.8.1
> fe80::dcb1:beff!fe30:9ee8
> DNS4 192.168.8.1
> DNS6 fe80::dcb1:beff!fe30:9ee8
>
> And with the working dongle
> default route 192.168.1.1
> DNS 192.168.1.1
>
> Please not that I have a single SIM that I switch and switch back from one dongle to the other one.
> > Am Wed, 19 Mar 2025 23:24:31 +0100
> > schrieb Patrick Dupre via users :
> > > Do I need to switch IPV6 from automatic to
> > > Disable or Automatic DHCP, manual ?
> > > or set the IPV6 DNS
> >
> > No, but it needs to be investigated what it doesn't work. You get
> > addresses assigned.
> >
> > Please test
> > traceroute -I 2a01:170:118f:1::1
> > traceroute -I 8.8.8.8
> > This doesn't involve DNS at all, so first check the IP connectivity.
> >
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Is that a 4G  network dongle ?   I  imagine issues may be related to driver. Some hardware are designed with windows in mind . K

[Patrick Dupre]

> Sent using the mobile mail app
>
> On 3/20/25 at 4:41 AM, Patrick Dupre via users wrote:
> > Thank Marco for your concerns.
> >
> > With the new LTE dongle not working properly, but when it works
> >
> > traceroute -I 2a01:170:118f:1::1
> > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max, 80 byte packets
> >  1  ik41.home (2a04:cec0:104d:c3d0:b163:755:4f7b:7d44)  1.140 ms  1.237 ms *
> >  2  2a04:cec0:104d:c3d0:0:57:ca48:7740 (2a04:cec0:104d:c3d0:0:57:ca48:7740)  33.437 ms  42.443 ms *
> >  3  * * *
> >  4  2001:860:b205:5100::1c:1 (2001:860:b205:5100::1c:1)  42.989 ms  43.048 ms  43.075 ms
> >  5  2001:860:b205:5100::15:2 (2001:860:b205:5100::15:2)  42.722 ms  42.758 ms  42.770 ms
> >  6  2001:860:b205:5100::11:4 (2001:860:b205:5100::11:4)  43.113 ms * *
> >  7  2001:860:bbe0:f6::1 (2001:860:bbe0:f6::1)  32.788 ms * *
> >  8  2001:860:bbee:d9::1 (2001:860:bbee:d9::1)  35.728 ms * *
> >  9  * * *
> > 10  * * *
> > 11  2003:0:130e:9::2274:1 (2003:0:130e:9::2274:1)  47.779 ms  51.888 ms  47.805 ms
> > 12  2a01:170:118f:1::1 (2a01:170:118f:1::1)  56.947 ms  55.344 ms  55.370 ms
> >
> > Same dongle after ~ 1 minute
> > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max, 80 byte packets
> >  1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)  2.088 ms !N  2.527 ms !N  2.823 ms !N
> >
> > With the working LTE
> > connect: Network is unreachable
> >
> > traceroute -I 8.8.8.8
> > Same answer before and after wit hthe new LTE
> > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> >  1  * * *
> >  2  * * *
> >  3  * * *
> >  4  * * *
> >  5  * * *
> >  6  * * *
> >  7  * * *
> >  8  * * *
> >  9  * * *
> > 10  * * *
> > 11  * * *
> > 12  * * *
> > 13  * * *
> > 14  * * *
> > 15  * * *
> > 16  * * *
> > 17  * * *
> > 18  * * *
> > 19  * * *
> > 20  * * *
> > 21  * * *
> > 22  * * *
> > 23  * * *
> > 24  * * *
> > 25  * * *
> > 26  * * *
> > 27  * * *
> > 28  * * *
> > 29  * * *
> > 30  * * *
> >
> > With the the working LTE
> > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> >  1  _gateway (192.168.1.1)  0.957 ms  1.164 ms  1.363 ms
> >  2  10.125.68.5 (10.125.68.5)  98.259 ms  106.266 ms  106.334 ms
> >  3  172.20.24.122 (172.20.24.122)  114.882 ms  114.958 ms  115.144 ms
> >  4  172.20.24.98 (172.20.24.98)  115.199 ms  115.352 ms  115.603 ms
> >  5  * * *
> >  6  212.194.171.69 (212.194.171.69)  115.486 ms * *
> >  7  * * *
> >  8  142.250.175.198 (142.250.175.198)  23.918 ms * *
> >  9  * * *
> > 10  * 142.251.49.131 (142.251.49.131)  27.228 ms  25.073 ms
> > 11  dns.google (8.8.8.8)  23.883 ms  24.983 ms  25.018 ms
> >
> > When the new LTE dongle, when it is working
> > I have
> > default route 192.168.8.1
> > DNS 192.168.8.1
> >
> > When it does not work
> > default route 192.168.8.1
> > fe80::dcb1:beff!fe30:9ee8
> > DNS4 192.168.8.1
> > DNS6 fe80::dcb1:beff!fe30:9ee8
> >
> > And with the working dongle
> > default route 192.168.1.1
> > DNS 192.168.1.1
> >
> > Please not that I have a single SIM that I switch and switch back from one dongle to the other one.
> > > Am Wed, 19 Mar 2025 23:24:31 +0100
> > > schrieb Patrick Dupre via users :
> > > > Do I need to switch IPV6 from automatic to
> > > > Disable or Automatic DHCP, manual ?
> > > > or set the IPV6 DNS
> > >
> > > No, but it needs to be investigated what it doesn't work. You get
> > > addresses assigned.
> > >
> > > Please test
> > > traceroute -I 2a01:170:118f:1::1
> > > traceroute -I 8.8.8.8
> > > This doesn't involve DNS at all, so first check the IP connectivity.
> > >
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> Is that a 4G  network dongle ?   I  imagine issues may be related to driver. Some hardware are designed with windows in mind . K

Yes it is 4G LTE

The Alcatel IK41 series M2M LTE Cat4 USB stick connects to the host system using USB2 data interface and will appear in the system with USB Vendor ID: 1bbb and Product ID: 00b6 in default USB mode.

The device expose a USB MBIM network interface (Mobile Broadband Interface Model) and three usb serial interfaces. It is commonly used by Windows 8/10 for connecting mobile broadband devices, but can also be used in Linux environments.

Sent using the mobile mail app

On 3/20/25 at 5:14 AM, Patrick Dupre via users wrote:
> > Sent using the mobile mail app
> >
> > On 3/20/25 at 4:41 AM, Patrick Dupre via users wrote:
> > > Thank Marco for your concerns.
> > >
> > > With the new LTE dongle not working properly, but when it works
> > >
> > > traceroute -I 2a01:170:118f:1::1
> > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max, 80 byte packets
> > >  1  ik41.home (2a04:cec0:104d:c3d0:b163:755:4f7b:7d44)  1.140 ms  1.237 ms *
> > >  2  2a04:cec0:104d:c3d0:0:57:ca48:7740 (2a04:cec0:104d:c3d0:0:57:ca48:7740)  33.437 ms  42.443 ms *
> > >  3  * * *
> > >  4  2001:860:b205:5100::1c:1 (2001:860:b205:5100::1c:1)  42.989 ms  43.048 ms  43.075 ms
> > >  5  2001:860:b205:5100::15:2 (2001:860:b205:5100::15:2)  42.722 ms  42.758 ms  42.770 ms
> > >  6  2001:860:b205:5100::11:4 (2001:860:b205:5100::11:4)  43.113 ms * *
> > >  7  2001:860:bbe0:f6::1 (2001:860:bbe0:f6::1)  32.788 ms * *
> > >  8  2001:860:bbee:d9::1 (2001:860:bbee:d9::1)  35.728 ms * *
> > >  9  * * *
> > > 10  * * *
> > > 11  2003:0:130e:9::2274:1 (2003:0:130e:9::2274:1)  47.779 ms  51.888 ms  47.805 ms
> > > 12  2a01:170:118f:1::1 (2a01:170:118f:1::1)  56.947 ms  55.344 ms  55.370 ms
> > >
> > > Same dongle after ~ 1 minute
> > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max, 80 byte packets
> > >  1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)  2.088 ms !N  2.527 ms !N  2.823 ms !N
> > >
> > > With the working LTE
> > > connect: Network is unreachable
> > >
> > > traceroute -I 8.8.8.8
> > > Same answer before and after wit hthe new LTE
> > > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> > >  1  * * *
> > >  2  * * *
> > >  3  * * *
> > >  4  * * *
> > >  5  * * *
> > >  6  * * *
> > >  7  * * *
> > >  8  * * *
> > >  9  * * *
> > > 10  * * *
> > > 11  * * *
> > > 12  * * *
> > > 13  * * *
> > > 14  * * *
> > > 15  * * *
> > > 16  * * *
> > > 17  * * *
> > > 18  * * *
> > > 19  * * *
> > > 20  * * *
> > > 21  * * *
> > > 22  * * *
> > > 23  * * *
> > > 24  * * *
> > > 25  * * *
> > > 26  * * *
> > > 27  * * *
> > > 28  * * *
> > > 29  * * *
> > > 30  * * *
> > >
> > > With the the working LTE
> > > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> > >  1  _gateway (192.168.1.1)  0.957 ms  1.164 ms  1.363 ms
> > >  2  10.125.68.5 (10.125.68.5)  98.259 ms  106.266 ms  106.334 ms
> > >  3  172.20.24.122 (172.20.24.122)  114.882 ms  114.958 ms  115.144 ms
> > >  4  172.20.24.98 (172.20.24.98)  115.199 ms  115.352 ms  115.603 ms
> > >  5  * * *
> > >  6  212.194.171.69 (212.194.171.69)  115.486 ms * *
> > >  7  * * *
> > >  8  142.250.175.198 (142.250.175.198)  23.918 ms * *
> > >  9  * * *
> > > 10  * 142.251.49.131 (142.251.49.131)  27.228 ms  25.073 ms
> > > 11  dns.google (8.8.8.8)  23.883 ms  24.983 ms  25.018 ms
> > >
> > > When the new LTE dongle, when it is working
> > > I have
> > > default route 192.168.8.1
> > > DNS 192.168.8.1
> > >
> > > When it does not work
> > > default route 192.168.8.1
> > > fe80::dcb1:beff!fe30:9ee8
> > > DNS4 192.168.8.1
> > > DNS6 fe80::dcb1:beff!fe30:9ee8
> > >
> > > And with the working dongle
> > > default route 192.168.1.1
> > > DNS 192.168.1.1
> > >
> > > Please not that I have a single SIM that I switch and switch back from one dongle to the other one.
> > > > Am Wed, 19 Mar 2025 23:24:31 +0100
> > > > schrieb Patrick Dupre via users :
> > > > > Do I need to switch IPV6 from automatic to
> > > > > Disable or Automatic DHCP, manual ?
> > > > > or set the IPV6 DNS
> > > >
> > > > No, but it needs to be investigated what it doesn't work. You get
> > > > addresses assigned.
> > > >
> > > > Please test
> > > > traceroute -I 2a01:170:118f:1::1
> > > > traceroute -I 8.8.8.8
> > > > This doesn't involve DNS at all, so first check the IP connectivity.
> > > >
> > > > users mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > 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/[e-mail]
> > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > >
> > > -- 
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > Is that a 4G  network dongle ?   I  imagine issues may be related to driver. Some hardware are designed with windows in mind . K
>
> Yes it is 4G LTE
>
> The Alcatel IK41 series M2M LTE Cat4 USB stick connects to the host system using USB2 data interface and will appear in the system with USB Vendor ID: 1bbb and Product ID: 00b6 in default USB mode.
>
> The device expose a USB MBIM network interface (Mobile Broadband Interface Model) and three usb serial interfaces. It is commonly used by Windows 8/10 for connecting mobile broadband devices, but can also be used in Linux environments.
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

I Think new  recommended method  is usimg RNDIS instead. 
Suggest  looking more  into Usimg usb_modeswitch and RNDIS in Linux

[Marco Moock]

On 20.03.2025 12:38 Patrick Dupre via users wrote:
> Same dongle after ~ 1 minute
> traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> 80 byte packets 1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)
> 2.088 ms !N  2.527 ms !N  2.823 ms !N

I assume the connection is being interrupted, as it basically works
with IPv4 and IPv6. After the minute the connection doesn't work
anymore, no route to destination.

Does the web interface provide any logs etc.?
Does it show that the connection is still established?

For the other dongle:
Does this have a web interface too or does it behave like a real modem?

mmcli -L

[Patrick Dupre]

> > Same dongle after ~ 1 minute
> > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> > 80 byte packets 1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)
> > 2.088 ms !N  2.527 ms !N  2.823 ms !N
>
> I assume the connection is being interrupted, as it basically works
> with IPv4 and IPv6. After the minute the connection doesn't work
> anymore, no route to destination.
>
> Does the web interface provide any logs etc.?

No
> Does it show that the connection is still established?

Yes the connection remains establish
Indeed, with the new dongle, I cannot disconnect it. Fails!!
> For the other dongle:
> Does this have a web interface too or does it behave like a real modem?

The old dongle has also an interface, less modern, but there is no much information
but is is only IPV4
it has 10.221.67.222 for the IPV4 address

In all cases
mmcli -L
No modems were found
> mmcli -L
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Marco Moock]

Am 20.03.2025 um 19:55:49 Uhr schrieb Patrick Dupre via users:
> > > Same dongle after ~ 1 minute
> > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops
> > > max, 80 byte packets 1  _gateway
> > > (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11) 2.088 ms !N  2.527 ms !N
> > >  2.823 ms !N
> >
> > I assume the connection is being interrupted, as it basically works
> > with IPv4 and IPv6. After the minute the connection doesn't work
> > anymore, no route to destination.
> >
> > Does the web interface provide any logs etc.?
>
> No
> > Does it show that the connection is still established?
>
> Yes the connection remains establish
> Indeed, with the new dongle, I cannot disconnect it. Fails!!

Do you have a Windows machine to test?
Maybe it is faulty. I don't see a problem in Linux itself here, as the
net unreach message comes from the device itself.
> In all cases
> mmcli -L
> No modems were found

That means that both devices don't show up as modem to the OS.

[Patrick Dupre]

> > > > Same dongle after ~ 1 minute
> > > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops
> > > > max, 80 byte packets 1  _gateway
> > > > (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11) 2.088 ms !N  2.527 ms !N
> > > >  2.823 ms !N
> > >
> > > I assume the connection is being interrupted, as it basically works
> > > with IPv4 and IPv6. After the minute the connection doesn't work
> > > anymore, no route to destination.
> > >
> > > Does the web interface provide any logs etc.?
> >
> > No
> > > Does it show that the connection is still established?
> >
> > Yes the connection remains establish
> > Indeed, with the new dongle, I cannot disconnect it. Fails!!
>
> Do you have a Windows machine to test?

No,
except a VM with windows 7
> Maybe it is faulty. I don't see a problem in Linux itself here, as the
> net unreach message comes from the device itself.
> > In all cases
> > mmcli -L
> > No modems were found
>
> That means that both devices don't show up as modem to the OS.
>
> -- 
> Gruß
> Marco
> Send unsolicited bulk mail to [e-mail]
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Sent using the mobile mail app

On 3/20/25 at 11:56 AM, Patrick Dupre via users wrote:
> > > Same dongle after ~ 1 minute
> > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> > > 80 byte packets 1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)
> > > 2.088 ms !N  2.527 ms !N  2.823 ms !N
> >
> > I assume the connection is being interrupted, as it basically works
> > with IPv4 and IPv6. After the minute the connection doesn't work
> > anymore, no route to destination.
> >
> > Does the web interface provide any logs etc.?
>
> No
> > Does it show that the connection is still established?
>
> Yes the connection remains establish
> Indeed, with the new dongle, I cannot disconnect it. Fails!!
> > For the other dongle:
> > Does this have a web interface too or does it behave like a real modem?
>
> The old dongle has also an interface, less modern, but there is no much information
> but is is only IPV4
> it has 10.221.67.222 for the IPV4 address
>
> In all cases
> mmcli -L
> No modems were found
> > mmcli -L
> >
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Fedora wont detect it unless switch to RNDIS mode using usb_modeswitch

[Patrick Dupre]

> Sent using the mobile mail app
>
> On 3/20/25 at 11:56 AM, Patrick Dupre via users wrote:
> > > > Same dongle after ~ 1 minute
> > > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> > > > 80 byte packets 1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)
> > > > 2.088 ms !N  2.527 ms !N  2.823 ms !N
> > >
> > > I assume the connection is being interrupted, as it basically works
> > > with IPv4 and IPv6. After the minute the connection doesn't work
> > > anymore, no route to destination.
> > >
> > > Does the web interface provide any logs etc.?
> >
> > No
> > > Does it show that the connection is still established?
> >
> > Yes the connection remains establish
> > Indeed, with the new dongle, I cannot disconnect it. Fails!!
> > > For the other dongle:
> > > Does this have a web interface too or does it behave like a real modem?
> >
> > The old dongle has also an interface, less modern, but there is no much information
> > but is is only IPV4
> > it has 10.221.67.222 for the IPV4 address
> >
> > In all cases
> > mmcli -L
> > No modems were found
> > > mmcli -L
> > >
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> Fedora wont detect it unless switch to RNDIS mode using usb_modeswitch

Thank, how I can to this?
man usb_modeswitch does not mention RNDIS mode

By the way, why should I do that with this new dongle?

Thank
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Marco Moock]

Am 20.03.2025 um 20:09:43 Uhr schrieb Patrick Dupre via users:
> No,
> except a VM with windows 7

Should be enough.
You can passthrough USB devices to that, e.g. test a VM with Win 10/11
to have a current OS.

Suggestion try

Use lsusb to identify PID and VID Then once identified

Use  usb_modeswitch -v vid - p PID  -J 
This tell the device to flip mode , RNDIS

Check again 
lsusb

ip a 
modprobe cdc_ether may be needed

Sent using the mobile mail app

On 3/20/25 at 12:32 PM, Patrick Dupre via users wrote:
> > Sent using the mobile mail app
> >
> > On 3/20/25 at 11:56 AM, Patrick Dupre via users wrote:
> > > > > Same dongle after ~ 1 minute
> > > > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> > > > > 80 byte packets 1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)
> > > > > 2.088 ms !N  2.527 ms !N  2.823 ms !N
> > > >
> > > > I assume the connection is being interrupted, as it basically works
> > > > with IPv4 and IPv6. After the minute the connection doesn't work
> > > > anymore, no route to destination.
> > > >
> > > > Does the web interface provide any logs etc.?
> > >
> > > No
> > > > Does it show that the connection is still established?
> > >
> > > Yes the connection remains establish
> > > Indeed, with the new dongle, I cannot disconnect it. Fails!!
> > > > For the other dongle:
> > > > Does this have a web interface too or does it behave like a real modem?
> > >
> > > The old dongle has also an interface, less modern, but there is no much information
> > > but is is only IPV4
> > > it has 10.221.67.222 for the IPV4 address
> > >
> > > In all cases
> > > mmcli -L
> > > No modems were found
> > > > mmcli -L
> > > >
> > > > users mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > 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/[e-mail]
> > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > >
> > > -- 
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > Fedora wont detect it unless switch to RNDIS mode using usb_modeswitch
>
> Thank, how I can to this?
> man usb_modeswitch does not mention RNDIS mode
>
> By the way, why should I do that with this new dongle?
>
> Thank
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Patrick Dupre]

> Am 20.03.2025 um 20:09:43 Uhr schrieb Patrick Dupre via users:
> > No,
> > except a VM with windows 7
>
> Should be enough.
> You can passthrough USB devices to that, e.g. test a VM with Win 10/11
> to have a current OS.

Look at that.

I am now connected fine for ~ 15 minutes!
I started my VM with Win7!
At the beginning, I passthrough the USB device, connect to http://192.168.8.1
It was already connect from linux.
But I could not use the network.
Then I "disconnected" the USB device to have the control from linux
It is still working.
Why?
The only difference that I can see is that the "link speed 425 Mb/s"
is not shown up (Details NetworkManager).
I do not know how I could manage this

Here some outputs

enp0s20f0u11: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.8.150  netmask 255.255.255.0  broadcast 192.168.8.255
        inet6 2a04:cec0:11fa:a98d:f531:38b3:2c62:6316  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::f40e:975b:b76a:70cd  prefixlen 64  scopeid 0x20<link>
        ether 9a:78:3e:01:9b:67  txqueuelen 1000  (Ethernet)
        RX packets 24606  bytes 13570762 (12.9 MiB)
        RX errors 2  dropped 0  overruns 0  frame 2
        TX packets 21796  bytes 6157721 (5.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

dig google.de @fe80::84d1:a9ff:fee7:c482%enp0s20f0u11
;; communications error to fe80::84d1:a9ff:fee7:c482%17#53: timed out

ip -6 r s
2a04:cec0:11fa:a98d::/64 dev enp0s20f0u11 proto ra metric 100 pref medium
fe80::/64 dev enp0s20f0u11 proto kernel metric 1024 pref medium
default via fe80::9051:8689:759f:501d dev enp0s20f0u11 proto ra metric 100 pref medium

ip a
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
17: enp0s20f0u11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
    link/ether 9a:78:3e:01:9b:67 brd ff:ff:ff:ff:ff:ff
    inet 192.168.8.150/24 brd 192.168.8.255 scope global dynamic noprefixroute enp0s20f0u11
       valid_lft 6678sec preferred_lft 6678sec
    inet6 2a04:cec0:11fa:a98d:f531:38b3:2c62:6316/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

ip r s
default via 192.168.8.1 dev enp0s20f0u11 proto dhcp src 192.168.8.150 metric 100
192.168.8.0/24 dev enp0s20f0u11 proto kernel scope link src 192.168.8.150 metric 100
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.8.1     0.0.0.0         UG    100    0        0 enp0s20f0u11
192.168.8.0     0.0.0.0         255.255.255.0   U     100    0        0 enp0s20f0u11
192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0

traceroute -I 2a01:170:118f:1::1
traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max, 80 byte packets
 1  ik41.home (2a04:cec0:11fa:a98d:8980:ce75:841b:48d6)  2.360 ms  3.220 ms *
 2  2a04:cec0:11fa:a98d:0:62:273c:f140 (2a04:cec0:11fa:a98d:0:62:273c:f140)  64.183 ms  74.291 ms *
 3  * * *
 4  2001:860:b204:5100::19:4 (2001:860:b204:5100::19:4)  74.640 ms  74.664 ms  74.721 ms
 5  2001:860:b204:5100::15:3 (2001:860:b204:5100::15:3)  74.430 ms  74.427 ms  74.477 ms
 6  2001:860:b204:5100::11:4 (2001:860:b204:5100::11:4)  79.856 ms * *
 7  2001:860:bbe0:e1::1 (2001:860:bbe0:e1::1)  52.430 ms * *
 8  2001:860:bbee:d9::1 (2001:860:bbee:d9::1)  33.476 ms * *
 9  * * *
10  * * *
11  2003:0:130e:9::2274:1 (2003:0:130e:9::2274:1)  49.865 ms  49.946 ms  53.484 ms
12  2a01:170:118f:1::1 (2a01:170:118f:1::1)  46.012 ms  49.868 ms  49.899 ms

traceroute -I 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * _gateway (192.168.8.1)  2.335 ms !N *

[Marco Moock]

Am 20.03.2025 um 21:15:08 Uhr schrieb Patrick Dupre via users:
> traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> 80 byte packets 1  ik41.home
> (2a04:cec0:11fa:a98d:8980:ce75:841b:48d6)  2.360 ms  3.220 ms * 2
> 2a04:cec0:11fa:a98d:0:62:273c:f140
> (2a04:cec0:11fa:a98d:0:62:273c:f140)  64.183 ms  74.291 ms * 3  * * *
> 4  2001:860:b204:5100::19:4 (2001:860:b204:5100::19:4)  74.640 ms
> 74.664 ms  74.721 ms 5  2001:860:b204:5100::15:3
> (2001:860:b204:5100::15:3)  74.430 ms  74.427 ms  74.477 ms 6
> 2001:860:b204:5100::11:4 (2001:860:b204:5100::11:4)  79.856 ms * * 7
> 2001:860:bbe0:e1::1 (2001:860:bbe0:e1::1)  52.430 ms * * 8
> 2001:860:bbee:d9::1 (2001:860:bbee:d9::1)  33.476 ms * * 9  * * * 10
> 11  2003:0:130e:9::2274:1 (2003:0:130e:9::2274:1)  49.865 ms
>
> 49.946 ms  53.484 ms 12  2a01:170:118f:1::1 (2a01:170:118f:1::1)
> 46.012 ms  49.868 ms  49.899 ms
>
> traceroute -I 8.8.8.8
> traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
>  1  * * *
>  2  * * *
>  3  * * *
>  4  * * *
>  5  * * *
>  6  * _gateway (192.168.8.1)  2.335 ms !N *

In this case, IPv6 worked, IPv4 doesn't.
Please test in windows only (disconnect it, the passthrough to
windows), to check if the dongle itself is working.

You can then also try to switch the mode, so it is a real modem that
will be used by ModemManager.

[Patrick Dupre]

> > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> > 80 byte packets 1  ik41.home
> > (2a04:cec0:11fa:a98d:8980:ce75:841b:48d6)  2.360 ms  3.220 ms * 2
> > 2a04:cec0:11fa:a98d:0:62:273c:f140
> > (2a04:cec0:11fa:a98d:0:62:273c:f140)  64.183 ms  74.291 ms * 3  * * *
> > 4  2001:860:b204:5100::19:4 (2001:860:b204:5100::19:4)  74.640 ms
> > 74.664 ms  74.721 ms 5  2001:860:b204:5100::15:3
> > (2001:860:b204:5100::15:3)  74.430 ms  74.427 ms  74.477 ms 6
> > 2001:860:b204:5100::11:4 (2001:860:b204:5100::11:4)  79.856 ms * * 7
> > 2001:860:bbe0:e1::1 (2001:860:bbe0:e1::1)  52.430 ms * * 8
> > 2001:860:bbee:d9::1 (2001:860:bbee:d9::1)  33.476 ms * * 9  * * * 10
> > 11  2003:0:130e:9::2274:1 (2003:0:130e:9::2274:1)  49.865 ms
> >
> > 49.946 ms  53.484 ms 12  2a01:170:118f:1::1 (2a01:170:118f:1::1)
> > 46.012 ms  49.868 ms  49.899 ms
> >
> > traceroute -I 8.8.8.8
> > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> >  1  * * *
> >  2  * * *
> >  3  * * *
> >  4  * * *
> >  5  * * *
> >  6  * _gateway (192.168.8.1)  2.335 ms !N *
>
> In this case, IPv6 worked, IPv4 doesn't.
> Please test in windows only (disconnect it, the passthrough to
> windows), to check if the dongle itself is working.

I am not sure to understand.
As I said, now, the USB dongle is disconnected from Win7, and the networks works fine
from both OS.
If I passthrough the dongle to Win7, I lost the connection under linux.
The thing that I should do now is to stop Win7
I do not have the equivalent of NetwrorkManager on Win7
> You can then also try to switch the mode, so it is a real modem that
> will be used by ModemManager.

I do not understand.
> -- 
> Gruß
> Marco
> Send unsolicited bulk mail to [e-mail]
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Patrick Dupre]

Hello,

What I do not understand is that I have to start my dongle under a
VM with Win7, to be able to run properly under linux.
If not, i.e., if I connect from Linux, I have 1-2 minutes to access
to the internet normally. and then the connections fail.

I could suggest one explanation.
There is a systematic update of the dongle through internet at the 
first connection.
The update is correct through win7, but not from Linux.

Would you have some ideas to solve this issue?

Thank.
> Sent: Thursday, March 20, 2025 at 9:31 PM
> From: "Patrick Dupre via users" 
> To: [e-mail]
> Cc: [e-mail], "Patrick Dupre" 
> Subject: Re: Dongle USB
> > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> > > 80 byte packets 1  ik41.home
> > > (2a04:cec0:11fa:a98d:8980:ce75:841b:48d6)  2.360 ms  3.220 ms * 2
> > > 2a04:cec0:11fa:a98d:0:62:273c:f140
> > > (2a04:cec0:11fa:a98d:0:62:273c:f140)  64.183 ms  74.291 ms * 3  * * *
> > > 4  2001:860:b204:5100::19:4 (2001:860:b204:5100::19:4)  74.640 ms
> > > 74.664 ms  74.721 ms 5  2001:860:b204:5100::15:3
> > > (2001:860:b204:5100::15:3)  74.430 ms  74.427 ms  74.477 ms 6
> > > 2001:860:b204:5100::11:4 (2001:860:b204:5100::11:4)  79.856 ms * * 7
> > > 2001:860:bbe0:e1::1 (2001:860:bbe0:e1::1)  52.430 ms * * 8
> > > 2001:860:bbee:d9::1 (2001:860:bbee:d9::1)  33.476 ms * * 9  * * * 10
> > > 11  2003:0:130e:9::2274:1 (2003:0:130e:9::2274:1)  49.865 ms
> > >
> > > 49.946 ms  53.484 ms 12  2a01:170:118f:1::1 (2a01:170:118f:1::1)
> > > 46.012 ms  49.868 ms  49.899 ms
> > >
> > > traceroute -I 8.8.8.8
> > > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> > >  1  * * *
> > >  2  * * *
> > >  3  * * *
> > >  4  * * *
> > >  5  * * *
> > >  6  * _gateway (192.168.8.1)  2.335 ms !N *
> >
> > In this case, IPv6 worked, IPv4 doesn't.
> > Please test in windows only (disconnect it, the passthrough to
> > windows), to check if the dongle itself is working.
>
> I am not sure to understand.
> As I said, now, the USB dongle is disconnected from Win7, and the networks works fine
> from both OS.
> If I passthrough the dongle to Win7, I lost the connection under linux.
> The thing that I should do now is to stop Win7
> I do not have the equivalent of NetwrorkManager on Win7
> > You can then also try to switch the mode, so it is a real modem that
> > will be used by ModemManager.
>
> I do not understand.
> > -- 
> > Gruß
> > Marco
> > Send unsolicited bulk mail to [e-mail]
> >
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Patrick Dupre]

Following my previous message

If I use my old dongle, I can easy have 2 PCs accessing the internet
Setting:
PC A has the USB dongle.
It set in Automatic DHCP for the Dongle interface 
and 
Shared to other computers for the interface connected to PC B

PC B is set automatic DHCP

If I do the same with my new Dongle.
It just do not let PC B accessing to the rest of the world.
In both cases, the addresses are the same

PC A
enp0s20f0u11: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.8.150  netmask 255.255.255.0  broadcast 192.168.8.255
DNS Servers: 192.168.8.1 fe80::8088:c1ff:fe35:74fe

enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.42.0.1  netmask 255.255.255.0  broadcast 10.42.0.255

On PC B,
        inet 10.42.0.82  netmask 255.255.255.0  broadcast 10.42.0.255
        inet6 fe80::c2c9:faa6:83fa:222e  prefixlen 64  scopeid 0x20<link>
Current DNS Server: 10.42.0.1
       DNS Servers: 10.42.0.1

On PC B
route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.42.0.1       0.0.0.0         UG    100    0        0 eno1
10.42.0.0       0.0.0.0         255.255.255.0   U     100    0        0 eno1

On PC A
route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.8.1     0.0.0.0         UG    100    0        0 enp0s20f0u11
10.42.0.0       0.0.0.0         255.255.255.0   U     101    0        0 enp1s0
192.168.8.0     0.0.0.0         255.255.255.0   U     100    0        0 enp0s20f0u11
192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 virbr0
> Sent: Friday, March 21, 2025 at 9:38 AM
> From: "Patrick Dupre via users" 
> To: [e-mail]
> Cc: [e-mail], "Patrick Dupre" 
> Subject: Re: Dongle USB
>
> Hello,
>
> What I do not understand is that I have to start my dongle under a
> VM with Win7, to be able to run properly under linux.
> If not, i.e., if I connect from Linux, I have 1-2 minutes to access
> to the internet normally. and then the connections fail.
>
> I could suggest one explanation.
> There is a systematic update of the dongle through internet at the 
> first connection.
> The update is correct through win7, but not from Linux.
>
> Would you have some ideas to solve this issue?
>
> Thank.
> > Sent: Thursday, March 20, 2025 at 9:31 PM
> > From: "Patrick Dupre via users" 
> > To: [e-mail]
> > Cc: [e-mail], "Patrick Dupre" 
> > Subject: Re: Dongle USB
> > > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> > > > 80 byte packets 1  ik41.home
> > > > (2a04:cec0:11fa:a98d:8980:ce75:841b:48d6)  2.360 ms  3.220 ms * 2
> > > > 2a04:cec0:11fa:a98d:0:62:273c:f140
> > > > (2a04:cec0:11fa:a98d:0:62:273c:f140)  64.183 ms  74.291 ms * 3  * * *
> > > > 4  2001:860:b204:5100::19:4 (2001:860:b204:5100::19:4)  74.640 ms
> > > > 74.664 ms  74.721 ms 5  2001:860:b204:5100::15:3
> > > > (2001:860:b204:5100::15:3)  74.430 ms  74.427 ms  74.477 ms 6
> > > > 2001:860:b204:5100::11:4 (2001:860:b204:5100::11:4)  79.856 ms * * 7
> > > > 2001:860:bbe0:e1::1 (2001:860:bbe0:e1::1)  52.430 ms * * 8
> > > > 2001:860:bbee:d9::1 (2001:860:bbee:d9::1)  33.476 ms * * 9  * * * 10
> > > > 11  2003:0:130e:9::2274:1 (2003:0:130e:9::2274:1)  49.865 ms
> > > >
> > > > 49.946 ms  53.484 ms 12  2a01:170:118f:1::1 (2a01:170:118f:1::1)
> > > > 46.012 ms  49.868 ms  49.899 ms
> > > >
> > > > traceroute -I 8.8.8.8
> > > > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> > > >  1  * * *
> > > >  2  * * *
> > > >  3  * * *
> > > >  4  * * *
> > > >  5  * * *
> > > >  6  * _gateway (192.168.8.1)  2.335 ms !N *
> > >
> > > In this case, IPv6 worked, IPv4 doesn't.
> > > Please test in windows only (disconnect it, the passthrough to
> > > windows), to check if the dongle itself is working.
> >
> > I am not sure to understand.
> > As I said, now, the USB dongle is disconnected from Win7, and the networks works fine
> > from both OS.
> > If I passthrough the dongle to Win7, I lost the connection under linux.
> > The thing that I should do now is to stop Win7
> > I do not have the equivalent of NetwrorkManager on Win7
> > > You can then also try to switch the mode, so it is a real modem that
> > > will be used by ModemManager.
> >
> > I do not understand.
> > > -- 
> > > Gruß
> > > Marco
> > > Send unsolicited bulk mail to [e-mail]
> > >
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Marco Moock]

Am Thu, 20 Mar 2025 21:31:41 +0100
schrieb Patrick Dupre via users :
> > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops
> > > max, 80 byte packets 1  ik41.home
> > > (2a04:cec0:11fa:a98d:8980:ce75:841b:48d6)  2.360 ms  3.220 ms * 2
> > > 2a04:cec0:11fa:a98d:0:62:273c:f140
> > > (2a04:cec0:11fa:a98d:0:62:273c:f140)  64.183 ms  74.291 ms * 3  *
> > > 4  2001:860:b204:5100::19:4 (2001:860:b204:5100::19:4)
> > >
> > > 74.640 ms 74.664 ms  74.721 ms 5  2001:860:b204:5100::15:3
> > > (2001:860:b204:5100::15:3)  74.430 ms  74.427 ms  74.477 ms 6
> > > 2001:860:b204:5100::11:4 (2001:860:b204:5100::11:4)  79.856 ms *
> > > 7 2001:860:bbe0:e1::1 (2001:860:bbe0:e1::1)  52.430 ms * * 8
> > >
> > > 2001:860:bbee:d9::1 (2001:860:bbee:d9::1)  33.476 ms * * 9  * * *
> > > 10
> > > 11  2003:0:130e:9::2274:1 (2003:0:130e:9::2274:1)  49.865 ms
> > >
> > > 49.946 ms  53.484 ms 12  2a01:170:118f:1::1 (2a01:170:118f:1::1)
> > > 46.012 ms  49.868 ms  49.899 ms
> > >
> > > traceroute -I 8.8.8.8
> > > traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
> > >  1  * * *
> > >  2  * * *
> > >  3  * * *
> > >  4  * * *
> > >  5  * * *
> > >  6  * _gateway (192.168.8.1)  2.335 ms !N *
> >
> > In this case, IPv6 worked, IPv4 doesn't.
> > Please test in windows only (disconnect it, the passthrough to
> > windows), to check if the dongle itself is working.
>
> I am not sure to understand.
> As I said, now, the USB dongle is disconnected from Win7, and the
> networks works fine from both OS.
> If I passthrough the dongle to Win7, I lost the connection under
> linux. The thing that I should do now is to stop Win7
> I do not have the equivalent of NetwrorkManager on Win7

This is the expected behavior, as the device is now directly connected
to the VM and not to the Linux OS anymore.

The idea is to test if it causes the same problems in the windows VM.
It will of course then only work in the VM, but it is just a test.
> > You can then also try to switch the mode, so it is a real modem that
> > will be used by ModemManager.
>
> I do not understand.

Some USB devices can act as 2 roles. In this case, it acts as an
ethernet adapter and the cellular stuff is being done by the dongle
itself. Maybe it also supports modem mode where it acts like a real
modem connected to the PC.

https://www.draisberghof.de/usb_modeswitch/

This application should be available in Fedora, no need to build it
manually.

[Patrick Dupre]

> Suggestion try
>
> Use lsusb to identify PID and VID Then once identified
>
> Use  usb_modeswitch -v vid - p PID  -J 
> This tell the device to flip mode , RNDIS
>
> Check again 
> lsusb

lsusb
Bus 001 Device 065: ID 1bbb:0908 T & A Mobile Phones LinkKey

usb_modeswitch -v 1bbb -p 0908 -J
Look for default devices ...
 Found devices in default mode (1)
Access device 065 on bus 001
Get the current device configuration ...
Current configuration number is 1
Use interface number 0
 with class 2
Error: can't use storage command in MessageContent with interface 0; interface class is 2, expected 8. Abort
> ip a 
> modprobe cdc_ether may be needed
>
> Sent using the mobile mail app
>
> On 3/20/25 at 12:32 PM, Patrick Dupre via users wrote:
> > > Sent using the mobile mail app
> > >
> > > On 3/20/25 at 11:56 AM, Patrick Dupre via users wrote:
> > > > > > Same dongle after ~ 1 minute
> > > > > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> > > > > > 80 byte packets 1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)
> > > > > > 2.088 ms !N  2.527 ms !N  2.823 ms !N
> > > > >
> > > > > I assume the connection is being interrupted, as it basically works
> > > > > with IPv4 and IPv6. After the minute the connection doesn't work
> > > > > anymore, no route to destination.
> > > > >
> > > > > Does the web interface provide any logs etc.?
> > > >
> > > > No
> > > > > Does it show that the connection is still established?
> > > >
> > > > Yes the connection remains establish
> > > > Indeed, with the new dongle, I cannot disconnect it. Fails!!
> > > > > For the other dongle:
> > > > > Does this have a web interface too or does it behave like a real modem?
> > > >
> > > > The old dongle has also an interface, less modern, but there is no much information
> > > > but is is only IPV4
> > > > it has 10.221.67.222 for the IPV4 address
> > > >
> > > > In all cases
> > > > mmcli -L
> > > > No modems were found
> > > > > mmcli -L
> > > > >
> > > > > users mailing list -- [e-mail]
> > > > > To unsubscribe send an email to [e-mail]
> > > > > 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/[e-mail]
> > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > >
> > > > -- 
> > > > _______________________________________________
> > > > users mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > 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/[e-mail]
> > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > >
> > > Fedora wont detect it unless switch to RNDIS mode using usb_modeswitch
> >
> > Thank, how I can to this?
> > man usb_modeswitch does not mention RNDIS mode
> >
> > By the way, why should I do that with this new dongle?
> >
> > Thank
> > > -- 
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Patrick Dupre]

Hello,

Unfortunately, the issue is still not solved.
Can somebody help me?
> > Suggestion try
> >
> > Use lsusb to identify PID and VID Then once identified
> >
> > Use  usb_modeswitch -v vid - p PID  -J 
> > This tell the device to flip mode , RNDIS
> >
> > Check again 
> > lsusb
>
> lsusb
> Bus 001 Device 065: ID 1bbb:0908 T & A Mobile Phones LinkKey
>
> usb_modeswitch -v 1bbb -p 0908 -J
> Look for default devices ...
>  Found devices in default mode (1)
> Access device 065 on bus 001
> Get the current device configuration ...
> Current configuration number is 1
> Use interface number 0
>  with class 2
> Error: can't use storage command in MessageContent with interface 0; interface class is 2, expected 8. Abort
> > ip a 
> > modprobe cdc_ether may be needed
> >
> > Sent using the mobile mail app
> >
> > On 3/20/25 at 12:32 PM, Patrick Dupre via users wrote:
> > > > Sent using the mobile mail app
> > > >
> > > > On 3/20/25 at 11:56 AM, Patrick Dupre via users wrote:
> > > > > > > Same dongle after ~ 1 minute
> > > > > > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> > > > > > > 80 byte packets 1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)
> > > > > > > 2.088 ms !N  2.527 ms !N  2.823 ms !N
> > > > > >
> > > > > > I assume the connection is being interrupted, as it basically works
> > > > > > with IPv4 and IPv6. After the minute the connection doesn't work
> > > > > > anymore, no route to destination.
> > > > > >
> > > > > > Does the web interface provide any logs etc.?
> > > > >
> > > > > No
> > > > > > Does it show that the connection is still established?
> > > > >
> > > > > Yes the connection remains establish
> > > > > Indeed, with the new dongle, I cannot disconnect it. Fails!!
> > > > > > For the other dongle:
> > > > > > Does this have a web interface too or does it behave like a real modem?
> > > > >
> > > > > The old dongle has also an interface, less modern, but there is no much information
> > > > > but is is only IPV4
> > > > > it has 10.221.67.222 for the IPV4 address
> > > > >
> > > > > In all cases
> > > > > mmcli -L
> > > > > No modems were found
> > > > > > mmcli -L
> > > > > >
> > > > > > users mailing list -- [e-mail]
> > > > > > To unsubscribe send an email to [e-mail]
> > > > > > 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/[e-mail]
> > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > >
> > > > > -- 
> > > > > _______________________________________________
> > > > > users mailing list -- [e-mail]
> > > > > To unsubscribe send an email to [e-mail]
> > > > > 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/[e-mail]
> > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > >
> > > > Fedora wont detect it unless switch to RNDIS mode using usb_modeswitch
> > >
> > > Thank, how I can to this?
> > > man usb_modeswitch does not mention RNDIS mode
> > >
> > > By the way, why should I do that with this new dongle?
> > >
> > > Thank
> > > > -- 
> > > > _______________________________________________
> > > > users mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > 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/[e-mail]
> > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > >
> > > -- 
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

This may help out

https://techship.com/support/faq/how-to-automated-always-on-connection-estab....

Sent using the mobile mail app

On 3/24/25 at 1:34 AM, Patrick Dupre via users wrote:
> Hello,
>
> Unfortunately, the issue is still not solved.
> Can somebody help me?
> > > Suggestion try
> > >
> > > Use lsusb to identify PID and VID Then once identified
> > >
> > > Use  usb_modeswitch -v vid - p PID  -J 
> > > This tell the device to flip mode , RNDIS
> > >
> > > Check again 
> > > lsusb
> >
> > lsusb
> > Bus 001 Device 065: ID 1bbb:0908 T & A Mobile Phones LinkKey
> >
> > usb_modeswitch -v 1bbb -p 0908 -J
> > Look for default devices ...
> >  Found devices in default mode (1)
> > Access device 065 on bus 001
> > Get the current device configuration ...
> > Current configuration number is 1
> > Use interface number 0
> >  with class 2
> > Error: can't use storage command in MessageContent with interface 0; interface class is 2, expected 8. Abort
> > > ip a 
> > > modprobe cdc_ether may be needed
> > >
> > > Sent using the mobile mail app
> > >
> > > On 3/20/25 at 12:32 PM, Patrick Dupre via users wrote:
> > > > > Sent using the mobile mail app
> > > > >
> > > > > On 3/20/25 at 11:56 AM, Patrick Dupre via users wrote:
> > > > > > >
> > > > > > > > Same dongle after ~ 1 minute
> > > > > > > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> > > > > > > > 80 byte packets 1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)
> > > > > > > > 2.088 ms !N  2.527 ms !N  2.823 ms !N
> > > > > > >
> > > > > > >
> > > > > > > I assume the connection is being interrupted, as it basically works
> > > > > > > with IPv4 and IPv6. After the minute the connection doesn't work
> > > > > > > anymore, no route to destination.
> > > > > > >
> > > > > > > Does the web interface provide any logs etc.?
> > > > > > No
> > > > > >
> > > > > > > Does it show that the connection is still established?
> > > > > > Yes the connection remains establish
> > > > > > Indeed, with the new dongle, I cannot disconnect it. Fails!!
> > > > > >
> > > > > > > For the other dongle:
> > > > > > > Does this have a web interface too or does it behave like a real modem?
> > > > > > The old dongle has also an interface, less modern, but there is no much information
> > > > > > but is is only IPV4
> > > > > > it has 10.221.67.222 for the IPV4 address
> > > > > >
> > > > > > In all cases
> > > > > > mmcli -L
> > > > > > No modems were found
> > > > > >
> > > > > > >
> > > > > > > mmcli -L
> > > > > > > --
> > > > > > > _______________________________________________
> > > > > > > users mailing list -- [e-mail]
> > > > > > > To unsubscribe send an email to [e-mail]
> > > > > > > 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/[e-mail]
> > > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > > > >
> > > > > >
> > > > > > users mailing list -- [e-mail]
> > > > > > To unsubscribe send an email to [e-mail]
> > > > > > 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/[e-mail]
> > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > >
> > > > > Fedora wont detect it unless switch to RNDIS mode using usb_modeswitch
> > > >
> > > > Thank, how I can to this?
> > > > man usb_modeswitch does not mention RNDIS mode
> > > >
> > > > By the way, why should I do that with this new dongle?
> > > >
> > > > Thank
> > > > > -- 
> > > > > _______________________________________________
> > > > > users mailing list -- [e-mail]
> > > > > To unsubscribe send an email to [e-mail]
> > > > > 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/[e-mail]
> > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > >
> > > > -- 
> > > > _______________________________________________
> > > > users mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > 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/[e-mail]
> > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > >
> > > -- 
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Patrick Dupre]

Thank for the feedback,

However, before I run these commands, I need to understand.
What it is this "command" AT+USBMODE=1

does not works
AT+USBMODE?

command not found

How do I find my router?
In  /dev/tty
I do not see something which could be a usb router

Can I deduce from?
Bus 001 Device 007: ID 1bbb:0195 T & A Mobile Phones Alcatel OneTouch L850V / Telekom Speedstick LTE
Is it
/dev/bus/usb/001/007

I tried
 echo -ne "AT+USBMODE?\r\n" > /dev/bus/usb/001/007

-bash: echo: write error: Invalid argument
> This may help out
>
> https://techship.com/support/faq/how-to-automated-always-on-connection-estab....
>
> Sent using the mobile mail app
>
> On 3/24/25 at 1:34 AM, Patrick Dupre via users wrote:
> > Hello,
> >
> > Unfortunately, the issue is still not solved.
> > Can somebody help me?
> > > > Suggestion try
> > > >
> > > > Use lsusb to identify PID and VID Then once identified
> > > >
> > > > Use  usb_modeswitch -v vid - p PID  -J 
> > > > This tell the device to flip mode , RNDIS
> > > >
> > > > Check again 
> > > > lsusb
> > >
> > > lsusb
> > > Bus 001 Device 065: ID 1bbb:0908 T & A Mobile Phones LinkKey
> > >
> > > usb_modeswitch -v 1bbb -p 0908 -J
> > > Look for default devices ...
> > >  Found devices in default mode (1)
> > > Access device 065 on bus 001
> > > Get the current device configuration ...
> > > Current configuration number is 1
> > > Use interface number 0
> > >  with class 2
> > > Error: can't use storage command in MessageContent with interface 0; interface class is 2, expected 8. Abort
> > > > ip a 
> > > > modprobe cdc_ether may be needed
> > > >
> > > > Sent using the mobile mail app
> > > >
> > > > On 3/20/25 at 12:32 PM, Patrick Dupre via users wrote:
> > > > > > Sent using the mobile mail app
> > > > > >
> > > > > > On 3/20/25 at 11:56 AM, Patrick Dupre via users wrote:
> > > > > >
> > > > > > > >
> > > > > > > > > Same dongle after ~ 1 minute
> > > > > > > > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> > > > > > > > > 80 byte packets 1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)
> > > > > > > > > 2.088 ms !N  2.527 ms !N  2.823 ms !N
> > > > > > > >
> > > > > > > >
> > > > > > > > I assume the connection is being interrupted, as it basically works
> > > > > > > > with IPv4 and IPv6. After the minute the connection doesn't work
> > > > > > > > anymore, no route to destination.
> > > > > > > >
> > > > > > > > Does the web interface provide any logs etc.?
> > > > > > > No
> > > > > > > 
> > > > > > > > Does it show that the connection is still established?
> > > > > > > Yes the connection remains establish
> > > > > > > Indeed, with the new dongle, I cannot disconnect it. Fails!!
> > > > > > > 
> > > > > > > 
> > > > > > > > For the other dongle:
> > > > > > > > Does this have a web interface too or does it behave like a real modem?
> > > > > > > The old dongle has also an interface, less modern, but there is no much information
> > > > > > > but is is only IPV4
> > > > > > > it has 10.221.67.222 for the IPV4 address
> > > > > > > 
> > > > > > > In all cases
> > > > > > > mmcli -L
> > > > > > > No modems were found
> > > > > > > 
> > > > > > > >
> > > > > > > > mmcli -L
> > > > > > > > --
> > > > > > > > _______________________________________________
> > > > > > > > users mailing list -- [e-mail]
> > > > > > > > To unsubscribe send an email to [e-mail]
> > > > > > > > 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/[e-mail]
> > > > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > > > > >
> > > > > > > -- 
> > > > > > > _______________________________________________
> > > > > > > users mailing list -- [e-mail]
> > > > > > > To unsubscribe send an email to [e-mail]
> > > > > > > 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/[e-mail]
> > > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > > > > 
> > > > > > Fedora wont detect it unless switch to RNDIS mode using usb_modeswitch
> > > > >
> > > > > Thank, how I can to this?
> > > > > man usb_modeswitch does not mention RNDIS mode
> > > > >
> > > > > By the way, why should I do that with this new dongle?
> > > > >
> > > > > Thank
> > > > > > -- 
> > > > > > _______________________________________________
> > > > > > users mailing list -- [e-mail]
> > > > > > To unsubscribe send an email to [e-mail]
> > > > > > 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/[e-mail]
> > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > >
> > > > > -- 
> > > > > _______________________________________________
> > > > > users mailing list -- [e-mail]
> > > > > To unsubscribe send an email to [e-mail]
> > > > > 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/[e-mail]
> > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > >
> > > > -- 
> > > > _______________________________________________
> > > > users mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > 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/[e-mail]
> > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > >
> > > -- 
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Some more info that may help sending AT commands to device,  also may need to read more on usb-modeswitch command

https://openwrt.org/docs/guide-user/network/wan/wwan/at_commands#:~:text=To%....

Sent using the mobile mail app

On 3/24/25 at 8:42 AM, Patrick Dupre via users wrote:
> Thank for the feedback,
>
> However, before I run these commands, I need to understand.
> What it is this "command" AT+USBMODE=1
>
> does not works
> AT+USBMODE?
>
> command not found
>
> How do I find my router?
> In  /dev/tty
> I do not see something which could be a usb router
>
> Can I deduce from?
> Bus 001 Device 007: ID 1bbb:0195 T & A Mobile Phones Alcatel OneTouch L850V / Telekom Speedstick LTE
> Is it
> /dev/bus/usb/001/007
>
> I tried
>  echo -ne "AT+USBMODE?\r\n" > /dev/bus/usb/001/007
>
> -bash: echo: write error: Invalid argument
> > This may help out
> >
> > https://techship.com/support/faq/how-to-automated-always-on-connection-estab....
> >
> > Sent using the mobile mail app
> >
> > On 3/24/25 at 1:34 AM, Patrick Dupre via users wrote:
> > > Hello,
> > >
> > > Unfortunately, the issue is still not solved.
> > > Can somebody help me?
> > > > > Suggestion try
> > > > >
> > > > > Use lsusb to identify PID and VID Then once identified
> > > > >
> > > > > Use  usb_modeswitch -v vid - p PID  -J 
> > > > > This tell the device to flip mode , RNDIS
> > > > >
> > > > > Check again 
> > > > > lsusb
> > > >
> > > > lsusb
> > > > Bus 001 Device 065: ID 1bbb:0908 T & A Mobile Phones LinkKey
> > > >
> > > > usb_modeswitch -v 1bbb -p 0908 -J
> > > > Look for default devices ...
> > > >  Found devices in default mode (1)
> > > > Access device 065 on bus 001
> > > > Get the current device configuration ...
> > > > Current configuration number is 1
> > > > Use interface number 0
> > > >  with class 2
> > > > Error: can't use storage command in MessageContent with interface 0; interface class is 2, expected 8. Abort
> > > > > ip a 
> > > > > modprobe cdc_ether may be needed
> > > > >
> > > > > Sent using the mobile mail app
> > > > >
> > > > > On 3/20/25 at 12:32 PM, Patrick Dupre via users wrote:
> > > > > > > Sent using the mobile mail app
> > > > > > > 
> > > > > > > On 3/20/25 at 11:56 AM, Patrick Dupre via users wrote:
> > > > > > > 
> > > > > > > > >
> > > > > > > > > > Same dongle after ~ 1 minute
> > > > > > > > > > traceroute to 2a01:170:118f:1::1 (2a01:170:118f:1::1), 30 hops max,
> > > > > > > > > > 80 byte packets 1  _gateway (fe80::dcb1:beff:fe30:9ee8%enp0s20f0u11)
> > > > > > > > > > 2.088 ms !N  2.527 ms !N  2.823 ms !N
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I assume the connection is being interrupted, as it basically works
> > > > > > > > > with IPv4 and IPv6. After the minute the connection doesn't work
> > > > > > > > > anymore, no route to destination.
> > > > > > > > >
> > > > > > > > > Does the web interface provide any logs etc.?
> > > > > > > > No
> > > > > > > > 
> > > > > > > > > Does it show that the connection is still established?
> > > > > > > > Yes the connection remains establish
> > > > > > > > Indeed, with the new dongle, I cannot disconnect it. Fails!!
> > > > > > > > 
> > > > > > > > 
> > > > > > > > > For the other dongle:
> > > > > > > > > Does this have a web interface too or does it behave like a real modem?
> > > > > > > > The old dongle has also an interface, less modern, but there is no much information
> > > > > > > > but is is only IPV4
> > > > > > > > it has 10.221.67.222 for the IPV4 address
> > > > > > > > 
> > > > > > > > In all cases
> > > > > > > > mmcli -L
> > > > > > > > No modems were found
> > > > > > > > 
> > > > > > > > >
> > > > > > > > > mmcli -L
> > > > > > > > > --
> > > > > > > > > _______________________________________________
> > > > > > > > > users mailing list -- [e-mail]
> > > > > > > > > To unsubscribe send an email to [e-mail]
> > > > > > > > > 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/[e-mail]
> > > > > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > > > > > >
> > > > > > > > -- 
> > > > > > > > _______________________________________________
> > > > > > > > users mailing list -- [e-mail]
> > > > > > > > To unsubscribe send an email to [e-mail]
> > > > > > > > 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/[e-mail]
> > > > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > > > > > 
> > > > > > > Fedora wont detect it unless switch to RNDIS mode using usb_modeswitch
> > > > > > Thank, how I can to this?
> > > > > > man usb_modeswitch does not mention RNDIS mode
> > > > > >
> > > > > > By the way, why should I do that with this new dongle?
> > > > > >
> > > > > > Thank
> > > > > >
> > > > > > > -- 
> > > > > > > _______________________________________________
> > > > > > > users mailing list -- [e-mail]
> > > > > > > To unsubscribe send an email to [e-mail]
> > > > > > > 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/[e-mail]
> > > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > > > >
> > > > > >
> > > > > > users mailing list -- [e-mail]
> > > > > > To unsubscribe send an email to [e-mail]
> > > > > > 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/[e-mail]
> > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > >
> > > > > -- 
> > > > > _______________________________________________
> > > > > users mailing list -- [e-mail]
> > > > > To unsubscribe send an email to [e-mail]
> > > > > 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/[e-mail]
> > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > >
> > > > -- 
> > > > _______________________________________________
> > > > users mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > 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/[e-mail]
> > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > >
> > > -- 
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Patrick Dupre]

Hello,

I am not make any progress.

1) There are no /dev/ttyUSB or /dev/ttyACM
or similar things.
I do have
Bus 001 Device 009: ID 1bbb:0908 T & A Mobile Phones LinkKey
/dev/bus/usb/001/009

2)
usb_modeswitch -v 1bbb -p 0908 PID -J
provides
Look for default devices ...
 Found devices in default mode (1)
Access device 009 on bus 001
Get the current device configuration ...
Current configuration number is 1
Use interface number 0
 with class 2
Error: can't use storage command in MessageContent with interface 0; interface class is 2, expected 8. Abort

Hence, I do not see how a could switch to RNDIS mode
> Cc: [e-mail]
> Subject: Re: Re: Re: Re: Re: Dongle USB
>
> Some more info that may help sending AT commands to device,  also may need to read more on usb-modeswitch command
>
> https://openwrt.org/docs/guide-user/network/wan/wwan/at_commands#:~:text=To%....

[Patrick Dupre]

Hello,

I received a lot of recommendations to try to have this LTE dongle working.
I wish to thank you.
But, finally, it still does not work.
I have never been able to turn to RNDIS mode,
probably because the device does not show up in /dev/tty
It is lost?

Thank.

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
===========================================================================

[Marco Moock]

On 27.03.2025 09:30 Patrick Dupre via users wrote:
> I have never been able to turn to RNDIS mode,
> probably because the device does not show up in /dev/tty
> It is lost?

I assume it doesn't support it.
Maybe ask the vendor or check wikidevi etc.

[Patrick Dupre]

> Sent: Thursday, March 27, 2025 at 11:45 AM
> From: "Marco Moock" 
> To: [e-mail]
> Subject: Re: Dongle USB
>
> On 27.03.2025 09:30 Patrick Dupre via users wrote:
> > I have never been able to turn to RNDIS mode,
> > probably because the device does not show up in /dev/tty
> > It is lost?
>
> I assume it doesn't support it.
> Maybe ask the vendor or check wikidevi etc.

The manufacturer says compatible Linux
> --
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Marco Moock]

On 27.03.2025 12:15 Patrick Dupre via users wrote:
> > Sent: Thursday, March 27, 2025 at 11:45 AM
> > From: "Marco Moock" 
> > To: [e-mail]
> > Subject: Re: Dongle USB
> >
> > On 27.03.2025 09:30 Patrick Dupre via users wrote:
> > > I have never been able to turn to RNDIS mode,
> > > probably because the device does not show up in /dev/tty
> > > It is lost?
> >
> > I assume it doesn't support it.
> > Maybe ask the vendor or check wikidevi etc.
>
> The manufacturer says compatible Linux

This doesn't say anything about the operation mode.
I recommend testing it on a windows machine to check if the
disconnection also occurs there.

[Tim]

On Thu, 2025-03-27 at 12:15 +0100, Patrick Dupre via users wrote:
> The manufacturer says compatible Linux

To be blunt, that may just mean it worked on one distro, perhaps one
that doesn't care about what software it installs (not as in malware,
but ones that include non-free things the other distros don't).

It might mean it worked when the user did a lot of work to enable it. 
Without details you won't know.  And there's also a chance that since
they first released it, and it did work on Linux, they've built a new
model with a different chipset.

Did you check if the manufacturer expects you to download a driver from
their website?

[Patrick Dupre]

This is the modem
https://www.alcatelmobile.com/product/mobile-broadband/mobile-wifi/linkkey-l...
Following the instructions
https://techship.com/support/faq/integrating-the-alcatel-ik41-series-m2m-lte...

mmcli --scan-modems
successfully requested to scan devices

mmcli --list-modems
No modems were found

The bizarre thing is that
an older modem onetouch works fine now

It seems working with windows.
but is is not detected correctly with Linux.

Bus 001 Device 011: ID 1bbb:0908 T & A Mobile Phones LinkKey
It is also not detected by
modem-manager-gui

enp0s20f0u11  ethernet  connected               Teucidide
nmcli connection add type gsm ifname '*' con-name '3-sweden' apn 'data.tre.se' connection.autoconnect yes gsm.pin
Connection '3-sweden' (b25e5d45-379a-42fe-b340-7a8477d058d5) successfully added.

nmcli radio
WIFI-HW  WIFI     WWAN-HW  WWAN
missing  enabled  missing  enabled

nmcli device show cdc-wdm
Error: Device 'cdc-wdm' not found.

nmcli connection show
NAME       UUID                                  TYPE      DEVICE
Teucidide  05bc1961-b71a-375a-80f0-d1d43969bfce  ethernet  enp0s20f0u11
lo         2f316384-0efb-49e0-891a-ecbc70275b83  loopback  lo
virbr0     6b485fdf-8003-46d4-bbcf-00e6c3b53151  bridge    virbr0
3-sweden   b25e5d45-379a-42fe-b340-7a8477d058d5  gsm       --

(enp0s20f0u11)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: fe80::68ac:7fff:fe44:5b09
       DNS Servers: 192.168.8.1 fe80::68ac:7fff:fe44:5b09

ip link set enp0s20f0u11 up

ping -4 -c 4 -I enp0s20f0u11 8.8.8.8
PING 8.8.8.8 (8.8.8.8) from 192.168.8.188 enp0s20f0u11: 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3108ms
> On Thu, 2025-03-27 at 12:15 +0100, Patrick Dupre via users wrote:
> > The manufacturer says compatible Linux
>
> To be blunt, that may just mean it worked on one distro, perhaps one
> that doesn't care about what software it installs (not as in malware,
> but ones that include non-free things the other distros don't).
>
> It might mean it worked when the user did a lot of work to enable it.
> Without details you won't know.  And there's also a chance that since
> they first released it, and it did work on Linux, they've built a new
> model with a different chipset.
>
> Did you check if the manufacturer expects you to download a driver from
> their website?
>
> --
>
> uname -rsvp
> Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
>
> Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
> I will only get to see the messages that are posted to the mailing list.

Probably   Modem needs firmware update. They are usually available from website

Sent using the mobile mail app

On 3/27/25 at 8:01 AM, Patrick Dupre via users wrote:
> This is the modem
> https://www.alcatelmobile.com/product/mobile-broadband/mobile-wifi/linkkey-l...
> Following the instructions
> https://techship.com/support/faq/integrating-the-alcatel-ik41-series-m2m-lte...
>
> mmcli --scan-modems
> successfully requested to scan devices
>
> mmcli --list-modems
> No modems were found
>
> The bizarre thing is that
> an older modem onetouch works fine now
>
> It seems working with windows.
> but is is not detected correctly with Linux.
>
> Bus 001 Device 011: ID 1bbb:0908 T & A Mobile Phones LinkKey
> It is also not detected by
> modem-manager-gui
>
> enp0s20f0u11  ethernet  connected               Teucidide
> nmcli connection add type gsm ifname '*' con-name '3-sweden' apn 'data.tre.se' connection.autoconnect yes gsm.pin
> Connection '3-sweden' (b25e5d45-379a-42fe-b340-7a8477d058d5) successfully added.
>
> nmcli radio
> WIFI-HW  WIFI     WWAN-HW  WWAN
> missing  enabled  missing  enabled
>
> nmcli device show cdc-wdm
> Error: Device 'cdc-wdm' not found.
>
> nmcli connection show
> NAME       UUID                                  TYPE      DEVICE
> Teucidide  05bc1961-b71a-375a-80f0-d1d43969bfce  ethernet  enp0s20f0u11
> lo         2f316384-0efb-49e0-891a-ecbc70275b83  loopback  lo
> virbr0     6b485fdf-8003-46d4-bbcf-00e6c3b53151  bridge    virbr0
> 3-sweden   b25e5d45-379a-42fe-b340-7a8477d058d5  gsm       --
>
> (enp0s20f0u11)
>     Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
>          Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
> Current DNS Server: fe80::68ac:7fff:fe44:5b09
>        DNS Servers: 192.168.8.1 fe80::68ac:7fff:fe44:5b09
>
> ip link set enp0s20f0u11 up
>
> ping -4 -c 4 -I enp0s20f0u11 8.8.8.8
> PING 8.8.8.8 (8.8.8.8) from 192.168.8.188 enp0s20f0u11: 56(84) bytes of data.
>
> --- 8.8.8.8 ping statistics ---
> 4 packets transmitted, 0 received, 100% packet loss, time 3108ms
> > On Thu, 2025-03-27 at 12:15 +0100, Patrick Dupre via users wrote:
> > > The manufacturer says compatible Linux
> >
> > To be blunt, that may just mean it worked on one distro, perhaps one
> > that doesn't care about what software it installs (not as in malware,
> > but ones that include non-free things the other distros don't).
> >
> > It might mean it worked when the user did a lot of work to enable it.
> > Without details you won't know.  And there's also a chance that since
> > they first released it, and it did work on Linux, they've built a new
> > model with a different chipset.
> >
> > Did you check if the manufacturer expects you to download a driver from
> > their website?
> >
> > --
> >
> > uname -rsvp
> > Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
> >
> > Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
> > I will only get to see the messages that are posted to the mailing list.
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Patrick Dupre]

Software Version: IK41_RD_02.00_05
It's already the latest version.

I tried from windows

However, it may be 
https://techship.com/?redirect_url=/downloads/alcatel-ik41-series-firmware-v...

But I cannot get it.

Why there is no /dev/ttyUSB0 ?

===========================================================================
 Patrick DUPRÉ                                 | | email: [e-mail]
===========================================================================
> Sent: Thursday, March 27, 2025 at 4:05 PM
> From: "None via users" 
> To: "Community support for Fedora users" 
> Cc: [e-mail]
> Subject: Re: Re: Dongle USB
>
> Probably   Modem needs firmware update. They are usually available from website
>
> Sent using the mobile mail app
>
> On 3/27/25 at 8:01 AM, Patrick Dupre via users wrote:
> > This is the modem
> > https://www.alcatelmobile.com/product/mobile-broadband/mobile-wifi/linkkey-l...
> > Following the instructions
> > https://techship.com/support/faq/integrating-the-alcatel-ik41-series-m2m-lte...
> >
> > mmcli --scan-modems
> > successfully requested to scan devices
> >
> > mmcli --list-modems
> > No modems were found
> >
> > The bizarre thing is that
> > an older modem onetouch works fine now
> >
> > It seems working with windows.
> > but is is not detected correctly with Linux.
> >
> > Bus 001 Device 011: ID 1bbb:0908 T & A Mobile Phones LinkKey
> > It is also not detected by
> > modem-manager-gui
> >
> > enp0s20f0u11  ethernet  connected               Teucidide
> > nmcli connection add type gsm ifname '*' con-name '3-sweden' apn 'data.tre.se' connection.autoconnect yes gsm.pin
> > Connection '3-sweden' (b25e5d45-379a-42fe-b340-7a8477d058d5) successfully added.
> >
> > nmcli radio
> > WIFI-HW  WIFI     WWAN-HW  WWAN
> > missing  enabled  missing  enabled
> >
> > nmcli device show cdc-wdm
> > Error: Device 'cdc-wdm' not found.
> >
> > nmcli connection show
> > NAME       UUID                                  TYPE      DEVICE
> > Teucidide  05bc1961-b71a-375a-80f0-d1d43969bfce  ethernet  enp0s20f0u11
> > lo         2f316384-0efb-49e0-891a-ecbc70275b83  loopback  lo
> > virbr0     6b485fdf-8003-46d4-bbcf-00e6c3b53151  bridge    virbr0
> > 3-sweden   b25e5d45-379a-42fe-b340-7a8477d058d5  gsm       --
> >
> > (enp0s20f0u11)
> >     Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
> >          Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
> > Current DNS Server: fe80::68ac:7fff:fe44:5b09
> >        DNS Servers: 192.168.8.1 fe80::68ac:7fff:fe44:5b09
> >
> > ip link set enp0s20f0u11 up
> >
> > ping -4 -c 4 -I enp0s20f0u11 8.8.8.8
> > PING 8.8.8.8 (8.8.8.8) from 192.168.8.188 enp0s20f0u11: 56(84) bytes of data.
> >
> > --- 8.8.8.8 ping statistics ---
> > 4 packets transmitted, 0 received, 100% packet loss, time 3108ms
> > > On Thu, 2025-03-27 at 12:15 +0100, Patrick Dupre via users wrote:
> > > > The manufacturer says compatible Linux
> > >
> > > To be blunt, that may just mean it worked on one distro, perhaps one
> > > that doesn't care about what software it installs (not as in malware,
> > > but ones that include non-free things the other distros don't).
> > >
> > > It might mean it worked when the user did a lot of work to enable it.
> > > Without details you won't know.  And there's also a chance that since
> > > they first released it, and it did work on Linux, they've built a new
> > > model with a different chipset.
> > >
> > > Did you check if the manufacturer expects you to download a driver from
> > > their website?
> > >
> > > --
> > >
> > > uname -rsvp
> > > Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
> > >
> > > Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
> > > I will only get to see the messages that are posted to the mailing list.
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Marco Moock]

On 27.03.2025 16:56 Patrick Dupre via users wrote:
> Why there is no /dev/ttyUSB0 ?

If it doesn't act as a modem (as it does), there is no need for a
serial device.
It currently operates as an ethernet adapter.

lsusb search for PID like 1bbb vid like 00bc

The cdc_mbin kernel module may be needed newer kernel have it
Think modem by default uses mbin,
RNDIS is recommended

Use minicom to pass AT command to modem to switch modem like
AT=USBMODE=1

Sent using the mobile mail app

On 3/27/25 at 8:57 AM, Patrick Dupre via users wrote:
> Software Version: IK41_RD_02.00_05
> It's already the latest version.
>
> I tried from windows
>
> However, it may be 
> https://techship.com/?redirect_url=/downloads/alcatel-ik41-series-firmware-v...
>
> But I cannot get it.
>
> Why there is no /dev/ttyUSB0 ?
>
> ===========================================================================
>  Patrick DUPRÉ                                 | | email: [e-mail]
> ===========================================================================
> > Sent: Thursday, March 27, 2025 at 4:05 PM
> > From: "None via users" 
> > To: "Community support for Fedora users" 
> > Cc: [e-mail]
> > Subject: Re: Re: Dongle USB
> >
> > Probably   Modem needs firmware update. They are usually available from website
> >
> > Sent using the mobile mail app
> >
> > On 3/27/25 at 8:01 AM, Patrick Dupre via users wrote:
> > > This is the modem
> > > https://www.alcatelmobile.com/product/mobile-broadband/mobile-wifi/linkkey-l...
> > > Following the instructions
> > > https://techship.com/support/faq/integrating-the-alcatel-ik41-series-m2m-lte...
> > >
> > > mmcli --scan-modems
> > > successfully requested to scan devices
> > >
> > > mmcli --list-modems
> > > No modems were found
> > >
> > > The bizarre thing is that
> > > an older modem onetouch works fine now
> > >
> > > It seems working with windows.
> > > but is is not detected correctly with Linux.
> > >
> > > Bus 001 Device 011: ID 1bbb:0908 T & A Mobile Phones LinkKey
> > > It is also not detected by
> > > modem-manager-gui
> > >
> > > enp0s20f0u11  ethernet  connected               Teucidide
> > > nmcli connection add type gsm ifname '*' con-name '3-sweden' apn 'data.tre.se' connection.autoconnect yes gsm.pin
> > > Connection '3-sweden' (b25e5d45-379a-42fe-b340-7a8477d058d5) successfully added.
> > >
> > > nmcli radio
> > > WIFI-HW  WIFI     WWAN-HW  WWAN
> > > missing  enabled  missing  enabled
> > >
> > > nmcli device show cdc-wdm
> > > Error: Device 'cdc-wdm' not found.
> > >
> > > nmcli connection show
> > > NAME       UUID                                  TYPE      DEVICE
> > > Teucidide  05bc1961-b71a-375a-80f0-d1d43969bfce  ethernet  enp0s20f0u11
> > > lo         2f316384-0efb-49e0-891a-ecbc70275b83  loopback  lo
> > > virbr0     6b485fdf-8003-46d4-bbcf-00e6c3b53151  bridge    virbr0
> > > 3-sweden   b25e5d45-379a-42fe-b340-7a8477d058d5  gsm       --
> > >
> > > (enp0s20f0u11)
> > >     Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
> > >          Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
> > > Current DNS Server: fe80::68ac:7fff:fe44:5b09
> > >        DNS Servers: 192.168.8.1 fe80::68ac:7fff:fe44:5b09
> > >
> > > ip link set enp0s20f0u11 up
> > >
> > > ping -4 -c 4 -I enp0s20f0u11 8.8.8.8
> > > PING 8.8.8.8 (8.8.8.8) from 192.168.8.188 enp0s20f0u11: 56(84) bytes of data.
> > >
> > > --- 8.8.8.8 ping statistics ---
> > > 4 packets transmitted, 0 received, 100% packet loss, time 3108ms
> > > > On Thu, 2025-03-27 at 12:15 +0100, Patrick Dupre via users wrote:
> > > > > The manufacturer says compatible Linux
> > > >
> > > > To be blunt, that may just mean it worked on one distro, perhaps one
> > > > that doesn't care about what software it installs (not as in malware,
> > > > but ones that include non-free things the other distros don't).
> > > >
> > > > It might mean it worked when the user did a lot of work to enable it.
> > > > Without details you won't know.  And there's also a chance that since
> > > > they first released it, and it did work on Linux, they've built a new
> > > > model with a different chipset.
> > > >
> > > > Did you check if the manufacturer expects you to download a driver from
> > > > their website?
> > > >
> > > > --
> > > >
> > > > uname -rsvp
> > > > Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
> > > >
> > > > Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
> > > > I will only get to see the messages that are posted to the mailing list.
> > >
> > > -- 
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Patrick Dupre]

> lsusb search for PID like 1bbb vid like 00bc
>
> The cdc_mbin kernel module may be needed newer kernel have it
> Think modem by default uses mbin,
> RNDIS is recommended
>
> Use minicom to pass AT command to modem to switch modem like
> AT=USBMODE=1

I guess AT+USNMODE=1 ?

To /dev/bus/usb/001/063 ?
Bus 001 Device 063: ID 1bbb:0908 T & A Mobile Phones LinkKey

minicom
Cannot create lockfile for /dev/modem: No such file or directory

minicom -s

| Serial port setup
| Modem and dialing
??

I do not have cdc_mbin
Is it available in fedora ?

I am a bit confused.
> Sent using the mobile mail app
>
> On 3/27/25 at 8:57 AM, Patrick Dupre via users wrote:
> > Software Version: IK41_RD_02.00_05
> > It's already the latest version.
> >
> > I tried from windows
> >
> > However, it may be 
> > https://techship.com/?redirect_url=/downloads/alcatel-ik41-series-firmware-v...
> >
> > But I cannot get it.
> >
> > Why there is no /dev/ttyUSB0 ?
> >
> > ===========================================================================
> >  Patrick DUPRÉ                                 | | email: [e-mail]
> > ===========================================================================
> > > Sent: Thursday, March 27, 2025 at 4:05 PM
> > > From: "None via users" 
> > > To: "Community support for Fedora users" 
> > > Cc: [e-mail]
> > > Subject: Re: Re: Dongle USB
> > >
> > > Probably   Modem needs firmware update. They are usually available from website
> > >
> > > Sent using the mobile mail app
> > >
> > > On 3/27/25 at 8:01 AM, Patrick Dupre via users wrote:
> > > > This is the modem
> > > > https://www.alcatelmobile.com/product/mobile-broadband/mobile-wifi/linkkey-l...
> > > > Following the instructions
> > > > https://techship.com/support/faq/integrating-the-alcatel-ik41-series-m2m-lte...
> > > >
> > > > mmcli --scan-modems
> > > > successfully requested to scan devices
> > > >
> > > > mmcli --list-modems
> > > > No modems were found
> > > >
> > > > The bizarre thing is that
> > > > an older modem onetouch works fine now
> > > >
> > > > It seems working with windows.
> > > > but is is not detected correctly with Linux.
> > > >
> > > > Bus 001 Device 011: ID 1bbb:0908 T & A Mobile Phones LinkKey
> > > > It is also not detected by
> > > > modem-manager-gui
> > > >
> > > > enp0s20f0u11  ethernet  connected               Teucidide
> > > > nmcli connection add type gsm ifname '*' con-name '3-sweden' apn 'data.tre.se' connection.autoconnect yes gsm.pin
> > > > Connection '3-sweden' (b25e5d45-379a-42fe-b340-7a8477d058d5) successfully added.
> > > >
> > > > nmcli radio
> > > > WIFI-HW  WIFI     WWAN-HW  WWAN
> > > > missing  enabled  missing  enabled
> > > >
> > > > nmcli device show cdc-wdm
> > > > Error: Device 'cdc-wdm' not found.
> > > >
> > > > nmcli connection show
> > > > NAME       UUID                                  TYPE      DEVICE
> > > > Teucidide  05bc1961-b71a-375a-80f0-d1d43969bfce  ethernet  enp0s20f0u11
> > > > lo         2f316384-0efb-49e0-891a-ecbc70275b83  loopback  lo
> > > > virbr0     6b485fdf-8003-46d4-bbcf-00e6c3b53151  bridge    virbr0
> > > > 3-sweden   b25e5d45-379a-42fe-b340-7a8477d058d5  gsm       --
> > > >
> > > > (enp0s20f0u11)
> > > >     Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
> > > >          Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
> > > > Current DNS Server: fe80::68ac:7fff:fe44:5b09
> > > >        DNS Servers: 192.168.8.1 fe80::68ac:7fff:fe44:5b09
> > > >
> > > > ip link set enp0s20f0u11 up
> > > >
> > > > ping -4 -c 4 -I enp0s20f0u11 8.8.8.8
> > > > PING 8.8.8.8 (8.8.8.8) from 192.168.8.188 enp0s20f0u11: 56(84) bytes of data.
> > > >
> > > > --- 8.8.8.8 ping statistics ---
> > > > 4 packets transmitted, 0 received, 100% packet loss, time 3108ms
> > > > > On Thu, 2025-03-27 at 12:15 +0100, Patrick Dupre via users wrote:
> > > > > > The manufacturer says compatible Linux
> > > > >
> > > > > To be blunt, that may just mean it worked on one distro, perhaps one
> > > > > that doesn't care about what software it installs (not as in malware,
> > > > > but ones that include non-free things the other distros don't).
> > > > >
> > > > > It might mean it worked when the user did a lot of work to enable it.
> > > > > Without details you won't know.  And there's also a chance that since
> > > > > they first released it, and it did work on Linux, they've built a new
> > > > > model with a different chipset.
> > > > >
> > > > > Did you check if the manufacturer expects you to download a driver from
> > > > > their website?
> > > > >
> > > > > --
> > > > >
> > > > > uname -rsvp
> > > > > Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
> > > > >
> > > > > Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
> > > > > I will only get to see the messages that are posted to the mailing list.
> > > >
> > > > -- 
> > > > _______________________________________________
> > > > users mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > 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/[e-mail]
> > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > >
> > > -- 
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Marco Moock]

Am 27.03.2025 um 20:28:31 Uhr schrieb Patrick Dupre via users:
> I guess AT+USNMODE=1 ?
>
> To /dev/bus/usb/001/063 ?
> Bus 001 Device 063: ID 1bbb:0908 T & A Mobile Phones LinkKey

If that device doesn't provide a serial modem, you can't enter AT
commands.
> minicom
> Cannot create lockfile for /dev/modem: No such file or directory

This would be set to the serial device, if there were one.
If there is no ttyACM ot ttyUSB, no chance.

You can try sudo modprobe cdc_mbim 
lsmod |grep cdc_mbim
To verify

Sent using the mobile mail app

On 3/27/25 at 12:29 PM, Patrick Dupre via users wrote:
> > lsusb search for PID like 1bbb vid like 00bc
> >
> > The cdc_mbin kernel module may be needed newer kernel have it
> > Think modem by default uses mbin,
> > RNDIS is recommended
> >
> > Use minicom to pass AT command to modem to switch modem like
> > AT=USBMODE=1
>
> I guess AT+USNMODE=1 ?
>
> To /dev/bus/usb/001/063 ?
> Bus 001 Device 063: ID 1bbb:0908 T & A Mobile Phones LinkKey
>
> minicom
> Cannot create lockfile for /dev/modem: No such file or directory
>
> minicom -s
>
> | Serial port setup
> | Modem and dialing
> ??
>
> I do not have cdc_mbin
> Is it available in fedora ?
>
> I am a bit confused.
> > Sent using the mobile mail app
> >
> > On 3/27/25 at 8:57 AM, Patrick Dupre via users wrote:
> > > Software Version: IK41_RD_02.00_05
> > > It's already the latest version.
> > >
> > > I tried from windows
> > >
> > > However, it may be 
> > > https://techship.com/?redirect_url=/downloads/alcatel-ik41-series-firmware-v...
> > >
> > > But I cannot get it.
> > >
> > > Why there is no /dev/ttyUSB0 ?
> > >
> > > ===========================================================================
> > >  Patrick DUPRÉ                                 | | email: [e-mail]
> > > ===========================================================================
> > > > Sent: Thursday, March 27, 2025 at 4:05 PM
> > > > From: "None via users" 
> > > > To: "Community support for Fedora users" 
> > > > Cc: [e-mail]
> > > > Subject: Re: Re: Dongle USB
> > > >
> > > > Probably   Modem needs firmware update. They are usually available from website
> > > >
> > > > Sent using the mobile mail app
> > > >
> > > > On 3/27/25 at 8:01 AM, Patrick Dupre via users wrote:
> > > > > This is the modem
> > > > > https://www.alcatelmobile.com/product/mobile-broadband/mobile-wifi/linkkey-l...
> > > > > Following the instructions
> > > > > https://techship.com/support/faq/integrating-the-alcatel-ik41-series-m2m-lte...
> > > > >
> > > > > mmcli --scan-modems
> > > > > successfully requested to scan devices
> > > > >
> > > > > mmcli --list-modems
> > > > > No modems were found
> > > > >
> > > > > The bizarre thing is that
> > > > > an older modem onetouch works fine now
> > > > >
> > > > > It seems working with windows.
> > > > > but is is not detected correctly with Linux.
> > > > >
> > > > > Bus 001 Device 011: ID 1bbb:0908 T & A Mobile Phones LinkKey
> > > > > It is also not detected by
> > > > > modem-manager-gui
> > > > >
> > > > > enp0s20f0u11  ethernet  connected               Teucidide
> > > > > nmcli connection add type gsm ifname '*' con-name '3-sweden' apn 'data.tre.se' connection.autoconnect yes gsm.pin
> > > > > Connection '3-sweden' (b25e5d45-379a-42fe-b340-7a8477d058d5) successfully added.
> > > > >
> > > > > nmcli radio
> > > > > WIFI-HW  WIFI     WWAN-HW  WWAN
> > > > > missing  enabled  missing  enabled
> > > > >
> > > > > nmcli device show cdc-wdm
> > > > > Error: Device 'cdc-wdm' not found.
> > > > >
> > > > > nmcli connection show
> > > > > NAME       UUID                                  TYPE      DEVICE
> > > > > Teucidide  05bc1961-b71a-375a-80f0-d1d43969bfce  ethernet  enp0s20f0u11
> > > > > lo         2f316384-0efb-49e0-891a-ecbc70275b83  loopback  lo
> > > > > virbr0     6b485fdf-8003-46d4-bbcf-00e6c3b53151  bridge    virbr0
> > > > > 3-sweden   b25e5d45-379a-42fe-b340-7a8477d058d5  gsm       --
> > > > >
> > > > > (enp0s20f0u11)
> > > > >     Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
> > > > >          Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
> > > > > Current DNS Server: fe80::68ac:7fff:fe44:5b09
> > > > >        DNS Servers: 192.168.8.1 fe80::68ac:7fff:fe44:5b09
> > > > >
> > > > > ip link set enp0s20f0u11 up
> > > > >
> > > > > ping -4 -c 4 -I enp0s20f0u11 8.8.8.8
> > > > > PING 8.8.8.8 (8.8.8.8) from 192.168.8.188 enp0s20f0u11: 56(84) bytes of data.
> > > > >
> > > > > --- 8.8.8.8 ping statistics ---
> > > > > 4 packets transmitted, 0 received, 100% packet loss, time 3108ms
> > > > > > On Thu, 2025-03-27 at 12:15 +0100, Patrick Dupre via users wrote:
> > > > > > > The manufacturer says compatible Linux
> > > > > >
> > > > > > To be blunt, that may just mean it worked on one distro, perhaps one
> > > > > > that doesn't care about what software it installs (not as in malware,
> > > > > > but ones that include non-free things the other distros don't).
> > > > > >
> > > > > > It might mean it worked when the user did a lot of work to enable it.
> > > > > > Without details you won't know.  And there's also a chance that since
> > > > > > they first released it, and it did work on Linux, they've built a new
> > > > > > model with a different chipset.
> > > > > >
> > > > > > Did you check if the manufacturer expects you to download a driver from
> > > > > > their website?
> > > > > >
> > > > > > --
> > > > > >
> > > > > > uname -rsvp
> > > > > > Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
> > > > > >
> > > > > > Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
> > > > > > I will only get to see the messages that are posted to the mailing list.
> > > > >
> > > > > -- 
> > > > > _______________________________________________
> > > > > users mailing list -- [e-mail]
> > > > > To unsubscribe send an email to [e-mail]
> > > > > 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/[e-mail]
> > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > >
> > > > -- 
> > > > _______________________________________________
> > > > users mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > 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/[e-mail]
> > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > >
> > > -- 
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Patrick Dupre]

> You can try sudo modprobe cdc_mbim 
> lsmod |grep cdc_mbim
> To verify

OK Good,

cdc_mbim               24576  0
cdc_wdm                36864  1 cdc_mbim
cdc_ncm                53248  1 cdc_mbim
usbnet                 65536  4 cdc_mbim,cdc_ncm,rndis_host,cdc_ether

What is next ?
See below
> Sent using the mobile mail app
>
> On 3/27/25 at 12:29 PM, Patrick Dupre via users wrote:
> > > lsusb search for PID like 1bbb vid like 00bc
> > >
> > > The cdc_mbin kernel module may be needed newer kernel have it
> > > Think modem by default uses mbin,
> > > RNDIS is recommended
> > >
> > > Use minicom to pass AT command to modem to switch modem like
> > > AT=USBMODE=1
> >
> > I guess AT+USNMODE=1 ?
> >
> > To /dev/bus/usb/001/063 ?
> > Bus 001 Device 063: ID 1bbb:0908 T & A Mobile Phones LinkKey
> >
> > minicom
> > Cannot create lockfile for /dev/modem: No such file or directory
> >
> > minicom -s
> >
> > | Serial port setup
> > | Modem and dialing
> > ??
> >
> > I do not have cdc_mbin
> > Is it available in fedora ?
> >
> > I am a bit confused.
> > > Sent using the mobile mail app
> > >
> > > On 3/27/25 at 8:57 AM, Patrick Dupre via users wrote:
> > > > Software Version: IK41_RD_02.00_05
> > > > It's already the latest version.
> > > >
> > > > I tried from windows
> > > >
> > > > However, it may be 
> > > > https://techship.com/?redirect_url=/downloads/alcatel-ik41-series-firmware-v...
> > > >
> > > > But I cannot get it.
> > > >
> > > > Why there is no /dev/ttyUSB0 ?
> > > >
> > > > ===========================================================================
> > > >  Patrick DUPRÉ                                 | | email: [e-mail]
> > > > ===========================================================================
> > > > > Sent: Thursday, March 27, 2025 at 4:05 PM
> > > > > From: "None via users" 
> > > > > To: "Community support for Fedora users" 
> > > > > Cc: [e-mail]
> > > > > Subject: Re: Re: Dongle USB
> > > > >
> > > > > Probably   Modem needs firmware update. They are usually available from website
> > > > >
> > > > > Sent using the mobile mail app
> > > > >
> > > > > On 3/27/25 at 8:01 AM, Patrick Dupre via users wrote:
> > > > > > This is the modem
> > > > > > https://www.alcatelmobile.com/product/mobile-broadband/mobile-wifi/linkkey-l...
> > > > > > Following the instructions
> > > > > > https://techship.com/support/faq/integrating-the-alcatel-ik41-series-m2m-lte...
> > > > > >
> > > > > > mmcli --scan-modems
> > > > > > successfully requested to scan devices
> > > > > >
> > > > > > mmcli --list-modems
> > > > > > No modems were found
> > > > > >
> > > > > > The bizarre thing is that
> > > > > > an older modem onetouch works fine now
> > > > > >
> > > > > > It seems working with windows.
> > > > > > but is is not detected correctly with Linux.
> > > > > >
> > > > > > Bus 001 Device 011: ID 1bbb:0908 T & A Mobile Phones LinkKey
> > > > > > It is also not detected by
> > > > > > modem-manager-gui
> > > > > >
> > > > > > enp0s20f0u11  ethernet  connected               Teucidide
> > > > > > nmcli connection add type gsm ifname '*' con-name '3-sweden' apn 'data.tre.se' connection.autoconnect yes gsm.pin
> > > > > > Connection '3-sweden' (b25e5d45-379a-42fe-b340-7a8477d058d5) successfully added.
> > > > > >
> > > > > > nmcli radio
> > > > > > WIFI-HW  WIFI     WWAN-HW  WWAN
> > > > > > missing  enabled  missing  enabled
> > > > > >
> > > > > > nmcli device show cdc-wdm
> > > > > > Error: Device 'cdc-wdm' not found.
> > > > > >
> > > > > > nmcli connection show
> > > > > > NAME       UUID                                  TYPE      DEVICE
> > > > > > Teucidide  05bc1961-b71a-375a-80f0-d1d43969bfce  ethernet  enp0s20f0u11
> > > > > > lo         2f316384-0efb-49e0-891a-ecbc70275b83  loopback  lo
> > > > > > virbr0     6b485fdf-8003-46d4-bbcf-00e6c3b53151  bridge    virbr0
> > > > > > 3-sweden   b25e5d45-379a-42fe-b340-7a8477d058d5  gsm       --
> > > > > >
> > > > > > (enp0s20f0u11)
> > > > > >     Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
> > > > > >          Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
> > > > > > Current DNS Server: fe80::68ac:7fff:fe44:5b09
> > > > > >        DNS Servers: 192.168.8.1 fe80::68ac:7fff:fe44:5b09
> > > > > >
> > > > > > ip link set enp0s20f0u11 up
> > > > > >
> > > > > > ping -4 -c 4 -I enp0s20f0u11 8.8.8.8
> > > > > > PING 8.8.8.8 (8.8.8.8) from 192.168.8.188 enp0s20f0u11: 56(84) bytes of data.
> > > > > >
> > > > > > --- 8.8.8.8 ping statistics ---
> > > > > > 4 packets transmitted, 0 received, 100% packet loss, time 3108ms
> > > > > >
> > > > > > > On Thu, 2025-03-27 at 12:15 +0100, Patrick Dupre via users wrote:
> > > > > > > > The manufacturer says compatible Linux
> > > > > > >
> > > > > > > To be blunt, that may just mean it worked on one distro, perhaps one
> > > > > > > that doesn't care about what software it installs (not as in malware,
> > > > > > > but ones that include non-free things the other distros don't).
> > > > > > >
> > > > > > > It might mean it worked when the user did a lot of work to enable it.
> > > > > > > Without details you won't know.  And there's also a chance that since
> > > > > > > they first released it, and it did work on Linux, they've built a new
> > > > > > > model with a different chipset.
> > > > > > >
> > > > > > > Did you check if the manufacturer expects you to download a driver from
> > > > > > > their website?
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > uname -rsvp
> > > > > > > Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
> > > > > > >
> > > > > > > Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
> > > > > > > I will only get to see the messages that are posted to the mailing list.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > users mailing list -- [e-mail]
> > > > > > To unsubscribe send an email to [e-mail]
> > > > > > 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/[e-mail]
> > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > >
> > > > > -- 
> > > > > _______________________________________________
> > > > > users mailing list -- [e-mail]
> > > > > To unsubscribe send an email to [e-mail]
> > > > > 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/[e-mail]
> > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > >
> > > > -- 
> > > > _______________________________________________
> > > > users mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > 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/[e-mail]
> > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > >
> > > -- 
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Patrick Dupre]

The bizarre thing (I check with another computer).
is that it works during ~1 mn, and it stops to work.

The only difference that I noted.
is

When it works
Link 18 (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::34a3:96ff:feba:2f41

When it stops to work

Link 18 (enp0s20f0u11)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS
                    DNSSEC=no/unsupported
Current DNS Server: fe80::34a3:96ff:feba:2f41
       DNS Servers: 192.168.8.1 fe80::34a3:96ff:feba:2f41

The current DNS switched from ipv4 to ivp6, and it stops to work ?
> You can try sudo modprobe cdc_mbim 
> lsmod |grep cdc_mbim
> To verify
>
> Sent using the mobile mail app
>
> On 3/27/25 at 12:29 PM, Patrick Dupre via users wrote:
> > > lsusb search for PID like 1bbb vid like 00bc
> > >
> > > The cdc_mbin kernel module may be needed newer kernel have it
> > > Think modem by default uses mbin,
> > > RNDIS is recommended
> > >
> > > Use minicom to pass AT command to modem to switch modem like
> > > AT=USBMODE=1
> >
> > I guess AT+USNMODE=1 ?
> >
> > To /dev/bus/usb/001/063 ?
> > Bus 001 Device 063: ID 1bbb:0908 T & A Mobile Phones LinkKey
> >
> > minicom
> > Cannot create lockfile for /dev/modem: No such file or directory
> >
> > minicom -s
> >
> > | Serial port setup
> > | Modem and dialing
> > ??
> >
> > I do not have cdc_mbin
> > Is it available in fedora ?
> >
> > I am a bit confused.
> > > Sent using the mobile mail app
> > >
> > > On 3/27/25 at 8:57 AM, Patrick Dupre via users wrote:
> > > > Software Version: IK41_RD_02.00_05
> > > > It's already the latest version.
> > > >
> > > > I tried from windows
> > > >
> > > > However, it may be 
> > > > https://techship.com/?redirect_url=/downloads/alcatel-ik41-series-firmware-v...
> > > >
> > > > But I cannot get it.
> > > >
> > > > Why there is no /dev/ttyUSB0 ?
> > > >
> > > > ===========================================================================
> > > >  Patrick DUPRÉ                                 | | email: [e-mail]
> > > > ===========================================================================
> > > > > Sent: Thursday, March 27, 2025 at 4:05 PM
> > > > > From: "None via users" 
> > > > > To: "Community support for Fedora users" 
> > > > > Cc: [e-mail]
> > > > > Subject: Re: Re: Dongle USB
> > > > >
> > > > > Probably   Modem needs firmware update. They are usually available from website
> > > > >
> > > > > Sent using the mobile mail app
> > > > >
> > > > > On 3/27/25 at 8:01 AM, Patrick Dupre via users wrote:
> > > > > > This is the modem
> > > > > > https://www.alcatelmobile.com/product/mobile-broadband/mobile-wifi/linkkey-l...
> > > > > > Following the instructions
> > > > > > https://techship.com/support/faq/integrating-the-alcatel-ik41-series-m2m-lte...
> > > > > >
> > > > > > mmcli --scan-modems
> > > > > > successfully requested to scan devices
> > > > > >
> > > > > > mmcli --list-modems
> > > > > > No modems were found
> > > > > >
> > > > > > The bizarre thing is that
> > > > > > an older modem onetouch works fine now
> > > > > >
> > > > > > It seems working with windows.
> > > > > > but is is not detected correctly with Linux.
> > > > > >
> > > > > > Bus 001 Device 011: ID 1bbb:0908 T & A Mobile Phones LinkKey
> > > > > > It is also not detected by
> > > > > > modem-manager-gui
> > > > > >
> > > > > > enp0s20f0u11  ethernet  connected               Teucidide
> > > > > > nmcli connection add type gsm ifname '*' con-name '3-sweden' apn 'data.tre.se' connection.autoconnect yes gsm.pin
> > > > > > Connection '3-sweden' (b25e5d45-379a-42fe-b340-7a8477d058d5) successfully added.
> > > > > >
> > > > > > nmcli radio
> > > > > > WIFI-HW  WIFI     WWAN-HW  WWAN
> > > > > > missing  enabled  missing  enabled
> > > > > >
> > > > > > nmcli device show cdc-wdm
> > > > > > Error: Device 'cdc-wdm' not found.
> > > > > >
> > > > > > nmcli connection show
> > > > > > NAME       UUID                                  TYPE      DEVICE
> > > > > > Teucidide  05bc1961-b71a-375a-80f0-d1d43969bfce  ethernet  enp0s20f0u11
> > > > > > lo         2f316384-0efb-49e0-891a-ecbc70275b83  loopback  lo
> > > > > > virbr0     6b485fdf-8003-46d4-bbcf-00e6c3b53151  bridge    virbr0
> > > > > > 3-sweden   b25e5d45-379a-42fe-b340-7a8477d058d5  gsm       --
> > > > > >
> > > > > > (enp0s20f0u11)
> > > > > >     Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
> > > > > >          Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
> > > > > > Current DNS Server: fe80::68ac:7fff:fe44:5b09
> > > > > >        DNS Servers: 192.168.8.1 fe80::68ac:7fff:fe44:5b09
> > > > > >
> > > > > > ip link set enp0s20f0u11 up
> > > > > >
> > > > > > ping -4 -c 4 -I enp0s20f0u11 8.8.8.8
> > > > > > PING 8.8.8.8 (8.8.8.8) from 192.168.8.188 enp0s20f0u11: 56(84) bytes of data.
> > > > > >
> > > > > > --- 8.8.8.8 ping statistics ---
> > > > > > 4 packets transmitted, 0 received, 100% packet loss, time 3108ms
> > > > > >
> > > > > > > On Thu, 2025-03-27 at 12:15 +0100, Patrick Dupre via users wrote:
> > > > > > > > The manufacturer says compatible Linux
> > > > > > >
> > > > > > > To be blunt, that may just mean it worked on one distro, perhaps one
> > > > > > > that doesn't care about what software it installs (not as in malware,
> > > > > > > but ones that include non-free things the other distros don't).
> > > > > > >
> > > > > > > It might mean it worked when the user did a lot of work to enable it.
> > > > > > > Without details you won't know.  And there's also a chance that since
> > > > > > > they first released it, and it did work on Linux, they've built a new
> > > > > > > model with a different chipset.
> > > > > > >
> > > > > > > Did you check if the manufacturer expects you to download a driver from
> > > > > > > their website?
> > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > > uname -rsvp
> > > > > > > Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
> > > > > > >
> > > > > > > Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
> > > > > > > I will only get to see the messages that are posted to the mailing list.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > users mailing list -- [e-mail]
> > > > > > To unsubscribe send an email to [e-mail]
> > > > > > 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/[e-mail]
> > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > >
> > > > > -- 
> > > > > _______________________________________________
> > > > > users mailing list -- [e-mail]
> > > > > To unsubscribe send an email to [e-mail]
> > > > > 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/[e-mail]
> > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > >
> > > > -- 
> > > > _______________________________________________
> > > > users mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > 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/[e-mail]
> > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > >
> > > -- 
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

Interesting, my opinion sounds like device is resetting probably faulty driver., firmware. When it resets it losses connection.

Sent using the mobile mail app

On 3/27/25 at 4:08 PM, Patrick Dupre via users wrote:
> The bizarre thing (I check with another computer).
> is that it works during ~1 mn, and it stops to work.
>
> The only difference that I noted.
> is
>
> When it works
> Link 18 (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::34a3:96ff:feba:2f41
>
> When it stops to work
>
> Link 18 (enp0s20f0u11)
>     Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
>          Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS
>                     DNSSEC=no/unsupported
> Current DNS Server: fe80::34a3:96ff:feba:2f41
>        DNS Servers: 192.168.8.1 fe80::34a3:96ff:feba:2f41
>
> The current DNS switched from ipv4 to ivp6, and it stops to work ?
> > You can try sudo modprobe cdc_mbim 
> > lsmod |grep cdc_mbim
> > To verify
> >
> > Sent using the mobile mail app
> >
> > On 3/27/25 at 12:29 PM, Patrick Dupre via users wrote:
> > > > lsusb search for PID like 1bbb vid like 00bc
> > > >
> > > > The cdc_mbin kernel module may be needed newer kernel have it
> > > > Think modem by default uses mbin,
> > > > RNDIS is recommended
> > > >
> > > > Use minicom to pass AT command to modem to switch modem like
> > > > AT=USBMODE=1
> > >
> > > I guess AT+USNMODE=1 ?
> > >
> > > To /dev/bus/usb/001/063 ?
> > > Bus 001 Device 063: ID 1bbb:0908 T & A Mobile Phones LinkKey
> > >
> > > minicom
> > > Cannot create lockfile for /dev/modem: No such file or directory
> > >
> > > minicom -s
> > >
> > > | Serial port setup
> > > | Modem and dialing
> > > ??
> > >
> > > I do not have cdc_mbin
> > > Is it available in fedora ?
> > >
> > > I am a bit confused.
> > > > Sent using the mobile mail app
> > > >
> > > > On 3/27/25 at 8:57 AM, Patrick Dupre via users wrote:
> > > > > Software Version: IK41_RD_02.00_05
> > > > > It's already the latest version.
> > > > >
> > > > > I tried from windows
> > > > >
> > > > > However, it may be 
> > > > > https://techship.com/?redirect_url=/downloads/alcatel-ik41-series-firmware-v...
> > > > >
> > > > > But I cannot get it.
> > > > >
> > > > > Why there is no /dev/ttyUSB0 ?
> > > > >
> > > > > ===========================================================================
> > > > >  Patrick DUPRÉ                                 | | email: [e-mail]
> > > > > ===========================================================================
> > > > > > Sent: Thursday, March 27, 2025 at 4:05 PM
> > > > > > From: "None via users" 
> > > > > > To: "Community support for Fedora users" 
> > > > > > Cc: [e-mail]
> > > > > > Subject: Re: Re: Dongle USB
> > > > > >
> > > > > > Probably   Modem needs firmware update. They are usually available from website
> > > > > >
> > > > > > Sent using the mobile mail app
> > > > > >
> > > > > > On 3/27/25 at 8:01 AM, Patrick Dupre via users wrote:
> > > > > >
> > > > > > > This is the modem
> > > > > > > https://www.alcatelmobile.com/product/mobile-broadband/mobile-wifi/linkkey-l...
> > > > > > > Following the instructions
> > > > > > > https://techship.com/support/faq/integrating-the-alcatel-ik41-series-m2m-lte...
> > > > > > > 
> > > > > > > mmcli --scan-modems
> > > > > > > successfully requested to scan devices
> > > > > > > 
> > > > > > > mmcli --list-modems
> > > > > > > No modems were found
> > > > > > > 
> > > > > > > The bizarre thing is that
> > > > > > > an older modem onetouch works fine now
> > > > > > > 
> > > > > > > It seems working with windows.
> > > > > > > but is is not detected correctly with Linux.
> > > > > > > 
> > > > > > > Bus 001 Device 011: ID 1bbb:0908 T & A Mobile Phones LinkKey
> > > > > > > It is also not detected by
> > > > > > > modem-manager-gui
> > > > > > > 
> > > > > > > enp0s20f0u11  ethernet  connected               Teucidide
> > > > > > > nmcli connection add type gsm ifname '*' con-name '3-sweden' apn 'data.tre.se' connection.autoconnect yes gsm.pin
> > > > > > > Connection '3-sweden' (b25e5d45-379a-42fe-b340-7a8477d058d5) successfully added.
> > > > > > > 
> > > > > > > nmcli radio
> > > > > > > WIFI-HW  WIFI     WWAN-HW  WWAN
> > > > > > > missing  enabled  missing  enabled
> > > > > > > 
> > > > > > > nmcli device show cdc-wdm
> > > > > > > Error: Device 'cdc-wdm' not found.
> > > > > > > 
> > > > > > > nmcli connection show
> > > > > > > NAME       UUID                                  TYPE      DEVICE
> > > > > > > Teucidide  05bc1961-b71a-375a-80f0-d1d43969bfce  ethernet  enp0s20f0u11
> > > > > > > lo         2f316384-0efb-49e0-891a-ecbc70275b83  loopback  lo
> > > > > > > virbr0     6b485fdf-8003-46d4-bbcf-00e6c3b53151  bridge    virbr0
> > > > > > > 3-sweden   b25e5d45-379a-42fe-b340-7a8477d058d5  gsm       --
> > > > > > > 
> > > > > > > 
> > > > > > > (enp0s20f0u11)
> > > > > > >     Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
> > > > > > >          Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
> > > > > > > Current DNS Server: fe80::68ac:7fff:fe44:5b09
> > > > > > >        DNS Servers: 192.168.8.1 fe80::68ac:7fff:fe44:5b09
> > > > > > > 
> > > > > > > ip link set enp0s20f0u11 up
> > > > > > > 
> > > > > > >  ping -4 -c 4 -I enp0s20f0u11 8.8.8.8
> > > > > > > PING 8.8.8.8 (8.8.8.8) from 192.168.8.188 enp0s20f0u11: 56(84) bytes of data.
> > > > > > > 
> > > > > > > --- 8.8.8.8 ping statistics ---
> > > > > > > 4 packets transmitted, 0 received, 100% packet loss, time 3108ms
> > > > > > > 
> > > > > > > 
> > > > > > > 
> > > > > > > > On Thu, 2025-03-27 at 12:15 +0100, Patrick Dupre via users wrote:
> > > > > > > > > The manufacturer says compatible Linux
> > > > > > > >
> > > > > > > > To be blunt, that may just mean it worked on one distro, perhaps one
> > > > > > > > that doesn't care about what software it installs (not as in malware,
> > > > > > > > but ones that include non-free things the other distros don't).
> > > > > > > >
> > > > > > > > It might mean it worked when the user did a lot of work to enable it.
> > > > > > > > Without details you won't know.  And there's also a chance that since
> > > > > > > > they first released it, and it did work on Linux, they've built a new
> > > > > > > > model with a different chipset.
> > > > > > > >
> > > > > > > > Did you check if the manufacturer expects you to download a driver from
> > > > > > > > their website?
> > > > > > > >
> > > > > > > > --
> > > > > > > >
> > > > > > > > uname -rsvp
> > > > > > > > Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64
> > > > > > > >
> > > > > > > > Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
> > > > > > > > I will only get to see the messages that are posted to the mailing list.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > -- 
> > > > > > > _______________________________________________
> > > > > > > users mailing list -- [e-mail]
> > > > > > > To unsubscribe send an email to [e-mail]
> > > > > > > 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/[e-mail]
> > > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > > > >
> > > > > >
> > > > > > -- 
> > > > > > _______________________________________________
> > > > > > users mailing list -- [e-mail]
> > > > > > To unsubscribe send an email to [e-mail]
> > > > > > 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/[e-mail]
> > > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > > >
> > > > > -- 
> > > > > _______________________________________________
> > > > > users mailing list -- [e-mail]
> > > > > To unsubscribe send an email to [e-mail]
> > > > > 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/[e-mail]
> > > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > > >
> > > > -- 
> > > > _______________________________________________
> > > > users mailing list -- [e-mail]
> > > > To unsubscribe send an email to [e-mail]
> > > > 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/[e-mail]
> > > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> > >
> > > -- 
> > > _______________________________________________
> > > users mailing list -- [e-mail]
> > > To unsubscribe send an email to [e-mail]
> > > 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/[e-mail]
> > > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
> >
> > -- 
> > _______________________________________________
> > users mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > 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/[e-mail]
> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
>
> -- 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Marco]

On 28.03.2025 00:07 Patrick Dupre via users wrote:
> Link 18 (enp0s20f0u11)
>     Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
>          Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS
>                     DNSSEC=no/unsupported
> Current DNS Server: fe80::34a3:96ff:feba:2f41
>        DNS Servers: 192.168.8.1 fe80::34a3:96ff:feba:2f41
>
> The current DNS switched from ipv4 to ivp6, and it stops to work ?

As we already discussed, the networking stop working in general, so
systemd-resolved will test all DNS servers (if one doesn't answer it
uses another) and rotates them.
This is not the issue.