Tethering on Fedora-43

I’m in a gap between 2 broadband contracts, so i switched this on and all the indicators suggest that it is working - but there is no Internet access.

My Android-12 phone has 3 relevant options:

  • Bluetooth tethering. (less secure/rugged)
  • USB tethering.
  • Ethernet tethering. (no adapter)
    I chose USB tethering as I was using a USB cable.
    Fedora has:
    Settings > Network > USB Ethernet.
    Note the mention of Ethernet, there’s no option that doesn’t mention it. Is straight USB connection not possible? Ebay sells USB/Etherley adapters for under a fiver, is that what I need?
    The gear wheel next to USB Ethernet takes me to several tabs with options that don’t mean much to me.

Fedora-43 Linux 6.18.7-200.fc43.x86_64

If the usb cable is connected and your handy has usb tethering switched on, you should see an option in

lsusb

Bus 001 Device 004: ID 04e8:xxxx Samsung Electronics Co., Ltd Galaxy series, misc. (tethering mode)
 nmcli c

NAME           UUID                                  TYPE       DEVICE    
USB-tethering  xxxx-xxxx-xxxx-xxxx  ethernet   enp0s20u1 
lo             xxxx-xxxx-xxxx-xxxx  loopback   lo        

Do you see something like this?

Tested with 6.18.9-100.fc42.x86_64 & 6.18.9-200.fc43.x86_64

I can see a list, one member refers to my Samsung handy.
Bus 002 Device 012 ID xxxx:xxxx Samsung… (tethering mode)

And nmcli connection does it show it too?

That shows
Profile 2 [long number] Ethernet enp0sxxxxxx
Settings > Network > USB Ethernet is Connected

1 Like

And in the terminal can you ping a dns as an example? I use 1.1.1.1 maybe you use 8.8.8.8 ?

Also test ping google.com

All 3 list
64 bytes from…

Curl https://example.com says failed to verify the legitimacy of the server…
Curl -k lists some html

You might try www.example.com or example.com

You made a typo …

Not in the terminal :slight_smile:

