YaCy-Bugtracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000713YaCy[All Projects] Generalpublic2016-12-01 05:532016-12-09 00:52
ReporterDNcrawler 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
ETAnone 
Platformx86-64OSFreeBSDOS Version10.3
Product Version 
Target VersionFixed in Version 
Summary0000713: yacy web interface doesn't listen on ::1
DescriptionYacy interface only listens on 127.0.0.1, not ::1. In fact, you can't configure the web interface to listen on ::1 or yacy reports an invalid address in the configuration. Any properly configured system is going to attempt ::1 before 127.0.0.1 (ipv6 before ipv4).
Steps To Reproducewget localhost:8090
--2016-12-01 04:49:50-- http://localhost:8090/ [^]
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8090... failed: Operation timed out.
Connecting to localhost (localhost)|127.0.0.1|:8090... connected.
HTTP request sent, awaiting response... 200 OK
Tagsipv6
Attached Filespng file icon c1.PNG [^] (13,766 bytes) 2016-12-05 02:29

- Relationships

-  Notes
(0001349)
DNcrawler (reporter)
2016-12-01 05:57

The result is this means every connection to localhost needs to wait for an http timeout before getting a response.
(0001350)
BuBu (developer)
2016-12-05 02:32
edited on: 2016-12-05 02:36

The try to access the UI via ::1 works fine here (without any customizing),
see picture
http://mantis.tokeek.de/file_download.php?file_id=248&type=bug [^]

(0001351)
DNcrawler (reporter)
2016-12-05 15:37

It doesn't seem to do so for me:

sockstat -l
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
yacy java 86018 93 stream (not connected)
yacy java 86018 97 stream (not connected)
yacy java 86018 148 tcp4 *:8090 *:*
yacy java 86018 170 stream(not connected)
yacy java 86018 209 stream(not connected)
yacy java 86018 220 stream(not connected)
yacy java 86018 265 stream(not connected)
(0001352)
DNcrawler (reporter)
2016-12-05 16:24
edited on: 2016-12-05 16:24

I'm in robinson mode as a private peer. I cannot find any documentation on how to configure the jetty contained within yacy. By default, jetty should listen on tcp4 and tcp6. The embedded web.xml implies this is the case as well.

On this page http://localhost:8090/Settings_p.html?page=ServerAccess [^] I see it only has 127.0.0.1 in the "IP Number Filter" field. Entering ::1 causes the interface to not start when yacy is restarted.

(0001355)
DNcrawler (reporter)
2016-12-07 20:40

When I start up yacy, it only binds to ipv4 localhost:

I 2016/12/07 19:39:52 Domain Init local host address: 127.0.0.1 (local)
I 2016/12/07 19:39:52 Domain Init local host address: xx.xx.xx.xx (public)
(0001356)
BuBu (developer)
2016-12-09 00:14

Yes, you pointed out the causing difference.

In my test "IP Number Filter" is set to default "*" (able to bind to all IPs)

By setting the filter, internally a Jetty ipfilter is used. The current version of this ipfilter only accepts ipv4 adresses.

For the moment there we can only add that to the documentation ("IP Number Filter" only accepts * or ipv4).
(0001357)
DNcrawler (reporter)
2016-12-09 00:52

Ok, I was spelunking the code to find this. However, you answered the question, so great. Feel free to close. Thank you.

- Issue History
Date Modified Username Field Change
2016-12-01 05:53 DNcrawler New Issue
2016-12-01 05:57 DNcrawler Note Added: 0001349
2016-12-01 05:57 DNcrawler Tag Attached: ipv6
2016-12-05 02:29 BuBu File Added: c1.PNG
2016-12-05 02:32 BuBu Note Added: 0001350
2016-12-05 02:36 BuBu Note Edited: 0001350 View Revisions
2016-12-05 15:37 DNcrawler Note Added: 0001351
2016-12-05 16:24 DNcrawler Note Added: 0001352
2016-12-05 16:24 DNcrawler Note Edited: 0001352 View Revisions
2016-12-07 20:40 DNcrawler Note Added: 0001355
2016-12-09 00:14 BuBu Note Added: 0001356
2016-12-09 00:52 DNcrawler Note Added: 0001357


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker