Ping tool should force IPv4 for IPv4 addresses, regardless of DNS resolution.

[zaxlofful]

I use a VPN and on my mobile connection (T-mobile) force CG-NaT behind IPv6.

The ping tool for some reason tries to automatically translate the IPv4 address I input (directly) to IPv6.

But if I put in a dNS entry that resolves to IPv4, it will ping IPv4.

The logic should be changed, so that if an IPv4 address is detected in the input field. It forces IPv4.

[isontheline]

But if your provider is using NAT64, you don't have an IPv4 available on your device so WebSSH can't ping over IPv4 unfortunately

[isontheline]

OK I seem to better understand now 😅

I will make a look at it tonight, I’ll keep you know

[isontheline]

Could you make screenshots about your issue?

On my side one.one.one.one :

And 1.1.1.1 :

Both resolves through NAT64 and don't use old IPv4 when the carrier only supports IPv6

[zaxlofful]

The problem IS the auto-translate. I want it to not do that at all.

Can you add a checkbox that will force IPv4?

FYI, this happens for both pings and actual connections.

It does work for connection with certain settings, but not ping.

This makes it so I cannot use your ping tool while on mobile+VPN. Yet, I can use other ping tools.

Even though my network might “advertise” that is has no IPv4, it’s lying.

On t-mobile, it’s CG-NAT; but I also have a private link VPN via TailScale which punches thru the CG-NAT. The VPN offers routes for IPv4, which is the IP of the host I want to use.

Due to my VPN being active, I actually do have an IPv4 network available; it’s just not the main one.

Let me give you two examples to illustrate:

Example #1:

1. 10.49.80.23 is put into ping input field
2. It’s auto-translated into IPv6 and then your app actually tries to ping it via IPv6
3. That host is not available via IPv6 (especially not a NAT64 IP on the public internet)
4. Complete failure

Example #2

1. <DNS-NAME-LOCAL> is inserted into the ping input field
2. DNS returns an IPv4 (as it should in my IPv4 only network) [Does what it's supposed to with split-dns and search domains]
3. Your app pings the IPv4 address it gets
4. Success

I also tried to select (IPv4) in the ping tool, hoping it would force it to use IPv4 and it still has the same issue. Only tricking it with DNS does anything.

[isontheline]

OK I have identified a possible root cause and I will replace the getaddrinfo based implementation with inet_pton, which parses a literal IP address string directly into a sockaddr struct without any DNS resolution or NAT64 synthesis.

A new beta release should be available tomorrow, hope it will fix this trouble Zachary

[isontheline]

Hey @zaxlofful 👋

Could you please try WebSSH 31.2.1678?
https://testflight.apple.com/join/QSrBK59z