Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exit node IP address not visible in BE (no matter if IPv4 or IPv6) #4

Open
ronnylov opened this issue Oct 11, 2018 · 2 comments
Open

Comments

@ronnylov
Copy link

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.

@ronnylov
Copy link
Author

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.

@ronnylov
Copy link
Author

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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant