YaCy-Bugtracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000688YaCy[All Projects] Generalpublic2016-09-22 21:262016-09-22 21:49
ReporterPythagoras 
Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
StatusnewResolutionopen 
ETAnone 
Platformopenjdk version "1.8.0_102"OSFedoraOS Version24
Product Version 
Target VersionFixed in Version 
Summary0000688: IPv6 conflicts with staticIP parameter
DescriptionI'm using proxy on a machine behind IPv4 NAT in a network that supports IPv6. I have set up my router to forward 8090 port to the yacy machine.

Now if I leave the staticIP parameter blank, my peer would only be accessible with IPv6. I suppose that the network is unable to determine my IPv4 address based on outgoing connections from my peer.

On the other hand, if I set the staticIP parameter with my domain name, the peer gets to be only accessible by IPv4. Thus, for some reason I cannot have both IPv4 and IPv6 at the same time!

The domain name has both A and AAAA records on it. However it seems the network is not able to get my IPv6 address.
Steps To Reproduce1. Set up a yacy peer in a IPv6-enabled network behind an IPv4 NAT.
2. Go to the bottom of /Network.html page to the 'Your peer' table. You'll notice you're an IPv6 peer but not IPv4.
3. Set up the staticIP parameter with correct domain name.
4. Go back to /Network.html. You'll notice you're now an IPv4 peer but not IPv6 any more.
Additional InformationYaCy version 1.91/9188.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2016-09-22 21:26 Pythagoras New Issue


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker