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.
--
Gruß
Marco
Send unsolicited b
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 S
>
> 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
ect_url=/downloads/alcatel-ik41-series-firmware-v-01-02-00-15-release-notes
> > > > >
> > > > > But I cannot get it.
> > > > >
> > > > >
> > > > > Why there is no /dev/ttyUSB0 ?
> > > > >
> > > > >
; > https://techship.com/?redirect_url=/downloads/alcatel-ik41-series-firmware-v-01-02-00-15-release-notes
> > > >
> > > > But I cannot get it.
> > > >
> > > >
> > > > Why there is no /dev/ttyUSB0 ?
> > > >
> > > > =======
; > https://techship.com/?redirect_url=/downloads/alcatel-ik41-series-firmware-v-01-02-00-15-release-notes
> > > >
> > > > But I cannot get it.
> > > >
> > > >
> > > > Why there is no /dev/ttyUSB0 ?
> > > >
> > > > ======
gt; But I cannot get it.
> > >
> > >
> > > Why there is no /dev/ttyUSB0 ?
> > >
> > > ===
> > > Patrick DUPRÉ | | email: pdu...@gmx.com
> > > ===
=
> > Patrick DUPRÉ | | email: pdu...@gmx.com
> > ===
> >
> >
> > > Sent: Thursday, March 27, 2025 at 4:05 PM
> > > From: "None
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
>
>
> > Sent: Thursday, March 27, 2025 at 4:05 PM
> > From: "None via users"
> > To: "Community support for Fedora users"
> > Cc: edwardgib...@gmx.com
> > Subject: Re: Re: Dongle USB
> >
> > Probably Modem needs f
This is the modem
https://www.alcatelmobile.com/product/mobile-broadband/mobile-wifi/linkkey-lte-cat4-usb-dongle/
Following the instructions
https://techship.com/support/faq/integrating-the-alcatel-ik41-series-m2m-lte-cat4-usb-sticks-in-linux-using-mbim-usb-mode/
mmcli --scan-modems
successfully r
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.
--
___
users mailing list -- users@lists.
: "Community support for Fedora users"
> Cc: edwardgib...@gmx.com
> 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, Patr
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-lte-cat4-usb-dongle/
> Following
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 dist
On 27.03.2025 12:15 Patrick Dupre via users wrote:
> > Sent: Thursday, March 27, 2025 at 11:45 AM
> > From: "Marco Moock"
> > To: users@lists.fedoraproject.org
> > Subject: Re: Dongle USB
> >
> > On 27.03.2025 09:30 Patrick Dupre via users wrote:
> Sent: Thursday, March 27, 2025 at 11:45 AM
> From: "Marco Moock"
> To: users@lists.fedoraproject.org
> 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 beca
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.
--
_
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.
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,
ld switch to RNDIS mode
> Cc: edwardgib...@gmx.com
> 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_c
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%20send%20AT%20commands%20directly,through%20to%20/dev/ttyUSB3%20.&text=For%20some%20modems%20ttyACM%20devi
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:2
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 00
This may help out
https://techship.com/support/faq/how-to-automated-always-on-connection-establishment-with-alcatel-ik41-series-lte-data-sticks-using-rndis-usb-mode/#:~:text=Both%20Windows%20and%20Linux%20systems%20can%20support%20RNDIS,driver%20supporting%20RNDIS%20USB%20network%20interfaces%20
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
> >
>
> > 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
> w
> > 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
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
> > > (
ct.org, "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 intern
ot;
> To: users@lists.fedoraproject.org
> Cc: users@lists.fedoraproject.org, "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:
> 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
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
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.
--
Gruß
Marco
Send unsolicited bulk mail to 1742497783mu...@cartoonies.org
--
__
> 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)
> > > >
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.
> > >
> > > > 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
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 m
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
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 wh
>
> 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
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 2a0
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:1
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: +Defa
>
> 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 devic
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
>
On 3/19/25 10:05, Tim via users wrote:
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 -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@li
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
OK Marco,
When the "bad" dongle works "~1 minute"
1: lo: 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 for
OK Marco,
When the "bad" dongle works "~1 minute"
1: lo: 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 noprefix
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 1742383948mu...@cartoonies.org
--
___
users mailing list -- users@lists.f
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
;; communicati
> 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
>
> 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
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 unsoli
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?
--
Gruß
Marco
Send unsolicited bulk mail to 1742380141mu...@cartoonies.org
--
__
>
> > 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 re
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 wo
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?
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
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 a
>
> 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 ht
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 t
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
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
--
Gr
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.
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.
--
_
===
> Sent: Tuesday, March 18, 2025 at 9:38 PM
> From: "Marco Moock"
> To: users@lists.fedoraproject.org
> Subject: Re: Dongle USB
>
> Am 18.03.2025 um 21:35:50 Uhr schrieb Patrick Dupre via users:
>
> > 127.0.0.1 lo
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.
--
Gruß
Marco
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.1
> To: users@lists.fedoraproject.org
> 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 wh
Every thing OK, I just cannot connect to 198.162.1.1
Mar 18 19:41:43 Teucidide NetworkManager[1491]: [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]: [1742323315.7381
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.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubs
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 DEVI
Am 18.03.2025 um 20:00:26 Uhr schrieb Patrick Dupre via users:
> Mar 18 19:42:46 Teucidide NetworkManager[1491]:
> [1742323366.9843] manager: NetworkManager state is now CONNECTED_LOCAL
> Mar 18 19:42:46 Teucidide NetworkManager[1491]: [1742323366.9847]
> audit: op="connection-activate" uuid=
>
> 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-
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 dme
> 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 ma
>
> 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: 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
> >
>
> 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.
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: 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.
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
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
83 matches
Mail list logo
