FS#650 - 6in4 addresses are not advertised via DHCP.

[aparcar]

neheb:

Supply the following if possible:

• Archer C7v2
• master

• Steps to reproduce Set up a 6in4 tunnel. Connect to the network using DHCP.

  I'm guessing this is an odhcpd bug since IPv6 advertising is done through it. Not sure if this applies to router advertisements or DHCPv6.

  As a result, the router has an IPv6 connection but nothing else does. Interestingly enough the log is full of spam like this:

  odhcpd[962]: A default route is present but there is no public prefix on br-lan thus we don't announce a default route!

[aparcar]

dedeckeh:

The odhcpd trace indicates there's no public IPv6 prefix on the lan and as such RAs cannot be sent with router lifetime different from 0. Can you attach the network config used in the scenario, ifstatus lan and also the output of ip -6 addr show

[aparcar]

neheb:

http://pastebin.com/Vv4NJcrM

Weird since in the 6in4 config there is a routed prefix specified.

[aparcar]

dedeckeh:

Confirms indeed there's no public IPv6 prefix on the lan; thus odhcpd behaves as expected. Attach your network config to the task otherwise it's hard to trouble shoot what's going on with the limited available info together with the output of ifstatus <6in4 interface>

[aparcar]

neheb:

http://pastebin.com/m2nr1U0i

All I know is, it used to work at some point back in OpenWrt.

[aparcar]

dedeckeh:

Please upload this as attachment

[aparcar]

neheb:

Here.

[aparcar]

arjendekorte:

You have not specified a prefix length. The line

    option ip6prefix '2001:470:1f05:c3e::'

should be

    option ip6prefix '2001:470:1f05:c3e::/64'

assuming you have just the default /64 assigned to you.

[aparcar]

neheb:

Aaand that was the issue. I think I did this out of habit from my tomato days where you stripped the 64 from the prefix.