Ping blockage in Youprice tethering (Orange)
PascalHarbo Posted messages 3 Status Member -
Hello everyone,
I'm encountering a rather specific network issue while using my Samsung S24 Ultra in mobile hotspot mode with a YouPrice SIM (Orange network). I also have a Prixtel eSIM (SFR network), which has allowed me to compare behaviors.
???? Observation:
- With Prixtel (SFR): ping to
github.comworks perfectly from my PC connected via Wi-Fi to the phone. - With YouPrice (Orange): ping consistently fails, whether in IPv6 (NAT64 address of type
64:ff9b::...) or in IPv4 (140.82.121.3).
???? Tests conducted:
ping github.com→ failure with YouPrice, response with Prixtel.ping -4 github.com→ failure with YouPrice despite correct resolution.tracert github.com→ lost packets after the 6th hop (towards NAT64).https://github.comin the browser → works, but direct access to the IP triggers an SSL error (as expected).ipconfig→ the PC correctly receives a private IPv4 (10.x.x.x) and a global IPv6.
???? Hypothesis:
YouPrice seems to be using IPv6-only connectivity with NAT64/DNS64, but the NAT64 relay either blocks or does not properly translate ICMP packets (ping). The Android tethering could also be a factor (filtering or poor NAT management).
❓ Questions:
- Have other YouPrice subscribers (Orange network) observed this behavior?
- Is this a deliberate blocking of ping/ICMP in modem mode?
- Does the same problem exist on YouPrice with the SFR network?
- Any known solutions to force full IPv4 connectivity in hotspot mode?
Thank you in advance for your feedback or leads. I welcome any technical information or experiences!
Pascal
4 answers
-
I need to add an important point that I just tested:
-
- “Note: when I activate the McAfee VPN on my PC, the ping to GitHub works perfectly. This confirms that the blockage comes from the routing or network filtering on the YouPrice side.”
-
-
Hello,
Why want to ping the site if it's normally accessible?
From my SFR Box, which has nothing to do with a mobile access point, the ping succeeds to www.github.com but fails to 140.182.121.3.
The ping of the domain resolves it by definition to the IP via DNS.
The behavior is curious; in some cases, certain sites prohibit pinging their server, while in others, aside from considerations regarding the firewall allowing or not ICMP packets (but who would oppose it when going through the domain name), it is the operator and/or the connection device that can filter it. -
Hello,
feedback:
1/ with all the Android devices I've had so far, I've never had an IPv6 address other than local on a hotspot connection (ipconfig/all)
2/ Apparently www.github.com does not have an IPv6 address:
brupala@Mate-X-PRO:~$ host github.com github.com has address 140.82.121.3 github.com mail is handled by 1 aspmx.l.google.com. github.com mail is handled by 5 alt1.aspmx.l.google.com. github.com mail is handled by 10 alt4.aspmx.l.google.com. github.com mail is handled by 5 alt2.aspmx.l.google.com. github.com mail is handled by 10 alt3.aspmx.l.google.com. brupala@Mate-X-PRO:~$ host www.github.com www.github.com is an alias for github.com. github.com has address 140.82.121.4 github.com mail is handled by 1 aspmx.l.google.com. github.com mail is handled by 5 alt1.aspmx.l.google.com. github.com mail is handled by 5 alt2.aspmx.l.google.com. github.com mail is handled by 10 alt3.aspmx.l.google.com. github.com mail is handled by 10 alt4.aspmx.l.google.com. brupala@Mate-X-PRO:~$ brupala@Mate-X-PRO:~$ host google.com google.com has address 142.250.179.110 google.com has IPv6 address 2a00:1450:4007:806::200e google.com mail is handled by 10 smtp.google.com. brupala@Mate-X-PRO:~$
After all, internet on mobile networks isn't quite internet.
I forgot:
a mobile hotspot is not a modem, but a NAT router.
And there we go, voila ....
But goodness, those line breaks are so annoying!!-
Edit:
Out of a sense of due diligence, I just took another measurement, it's been a few months since I last checked, a mobile hotspot on my current mobile connection, Bouygues:
No own public IPv4, probably the one from CGN at 89.85.242.111, two IPv6 addresses (both) in the same /64 as the mobile at 2a04:
Wireless network card Wi-Fi : DNS suffix specific to the connection. . . : Description. . . . . . . . . . . . . . : Intel(R) Wi-Fi 6 AX201 160MHz Physical address . . . . . . . . . . . : FA-BB-9E-E3-57-** DHCP enabled. . . . . . . . . . . . . . : Yes Autoconfiguration enabled. . . : Yes IPv6 Address. . . . . . . . . . . . . .: 2a04:cec0:10e6:5f18:2197:26fa:c26c:****(preferred) Temporary IPv6 address . . . . . . . .: 2a04:cec0:10e6:5f18:dd16:c563:2051:****(preferred) Link-local IPv6 address. . . . .: fe80::4701:7bb3:7d47:213b%4(preferred) IPv4 Address. . . . . . . . . . . . . .: 10.102.219.92(preferred) Subnet mask. . . . . . . . . : 255.255.255.0 Lease obtained. . . . . . . . . . . . . . : Friday, October 3, 2025 10:30:08 Lease expires. . . . . . . . . . . . . : Friday, October 3, 2025 11:30:26 Default gateway. . . . . . . . . : fe80::d4f4:daff:feab:9e42%4 10.102.219.80 DHCP Server . . . . . . . . . . . . . : 10.102.219.80 DHCPv6 IAID . . . . . . . . . . . : 70528695 DHCPv6 Client DUID. . . . . . . . : 00-03-00-01-FA-BB-9E-E3-57-** DNS Servers. . . . . . . . . . . . . : 1.1.1.1 DoH: https://cloudflare-dns.com/dns-query 9.9.9.9 DoH: https://dns.quad9.net/dns-query 2a04:cec0:10e6:5f18::72 NetBIOS over Tcpip. . . . . . . . . . . : Enabled
A ping to www.github.com does indeed get a response via Bouygues' CGN/nat64:
C:\Users\Brupala>tracert www.github.com
Determining route to github.com [140.82.121.3]
with a maximum of 30 hops:1 160 ms 164 ms 143 ms 10.102.219.80
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 149 ms 143 ms 135 ms 10.110.147.50
7 170 ms 136 ms 137 ms 212.195.60.0
8 164 ms 149 ms 152 ms be41.cbr01-ntr.net.bbox.fr [212.194.171.132]
9 134 ms 148 ms 147 ms 62.34.2.248
10 263 ms 144 ms 136 ms 62.34.2.134
11 152 ms 156 ms 145 ms de-cix.fra.github.com [80.81.196.79]
12 * * * Request timed out.
13 * * * Request timed out.
14 173 ms 148 ms 151 ms lb-140-82-121-3-fra.github.com [140.82.121.3]Route determined.
C:\Users\Brupala>ping github.com
Sending a ping request to github.com [64:ff9b::8c52:7903] with 32 bytes of data:
Reply from 64:ff9b::8c52:7903: time=39 ms
Reply from 64:ff9b::8c52:7903: time=57 ms
Reply from 64:ff9b::8c52:7903: time=44 ms
Reply from 64:ff9b::8c52:7903: time=47 msPing statistics for 64:ff9b::8c52:7903:
Packets: sent = 4, received = 4, lost = 0 (loss 0%),
Approximate round trip times in milliseconds:
Minimum = 39ms, Maximum = 57ms, Average = 46ms****
8c52:7903 indeed corresponds to 140.82.121.3 in hexadecimal
****
All this doesn’t contribute anything to your problem since it's not the same operator, but just to indicate that the Bouygues mobile hotspot is now, and I recently discovered this, behind a nat64 with only private IPv4s and public IPv6s, as their fixed network sometimes already was.
After that, it may depend on the APNs; I just noticed that I had forced on IPV6 APN instead of ipV4 & ipV6, certainly for another test before.
-
-
Well, I received a response from YOUPRICE that I think could be useful for many of you, if you are troubled by this aspect, because after setting the APN manually it works. Here’s what their support recommends:
- Name: youprice
- APN: orange
- Proxy: Not defined (default)
- Port: Not defined (default)
- Username: orange
- Password: orange
- Server: Not defined (default)
- MMSC: http://mms.orange.fr
- MMS Proxy: 192.168.10.200
- MMS Port: 8080
- MCC: 208 (default)
- MNC: 01
- Authentication type: PAP
- APN type: default,supl,mms,xcap,dun
- APN protocol: IPv4
- APN roaming protocol: IPv4
- Enable/disable APN: APN enabled (default)
- Support: Not defined (default)
(P.S. the default configured APN is not modifiable, so you will need to create a new one and switch to that for the connection)
I wish you good reception.
