Good morning, Since upgrading to 6.37, router is having trouble getting IPv6 prefix delegation after reboot. Sometimes the dhcp client will finally renew and bind the PD, after 5 minutes or more. Sometimes it fails. Forcing renewal doesn’t help. But if I disable & reenable the dhcpv6 client on the pppoe interface, then it gets PD immediately. Personal observation says there is a timing issue, with dhcp client trying to get PD before pppoe interface is up (but that’s just a guess). Is this a known/common problem? Or an issue with v6.37? What can I do to resolve it? Thanks, Charlie -- Charlie Garrison <garrison@zeta.org.au> github.com/cngarrison metacpan.org/author/CNG
Bumping this old message… any suggestions? Same problem persists with 6.37.1 & .2. On 26 Sep 2016, at 9:45, Charlie Garrison wrote:
Good morning,
Since upgrading to 6.37, router is having trouble getting IPv6 prefix delegation after reboot.
Sometimes the dhcp client will finally renew and bind the PD, after 5 minutes or more. Sometimes it fails. Forcing renewal doesn’t help. But if I disable & reenable the dhcpv6 client on the pppoe interface, then it gets PD immediately.
Personal observation says there is a timing issue, with dhcp client trying to get PD before pppoe interface is up (but that’s just a guess).
Is this a known/common problem? Or an issue with v6.37? What can I do to resolve it?
Thanks, Charlie
--
Charlie Garrison <garrison@zeta.org.au> github.com/cngarrison metacpan.org/author/CNG
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
-- Charlie Garrison <garrison@zeta.org.au> github.com/cngarrison metacpan.org/author/CNG
On Fri, 2016-11-25 at 08:38 +1100, Charlie Garrison wrote:
But if I disable & reenable the dhcpv6 client on the pppoe interface, then it gets PD immediately.
Run a script that disables the client, waits two seconds, then enables the client. Run it every minute. You could make it sophisticated enough to check whether the problem exists first, but even if you just blindly disable/enable it shouldn't hurt anything. It's a kludge though. Regards, K. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Karl Auer (kauer@nullarbor.com.au) work +61 2 64957435 http://www.nullarbor.com.au mobile +61 428 957160 GPG fingerprint: 6D59 8AE6 810D 44E3 7626 7040 4DD6 F89F 3053 4774 Old fingerprint: 9DCA 0903 BCBD 0647 BCCC 2FA7 A35C 57A1 ACF9 00BB
Good morning, On 25 Nov 2016, at 9:54, Karl Auer wrote:
Run a script that disables the client, waits two seconds, then enables the client. Run it every minute. You could make it sophisticated enough to check whether the problem exists first, but even if you just blindly disable/enable it shouldn't hurt anything.
Thanks for that, good idea. The problem only happens after a reboot, so a startup script should suffice. Yep, it’s a kludge, but will be heaps better than logging into router and doing it manually after each reboot. Does anyone have any troubleshooting tips? I could try ISP again, but last query resulted in “we don’t support that hardware”. Thanks, Charlie -- Charlie Garrison <garrison@zeta.org.au> github.com/cngarrison metacpan.org/author/CNG
Hi Charlie, What ISP are you with? I have an Internode plan with a Power Pack, and IPv6 set up on my RB850 running 6.37.2 and I don't see any issues like what you've described. Within 5-10 seconds of the PPPoE connecting, the IPv6 client grabs its prefix as well. Regards, Ben Farmer -----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Charlie Garrison Sent: Friday, 25 November 2016 9:17 To: MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] ROS 6.37 and DHCPv6 client Good morning, On 25 Nov 2016, at 9:54, Karl Auer wrote:
Run a script that disables the client, waits two seconds, then enables the client. Run it every minute. You could make it sophisticated enough to check whether the problem exists first, but even if you just blindly disable/enable it shouldn't hurt anything.
Thanks for that, good idea. The problem only happens after a reboot, so a startup script should suffice. Yep, it’s a kludge, but will be heaps better than logging into router and doing it manually after each reboot. Does anyone have any troubleshooting tips? I could try ISP again, but last query resulted in “we don’t support that hardware”. Thanks, Charlie -- Charlie Garrison <garrison@zeta.org.au> github.com/cngarrison metacpan.org/author/CNG _______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
Good morning, On 25 Nov 2016, at 10:35, Ben Farmer wrote:
What ISP are you with? I have an Internode plan with a Power Pack, and IPv6 set up on my RB850 running 6.37.2 and I don't see any issues like what you've described.
I’m using Internode.
Within 5-10 seconds of the PPPoE connecting, the IPv6 client grabs its prefix as well.
I’m certainly seeing different behaviour. :-\ Anyone see issues with config: [charlie@Router - RB2011] > /ipv6 dhcp-client export verbose # nov/25/2016 10:00:45 by RouterOS 6.37.2 # software id = IP92-LX4F # /ipv6 dhcp-client add add-default-route=yes disabled=no interface=pppoe-out1 pool-name=node-ipv6 pool-prefix-length=64 prefix-hint=::/0 request=prefix use-peer-dns=no Thanks, Charlie -- Charlie Garrison <garrison@zeta.org.au> github.com/cngarrison metacpan.org/author/CNG
participants (3)
-
Ben Farmer -
Charlie Garrison -
Karl Auer