Opened 4 weeks ago

Last modified 4 weeks ago

#2807 accepted defect

IPv6 falsely reported as firewalled

Reported by: jogger Owned by: zzz
Priority: minor Milestone: 0.9.50
Component: router/transport Version: 0.9.49
Keywords: Cc:
Parent Tickets: Sensitive: no

Description

Interfaces on debian system enumerated as follows:

  • loopback
  • internal ethernet without routable adresses
  • external ethernet without routable adresses
  • VLAN on top of external ethernet without routable adresses
  • ppp0 on top of VLAN with publically routable v4/v6 addresses acquired

v4/v6 external addresses correctly shown on /confignet and used for traffic. v6 reported as firewalled.

Workaround: I used wide-dhcpv6-client to acquire a publically routable (but firewalled) v6 address for the internal ethernet interface. Network status immediately jumped to OK, new firewalled v6 address added to /confignet.

I guess, IPv6 firewall status is derived from the wrong interface.

Subtickets

Change History (1)

comment:1 Changed 4 weeks ago by zzz

Milestone: undecided0.9.50
Status: newaccepted

Yup. I've done extensive work on IPv6 state detection and transitions, and IPv6 UPnP, in the 0.9.49-x dev cycle. I suspect these changes will fix your issue.

i2pd is working on implementing IPv6 peer testing, that they didn't have before, right now.

We're both working on IPv6 introductions and introducers (proposal 158).

I don't believe it's an interface issue. If we find a public address on any interface we'll use it.

'java -jar /path/to/i2p.jar addresses' will tell you what we see.

Please test 0.9.49-10 or higher and report results

Note: See TracTickets for help on using tickets.