Please update odhcpd to latest version

I’m experiencing the issue described here with current turrisos odhcpd-2015-05-21 package.

My turris omnia router sits behind my isp’s router/cable modem (which I have to use) I depend on NDP to proxy and delegate an ipv6 address space. The issue with odhcpd-2015-05-21 package is that it doesn’t send neighbor solicitation requests for global scope ipv6 addresses. I have to either ping the router’s global ipv6 address from my client or run this from the router:
ping6 -c 5 -I (global ipv6 address) ff02::1

to be able to route out to the internet with ipv6.

I’ve compile the odhcpd package with the Makefile found here:

and can confirm that my router is now correctly finding the global ipv6 address of my clients.

old version:
16:08:08.257259 IP6 :: > ff02::1:fff5:dc47: ICMP6, neighbor solicitation, who has 2a02:8070:4b8:200:b40d:cc29:82f5:dc47, length 24
16:08:08.321195 IP6 :: > ff02::1:ffdd:a029: ICMP6, neighbor solicitation, who has 2a02:8070:4b8:200:4fe:68ba:abdd:a029, length 24
16:08:11.055310 IP6 fe80::da58:d7ff:fe00:472b > ff02::1: ICMP6, router advertisement, length 152
16:08:12.557620 IP6 fe80::da58:d7ff:fe00:472b > fe80::ae34:95ab:feb6:d0f7: ICMP6, neighbor solicitation, who has fe80::ae34:95ab:feb6:d0f7, length 32
16:08:12.557892 IP6 fe80::ae34:95ab:feb6:d0f7 > fe80::da58:d7ff:fe00:472b: ICMP6, neighbor advertisement, tgt is fe80::ae34:95ab:feb6:d0f7, length 24
16:08:16.063983 IP6 fe80::da58:d7ff:fe00:472b > ff02::1: ICMP6, router advertisement, length 152
16:08:16.832818 IP6 fe80::ae34:95ab:feb6:d0f7 > fe80::da58:d7ff:fe00:472b: ICMP6, neighbor solicitation, who has fe80::da58:d7ff:fe00:472b, length 32
16:08:16.832872 IP6 fe80::da58:d7ff:fe00:472b > fe80::ae34:95ab:feb6:d0f7: ICMP6, neighbor advertisement, tgt is fe80::da58:d7ff:fe00:472b, length 24

new version:
16:00:17.742589 IP6 :: > ff02::1:ffdd:a029: ICMP6, neighbor solicitation, who has 2a02:8070:4b8:200:4fe:68ba:abdd:a029, length 24
16:00:17.750550 IP6 :: > ff02::1:ffdd:a029: ICMP6, neighbor solicitation, who has fd53:f10b:abc8::4fe:68ba:abdd:a029, length 24
16:00:17.958533 IP6 :: > ff02::1:fff5:dc47: ICMP6, neighbor solicitation, who has 2a02:8070:4b8:200:b40d:cc29:82f5:dc47, length 24
16:00:18.102604 IP6 :: > ff02::1:fff0:3462: ICMP6, neighbor solicitation, who has fd53:f10b:abc8::690b:55fb:f7f0:3462, length 24
16:00:20.927878 IP6 fe80::da58:d7ff:fe00:472b > 2a02:8070:4b8:200:4fe:68ba:abdd:a029: ICMP6, neighbor solicitation, who has 2a02:8070:4b8:200:4fe:68ba:abdd:a029, length 32
16:00:20.928140 IP6 2a02:8070:4b8:200:4fe:68ba:abdd:a029 > fe80::da58:d7ff:fe00:472b: ICMP6, neighbor advertisement, tgt is 2a02:8070:4b8:200:4fe:68ba:abdd:a029, length 24
16:00:22.537922 IP6 fe80::da58:d7ff:fe00:472b > fe80::ae34:95ab:feb6:d0f7: ICMP6, neighbor solicitation, who has fe80::ae34:95ab:feb6:d0f7, length 32
16:00:22.538203 IP6 fe80::ae34:95ab:feb6:d0f7 > fe80::da58:d7ff:fe00:472b: ICMP6, neighbor advertisement, tgt is fe80::ae34:95ab:feb6:d0f7, length 24

1 Like

This fork seems to well updated:

this github repo is just a mirror of git.openwrt.org Git - project/odhcpd.git/summary (git.openwrt.org Git - project/odhcpd.git/summary), which is indeed actively maintained

Ah didn’t notice that. Yeah would be nice to have that version, since I think that’s my issue with IPv6 at the moment.

