Mageia forum

share the magic
http://forums.mageia.org/en/

[SOLVED] Problems with Mobile Tethering

http://forums.mageia.org/en/viewtopic.php?f=25&t=15668

Page 1 of 2

[SOLVED] Problems with Mobile Tethering

PostPosted: May 12th, '25, 07:47
by hosadeeb
Dear all,
Sometimes my ISP dies on me, and I try to connect through my mobile data connection. Now, the problem is: my Mageia 9 box declares the connection established, but no browser finds any address! I'm not using any proxy, so all my browsers are directly connected to the Internet. And when I checked, the tethered connection does have its own DNS servers.

I even tried connecting through the mobile's Hot Spot, still to no avail, although, again, the connection is declared established.

Strangest thing of all: using the same mobile and SIM card, when I use my laptop (instead of my Mageia desktop), the connection works just fine, whether I'm using tethering or the Hot Spot.

So, what I'm asking for here is: where should I look for the culprit? What could be that I'm doing wrong?

A million thanks in advance for your effort <3

Hosam Adeeb Nashed

Re: Problems with Mobile Tethering

PostPosted: May 12th, '25, 16:47
by morgano
You could try
https://wiki.mageia.org/en/Switching_to_networkmanager
as that works better for some.

Re: Problems with Mobile Tethering

PostPosted: May 12th, '25, 17:29
by doktor5000
Well, it would be helpful to know if you use net_applet (default MCC tool) or networkmanager to manage your network connections.
Also when you are tethered to your phone, some more details would be helpful in the case where it doesn't work

can you reach your default gateway? can ping any adress like 8.8.8.8 ?
what does your routing look like, what does your resolv.conf look like, and what does the browser show as exact error message?
what happens if you resolve any DNS entry?
Code: Select all
ip -o a
ip -o r
cat /etc/resolv.conf
dig mageia.org

Re: Problems with Mobile Tethering

PostPosted: May 13th, '25, 16:14
by hosadeeb
I do have NetworkManager. And its applet is indeed the one XFCE has.

Still, when I try
Code: Select all
sudo systemctl enable --now Networkmanager.service

I get an error:
Failed to enable unit: Unit file Networkmanager.service does not exist.


And, no: pinging doesn't work at all when tethered to the mobile. I believe I did mention this in my original post.

Re: Problems with Mobile Tethering

PostPosted: May 13th, '25, 16:16
by hosadeeb
ip -o a output:
Code: Select all
1: lo    inet 127.0.0.1/8 scope host lo\       valid_lft forever preferred_lft forever
1: lo    inet6 ::1/128 scope host noprefixroute \       valid_lft forever preferred_lft forever
2: enp8s0    inet 192.168.1.2/24 brd 192.168.1.255 scope global noprefixroute enp8s0\       valid_lft forever preferred_lft forever
2: enp8s0    inet6 fe80::b62e:99ff:fe18:eca6/64 scope link noprefixroute \       valid_lft forever preferred_lft forever
3: virbr0    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0\       valid_lft forever preferred_lft forever
4: docker0    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0\       valid_lft forever preferred_lft forever
6: enp1s0f0u10    inet 192.168.42.61/24 brd 192.168.42.255 scope global dynamic noprefixroute enp1s0f0u10\       valid_lft 3583sec preferred_lft 3583sec
6: enp1s0f0u10    inet6 fe80::51:1ff:fe53:3b33/64 scope link proto kernel_ll \       valid_lft forever preferred_lft forever


ip -o r output:
Code: Select all
default via 192.168.1.1 dev enp8s0 proto static metric 101
default via 192.168.42.129 dev enp1s0f0u10 proto dhcp src 192.168.42.61 metric 102
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
192.168.1.0/24 dev enp8s0 proto kernel scope link src 192.168.1.2 metric 101
192.168.42.0/24 dev enp1s0f0u10 proto kernel scope link src 192.168.42.61 metric 102
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown


Code: Select all
dig mageia.org
;; communications error to 192.168.42.129#53: connection refused
;; communications error to 192.168.42.129#53: connection refused
;; communications error to 192.168.42.129#53: connection refused

; <<>> DiG 9.18.33 <<>> mageia.org
;; global options: +cmd
;; no servers could be reached


Code: Select all
cat /etc/resolv.conf
# Generated by NetworkManager
search bedroom.home
nameserver 8.8.8.8
nameserver 4.4.4.4
nameserver 192.168.42.129

Re: Problems with Mobile Tethering

PostPosted: May 13th, '25, 17:55
by doktor5000
hosadeeb wrote:ip -o a output:

2: enp8s0 inet 192.168.1.2/24 brd 192.168.1.255 scope global noprefixroute enp8s0\ valid_lft forever preferred_lft forever
2: enp8s0 inet6 fe80::b62e:99ff:fe18:eca6/64 scope link noprefixroute \ valid_lft forever preferred_lft forever
[...]
6: enp1s0f0u10 inet 192.168.42.61/24 brd 192.168.42.255 scope global dynamic noprefixroute enp1s0f0u10\ valid_lft 3583sec preferred_lft 3583sec
6: enp1s0f0u10 inet6 fe80::51:1ff:fe53:3b33/64 scope link proto kernel_ll \ valid_lft forever preferred_lft forever[/code]

ip -o r output:
default via 192.168.1.1 dev enp8s0 proto static metric 101
default via 192.168.42.129 dev enp1s0f0u10 proto dhcp src 192.168.42.61 metric 102


Well you have 2 default routes, that by itself is a problem because the system does not know where to send outgoing packets.
From the order of the routing table it first tries to send them over your your wired interface enp8s0 so that's why you cannot reach a DNS server nor anything else.

