I2P Bugtracker: Ticket #2429: Firewall status reports OK when UDP is firewalled https://trac.i2p2.de/ticket/2429 <p> In the event that UDP is indicated as firewalled (on /peers) and introducers are required for SSU, the firewall status indicator in the sidebar should not indicate "OK" as this is misleading. </p> <p> On a related issue, the setup wizard could run a series of tests to determine TCP/UDP status and optimally configure the router or provide guidance on how to correct potential issues (port forwarding, general firewall/router configuration etc). </p> en-us I2P Bugtracker https://trac.i2p2.de/chrome/site/i2plogo.png https://trac.i2p2.de/ticket/2429 Trac 1.2.3 Reportage Thu, 07 Feb 2019 06:47:59 GMT description changed https://trac.i2p2.de/ticket/2429#comment:1 https://trac.i2p2.de/ticket/2429#comment:1 <ul> <li><strong>description</strong> modified (<a href="/ticket/2429?action=diff&amp;version=1">diff</a>) </li> </ul> Ticket jogger Tue, 16 Apr 2019 14:24:32 GMT https://trac.i2p2.de/ticket/2429#comment:2 https://trac.i2p2.de/ticket/2429#comment:2 <p> I would like to describe the situation around this. This has been around for years on my routers. Got 2 routers in the same family with perfect connectivity on the same IP with IPv6 and IPv4 w/ NAT. They even share the same firewall rules where possible. They only differ in port and local IP. Drove me nuts and I gave up on this one more than two years ago. </p> <p> IPv6 is fine all the time. One router comes up fine all the time. Second one rarely comes up fine or wrongly as completely IPv4 firewalled. Most of the time comes up as described in the OP. Working NTCPv4 address with inbound connections, but SSUv4 wrongly as firewalled with introducers. Lefthand panel says "Network OK", event log says: "Reachability change from IPv4: Testing; IPv6: OK to IPv4: Firewalled; IPv6: OK". When there is an IP change, it appears in the event log, but the NTCPv4 address stays unchanged and that type of traffic starves out. advanced config i2np.udp.port= jumps around in the range assigned by the masquerading rule. </p> <p> Settings used: i2np.ipv4.firewalled=false i2np.ipv6.firewalled=false i2np.laptopMode=false i2np.ntcp.autoip=always i2np.ntcp.enable=true i2np.ntcp.ipv6=preferIPv6 i2np.ntcp2.enable=true i2np.udp.addressSources=local,ssu i2np.udp.enable=true i2np.udp.internalPort=12345 i2np.udp.ipv6=preferIPv6 i2np.udp.maxConnections=2222 i2np.udp.port=55555 i2np.upnp.enable=false </p> Ticket jogger Tue, 16 Apr 2019 17:33:46 GMT https://trac.i2p2.de/ticket/2429#comment:3 https://trac.i2p2.de/ticket/2429#comment:3 <p> In the above situation found kind of a weird workaround: </p> <p> i2np.udp.addressSources=local,ssu corresponds to "Disable UPnP IP address detection". </p> <p> Setting i2np.udp.addressSources=upnp,ssu ("Ignore local interface IP address") gives a soft restart. A valid SSUv4 address appears and the SSUv6 address is killed (which is a further bug). </p> <p> Againg clicking "Disable UPnP IP address detection" makes the SSUv6 address reappear and voila: router fully connected as it should. </p> Ticket