+1 on this. While I’ve gotten ipv6 to work using brouter for OpenWRT, https://github.com/cvmiller/v6brouter , brouter requires a bit of skill to set up. The case of needing neighbor discovery proxy is common enough that it would help ipv6 adoption for odhcpd to work as it’s supposed to, because then it can be configured from luci.

So I pulled out my previous router and put on LEDE and I’m having the same issues, where I get DHCPv6 on WAN, but on the LAN I only get ULA, which doesn’t route. I had tried this: https://forum.openwrt.org/viewtopic.php?pid=315621#p315621 before, but seemed I needed to added a rule to allow ports through in the firewall, and as soon as I added a rule, everything broke on the Omnia.

IPv6 has been out for years, but the support for on these router firmwares are joke. IPv6 is pretty much a drunken dev fest that happened and lots of things don’t make sense with it. Is there any consumer grade routers that just work with IPv6 no matter what?

@ellisgl don’t know where you live but I know of one consumer router that works pretty well with AT&T and Comcast ipv6 in the US…the ASUS routers running ASUSWRT (or alternately you can run Merlin firmware, which kind of is ASUSWRT with bugfixes and some smaller add on features). There may be others, but I’ve used these on both AT&T and Comcast.

For AT&T, ipv6 works fine if you choose “Passthrough” on the ASUS ipv6 settings. It looks like what is going on here is that the Asus router uses 6relayd (since replaced by odhcpd on OpenWRT) to relay RA, DHCPv6 and NDP as necessary.

For Comcast, ipv6 works fine if you choose “Native” on the ASUS ipv6 settings. In this case, things work as you expect, the ASUS router gets a /60 from Comcast, then supports DHCPv6, SLAAC and RA for clients on the LAN.

I’m in the Dallas/Fort Worth area of Texas, pretty much the heart land of AT&T and Charter.I’ll pick up an ASUS router then. I’m really sadden that Big 2 (3) open source router firmware options are just crap when it come to IPv6.

@ellisgl np, let me know how this works out. At least with the Asus, easy to return it if it doesn’t work.

Just bought an ASUS RT-AC3200 and should have it tomorrow and will report back. I just want to be able to implement IPv6 and be part of the movement to try to get IPv6 implemented all over. Of course IPv6 means jack crap to lots of users. To me, I want to be part of the future, I want to learn about it (besides all the damned certs I have that involve IPv6) hands on.

OK. The RT-AC3200 works, after upgrading the firmware (to do IPv6 Passthought). The only issue I’m having is inbound connection - don’t have a way to really test that. Port scanner says the port is filtered. Internally it works of course.
http://[2602:306:3275:a2d0:98cf:c795:202d:81f8]:8080

the ASUS router has an ipv6 firewall, which I believe defaults to on.

I think my issue happens to be the 3800HGV-B’s - Even though it’s in DMZ-Plus mode, IPv6 incoming packets are blocked. Seeing if I can get a better modem from them. Of course Charter might be a better bet anyways, since it’s $30 for 100 Mb / 5 Mb (I think it’s $45 after one year - which is way less than the $68 ($70+ after taxes and fees) I’m paying for 18 Mb (I get 21 / 22 down though), but only 1.5 up.

@ellisgl that’s correct. All of AT&T’s gateways disallow unsolicited inbound ipv6. If you’re trying to run an ipv6 server that makes it rather difficult…trying to get a better gateway, I don’t think you’ll have much luck. I have their latest 5268AC for AT&T Fiber and it still has this restriction. It’s not the hardware, when these gateways are used by other providers they don’t have these restrictions. If you’ll be switching to Charter, you may want to research on other folks experiences as switching ISPs is always a good chunk of work. It looks to me llke Charter uses 6rd. A good place to ask questions on ASUS routers is snbforums.com, that’s where the popular Merlin firmware for these routers is also supported.

So it sounds like a block upstream, not the modem itself. If that is the case, it might be a call to tech support to allow it through (Just like I had to allow SMTP to allowed through so I could host an SMTP server (ugh - long story)).

Interesting, let me know if you can get it unblocked and who you talked to.

I have a similar problem where Android devices get their IPv6 addresses but not default IPv6 router.
It’s unbelievable that NIC.CZ are serving such massively outdated software, I was expecting more from the Turris Project. I think I’ve placed money on a wrong horse.

They’re planning to update all packages in version 3.6

Thank you @Pepe for update. Where can I track version roadmap and release schedule? That would clear up lots of misunderstands.

(Sorry it should be even in 3.6, but nothing in nightly right now)