To configure your tethered hotspot as backup connection you'd have to write a script which needs to at least
Code: Select all
ifdown enp8s0
to remove IP and route for it.
Or you can switch to networkmanager, which you don't have currently as otherwise the error would not show that you posted.
Please read the wiki page that morgano linked.

Re: Problems with Mobile Tethering

PostPosted: May 14th, '25, 01:04
by hosadeeb
I did manually disconnect my wired connection! Still to no avail.

Re: Problems with Mobile Tethering

PostPosted: May 14th, '25, 01:50
by doktor5000
If by manually disconnecting you mean unplugging the cable, that will do nothing to the interface configuration nor your routing table for a statically configured connection.
See above, you need to actually ifdown the interface or you will have the same configuration as before.

Re: Problems with Mobile Tethering

PostPosted: May 14th, '25, 09:51
by hosadeeb
I meant, I used NetworkManager applet to "Disconnect" the wired interface. Isn't that enough?

Re: Problems with Mobile Tethering

PostPosted: May 14th, '25, 19:26
by doktor5000
Doesn't seem like it. Might help if you would explain some details about the two interfaces enp8s0 and enp1s0f0u10

And please post the output as regular user of
Code: Select all
nmcli -f all con show
nmcli device
nmcli general

once you disconnected your connection.

Re: Problems with Mobile Tethering

PostPosted: May 15th, '25, 20:27
by hosadeeb
doktor5000 wrote:Doesn't seem like it. Might help if you would explain some details about the two interfaces enp8s0 and enp1s0f0u10


The first is my day-to-day wired connection, the second is the mobile tethered one.

doktor5000 wrote:And please post the output as regular user of
Code: Select all
nmcli -f all con show
nmcli device
nmcli general

once you disconnected your connection.


Code: Select all
nmcli -f all con show
NAME                   UUID                                  TYPE      TIMESTAM>
System enp1s0f0u10     a1f69242-4025-d98f-92c5-1b3098898de2  ethernet  17473332>
docker0                f53e80f6-90a2-4c0b-96a4-93c837b638e0  bridge    17473204>
virbr0                 e7b9793e-44f2-493e-9824-0e20c7a438bc  bridge    17473204>
HosAdeebAndroid        3878ff90-3320-4c9e-a88d-050e01c9ec6f  wifi      17470068>
MobiNil MobiNil MMS 1  0b86a526-4775-4770-8239-d3f7e0148516  gsm       0       >
System aros0           15eeace4-e96a-4758-4876-4889e7e1457d  ethernet  0       >
System docker0         b623421f-be81-dfe4-564c-49d5aeee4551  ethernet  0       >
System enp1s0f0u9      b9858ce1-5384-d209-94ae-840171f7bba8  ethernet  17019443>
System enp8s0          e3257772-0006-40e6-2a00-c86f31a6d3da  ethernet  17473332>
System macvtap0        1b825fd1-9007-d7ea-14b6-1809173a7ed0  ethernet  0       >
System wlp1s0f0u10     7c607c3e-f5d0-059c-4b84-64ac4dc7861e  ethernet  0       >
System wwp1s0f0u10i5   54c9ffe0-6504-80b5-4ca5-8272de09a4c5  ethernet  0       >
System wwp1s0f0u4i5    e0354191-d70d-097f-05b9-1251fa4afdb2  ethernet  0       >
System wwp1s0f0u9i5    da8ef88d-ac07-9545-2718-f0a98b77c014  ethernet  0       >
lines 1-15/15 (END)

nmcli device
DEVICE       TYPE      STATE                   CONNECTION         
enp1s0f0u10  ethernet  connected               System enp1s0f0u10
docker0      bridge    connected (externally)  docker0           
virbr0       bridge    connected (externally)  virbr0             
enp8s0       ethernet  disconnected            --                 
lo           loopback  unmanaged   


nmcli general
STATE                  CONNECTIVITY  WIFI-HW  WIFI     WWAN-HW  WWAN   
connected (site only)  none          missing  enabled  missing  enabled

Re: Problems with Mobile Tethering

PostPosted: May 16th, '25, 16:24
by doktor5000
hosadeeb wrote:nmcli device
DEVICE TYPE STATE CONNECTION
enp1s0f0u10 ethernet connected System enp1s0f0u10
docker0 bridge connected (externally) docker0
virbr0 bridge connected (externally) virbr0
enp8s0 ethernet disconnected --
lo loopback unmanaged


nmcli general
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
connected (site only) none missing enabled missing enabled


Well this is pretty clear - your mobile connection seems to be connected, but you have no network connectivity at all.
You need to check your mobile connection.

Please also post the output as root after disconnecting your wired connection:
Code: Select all
ps -ef | grep -i net
systemctl status NetworkManager -al -n 750

Re: Problems with Mobile Tethering

PostPosted: May 17th, '25, 12:48
by hosadeeb
hosadeeb wrote:I do have NetworkManager. And its applet is indeed the one XFCE has.

Still, when I try
Code: Select all
sudo systemctl enable --now Networkmanager.service

I get an error:
Failed to enable unit: Unit file Networkmanager.service does not exist.


And, no: pinging doesn't work at all when tethered to the mobile. I believe I did mention this in my original post.


That error I was getting, does it mean the functionality of NetworkManager is just not complete, or is somehow prevented?!

Re: Problems with Mobile Tethering

PostPosted: May 17th, '25, 18:37
by hosadeeb
The mobile connection, on the mobile itself, works fine.

