#17761 closed defect (othersoftware)
Download of Plugins failes with IPv6, with IPv4 only - no problems
| Reported by: | HeinerSchaefer | Owned by: | HeinerSchaefer |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | template_report ipv6 | Cc: | stoecker |
Description
What steps will reproduce the problem?
What is the expected result?
What happens instead?
Please provide any additional information below. Attach a screenshot if possible.
Relative:URL: ^/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2019-04-28 04:36:41 +0200 (Sun, 28 Apr 2019) Revision:15031 Build-Date:2019-04-28 02:37:58 URL:https://josm.openstreetmap.de/svn/trunk Identification: JOSM/1.5 (15031 de) Linux Ubuntu 18.04.2 LTS Memory Usage: 294 MB / 1944 MB (172 MB allocated, but free) Java version: 11.0.3+7-Ubuntu-1ubuntu218.04.1, Oracle Corporation, OpenJDK 64-Bit Server VM Screen: :0.0 1440x900 Maximum Screen Size: 1440x900 Java package: openjdk-11-jre:amd64-11.0.3+7-1ubuntu2~18.04.1 Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-20ubuntu0.1 VM arguments: [-Djosm.restart=true, -Djava.net.useSystemProxies=true] Plugins: + buildings_tools (34982) + measurement + reltoolbox (34977) Last errors/warnings: - W: No configuration settings found. Using hardcoded default values for all pools. - W: Region [TMS_BLOCK_v2] Resetting cache - W: Region [WMS_BLOCK_v2] Resetting cache - W: Region [WMTS_BLOCK_v2] Resetting cache - W: java.net.SocketException: Das Netzwerk ist nicht erreichbar (connect failed) - E: org.openstreetmap.josm.plugins.PluginDownloadException: java.net.SocketException: Das Netzwerk ist nicht erreichbar (connect failed). Ursache: java.net.SocketException: Das Netzwerk ist nicht erreichbar (connect failed) - W: Erweiterungen aktualisieren - <html>Die folgende Erweiterung konnte <strong>nicht</strong> heruntergeladen werden:<ul><li>measurement</li></ul><br>Fehlermeldung (englisch): java.net.SocketException: Das Netzwerk ist nicht erreichbar (connect failed)</html> - W: java.net.SocketException: Das Netzwerk ist nicht erreichbar (connect failed) - W: Already here java.net.SocketException: Das Netzwerk ist nicht erreichbar (connect failed) - E: org.openstreetmap.josm.plugins.PluginDownloadException: java.net.SocketException: Das Netzwerk ist nicht erreichbar (connect failed). Ursache: java.net.SocketException: Das Netzwerk ist nicht erreichbar (connect failed)
Attachments (0)
Change History (11)
comment:1 by , 5 years ago
comment:2 by , 5 years ago
| Cc: | added |
|---|---|
| Keywords: | ipv6 added |
comment:3 by , 5 years ago
It seems svn.openstreetmap.org address has issues with IPv6 for some providers. E.g. a "ping -6 svn.openstreetmap.org" does not work from my company DSL (Telekom) ATM. E.g. Hetzner and my home access both work.
What provider(s) do you have?
comment:4 by , 5 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → needinfo |
comment:5 by , 5 years ago
I habe also Telekom AS a DSL provider.
Is it a problem with routing oft IPv6 Ort DNS?
comment:6 by , 5 years ago
There is DNS available:
:~$ dig svn.openstreetmap.org any
; <<>> DiG 9.11.3-1ubuntu1.7-Ubuntu <<>> svn.openstreetmap.org any
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37208
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;svn.openstreetmap.org. IN ANY
;; ANSWER SECTION:
svn.openstreetmap.org. 86052 IN A 212.110.172.32
svn.openstreetmap.org. 86131 IN AAAA 2001:41c9:1:400::32
;; Query time: 12 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Tue May 28 06:52:43 CEST 2019
;; MSG SIZE rcvd: 94
But the routing seems to have a problem:
:~$ ping -6 2001:41c9:1:400::32
PING 2001:41c9:1:400::32(2001:41c9:1:400::32) 56 data bytes
From 2003:0:8600:2800::1 icmp_seq=1 Destination unreachable: No route
From 2003:0:8600:2800::1 icmp_seq=2 Destination unreachable: No route
...
So nothing you can fix with your software.
Didn't expect this result.
comment:7 by , 5 years ago
Please file a support ticket with Telekom. Very likely it's a fight between providers again and Telekom needs pressure from own customers or they wont solve it.
comment:8 by , 5 years ago
| Resolution: | → othersoftware |
|---|---|
| Status: | needinfo → closed |
follow-up: 11 comment:10 by , 5 years ago
That's right. Now it works.
Support ticket at Telekom is opened.
comment:11 by , 5 years ago
Replying to heiner.schaefer@…:
That's right. Now it works.
Support ticket at Telekom is opened.
I had very interesting contacts today for my ticket for the company DSL account. Wonder why always the phone line breaks when I contact support with complicated issues. :-)
Maybe it helped nevertheless...
I have josm on a PC with IPv6 enabled.
Since the last update I received this error.
If I switch IPv6 to link local only and restart josm, no problem anymore.
Unfortunately this error comes back if I enable IPv6 again.