Opened 2 years ago

Last modified 23 months ago

#1848 open defect

IPv4 Auto Detection Fails

Reported by: djx Owned by:
Priority: minor Milestone: undecided
Component: router/transport Version: 0.9.29
Keywords: Cc:
Parent Tickets:

Description (last modified by djx)

I2P version: 0.9.26-0
Java version: Oracle Corporation 1.8.0_101 (Java(TM) SE Runtime Environment 1.8.0_101-b13)
Wrapper version: 3.5.25
Server version: 8.1.17.v20150415
Servlet version: Jasper JSP 2.1 Engine
JSTL version: standard-taglib 1.2.0
Platform: Windows Server 2012 R2 amd64 6.3
Jcpuid version: 3
Processor: Nehalem (corei)
Jbigi: Locally optimized library jbigi-windows-corei_64.dll loaded from file
Jbigi version: 3
GMP version: 6.0.0
Encoding: Cp1252
Charset: windows-1252

I have an I2P router running that will not pick up the public IPv4 IP address and subsequently, fails the firewall check. On the webpage (http://127.0.0.1:7657/confignet) it picks up the IPv6 address but there are no other addresses listed even though the server has both IPv6 and IPv4 (NAT) addresses. If I manually enter the public IPv4 address on the "confignet" page, everything works fine. Let me know what what else you need from my side. Thanks.

Subtickets (add)

Attachments (1)

peers.png (203.4 KB) - added by djx 2 years ago.
Peers with IPv6 disabled and IPv4 entered manually

Download all attachments as: .zip

Change History (11)

comment:1 Changed 2 years ago by zzz

  • Component changed from unspecified to router/transport
  • Status changed from new to infoneeded_new
  • You have a UPnP firewall or have configured it manually?
  • If you do have a UPnP device, information on it and the success/failure of configuring the ports will be at the bottom of the /peers page in the console. Check there for clues

comment:2 Changed 2 years ago by djx

  • Status changed from infoneeded_new to new

I configured it manually.
I have a SonicWALL.

The ports are open and the same service objects are applied to both the IPv4 and IPv6 address objects. I2P detects the IPv6 as good to go but can not even detect any IPv4 addresses. IPv4 does work if there is no IPv4 NAT.

comment:3 Changed 2 years ago by djx

Still an issue with the latest release:
I2P version: 0.9.27-0
Java version: Oracle Corporation 1.8.0_111 (Java(TM) SE Runtime Environment 1.8.0_111-b14)
Wrapper version: 3.5.25
Server version: 8.1.17.v20150415
Servlet version: Jasper JSP 2.1 Engine
JSTL version: standard-taglib 1.2.0
Platform: Windows Server 2012 R2 amd64 6.3
Jcpuid version: 3
Processor: Nehalem (corei)
Jbigi: Native BigInteger? library jbigi-windows-corei_64.dll loaded from resource
Jbigi version: 3
GMP version: 6.0.0
Encoding: Cp1252
Charset: windows-1252

comment:4 Changed 2 years ago by zzz

  • Status changed from new to open

Yeah, I wouldn't expect any change in .27 as we never got any closer to what the problem is.

You take at face value what /confignet says (address unknown) and presume that's the cause of being firewalled, but it's almost certainly the reverse - tests show that you're firewalled, so the UI says 'address unknown'. If there's any successful IPv4 UDP connections in or out (look on /peers), it will know what its apparent IP is. But the UI hides that if firewalled, because it's not going to advertise it in its RouterInfo?.

So we're probably back to a typical firewalled issue. Either there's a second firewall behind sonicwall (internal Windows firewall, or an external NAT/firewall) that isn't configured to open the ports, or you've misconfigured sonicwall. I can't help with either case, but you may wish to post on forum.i2p for help.

Perhaps there's a change we could make to the wording on /confignet to make it more clear, I'm not sure... I believe we used to put the IP there even if firewalled, but due to unrelated changes it doesn't any more. We could put it back if that makes sense.

comment:5 Changed 2 years ago by djx

Thanks for the response.

I guarantee that my UDP port is open.
"/peers" shows 32 UDP connections at the moment (6 are IPv6).

I host many different services behind the SonicWALL.
P2P applications using UDP are on the same box and report direct connectivity.

IPv6 is also working just fine.

Not using the Windows firewall.

Let me know what other info you need from me.

Thanks.

comment:6 Changed 2 years ago by djx

Just on a whim, I manually typed in my external IPv4 IP address into the "IP Configuration: Specify hostname or IP" on the "/confignet" page and after I restarted I2P, all is good. It was previously on " Use all auto-detect methods". "/confignet" now reports "OK". It auto-detected my IPv6 address already so I didn't have to type that in.

Last edited 2 years ago by djx (previous) (diff)

comment:7 Changed 2 years ago by zzz

yeah, that will work, it essentially forces non-firewalled

I'm stuck for now but will keep pondering it.

Now that you've configured your ipv4 address, on /peers, check to see if you have incoming IPv4 UDP and TCP connections (big down arrow in 2nd column, no check in 3rd column)

Changed 2 years ago by djx

Peers with IPv6 disabled and IPv4 entered manually

comment:8 Changed 2 years ago by djx

  • Version changed from 0.9.26 to 0.9.27

comment:9 Changed 2 years ago by zzz

Thanks for the screenshot. I'm still stumped for now.

comment:10 Changed 23 months ago by djx

  • Description modified (diff)
  • Version changed from 0.9.27 to 0.9.29
Note: See TracTickets for help on using tickets.