Billion UK Forum

mickod wrote:Yes I can attach clients directly to the Billion ethernet ports and they get an IPv6 address and work without issue - however, not via dhcpv6.

They seem to get their IP address via SLAAC (ICMPv6) according to wireshark pcap files I've checked.

Thanks,
mick

If you mean 'Stateful' is not working, once set restart the router attached is some examples off my 8800 series.

Some feedback on this ...

It seems that DHCP6S will only start on my Billion 8800NL with the following software 2.32d.dm12 when the "Interface Address / Prefix Length" field is filled in as per below...
My macbook pro receives an IPv6 Global Unicast address from this prefix via the DHCP6S without issue and I have full native IPv6 connectivity.

I still have an issue in that my other wifi router downstream of the billion doesn't seem to receive an IPv6 address via DHCPv6 but I guess this isn't necessarily a billion issue.

This is a small bit buggy in my opinion as I should not need to configure the prefix on the LAN configuration IPv6 Autoconfig tab. The billion is clearly receiving my /56 prefix delegated from the ISP DHCPv6 server and this can be seen in the Summary information, but yet it does not want to run a DHCPv6 server using this prefix.

Any thoughts on this? Would a firmware upgrade be warranted here?

mickod wrote:Some feedback on this ...

It seems that DHCP6S will only start on my Billion 8800NL with the following software 2.32d.dm12 when the "Interface Address / Prefix Length" field is filled in as per below...

billion-lan-ipv6-autoconfig-mickod.png

My macbook pro receives an IPv6 Global Unicast address from this prefix via the DHCP6S without issue and I have full native IPv6 connectivity.

I still have an issue in that my other wifi router downstream of the billion doesn't seem to receive an IPv6 address via DHCPv6 but I guess this isn't necessarily a billion issue.

This is a small bit buggy in my opinion as I should not need to configure the prefix on the LAN configuration IPv6 Autoconfig tab. The billion is clearly receiving my /56 prefix delegated from the ISP DHCPv6 server and this can be seen in the Summary information, but yet it does not want to run a DHCPv6 server using this prefix.

Any thoughts on this? Would a firmware upgrade be warranted here?

I'll check with our engineers and get back to you.

Hi billion_fan,

Is it possible for the billion to do DHCPv6-PD (Prefix Delegation) instead of just a standard DHCPv6 server? I'd like to expand out the LAN also to multiple segments.

Thanks,
mick

mickod wrote:Hi billion_fan,

Is it possible for the billion to do DHCPv6-PD (Prefix Delegation) instead of just a standard DHCPv6 server? I'd like to expand out the LAN also to multiple segments.

Thanks,
mick

I'll check with our engineers and get back you.

I just tested the latest firmware 2.32e.d14, and all is working well without setting the Interface Address / Prefix Length. (firmware is attached at the bottom of the last screen shot)

Make sure you set the DNS to 'Obtain IPv6 DNS info from a WAN interface' to your VDSL interface (ppp1.1)

Tested with BT VDSL 8800NL 2.32e.d14 (as you are on 2.32d firmware it is advised to upgrade then reset back to factory default settings, then manually reconfigure again, this is ensure all changes are implemented correctly. Do not restore settings from previous firmware builds)

Screen shots attached

One last thing, once everything is set, you might need renew your IPv6 address

billion_fan I notice that the firmware you have attached to this thread is a different size to the 2.32e that is attached to the sticky post.

Is 2.32e.d14 different from the 2.32e in the sticky? I presume I am running 2.32e as that is what's reported under "Software Version" on my main status page. I notice in your screenshot above your software version is reported as "2.32e.d14" (mine doesn't mention the d14 part.

Should I flash the d14 version??

Thanks

ledgie wrote: ↑Fri Jan 26, 2018 12:48 pm billion_fan I notice that the firmware you have attached to this thread is a different size to the 2.32e that is attached to the sticky post.

Is 2.32e.d14 different from the 2.32e in the sticky? I presume I am running 2.32e as that is what's reported under "Software Version" on my main status page. I notice in your screenshot above your software version is reported as "2.32e.d14" (mine doesn't mention the d14 part.

Should I flash the d14 version??

Thanks

Yes you can upgrade if you want, 2.32.dh14 is latest version with the port forwarding fix

billion_fan wrote: ↑Fri Jan 26, 2018 12:53 pm

ledgie wrote: ↑Fri Jan 26, 2018 12:48 pm billion_fan I notice that the firmware you have attached to this thread is a different size to the 2.32e that is attached to the sticky post.

Is 2.32e.d14 different from the 2.32e in the sticky? I presume I am running 2.32e as that is what's reported under "Software Version" on my main status page. I notice in your screenshot above your software version is reported as "2.32e.d14" (mine doesn't mention the d14 part.

Should I flash the d14 version??

Thanks

Yes you can upgrade if you want, 2.32.dh14 is latest version with the port forwarding fix

Does it include the fix for the Upload Speed bug related to QoS?

GaZaai wrote: ↑Fri Jan 26, 2018 1:29 pm

billion_fan wrote: ↑Fri Jan 26, 2018 12:53 pm

ledgie wrote: ↑Fri Jan 26, 2018 12:48 pm billion_fan I notice that the firmware you have attached to this thread is a different size to the 2.32e that is attached to the sticky post.

Is 2.32e.d14 different from the 2.32e in the sticky? I presume I am running 2.32e as that is what's reported under "Software Version" on my main status page. I notice in your screenshot above your software version is reported as "2.32e.d14" (mine doesn't mention the d14 part.

Should I flash the d14 version??

Thanks

Yes you can upgrade if you want, 2.32.dh14 is latest version with the port forwarding fix

Does it include the fix for the Upload Speed bug related to QoS?

No that has been explained in previous posts