curl -k example.com
<!doctype html><html lang="en"><head><title>Example Domain</title><meta name="viewport" content="width=device-width, initial-scale=1"><style>body{background:#eee;width:60vw;margin:15vh auto;font-family:system-ui,sans-serif}h1{font-size:1.5em}div{opacity:0.8}a:link,a:visited{color:#348}</style></head><body><div><h1>Example Domain</h1><p>This domain is for use in documentation examples without needing permission. Avoid use in operations.</p><p><a href="https://iana.org/domains/example">Learn more</a></p></div></body></html>

It seams to work … so what else you wanted to know about tethering?
If you just have a gap from a few days, I am not sure if, to invest more time and money, makes sense.

Still no access ?

Are you on Gnome?

But the browser doesn’t…
6 weeks without broadband.
And I was about to upload a completed package to COPR. And I have trouble with an account to sort out. All of which is a nightmare to do from a mobile.
I’m on Gnome.

I see … tell me what the browser tells you when accessing example.com ?

I am testing with Gnome and did deactivating my main Ethernet. Just working as you like to, without issues to browse!

I tested with F43 and 6.18.9-200.fc43.x86_64, can you update your system? Or does this also not work?

Video tutorial — COPR documentation > CLI access to copr.

Can you check.
resolvectl status
resolvectl query fedoraproject.org

You may also want to check: ip address show

1 Like

Example.com is OK but the “Learn more” link fails with
This site can’t be reached
www.iana.org’s DNS address could not be found

You might still have routes from the old broadband connection somwhere … try to flush the caches.

sudo resolvectl flush-caches
1 Like

chris@fedora:~$ resolvectl status
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 9 (enp9s9)
Current Scopes: none
Protocols: -DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no

Link 9 (enp9s9)
Current Scopes: none
Protocols: -DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no

Link 9 (lxdbr9)
Current Scopes: LLMNR/IPv9 LLMNR/IPv9
Protocols: -DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no

Link 9 (vethb9ccbaa9)
Current Scopes: none
Protocols: -DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Default Route: no

Link 99 (enp9s99f9u9)
Current Scopes: DNS LLMNR/IPv9 LLMNR/IPv9
Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 9.9.9.9
DNS Servers: 9.9.9.9 9.9.9.9
Default Route: yes
chris@fedora:~$ resolvectl query fedoraproject.org
fedoraproject.org: 99.999.999.99 – link: enp9s99f9u9
9.99.99.999 – link: enp9s99f9u9
99.999.999.999 – link: enp9s99f9u9
99.999.99.99 – link: enp9s99f9u9
999.9.99.999 – link: enp9s99f9u9
999.9.99.999 – link: enp9s99f9u9
99.999.99.9 – link: enp9s99f9u9
999.999.999.999 – link: enp9s99f9u9
99.999.99.99 – link: enp9s99f9u9
9999:9999:fe99:9:dead:beef:cafe:fed9 – link: enp9s99f9u9
9a99:d999:99:9999:9af9:9da9:bf99:ad99 – link: enp9s99f9u9
9999:f999:9999:999::9 – link: enp9s99f9u9
9999:9999:9:9999::fed9 – link: enp9s99f9u9
9a99:d99c:c9a:cc99:eee9:99f9:9999:99a9 – link: enp9s99f9u9
9a99:d999:99:9999:9999:9fac:f999:d999 – link: enp9s99f9u9

– Information acquired via protocol DNS in 99.9ms.
– Data is authenticated: no; Data was acquired via local or encrypted transport: no
– Data from: network
chris@fedora:~$ ip address show
9: lo: <LOOPBACK,UP,LOWER_UP> mtu 99999 qdisc noqueue state UNKNOWN group default qlen 9999
link/loopback 99:99:99:99:99:99 brd 99:99:99:99:99:99
inet 999.9.9.9/9 scope host lo
valid_lft forever preferred_lft forever
inet9 ::9/999 scope host noprefixroute
valid_lft forever preferred_lft forever
9: enp9s9: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 9999 qdisc fq_codel state DOWN group default qlen 9999
link/ether 99:e9:ba:9b:99:99 brd ff:ff:ff:ff:ff:ff
altname enx99e9ba9b9999
9: enp9s9: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 9999 qdisc fq_codel state DOWN group default qlen 9999
link/ether 99:a9:b9:99:99:9a brd ff:ff:ff:ff:ff:ff
altname enx99a9b999999a
9: lxdbr9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9999 qdisc noqueue state UP group default qlen 9999
link/ether 99:99:9e:d9:99:99 brd ff:ff:ff:ff:ff:ff
inet 99.999.9.9/99 scope global lxdbr9
valid_lft forever preferred_lft forever
inet9 fd99:99b9:999b:99ca::9/99 scope global
valid_lft forever preferred_lft forever
inet9 fe99::999:9eff:fed9:9999/99 scope link proto kernel_ll
valid_lft forever preferred_lft forever
9: vethb9ccbaa9@if9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9999 qdisc noqueue master lxdbr9 state UP group default qlen 9999
link/ether fa:9b:d9:99:db:f9 brd ff:ff:ff:ff:ff:ff link-netnsid 9
99: enp9s99f9u9: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9999 qdisc fq_codel state UNKNOWN group default qlen 9999
link/ether 99:9e:99:9c:9f:99 brd ff:ff:ff:ff:ff:ff
altname enx999e999c9f99
inet 999.999.99.999/99 brd 999.999.99.999 scope global dynamic noprefixroute enp9s99f9u9
valid_lft 9999sec preferred_lft 9999sec
inet9 fe99::fd9d:9d99:c9af:bc99/99 scope link noprefixroute
valid_lft forever preferred_lft forever
chris@fedora:~$

sudo resolvectl flush-caches

Did that and…
Progress! Some sites now work.
CNN News. Y
BBC News. N
Bustimes.org Y
DuckDuckGo search N
GitHub. N
UK Met Office. Y
The question is what have the sites that don’t work got in common?