#18273: 6to4: stuck in INVALID_LOCAL_ADDRESS
--------------------------------------------+------------------------
Reporter: Catalin Patulea <cronos586@…> | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone:
Component: packages | Version: Trunk
Resolution: | Keywords: ipv6 6to4
--------------------------------------------+------------------------
Comment (by Catalin Patulea <cronoss586@…>):
I'm still running into this regularly. IPv6 is not a critical service on
my network, but it would be nice for it to work reliably.
To recap what I think is happening:
- My cable modem reboots for whatever reason (triggered by ISP, or maybe
occasional crash, I don't know).
- OpenWrt notices link cycle, and when link comes back up, starts DHCP
client.
- The *cable modem* gives the router an IP in 192.168.100.* because the CM
isn't on the upstream (coax) network yet.
- OpenWrt acquires this IP, and triggers wan6 6to4 to start, too.
- 6to4 notices the RFC1918 and wedges wan6 in 'INVALID_LOCAL_ADDRESS'
state.
- Somehow (not clear on this part), when the cable modem registers on the
network, OpenWrt acquires a new DHCP lease, with a valid IPv4 public
routable address. This lease comes from further up in the network (cable
modem switches to DHCP relaying). If 6to4 retried at this point, it would
succeed and bring up IPv6.
Is there a recommended workaround here? I do want to have connectivity to
my modem before it registers on the coax network.
Can 'INVALID_LOCAL_ADDRESS' be made retriable (I think I saw other errors
that are retriable, and could adapt that handling), so that wan6 retries
after wan gets its real public IPv4?
--
Ticket URL: <https://dev.openwrt.org/ticket/18273#comment:1>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
