You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Connected to the Lethernet CA Montreal proxy provider.
Whatsmyip.com show following:
Your Public IPv6 is: 2607:5300:60:120c:0:0:0:1
Your IPv4 is: 142.4.213.12
Your Local IP is: 192.168.1.44
Location: Beauharnois, QC CA
ISP: OVH Hosting Inc.
But the browser extension is showing my local external ip address, the same address as when BE is disconnected. This makes it confusing and made me think BE was disconnected while it actually was connected to the exit node. Everything works but it is a display error. I think it may be related to using IPv6 because the other exit nodes using IPv4 does show exit node IP address in BE.
The text was updated successfully, but these errors were encountered:
It looks like I have this problems on other exit nodes too even when they are IPv4 only.
V3.0.0.b2 Arch Linux client. I will try it on windows and see what happens.
The exit node address is not viewed in BE on Windows 10 either.
Does not have to do with ipv6 or ipv4, sorry for that.
Lethean GUI version v3.0.0.b2 54e0b4d
Browser extension 3.0.0
Tested on Lethernet FR (ipv4 only) and Lethernet CA (ipv6 and ipv4).
ronnylov
changed the title
Exit node IP address not visible in BE when using IPv6
Exit node IP address not visible in BE (no matter if IPv4 or IPv6)
Nov 5, 2018
Connected to the Lethernet CA Montreal proxy provider.
Whatsmyip.com show following:
Your Public IPv6 is: 2607:5300:60:120c:0:0:0:1
Your IPv4 is: 142.4.213.12
Your Local IP is: 192.168.1.44
Location: Beauharnois, QC CA
ISP: OVH Hosting Inc.
But the browser extension is showing my local external ip address, the same address as when BE is disconnected. This makes it confusing and made me think BE was disconnected while it actually was connected to the exit node. Everything works but it is a display error. I think it may be related to using IPv6 because the other exit nodes using IPv4 does show exit node IP address in BE.
The text was updated successfully, but these errors were encountered: