WLAN Hotspot IPV6 broken

Bug Reports
1

REPRODUCIBILITY: 100%
OS VERSION: 5.5.0
HARDWARE: Xperia 10 III
UI LANGUAGE: English (UK)
REGRESSION:

DESCRIPTION:

The “WLAN hotspot” feature

PRECONDITIONS:

WLAN hotspot does not work
It stopped working about 3 years ago on an earlier Sailfish device.
The network is EE in the UK.
The connection is established, I can browse the internet on my laptop if I connect then run
ssh user@sailfish-device -D 1024
… and then restart Chrome up with SOCKS5 on port 1024
Some user’s have suggested it’s related to CLAT IPv6

STEPS TO REPRODUCE:

  1. Use a Sailfish device in the UK with EE
  2. Start WLAN hotspot
  3. Observe that a Wifi connection can be establised
  4. Observe that ping google.com doesn’t work etc

EXPECTED RESULT:

Once a connection has been started, browsing the web should be possible

ACTUAL RESULT:

There is no web connection on the Wifi without using SOCKS5

MODIFICATIONS:

OKBoard

ADDITIONAL INFORMATION:

2

Is this a new bug? After giving the search a try I found:

and

3

OK but does ping 8.8.8.8 work?

4

No it does not work…

5

From my research it seems like the network connection is established between my laptop and my phone.

I can browse the internet using a SOCKS5 connection.

Can the WLAN hotspot work if an operator only gives a phone an IPv6 address?

Some people have suggested looking at something called CLAT?

6

Have the same issue on my xperia xz2. Setting the network to ipv4 only did not work. The workaround with ssh proxy worked though.

7

Disappointed to find that I have exactly the same problem on my Jolla Phone 2 running SfOS 5.2.0.17 . (Which means I can’t really work-around AAS GPS not working on the JP2 by using my old phone, as without internet sharing I can’t get traffic updates.)

The JP2 is connected to EE in the UK. Even ping 8.8.8.8 does not work.

8

@chr1s

So, I had a chat with Brave’s AI and wrote up a BASH script that will bridge an IPv6 carrier with an IPv4 laptop.

It requires development access turnned on and root access to run.

I use it here in the UK to tether my laptop to EE.

2 Likes
9

Thanks for the hint that IPv6 was the problem. That script looks rather complex, and I didn’t have the time to read & understand what it was doing (and if that had any risks or downsides), so I found a much simpler solution:

I went to Settings > Mobile network > Data access point > and changed Protocol from “Dual” to “IP”.
I then restarted my phone (probably overkill but I wanted to be sure it was using the new settings when I tested if this worked).

1 Like
10

It’s possible you are breaking codeberg’s TOS.

11

That script is rather scary, as it disables ALL firewall rules. I’m not sure what the built-in ones protect you against, but it surely makes you less secure. And if you use my Android Firewall script, those rules are all removed as well, meaning all Android apps get access to the internet again.

It might be possible to fix the script, but I played with it, and couldn’t get it to work at all (so I can’t test if my idea about fixes would break it).

If someone has this script working, it would be helpful to know which network interfaces it reports for “CLAT” & “Hotspot”, as I suspect that’s where it’s failing with me. (It may be my mobile network provider doesn’t support CLAT.)

1 Like
12

Exactly what I told @nshiell about their previous script.

This is what happens when “coders” don’t code anymore, and don’t understand what they are being handed by the LLM of their choice.

Not that this was never an issue before chatbots etc…

3 Likes
13

on 5.2.0.22 I had to spec. 172.28.172.1 as nameserver in networkmanager / > in resolv.conf
now I can access WAN with tethering from my linux machine (still not from other devices connected to it)

to use the workaround with

ssh -D 9090 -C defaultuser@172.28.172.1

I came across firefox-addon proxy-toggle which made switching config on different networks easier

chromium --proxy-server=“socks5://127.0.0.1:9090”

and for privoxy:
/etc/privoxy/config
forward-socks5 / 127.0.0.1:9090 .