Earlier (last time - couple months ago) it worked just fine.
Now, when I turn on wifi+hotspot connection and connecting a smartphone in the vicinity of my laptop, the speed of hospot is abnormally slow: it’s in range ~20-400 B/s. Can’t load/transfer anything.
What I’ve already tried with no avail: restart NetworkManager service, remove/create hotspot connection (also with wihotspot-gui tool, which was throwing errors), restart the machine.
Underway, it could also emit the following message (though I successfully entered the password on hotspot connection in separate popup) without formal connection breakage:
$ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 3c:2c:30:99:09:d6 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
link/ether b4:69:21:52:16:d8 brd ff:ff:ff:ff:ff:ff
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default
link/ether 02:42:05:8f:cc:97 brd ff:ff:ff:ff:ff:ff
$ ip route show
default via 176.36.3.1 dev eth0 proto dhcp src 176.36.3.30 metric 100
10.42.0.0/24 dev wlan0 proto kernel scope link src 10.42.0.1 metric 600
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
176.36.3.0/24 dev eth0 proto kernel scope link src 176.36.3.30 metric 100
$ ( nmcli dev list || nmcli dev show ) 2>/dev/null | grep DNS
IP4.DNS[1]: 194.50.85.5
IP4.DNS[2]: 194.50.85.7
As for DNS: it’s set for ethernet connection and was recently recommended by my ISP (some day the eth connection was down and tech support gave me those dns addresses).
As for IPv6 for the hotspot connection - it worked without enabling that.
The current config tab for hotspot is:
Ok, what got my attention is that both Ethernet and Wlan are up and running, and default route is set to eth. The hotspot has a private non-routable IP address, i’m not sure how this hotspot works, maybe someone can jump in. So i believe the problem is that your hotspot doesn’t take over the default route and then everything (including DNS) tries to go out via eth which won’t work if this is not connected. I would have expected that the hotspot would offer DNS and a default route. Could this be some config on the smartphone side?
Earlier I just needed to connect smartphone to the SSID (hotspot) and that got it to the internet.
If I understood correctly, DNS gets into the way of forwarding wlan IP-connection over ethernet?
Should I manually add the current eth IP address and DNS addresses to IP config of the wlan connection on the smartphone?
no, i think that won’t help. But i’m not the hotspot expert, someone else? Try to disable eth and see if this helps. Why is eth up anyway? Is it also connected to the Internet as it has a public IP? If not, it should be off.
ah, now i got it. You want to connect the smartphone to your cabled ethernet via hotspot. I always looked the other way round, connecting the laptop to a hotspot of the smartphone.
How did you enable the hotspot then on the laptop side?