![]() ![]() ![]() |
|
vulcannz:Finally clicked at what I'd done wrong in my static configuration - bit of a derp moment. Anyway now I have static working again I'm able monitor my IPv6 WAN interface for logiical failures.
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
NickMack:vulcannz:
Finally clicked at what I'd done wrong in my static configuration - bit of a derp moment. Anyway now I have static working again I'm able monitor my IPv6 WAN interface for logiical failures.
Good news - would you like to share for others?
Nick
WAN subnet was a /56, should have been a /64. In my defense I did post screenshots and nobody else spotted it :)
In the meantime my v6 has dropped out again. I didn't get an alert (not sure why) so my best guess is a failure between 7.30am and 10am at the moment. I need to figure out why I am not getting alerts sometime tonight.
Mine failed again, seems to be time related:
Up: 21:59:27 Nov 26 585 Network Alert WLB Resource is now available
Failed: 27 21:56:48 Nov 27 326 Network Alert Probing failure on PPPoE Client
I restarted my box, this did not fix the issue. I changed the WAN IPv6 interface from static to DHCPv6, this then fixed the connection. Then I changed it back to Static and connection stays up.
Note this still happens when the WAN interface is set to DHCPv6. Could it be related to RA timings/expiration's?
vulcannz:I restarted my box, this did not fix the issue. I changed the WAN IPv6 interface from static to DHCPv6, this then fixed the connection. Then I changed it back to Static and connection stays up.
Note this still happens when the WAN interface is set to DHCPv6. Could it be related to RA timings/expiration's?
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
No not fritzbox, but I'm not alone in the issue - it's happening across multiple hardware platforms. I do wonder if its an issue with the preferred lifetime flag which usually is 1440 mins, but shows up different (10000ish iirc). Probably going to need to go down to some packet level diagnostics on what is coming down the line.
Nick, be great if you could detail what settings that the Fritzbox typically connects your network with..
As the Fritzbox itself doesn't show on our end, maybe you can see on your end?
attewell:
Nick, be great if you could detail what settings that the Fritzbox typically connects your network with..
As the Fritzbox itself doesn't show on our end, maybe you can see on your end?
As per this thread - https://www.geekzone.co.nz/forums.asp?forumid=85&topicid=240157, what else specifically are you looking for/do you feel as though you need?
Nick
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
vulcannz:
No not fritzbox, but I'm not alone in the issue - it's happening across multiple hardware platforms. I do wonder if its an issue with the preferred lifetime flag which usually is 1440 mins, but shows up different (10000ish iirc). Probably going to need to go down to some packet level diagnostics on what is coming down the line.
Hiya,
We have the default setting on our side - As per our Juniper documentation the preferred lifetime is 24 hours = 1440 mins / 86400 seconds.
How are you capturing the value of ~10000? (CLI show command/packet capture etc?)
Nick
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
NickMack:
As per this thread - https://www.geekzone.co.nz/forums.asp?forumid=85&topicid=240157, what else specifically are you looking for/do you feel as though you need?
Nick
Settings like in here
@attewell You're going too far here, there is no way that 2degrees are going to support or provide settings for other routers, this is all on your own.
On another note - since implementing my dodgy script I've only ever had one outage on Sunday which was promptly resolved. I honestly think most people here have configuration issues on their end. Furthermore, EdgeOS isn't great with IPv6 and doesn't seem to re-establish a prefix on reconnect however the latest OS seems a little more stable with it.
Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)
Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.
attewell:
NickMack:
As per this thread - https://www.geekzone.co.nz/forums.asp?forumid=85&topicid=240157, what else specifically are you looking for/do you feel as though you need?
Nick
Settings like in here
Hiya,
Sorry, you need to engage with the Linux community for support, I can't add any value here.
Nick.
https://nick.mackechnie.co.nz | NZ ISP latency monitoring - https://smokeping.thenet.gen.nz
michaelmurfy:
@attewell You're going too far here, there is no way that 2degrees are going to support or provide settings for other routers, this is all on your own.
On another note - since implementing my dodgy script I've only ever had one outage on Sunday which was promptly resolved. I honestly think most people here have configuration issues on their end. Furthermore, EdgeOS isn't great with IPv6 and doesn't seem to re-establish a prefix on reconnect however the latest OS seems a little more stable with it.
I must be one of the few whom haven't had the issue since the ONT upgrades, IPv6 has been solid on all accounts. I have noticed some weirdness, however, but assuming thats related more to the ER than anything else.
steven@rtr01:~$ show log | grep -i eth0 | tail -n10
Nov 28 06:35:03 rtr01 kernel: eth0: Link down
Nov 28 06:35:04 rtr01 kernel: eth0: 1000 Mbps Full duplex, port 0
Nov 28 06:50:52 rtr01 kernel: eth0: Link down
Nov 28 06:50:54 rtr01 kernel: eth0: 1000 Mbps Full duplex, port 0
Nov 28 10:10:56 rtr01 kernel: eth0: Link down
Nov 28 10:10:59 rtr01 kernel: eth0: 1000 Mbps Full duplex, port 0
Nov 28 13:03:43 rtr01 kernel: eth0: Link down
Nov 28 13:03:46 rtr01 kernel: eth0: 1000 Mbps Full duplex, port 0
Nov 28 14:10:18 rtr01 kernel: eth0: Link down
Nov 28 14:10:19 rtr01 kernel: eth0: 1000 Mbps Full duplex, port 0
steven@rtr01:~$
Constantly.. who knows, will await a new ERLite firmware to see if it disappears. /hijack
Referral Links:
Quic - Use code R536299EPGOCN at checkout for free setup
Contact Energy - Use code FRTQDXB for $100 credit
vulcannz:
I restarted my box, this did not fix the issue. I changed the WAN IPv6 interface from static to DHCPv6, this then fixed the connection. Then I changed it back to Static and connection stays up.
Note this still happens when the WAN interface is set to DHCPv6. Could it be related to RA timings/expiration's?
Since the latest update to the Junipers you are connecting to, you will not get an IPv6 connection until you have done a DHCPv6 request to the Juniper. I previously had my ERL set up with my static IPv6 addresses, and when the new firmware was installed, I lost the IPv6 connection. To restore it, I kept the static addresses I am using, but also added some config to get the ERL to request a DHCPv6 delegation. The new config does nothing with the delegated prefix - it just throws it away. But until it is requested, the Juniper now refuses to route IPv6 packets, even if you have a static IPv6 assignment. My guess is that every time the PPPoE connection needs to be reestablished, you will need to request a DHCPv6 delegation.
So I lost IPv6 again last night, was working fine from the USG until around 8 or 9 when suddenly it went away again. As I'm using the Unifi range, I have the unifi controller running with IPv6 set to DHCPv6 and a 56 prefix in the settings. This laptop currently has an IPv6 address assigned to it but I can route out via 2degrees; ipv6.google.com does not work.
Why should the connection to the IPv6 range just drop out when it was working fine, yet still think its connected?
|
![]() ![]() ![]() |