N/A
N/A
We have the odd customer that will have CF-Connecting-IP showing an IPv6 address, and not IPv4.
Enabled Pseudo IPv4 to overwrite headers
I don’t know
Can’t replicaet through our VPN
So additionally… now I cannot edit the OP…
Enabling Psuedo IPv4 has resulted in an IPv4 address that does not match th customers, and I do not know what it is. It might be an Internal IP and not the public IP address of the customer. Is there a way to resolve this?
The user is showing an IPv6 address is connecting via IPv6 to Cloudflare’s edge. The IPv6 address is their address.
Is there a way to Show the actual IPv4? If Cloudflare is not in use, then the IP address is revealed, even by “whats my ip?” web sites so there should be a way to pass it through?
If the client is connecting over IPv6, you cannot know their IPv4 address from the same connection.
The way IP address showing sites work is that if the users connects over IPv6 to the server (as browsers try IPv6 first), a client-side script makes a separate connection to another hostname that only has A records, no AAAA records, to force read the IPv4 address, as here…
https://cf.sjr.org.uk/tools/connection
I was hoping to see if via a header if it was possible. It is present in a Request header when Cloudflare is off as IPv4.
Could it be that as we allowed IPv6 on Cloudflare, do we need to just turn this off then to force it? Or would that block their connection?
If you turn off IPv6 on Cloudflare, the Cloudflare DNS will only return IPv4 addresses for your domain so you’ll be forcing IPv4 always. This will apply to the domain and all subdomains in the zone.
What problem are you trying to solve? The IPv6 address is the user’s actual IP address.
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