Code: Select all
ps -ef | grep -i net
root           6       2  0 10:22 ?        00:00:00 [kworker/R-netns]
root          92       2  0 10:22 ?        00:00:00 [kworker/R-inet_]
systemd+     735       1  0 10:22 ?        00:00:00 /usr/lib/systemd/systemd-networkd
root        1207       1  0 10:23 ?        00:00:00 /usr/sbin/NetworkManager --no-daemon
root        4232       1  0 10:23 ?        00:00:00 /usr/sbin/xinetd -stayalive -dontfork
hosadeeb    7424    7371  0 13:19 ?        00:00:41 /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libnetload.so 8 14680077 netload Network Monitor Show network traffic
hosadeeb    8646    6775  0 13:20 ?        00:00:00 /usr/libexec/gvfsd-network --spawner :1.4 /org/gtk/gvfs/exec_spaw/1
root       35479       2  0 18:00 ?        00:00:00 [kworker/5:1-inet_frag_wq]
hosadeeb   44599   44556  0 19:28 ?        00:00:00 /usr/lib64/chromium-browser/chrome --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-GB --service-sandbox-type=none --crashpad-handler-pid=0 --enable-crash-reporter=,Mageia.Org 9 --change-stack-guard-on-fork=enable --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,12787151725017696108,13637203844209863944,262144 --enable-features=VaapiVideoDecoder,VaapiVideoEncoder --variations-seed-version
root       45751   45677  0 19:32 pts/0    00:00:00 grep --color -i net


Code: Select all
NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; preset: enabled)
     Active: active (running) since Sat 2025-05-17 10:23:07 EEST; 9h ago
       Docs: man:NetworkManager(8)
   Main PID: 1207 (NetworkManager)
      Tasks: 4 (limit: 9428)
     Memory: 9.1M
        CPU: 438ms
     CGroup: /system.slice/NetworkManager.service
             └─1207 /usr/sbin/NetworkManager --no-daemon

