ipcalf icon indicating copy to clipboard operation
ipcalf copied to clipboard

Network IP fails in Google Chrome

Open codingstill opened this issue 6 years ago • 8 comments

Visiting https://net.ipcalf.com/ in Google Chrome returns a guid-like value instead of the actual IP. For example

Your network IP is: 5811584f-3480-4te0-875f-60a1c8f4393c.local Make the locals proud.

Chrome version: Version 75.0.3770.100 (Official Build) (64-bit)

From what I've seen so far, in the candidate string of the RTCIceCandidate object, this guid-like appears where the actual IP used to be.

Is there a way to retrieve the actual client IP in Chrome?

Edit: This behavior is not consistent. For some users with the same Chrome version are able to get the actual client IP

codingstill avatar Jun 25 '19 08:06 codingstill

I also used to face this issue, it seems like chrome is doing an experimental to expose actual ip

image if #enable-webrtc-hide-local-ips-with-mdns flag is enabled you will get to see only mDNS (Multicast domain name) in web page

I am also looking for the solution, please help

SathishKumar140 avatar Jun 25 '19 09:06 SathishKumar140

Hi @SathishKumar140

Thanks for posting. Indeed, setting this feature to Disabled it resolves the issue. The option is in chrome://flags/#disable-webrtc for anyone that might ask.

Closing this as it is not related to ipcalf.

codingstill avatar Jun 25 '19 10:06 codingstill

If chrome make's this experimental feature live, then it became a bug and we don't get an option to enable/disable. How can we solve this issue at an early stage?

SathishKumar140 avatar Jun 25 '19 11:06 SathishKumar140

I think this is considered a security issue/concern, known as WebRTC leak. I am not sure if this can be addressed from the website's end.

codingstill avatar Jun 25 '19 11:06 codingstill

Is there any other way to get IP in the client?

SathishKumar140 avatar Jun 25 '19 11:06 SathishKumar140

Interesting, clever for them to go the mDNS route to hide those.

As an aside, if they actually start letting the user resolve mDNS addresses (e.g. my laptop's mDNS name from my phone) too, then that somewhat reduces the need for knowing the local IP address anyway….

But anyway, I'll re-open this assuming they might go ahead rolling this out and see if there's a way to let the user grant perms anyway.

natevw avatar Jun 25 '19 22:06 natevw

Via https://github.com/vitalets/webrtc-ips/issues/3#issuecomment-493507388, there's some discussion at https://groups.google.com/forum/#!msg/discuss-webrtc/l0gc3RjBhc0/FsMqOlOSBwAJ and even a draft RFC for the feature: https://tools.ietf.org/html/draft-ietf-rtcweb-mdns-ice-candidates-02

natevw avatar Jun 25 '19 22:06 natevw

Looks like the current flag for this is chrome://flags/#enable-webrtc-hide-local-ips-with-mdns "Anonymize local IPs exposed by WebRTC." if anyone wants to opt out of the privacy protections here.

natevw avatar Jul 29 '19 16:07 natevw