May 17 10:23:06 bedroom.home systemd[1]: Starting NetworkManager.service...
May 17 10:23:07 bedroom.home NetworkManager[1207]: <info>  [1747466587.0933] NetworkManager (version 1.40.18) is starting... (boot:4a131a4a-c70e-4287-b11b-d8b6d7a381e1)
May 17 10:23:07 bedroom.home NetworkManager[1207]: <info>  [1747466587.0934] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 31-mac-addr-change.conf)
May 17 10:23:07 bedroom.home systemd[1]: Started NetworkManager.service.
May 17 10:23:07 bedroom.home NetworkManager[1207]: <info>  [1747466587.0949] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
May 17 10:23:07 bedroom.home NetworkManager[1207]: <info>  [1747466587.3266] manager[0x29c220d0]: monitoring kernel firmware directory '/lib/firmware'.
May 17 10:23:07 bedroom.home NetworkManager[1207]: <info>  [1747466587.5749] hostname: hostname: using hostnamed
May 17 10:23:07 bedroom.home NetworkManager[1207]: <info>  [1747466587.5749] hostname: static hostname changed from (none) to "bedroom.home"
May 17 10:23:07 bedroom.home NetworkManager[1207]: <info>  [1747466587.5752] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink (auto)
May 17 10:23:07 bedroom.home NetworkManager[1207]: <info>  [1747466587.5755] manager[0x29c220d0]: rfkill: Wi-Fi hardware radio set enabled
May 17 10:23:07 bedroom.home NetworkManager[1207]: <info>  [1747466587.5755] manager[0x29c220d0]: rfkill: WWAN hardware radio set enabled
May 17 10:23:07 bedroom.home NetworkManager[1207]: <info>  [1747466587.9621] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.40.18/libnm-device-plugin->
lines 1-23
May 17 10:23:07 bedroom.home NetworkManager[1207]: <info>  [1747466587.9734] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.40.18/libnm-device-plugin-ad>
May 17 10:23:08 bedroom.home NetworkManager[1207]: <info>  [1747466588.0511] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.40.18/libnm-device-plugin-w>
May 17 10:23:08 bedroom.home NetworkManager[1207]: <info>  [1747466588.0603] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.40.18/libnm-device-plugin-w>
May 17 10:23:08 bedroom.home NetworkManager[1207]: <info>  [1747466588.0605] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
May 17 10:23:08 bedroom.home NetworkManager[1207]: <info>  [1747466588.0606] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
May 17 10:23:08 bedroom.home NetworkManager[1207]: <info>  [1747466588.0607] manager: Networking is enabled by state file
May 17 10:23:08 bedroom.home NetworkManager[1207]: <info>  [1747466588.0952] settings: Loaded settings plugin: ifcfg-rh ("/usr/lib64/NetworkManager/1.40.18/libnm-setting>
May 17 10:23:08 bedroom.home NetworkManager[1207]: <info>  [1747466588.0953] settings: Loaded settings plugin: keyfile (internal)
May 17 10:23:08 bedroom.home NetworkManager[1207]: <info>  [1747466588.4054] dhcp: init: Using DHCP client 'internal'
May 17 10:23:08 bedroom.home NetworkManager[1207]: <info>  [1747466588.4055] device (lo): carrier: link connected
May 17 10:23:08 bedroom.home NetworkManager[1207]: <info>  [1747466588.4057] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
May 17 10:23:08 bedroom.home NetworkManager[1207]: <info>  [1747466588.4067] manager: (enp8s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
May 17 10:23:08 bedroom.home NetworkManager[1207]: <info>  [1747466588.4070] device (enp8s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: >
May 17 10:23:10 bedroom.home NetworkManager[1207]: <info>  [1747466590.4129] modem-manager: ModemManager not available
May 17 10:23:10 bedroom.home NetworkManager[1207]: <info>  [1747466590.4358] modem-manager: ModemManager now available
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.1453] device (enp8s0): carrier: link connected
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.1455] device (enp8s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-if>
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.1459] policy: auto-activating connection 'System enp8s0' (e3257772-0006-40e6-2a00-c86f31a6d3da)
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.1463] device (enp8s0): Activation: starting connection 'System enp8s0' (e3257772-0006-40e6-2a00-c8>
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.1463] device (enp8s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'man>
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.1466] manager: NetworkManager state is now CONNECTING
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.1467] device (enp8s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.1472] device (enp8s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed>
lines 24-46
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.1476] policy: set 'System enp8s0' (enp8s0) as default for IPv4 routing and DNS
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.2464] device (enp8s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'manag>
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.2489] device (enp8s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'man>
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.2490] device (enp8s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'ma>
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.2493] manager: NetworkManager state is now CONNECTED_SITE
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.2495] device (enp8s0): Activation: successful, device activated.
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.2500] manager: NetworkManager state is now CONNECTED_GLOBAL
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.2502] manager: startup complete
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.4590] audit: op="connections-reload" pid=1675 uid=0 result="success"
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.7230] audit: op="connections-load" args="/etc/sysconfig/network-scripts/ifcfg-HosAdeebAndroid" pid>
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.7568] audit: op="connections-load" args="/etc/sysconfig/network-scripts/ifcfg-aros0" pid=1830 uid=>
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.7825] agent-manager: agent[8586745aedbb2b1c,:1.35/nmcli-connect/0]: agent registered
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.7829] audit: op="connection-activate" uuid="15eeace4-e96a-4758-4876-4889e7e1457d" name="System aro>
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.8397] audit: op="connections-load" args="/etc/sysconfig/network-scripts/ifcfg-enp1s0f0u10" pid=187>
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.8668] agent-manager: agent[89cc3339551d2205,:1.40/nmcli-connect/0]: agent registered
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.8673] audit: op="connection-activate" uuid="a1f69242-4025-d98f-92c5-1b3098898de2" name="System enp>
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.9025] audit: op="connections-load" args="/etc/sysconfig/network-scripts/ifcfg-enp1s0f0u9" pid=1910>
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.9297] agent-manager: agent[89cc3339551d2205,:1.45/nmcli-connect/0]: agent registered
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.9301] audit: op="connection-activate" uuid="b9858ce1-5384-d209-94ae-840171f7bba8" name="System enp>
May 17 10:23:11 bedroom.home NetworkManager[1207]: <info>  [1747466591.9638] audit: op="connections-load" args="/etc/sysconfig/network-scripts/ifcfg-enp8s0" pid=1950 uid>
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.0097] audit: op="connections-load" args="/etc/sysconfig/network-scripts/ifcfg-macvtap0" pid=1984 u>
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.0365] agent-manager: agent[370eaf69f24d5c3f,:1.54/nmcli-connect/0]: agent registered
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.0369] audit: op="connection-activate" uuid="1b825fd1-9007-d7ea-14b6-1809173a7ed0" name="System mac>
lines 47-69
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.2492] audit: op="connections-load" args="/etc/sysconfig/network-scripts/ifcfg-wlp1s0f0u10" pid=203>
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.2754] agent-manager: agent[370eaf69f24d5c3f,:1.59/nmcli-connect/0]: agent registered
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.2758] audit: op="connection-activate" uuid="7c607c3e-f5d0-059c-4b84-64ac4dc7861e" name="System wlp>
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.3083] audit: op="connections-load" args="/etc/sysconfig/network-scripts/ifcfg-wwp1s0f0u10i5" pid=2>
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.3345] agent-manager: agent[d36f9467daeb2cc4,:1.64/nmcli-connect/0]: agent registered
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.3349] audit: op="connection-activate" uuid="54c9ffe0-6504-80b5-4ca5-8272de09a4c5" name="System wwp>
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.3677] audit: op="connections-load" args="/etc/sysconfig/network-scripts/ifcfg-wwp1s0f0u4i5" pid=21>
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.3949] agent-manager: agent[1e6e2851c4ec70fa,:1.69/nmcli-connect/0]: agent registered
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.3954] audit: op="connection-activate" uuid="e0354191-d70d-097f-05b9-1251fa4afdb2" name="System wwp>
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.4290] audit: op="connections-load" args="/etc/sysconfig/network-scripts/ifcfg-wwp1s0f0u9i5" pid=21>
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.4567] agent-manager: agent[b7857fd83f7e7182,:1.74/nmcli-connect/0]: agent registered
May 17 10:23:12 bedroom.home NetworkManager[1207]: <info>  [1747466592.4571] audit: op="connection-activate" uuid="da8ef88d-ac07-9545-2718-f0a98b77c014" name="System wwp>
May 17 10:23:13 bedroom.home NetworkManager[1207]: <info>  [1747466593.1369] dhcp6 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
May 17 10:23:13 bedroom.home NetworkManager[1207]: <info>  [1747466593.1373] policy: set 'System enp8s0' (enp8s0) as default for IPv6 routing and DNS
May 17 10:23:59 bedroom.home NetworkManager[1207]: <info>  [1747466639.0639] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/3)
May 17 10:23:59 bedroom.home NetworkManager[1207]: <info>  [1747466639.7544] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-if>
May 17 10:23:59 bedroom.home NetworkManager[1207]: <info>  [1747466639.7548] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed', sys>
May 17 10:23:59 bedroom.home NetworkManager[1207]: <info>  [1747466639.7553] device (virbr0): Activation: starting connection 'virbr0' (18a1667e-c15f-4299-bf8f-b2855b4c3>
May 17 10:23:59 bedroom.home NetworkManager[1207]: <info>  [1747466639.7553] device (virbr0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'ext>
May 17 10:23:59 bedroom.home NetworkManager[1207]: <info>  [1747466639.7556] device (virbr0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
May 17 10:23:59 bedroom.home NetworkManager[1207]: <info>  [1747466639.7557] device (virbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 'externa>
May 17 10:23:59 bedroom.home NetworkManager[1207]: <info>  [1747466639.7559] device (virbr0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'exter>
May 17 10:23:59 bedroom.home NetworkManager[1207]: <info>  [1747466639.7948] device (virbr0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'ext>
lines 70-92
May 17 10:23:59 bedroom.home NetworkManager[1207]: <info>  [1747466639.7949] device (virbr0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'ex>
May 17 10:23:59 bedroom.home NetworkManager[1207]: <info>  [1747466639.7953] device (virbr0): Activation: successful, device activated.
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.1499] manager: (docker0): new Bridge device (/org/freedesktop/NetworkManager/Devices/4)
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.1810] audit: op="connections-load" args="/etc/sysconfig/network-scripts/ifcfg-docker0" pid=5505 ui>
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.2187] agent-manager: agent[0f48956aa966c2a6,:1.170/nmcli-connect/0]: agent registered
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.2192] audit: op="connection-activate" uuid="b623421f-be81-dfe4-564c-49d5aeee4551" name="System doc>
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.2270] device (docker0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-i>
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.2274] device (docker0): state change: unavailable -> disconnected (reason 'connection-assumed', sy>
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.2278] device (docker0): Activation: starting connection 'docker0' (1b75bcd3-2d3e-4d7c-8a82-a3cb603>
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.2279] device (docker0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'ex>
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.2281] device (docker0): state change: prepare -> config (reason 'none', sys-iface-state: 'external>
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.2282] device (docker0): state change: config -> ip-config (reason 'none', sys-iface-state: 'extern>
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.2284] device (docker0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'exte>
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.2569] device (docker0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'ex>
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.2570] device (docker0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'e>
May 17 10:24:45 bedroom.home NetworkManager[1207]: <info>  [1747466685.2573] device (docker0): Activation: successful, device activated.
May 17 13:19:27 bedroom.home NetworkManager[1207]: <info>  [1747477167.9799] agent-manager: agent[6f2204f3df47044e,:1.221/org.freedesktop.nm-applet/500]: agent registered
May 17 19:31:57 bedroom.home NetworkManager[1207]: <info>  [1747499517.7953] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/5)
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.0015] device (usb0): interface index 5 renamed iface from 'usb0' to 'enp1s0f0u10'
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.1598] audit: op="connections-load" args="/etc/sysconfig/network-scripts/ifcfg-enp1s0f0u10" pid=455>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.2555] agent-manager: agent[98f86938ac4a00f0,:1.448/nmcli-connect/0]: agent registered
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.2560] audit: op="connection-activate" uuid="a1f69242-4025-d98f-92c5-1b3098898de2" name="System enp>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.3493] device (enp1s0f0u10): state change: unmanaged -> unavailable (reason 'managed', sys-iface-st>
lines 93-115

May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.3493] device (enp1s0f0u10): state change: unmanaged -> unavailable (reason 'managed', sys-iface-st>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.3658] device (enp1s0f0u10): carrier: link connected
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.3662] device (enp1s0f0u10): state change: unavailable -> disconnected (reason 'carrier-changed', s>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.3667] policy: auto-activating connection 'System enp1s0f0u10' (a1f69242-4025-d98f-92c5-1b3098898de>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.3670] device (enp1s0f0u10): Activation: starting connection 'System enp1s0f0u10' (a1f69242-4025-d9>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.3671] device (enp1s0f0u10): state change: disconnected -> prepare (reason 'none', sys-iface-state:>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.3673] device (enp1s0f0u10): state change: prepare -> config (reason 'none', sys-iface-state: 'mana>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.3676] device (enp1s0f0u10): state change: config -> ip-config (reason 'none', sys-iface-state: 'ma>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.3678] dhcp4 (enp1s0f0u10): activation: beginning transaction (timeout in 45 seconds)
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.4389] dhcp4 (enp1s0f0u10): state changed new lease, address=192.168.42.61
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.5905] device (enp1s0f0u10): state change: ip-config -> ip-check (reason 'none', sys-iface-state: '>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.6686] device (enp1s0f0u10): state change: ip-check -> secondaries (reason 'none', sys-iface-state:>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.6688] device (enp1s0f0u10): state change: secondaries -> activated (reason 'none', sys-iface-state>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info>  [1747499518.6692] device (enp1s0f0u10): Activation: successful, device activated.
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info>  [1747499528.6396] device (enp8s0): state change: activated -> deactivating (reason 'user-requested', sys-iface>
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info>  [1747499528.6403] manager: NetworkManager state is now CONNECTED_LOCAL
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info>  [1747499528.6405] audit: op="device-disconnect" interface="enp8s0" ifindex=2 pid=7731 uid=500 result="success"
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info>  [1747499528.7007] device (enp8s0): state change: deactivating -> disconnected (reason 'user-requested', sys-if>
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info>  [1747499528.7014] dhcp6 (enp8s0): canceled DHCP transaction
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info>  [1747499528.7014] dhcp6 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info>  [1747499528.7014] dhcp6 (enp8s0): state changed no lease
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info>  [1747499528.7912] manager: NetworkManager state is now CONNECTED_SITE
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info>  [1747499528.7913] policy: set 'System enp1s0f0u10' (enp1s0f0u10) as default for IPv4 routing and DNS
lines 115-137/137 (END)

Re: Problems with Mobile Tethering

PostPosted: May 17th, '25, 19:40
by sturmvogel
hosadeeb wrote:
hosadeeb wrote:
Code: Select all
sudo systemctl enable --now Networkmanager.service

I get an error:
Failed to enable unit: Unit file Networkmanager.service does not exist.



By reading the wiki link from the first comment you could have found that you have a spelling error in your command....

WRONG (yours):
Code: Select all
sudo systemctl enable --now Networkmanager.service


CORRECT:
Code: Select all
sudo systemctl enable --now NetworkManager.service


AGAIN:
https://wiki.mageia.org/en/Switching_to_networkmanager

Re: Problems with Mobile Tethering

PostPosted: May 17th, '25, 20:32
by doktor5000
hosadeeb wrote:The mobile connection, on the mobile itself, works fine.

Code: Select all
ps -ef | grep -i net
root           6       2  0 10:22 ?        00:00:00 [kworker/R-netns]
root          92       2  0 10:22 ?        00:00:00 [kworker/R-inet_]
systemd+     735       1  0 10:22 ?        00:00:00 /usr/lib/systemd/systemd-networkd
root        1207       1  0 10:23 ?        00:00:00 /usr/sbin/NetworkManager --no-daemon
root        4232       1  0 10:23 ?        00:00:00 /usr/sbin/xinetd -stayalive -dontfork
hosadeeb    7424    7371  0 13:19 ?        00:00:41 /usr/lib64/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libnetload.so 8 14680077 netload Network Monitor Show network traffic
hosadeeb    8646    6775  0 13:20 ?        00:00:00 /usr/libexec/gvfsd-network --spawner :1.4 /org/gtk/gvfs/exec_spaw/1
root       35479       2  0 18:00 ?        00:00:00 [kworker/5:1-inet_frag_wq]
hosadeeb   44599   44556  0 19:28 ?        00:00:00 /usr/lib64/chromium-browser/chrome --type=utility --utility-sub-type=network.mojom.NetworkService --lang=en-GB --service-sandbox-type=none --crashpad-handler-pid=0 --enable-crash-reporter=,Mageia.Org 9 --change-stack-guard-on-fork=enable --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,12787151725017696108,13637203844209863944,262144 --enable-features=VaapiVideoDecoder,VaapiVideoEncoder --variations-seed-version
root       45751   45677  0 19:32 pts/0    00:00:00 grep --color -i net


You do have systemd-networkd running, but this is disabled by default. Why did you enable it ?

Here's what it looks like by default on Mageia 9:
[doktor5000@Mageia9]─[20:04:48]─[~] sudo systemctl status systemd-networkd
○ systemd-networkd.service - Network Configuration
Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; disabled; preset: disabled)
Active: inactive (dead)
TriggeredBy: ○ systemd-networkd.socket
Docs: man:systemd-networkd.service(8)
man:org.freedesktop.network1(5)


hosadeeb wrote:The mobile connection, on the mobile itself, works fine.

What does that mean in particular? The connection on your smartphone works fine, but you've never successfully used it on your PC with this setup?
Also as this seems to be based on some USB device, how do you tether to the phone exactly? Why not simply use a wireless hotspot for tethering ?

After activating your mobile connection your system changes from CONNECTED_GLOBAL to CONNECTED_LOCAL
hosadeeb wrote:NetworkManager.service - Network Manager

May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.3658] device (enp1s0f0u10): carrier: link connected
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.3662] device (enp1s0f0u10): state change: unavailable -> disconnected (reason 'carrier-changed', s>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.3667] policy: auto-activating connection 'System enp1s0f0u10' (a1f69242-4025-d98f-92c5-1b3098898de>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.3670] device (enp1s0f0u10): Activation: starting connection 'System enp1s0f0u10' (a1f69242-4025-d9>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.3671] device (enp1s0f0u10): state change: disconnected -> prepare (reason 'none', sys-iface-state:>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.3673] device (enp1s0f0u10): state change: prepare -> config (reason 'none', sys-iface-state: 'mana>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.3676] device (enp1s0f0u10): state change: config -> ip-config (reason 'none', sys-iface-state: 'ma>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.3678] dhcp4 (enp1s0f0u10): activation: beginning transaction (timeout in 45 seconds)
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.4389] dhcp4 (enp1s0f0u10): state changed new lease, address=192.168.42.61
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.5905] device (enp1s0f0u10): state change: ip-config -> ip-check (reason 'none', sys-iface-state: '>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.6686] device (enp1s0f0u10): state change: ip-check -> secondaries (reason 'none', sys-iface-state:>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.6688] device (enp1s0f0u10): state change: secondaries -> activated (reason 'none', sys-iface-state>
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.6692] device (enp1s0f0u10): Activation: successful, device activated.
May 17 19:31:58 bedroom.home NetworkManager[1207]: <info> [1747499518.6692] device (enp1s0f0u10): Activation: successful, device activated.
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info> [1747499528.6396] device (enp8s0): state change: activated -> deactivating (reason 'user-requested', sys-iface>
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info> [1747499528.6403] manager: NetworkManager state is now CONNECTED_LOCAL
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info> [1747499528.6405] audit: op="device-disconnect" interface="enp8s0" ifindex=2 pid=7731 uid=500 result="success"
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info> [1747499528.7007] device (enp8s0): state change: deactivating -> disconnected (reason 'user-requested', sys-if>
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info> [1747499528.7014] dhcp6 (enp8s0): canceled DHCP transaction
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info> [1747499528.7014] dhcp6 (enp8s0): activation: beginning transaction (timeout in 45 seconds)
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info> [1747499528.7014] dhcp6 (enp8s0): state changed no lease
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info> [1747499528.7912] manager: NetworkManager state is now CONNECTED_SITE
May 17 19:32:08 bedroom.home NetworkManager[1207]: <info> [1747499528.7913] policy: set 'System enp1s0f0u10' (enp1s0f0u10) as default for IPv4 routing and DNS
lines 115-137/137 (END)


Please show the connection details

Code: Select all
nmcli -t connection show "System enp1s0f0u10"

Re: Problems with Mobile Tethering

PostPosted: May 18th, '25, 08:46
by hosadeeb
doktor5000 wrote:
hosadeeb wrote:The mobile connection, on the mobile itself, works fine.


You do have systemd-networkd running, but this is disabled by default. Why did you enable it ?


I honestly have never interfered with that! Maybe it was enabled in a previous installation. I mean, I've been upgrading the distro for many years, not installing it from scratch. If I do need to have it disabled, how should I do that?

hosadeeb wrote:The mobile connection, on the mobile itself, works fine.

[doktor5000@Mageia9]What does that mean in particular? The connection on your smartphone works fine, but you've never successfully used it on your PC with this setup?

Exactly!
[doktor5000@Mageia9]Also as this seems to be based on some USB device, how do you tether to the phone exactly? Why not simply use a wireless hotspot for tethering ?

I have neither bluetooth or wifi on that particular desktop. But, in order to cover all bases, I did borrow a USB WiFi thing and tested using the mobile's HotSpot. Same frustration!

Re: Problems with Mobile Tethering

PostPosted: May 18th, '25, 14:00
by doktor5000
You forgot an important part, besides the connection details via nmcli:
doktor5000 wrote:Also as this seems to be based on some USB device, how do you tether to the phone exactly?

Re: Problems with Mobile Tethering

PostPosted: May 21st, '25, 20:35
by hosadeeb
nmcli -t connection show "System enp1s0f0u10"
Code: Select all
connection.id:System enp1s0f0u10
connection.uuid:a1f69242-4025-d98f-92c5-1b3098898de2
connection.stable-id:
connection.type:802-3-ethernet
connection.interface-name:enp1s0f0u10
connection.autoconnect:yes
connection.autoconnect-priority:0
connection.autoconnect-retries:-1
connection.multi-connect:0
connection.auth-retries:-1
connection.timestamp:1747852272
connection.read-only:no
connection.permissions:
connection.zone:
connection.master:
connection.slave-type:
connection.autoconnect-slaves:-1
connection.secondaries:
connection.gateway-ping-timeout:0
connection.metered:unknown
connection.lldp:default
connection.mdns:-1
connection.llmnr:-1
connection.dns-over-tls:-1
connection.mptcp-flags:0x0
connection.wait-device-timeout:-1
connection.wait-activation-delay:-1
802-3-ethernet.port:
802-3-ethernet.speed:0
802-3-ethernet.duplex:
802-3-ethernet.auto-negotiate:no
802-3-ethernet.mac-address:
802-3-ethernet.cloned-mac-address:
802-3-ethernet.generate-mac-address-mask:
802-3-ethernet.mac-address-blacklist:
802-3-ethernet.mtu:auto
802-3-ethernet.s390-subchannels:
802-3-ethernet.s390-nettype:
802-3-ethernet.s390-options:
802-3-ethernet.wake-on-lan:default
802-3-ethernet.wake-on-lan-password:
802-3-ethernet.accept-all-mac-addresses:-1
ipv4.method:auto
ipv4.dns:
ipv4.dns-search:
ipv4.dns-options:
ipv4.dns-priority:0
ipv4.addresses:
ipv4.gateway:
ipv4.routes:
ipv4.route-metric:-1
ipv4.route-table:0
ipv4.routing-rules:
ipv4.ignore-auto-routes:no
ipv4.ignore-auto-dns:no
ipv4.dhcp-client-id:
ipv4.dhcp-iaid:
ipv4.dhcp-timeout:0
ipv4.dhcp-send-hostname:yes
ipv4.dhcp-hostname:
ipv4.dhcp-fqdn:
ipv4.dhcp-hostname-flags:0x0
ipv4.never-default:no
ipv4.may-fail:yes
ipv4.required-timeout:-1
ipv4.dad-timeout:-1
ipv4.dhcp-vendor-class-identifier:
ipv4.link-local:0
ipv4.dhcp-reject-servers:
ipv6.method:ignore
ipv6.dns:
ipv6.dns-search:
ipv6.dns-options:
ipv6.dns-priority:0
ipv6.addresses:
ipv6.gateway:
ipv6.routes:
ipv6.route-metric:-1
ipv6.route-table:0
ipv6.routing-rules:
ipv6.ignore-auto-routes:no
ipv6.ignore-auto-dns:no
ipv6.never-default:no
ipv6.may-fail:yes
ipv6.required-timeout:-1
ipv6.ip6-privacy:-1
ipv6.addr-gen-mode:default-or-eui64
ipv6.ra-timeout:0
ipv6.mtu:auto
ipv6.dhcp-duid:
ipv6.dhcp-iaid:
ipv6.dhcp-timeout:0
ipv6.dhcp-send-hostname:yes
ipv6.dhcp-hostname:
ipv6.dhcp-hostname-flags:0x0
ipv6.token:
proxy.method:none
proxy.browser-only:no
proxy.pac-url:
proxy.pac-script:
GENERAL.NAME:System enp1s0f0u10
GENERAL.UUID:a1f69242-4025-d98f-92c5-1b3098898de2
GENERAL.DEVICES:enp1s0f0u10
GENERAL.IP-IFACE:enp1s0f0u10
GENERAL.STATE:activated
GENERAL.DEFAULT:no
GENERAL.DEFAULT6:no
GENERAL.SPEC-OBJECT:
GENERAL.VPN:no
GENERAL.DBUS-PATH:/org/freedesktop/NetworkManager/ActiveConnection/4
GENERAL.CON-PATH:/org/freedesktop/NetworkManager/Settings/5
GENERAL.ZONE:
GENERAL.MASTER-PATH:
IP4.ADDRESS[1]:192.168.42.61/24
IP4.GATEWAY:192.168.42.129
IP4.ROUTE[1]:dst = 192.168.42.0/24, nh = 0.0.0.0, mt = 101
IP4.ROUTE[2]:dst = 0.0.0.0/0, nh = 192.168.42.129, mt = 101
IP4.DNS[1]:192.168.42.129
DHCP4.OPTION[1]:broadcast_address = 192.168.42.255
DHCP4.OPTION[2]:dhcp_client_identifier = 01:02:51:01:53:3b:33
DHCP4.OPTION[3]:dhcp_lease_time = 3600
DHCP4.OPTION[4]:dhcp_server_identifier = 192.168.42.129
DHCP4.OPTION[5]:domain_name_servers = 192.168.42.129
DHCP4.OPTION[6]:expiry = 1747855871
DHCP4.OPTION[7]:host_name = bedroom
DHCP4.OPTION[8]:ip_address = 192.168.42.61
DHCP4.OPTION[9]:next_server = 192.168.42.129
DHCP4.OPTION[10]:requested_broadcast_address = 1
DHCP4.OPTION[11]:requested_domain_name = 1
DHCP4.OPTION[12]:requested_domain_name_servers = 1
DHCP4.OPTION[13]:requested_domain_search = 1
DHCP4.OPTION[14]:requested_host_name = 1
DHCP4.OPTION[15]:requested_interface_mtu = 1
DHCP4.OPTION[16]:requested_ms_classless_static_routes = 1
DHCP4.OPTION[17]:requested_nis_domain = 1
DHCP4.OPTION[18]:requested_nis_servers = 1
DHCP4.OPTION[19]:requested_ntp_servers = 1
DHCP4.OPTION[20]:requested_rfc3442_classless_static_routes = 1
DHCP4.OPTION[21]:requested_root_path = 1
DHCP4.OPTION[22]:requested_routers = 1
DHCP4.OPTION[23]:requested_static_routes = 1
DHCP4.OPTION[24]:requested_subnet_mask = 1
DHCP4.OPTION[25]:requested_time_offset = 1
DHCP4.OPTION[26]:requested_wpad = 1
DHCP4.OPTION[27]:routers = 192.168.42.129
DHCP4.OPTION[28]:subnet_mask = 255.255.255.0
IP6.ADDRESS[1]:fe80::51:1ff:fe53:3b33/64
IP6.GATEWAY:
IP6.ROUTE[1]:dst = fe80::/64, nh = ::, mt = 256

Re: Problems with Mobile Tethering

PostPosted: May 21st, '25, 20:48
by hosadeeb
doktor5000 wrote:You forgot an important part, besides the connection details via nmcli:
doktor5000 wrote:Also as this seems to be based on some USB device, how do you tether to the phone exactly?


I simply connect the USB cable, and then choose "USB Tethering" instead of "File Transfer" from the connection options available. That's exactly what I do every time with my laptop (not Mageia, though).


Removed duplicate post. ~Germ

Re: Problems with Mobile Tethering

PostPosted: May 22nd, '25, 18:04
by doktor5000
It has "ipv4.never-default:no" which means DEFROUTE=yes which means that NetworkManager will move the default route to this interface when it's activated.

And you get an IP adress over the tethered connection via DHCP, so that seems to work fine.

Although you still didn't mention if it works if you manually ifdown the other connection.

doktor5000 wrote:To configure your tethered hotspot as backup connection you'd have to write a script which needs to at least
Code: Select all
ifdown enp8s0
to remove IP and route for it.


Another option would be to reduce the cost for that interface (metric) as it's currently higher than the wired connection
Code: Select all
nmcli connection modify 'System enp1s0f0u10' ipv4.route-metric 50
nmcli connection reload 'System enp1s0f0u10'
nmcli connection up 'System enp1s0f0u10'

and then reactivate the connection as that is not applied live by networkmanager.

Re: Problems with Mobile Tethering

PostPosted: May 28th, '25, 20:10
by hosadeeb
Well, since I only need that tethering in the event my ISP is down, I turned the router off completely. Even then, the tethered connection didn't function. I mean, the desktop couldn't reach the Net, although on the mobile itself the connection worked just fine.

Still, I'll give it a try the modifications you suggested for the tethered connection and tell what transpires.

Thank you a lot for bearing with me.

Re: Problems with Mobile Tethering

PostPosted: May 28th, '25, 20:16
by hosadeeb
The connection modifications didn't work either. Unfortunately.

Re: Problems with Mobile Tethering

PostPosted: May 28th, '25, 20:22
by doktor5000
"didn't work" is not really helpful. What was the outcome? At least provide
Code: Select all
ip -o r
output, otherwise nobody can really help you remotely.
Also it doesn't matter if you turn off your router, if your default gateway still points to the wired connection as the first in your routing table, then you will still have the same initial problem.
This is the same where simply unplugging your wired connection does nothing if the interface is still configured.

Re: Problems with Mobile Tethering

PostPosted: May 31st, '25, 00:25
by pmr
I would check firewall settings.
If you use shorewall, check if the new interface is present in /etc/shorewall/interfaces
All times are UTC + 1 hour [ DST ]
Page 1 of 2
Powered by phpBB® Forum Software © phpBB Group
https://www.phpbb.com/