8900AX-1600R2 - intermittent WAN connection failure

Discussions for BiPAC 8900 series: 8900AX-1600, 8900AX-2400, 8900X
Pete B
Posts: 24
Joined: Tue Sep 15, 2015 3:15 pm

8900AX-1600R2 - intermittent WAN connection failure

Post by Pete B » Tue Nov 05, 2019 12:55 pm

Hi
Over the past few days I've had my router intermittently rebooting itself for reasons I don't yet understand. On one occasion I had 3 reboots inside an hour but then it might go 3 or 4 days, or longer, without rebooting itself. I have included an extract (slightly edited) from the syslog showing a typical lead up to a reboot and would welcome suggestions as to why this might be happening...

Code: Select all

Nov  5 11:55:28 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:28 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:28 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:28 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:28 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:28 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:28 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:29 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:29 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:29 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:29 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:29 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:29 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:29 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:29 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:29 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:30 kern crit kernel: eth4 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Nov  5 11:55:30 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:30 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:30 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:30 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:30 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:30 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:31 daemon warn radvd[9135]: poll error: Interrupted system call
Nov  5 11:55:31 daemon warn radvd[9135]: Exiting, sigterm received.
Nov  5 11:55:31 daemon err dhcp6c[8982]: client6_send: transmit failed: Network is unreachable
Nov  5 11:55:32 kern warn kernel: ETH Init: Ch:1 - 200 tx BDs at 0xb0820650
Nov  5 11:55:32 kern warn kernel: ETH Init: Ch:1 - 600 rx BDs at 0xb0a21910
Nov  5 11:55:32 kern warn kernel: [FAP1] enetRxChannel 1
Nov  5 11:55:32 kern crit kernel: eth4 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Nov  5 11:55:35 daemon info email[17496]: eMail: SMTP_SERVER:smtp.fastmail.com SMTP_USER:xxxxxxxx@fastmail.net SMTP_PASS:xxxxx SENDER_MAIL:xxxxxxxxt@fastmail.net PORT:587 USE_TLS:true
Nov  5 11:55:35 daemon info email[17496]: eMail: Subject:WAN IP Change (new IP:192.168.2.0)
Nov  5 11:55:37 kern warn kernel: eth4.1 MAC address set to 60:03:47:4B:6C:25
Nov  5 11:55:37 kern warn kernel: netdev path : eth4.1 -> eth4
Nov  5 11:55:37 kern warn kernel: BCMVLAN : eth4 mode was set to RG
Nov  5 11:55:37 daemon notice syslog: pppd:cms logging initialized.
For info also, the EWAN port is fed by a DrayTek Vigor 130 modem, hence the subnet at 192.168.2.x, the router is 192.168.1.1 and clearly it's IPv6 enabled, which I think might be where the problem is... some IPv6 addressing conflict ? The entry for eth4 at 11:55:30 is perhaps slightly odd (and probably a 'red herring' ?) because eth4 is not in use on this router, only eth1, 2 & 3 are used. Any ideas as to what might be going on here would be appreciated thanks.
Last edited by Pete B on Thu Nov 07, 2019 4:03 pm, edited 1 time in total.

billion_fan
Posts: 5205
Joined: Tue Jul 19, 2011 4:30 pm

Re: 8900AX-1600R2 - intermittent rebooting

Post by billion_fan » Tue Nov 05, 2019 1:44 pm

Pete B wrote:
Tue Nov 05, 2019 12:55 pm
Hi
Over the past few days I've had my router intermittently rebooting itself for reasons I don't yet understand. On one occasion I had 3 reboots inside an hour but then it might go 3 or 4 days, or longer, without rebooting itself. I have included an extract (slightly edited) from the syslog showing a typical lead up to a reboot and would welcome suggestions as to why this might be happening...

Code: Select all

Nov  5 11:55:28 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:28 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:28 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:28 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:28 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:28 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:28 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:29 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:29 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:29 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:29 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:29 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:29 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:29 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:29 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:29 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:30 kern crit kernel: eth4 (Int switch port: 3) (Logical Port: 3) Link DOWN.
Nov  5 11:55:30 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:30 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:30 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:30 daemon info radvd[9135]: attempting to reread config file
Nov  5 11:55:30 daemon info radvd[9135]: resuming normal operation
Nov  5 11:55:30 daemon warn radvd[9135]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  5 11:55:31 daemon warn radvd[9135]: poll error: Interrupted system call
Nov  5 11:55:31 daemon warn radvd[9135]: Exiting, sigterm received.
Nov  5 11:55:31 daemon err dhcp6c[8982]: client6_send: transmit failed: Network is unreachable
Nov  5 11:55:32 kern warn kernel: ETH Init: Ch:1 - 200 tx BDs at 0xb0820650
Nov  5 11:55:32 kern warn kernel: ETH Init: Ch:1 - 600 rx BDs at 0xb0a21910
Nov  5 11:55:32 kern warn kernel: [FAP1] enetRxChannel 1
Nov  5 11:55:32 kern crit kernel: eth4 (Int switch port: 3) (Logical Port: 3) Link UP 100 mbps full duplex
Nov  5 11:55:35 daemon info email[17496]: eMail: SMTP_SERVER:smtp.fastmail.com SMTP_USER:xxxxxxxx@fastmail.net SMTP_PASS:xxxxx SENDER_MAIL:xxxxxxxxt@fastmail.net PORT:587 USE_TLS:true
Nov  5 11:55:35 daemon info email[17496]: eMail: Subject:WAN IP Change (new IP:192.168.2.0)
Nov  5 11:55:37 kern warn kernel: eth4.1 MAC address set to 60:03:47:4B:6C:25
Nov  5 11:55:37 kern warn kernel: netdev path : eth4.1 -> eth4
Nov  5 11:55:37 kern warn kernel: BCMVLAN : eth4 mode was set to RG
Nov  5 11:55:37 daemon notice syslog: pppd:cms logging initialized.
For info also, the EWAN port is fed by a DrayTek Vigor 130 modem, hence the subnet at 192.168.2.x, the router is 192.168.1.1 and clearly it's IPv6 enabled, which I think might be where the problem is... some IPv6 addressing conflict ? The entry for eth4 at 11:55:30 is perhaps slightly odd (and probably a 'red herring' ?) because eth4 is not in use on this router, only eth1, 2 & 3 are used. Any ideas as to what might be going on here would be appreciated thanks.
I see the following message Subject:WAN IP Change (new IP:192.168.2.0), is the Draytek set to Bridge mode, (I am assuming it is) which means the Draytek has a issue, and is assigning a private IP to the Billion instead of a proper public WAN IP.

I assume when you mean the device is rebooting, the system up time (found on the status page) resets to 0D 0H M 00S ?? Or is it the 'WAN>>> Connection Time that is resetting

Is the Billion setup in ETH >> PPPoE mode? ( I assume its IPOE, and you are with either talktalk or Sky)

Finally confirm the software/firmware version

Pete B
Posts: 24
Joined: Tue Sep 15, 2015 3:15 pm

Re: 8900AX-1600R2 - intermittent rebooting

Post by Pete B » Tue Nov 05, 2019 2:32 pm

Hi & thanks for a really quick reply
I see the following message Subject:WAN IP Change (new IP:192.168.2.0), is the Draytek set to Bridge mode, (I am assuming it is) which means the Draytek has a issue, and is assigning a private IP to the Billion instead of a proper public WAN IP.
No, the DrayTek isn't in bridge mode, it's set as a 'straightthrough' (forgive my terminology) VDSL2 modem. Its DHCP server is turned off.
I assume when you mean the device is rebooting, the system up time (found on the status page) resets to 0D 0H M 00S ?? Or is it the 'WAN>>> Connection Time that is resetting
:oops: I needed to be clearer. System does not reset. It's the WAN connection time which resets.
Is the Billion setup in ETH >> PPPoE mode? ( I assume its IPOE, and you are with either talktalk or Sky)
The Billion is in ETH >> PPPoE mode, my ISP is IDNet. I have an IPoE link setup in the Billion which allows me to access / control the DrayTek on the 192.168.2.x subnet.

Current Billion software in use: 2.50a.d24

The DrayTek has been in use for a few years already with its current VDSL2 setup but feeding a 7800DXL, there were no issues of this nature with that router but it was never IPv6 enabled. The 7800DXL does also of course have the configurable EWAN port which was was used then, as opposed to the dedicated EWAN port I'm now using on the 8900AX-1600. Differences so far, are change of EWAN port from configurable to dedicated and IPv6 enabled.

billion_fan
Posts: 5205
Joined: Tue Jul 19, 2011 4:30 pm

Re: 8900AX-1600R2 - intermittent rebooting

Post by billion_fan » Tue Nov 05, 2019 2:49 pm

Pete B wrote:
Tue Nov 05, 2019 2:32 pm
Hi & thanks for a really quick reply
I see the following message Subject:WAN IP Change (new IP:192.168.2.0), is the Draytek set to Bridge mode, (I am assuming it is) which means the Draytek has a issue, and is assigning a private IP to the Billion instead of a proper public WAN IP.
No, the DrayTek isn't in bridge mode, it's set as a 'straightthrough' (forgive my terminology) VDSL2 modem. Its DHCP server is turned off.
I assume when you mean the device is rebooting, the system up time (found on the status page) resets to 0D 0H M 00S ?? Or is it the 'WAN>>> Connection Time that is resetting
:oops: I needed to be clearer. System does not reset. It's the WAN connection time which resets.
Is the Billion setup in ETH >> PPPoE mode? ( I assume its IPOE, and you are with either talktalk or Sky)
The Billion is in ETH >> PPPoE mode, my ISP is IDNet. I have an IPoE link setup in the Billion which allows me to access / control the DrayTek on the 192.168.2.x subnet.

Current Billion software in use: 2.50a.d24

The DrayTek has been in use for a few years already with its current VDSL2 setup but feeding a 7800DXL, there were no issues of this nature with that router but it was never IPv6 enabled. The 7800DXL does also of course have the configurable EWAN port which was was used then, as opposed to the dedicated EWAN port I'm now using on the 8900AX-1600. Differences so far, are change of EWAN port from configurable to dedicated and IPv6 enabled.
Is your IPv6 setup, like the attached screen shot??
You do not have the required permissions to view the files attached to this post.

Pete B
Posts: 24
Joined: Tue Sep 15, 2015 3:15 pm

Re: 8900AX-1600R2 - intermittent rebooting

Post by Pete B » Tue Nov 05, 2019 3:10 pm

Ah ha... no the IPv6 autoconfig isn't setup like your example :idea: The 'ULA Prefix Advertisement' is not enabled, consequently there is no prefix :roll: I suspect there's a very good chance you've nailed it here ! I will supply the prefix and reboot. Give it a few days to test the change and check if all is well.

I will be posting back in due course, to let you know what happens in any case, because at the very least it will be to offer a significant vote of thanks for the endlessly and superbly helpful work you put into this forum. Cheers :!:

billion_fan
Posts: 5205
Joined: Tue Jul 19, 2011 4:30 pm

Re: 8900AX-1600R2 - intermittent rebooting

Post by billion_fan » Tue Nov 05, 2019 3:15 pm

Pete B wrote:
Tue Nov 05, 2019 3:10 pm
Ah ha... no the IPv6 autoconfig isn't setup like your example :idea: The 'ULA Prefix Advertisement' is not enabled, consequently there is no prefix :roll: I suspect there's a very good chance you've nailed it here ! I will supply the prefix and reboot. Give it a few days to test the change and check if all is well.

I will be posting back in due course, to let you know what happens in any case, because at the very least it will be to offer a significant vote of thanks for the endlessly and superbly helpful work you put into this forum. Cheers :!:
I have a feeling it is related to the 'ULA Prefix Advertisement' (but not 100% sure, just had to double check some other cases) I also have a newer firmware for you, but let this test run its course and then take it from there

Also if its the WAN dropping (which is what seems to be the issue), you might need to check the Draytek to see if it is dropping the DSL connection, hence dropping the PPPoE connection to the Billion.

Pete B
Posts: 24
Joined: Tue Sep 15, 2015 3:15 pm

Re: 8900AX-1600R2 - intermittent rebooting

Post by Pete B » Tue Nov 05, 2019 3:38 pm

Yes, thanks and BTW, In this case I have statically configured the 'ULA Prefix Advertisement' with the prefix from my ISP. Given a prefix, I have hopefully correctly assumed this is the right way to go. All currently appears to be working well, IPv6 testing has been successful.
Also if its the WAN dropping, you might need to check the Draytek to see if it is dropping the DSL connection
I will keep an eye on this but to date, I have never seen the DrayTek drop the VDSL connection with this situation.
Last edited by Pete B on Tue Nov 05, 2019 3:42 pm, edited 1 time in total.

Pete B
Posts: 24
Joined: Tue Sep 15, 2015 3:15 pm

Re: 8900AX-1600R2 - intermittent WAN connection failure

Post by Pete B » Thu Nov 07, 2019 4:31 pm

Hi, unfortunately I'm still in trouble with this WAN connection dropping issue. Since last posting I have tried various configurations...

1. Used both statically & dynamically configured 'ULA Prefix Advertisement' prefixes.

2. Run with and without MLD snooping (default was on with this router)

3. Router & VDSL modem (DrayTek Vigor 130) rebooted. The DrayTek is quoted as IPv6 compatible in its specification and is running their latest firmware.

I've had multiple WAN dis/reconnects. It can and does often run for several hours without issue, then I'll see 2 or 3 WAN connections failures within the space of 2 to 3 minutes (if there are 3 consecutive failures, I will typically see the first 2 in rapid succession followed by a 3rd around 20 minutes later), there's almost a pattern to this behaviour. Worst case seen, router and network totally unreachable (resolved only by router's power switch :roll: )... best case, it all still works after the upheaval. So. usable but really unreliable. FWIW the only conclusion I reached is that it's IPv6 related but I think we knew that ;) Would seriously appreciate more advice / ideas on how to proceed and get out of this situation.

I have attached another section of syslog which shows the build up to a typical WAN disconnect (slightly edited for IPs). Hope it may help...

Code: Select all

Nov  7 12:50:04 daemon crit syslog: PPP session established.
Nov  7 12:50:04 daemon info radvd[11665]: attempting to reread config file
Nov  7 12:50:04 kern warn kernel: netdev path : 
Nov  7 12:50:04 kern info kernel: ppp2.1 -> eth4.1 -> 
Nov  7 12:50:04 kern info kernel: eth4
Nov  7 12:50:04 daemon notice syslog: pppd:Using interface ppp2.1
Nov  7 12:50:04 daemon notice syslog: pppd:Connect: ppp2.1 <--> eth4.1
Nov  7 12:50:04 daemon notice syslog: pppd:Couldn't increase MTU to 1500.
Nov  7 12:50:04 daemon err syslog: pppd:Couldn't increase MRU to 1500
Nov  7 12:50:04 daemon info radvd[11665]: resuming normal operation
Nov  7 12:50:04 daemon warn radvd[11665]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:04 daemon err syslog: pppd:Couldn't increase MRU to 1500
Nov  7 12:50:04 daemon crit syslog: PPP LCP UP.
Nov  7 12:50:05 daemon notice syslog: pppd:Couldn't increase MTU to 1500.
Nov  7 12:50:05 daemon err syslog: pppd:Couldn't increase MRU to 1500
Nov  7 12:50:05 daemon err syslog: pppd:Couldn't increase MRU to 1500
Nov  7 12:50:05 daemon crit syslog: PPP LCP UP.
Nov  7 12:50:05 daemon info radvd[11665]: attempting to reread config file
Nov  7 12:50:05 daemon notice syslog: pppd:local  LL address fe80::742d:b416:96e9:c98f
Nov  7 12:50:05 daemon notice syslog: pppd:remote LL address fe80::02a3:8eff:feca:ae80
Nov  7 12:50:05 daemon info radvd[11665]: resuming normal operation
Nov  7 12:50:05 daemon warn radvd[11665]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:05 daemon notice syslog: pppd:local  IP address 91.135.xxx.xxx
Nov  7 12:50:05 daemon notice syslog: pppd:remote IP address 212.69.xxx.xxx
Nov  7 12:50:05 daemon notice syslog: pppd:primary   DNS address 212.69.40.23
Nov  7 12:50:05 daemon notice syslog: pppd:secondary DNS address 212.69.36.23
Nov  7 12:50:05 daemon crit syslog: Received valid IP address from server.  Connection UP.
Nov  7 12:50:05 daemon info syslog: Hop limit                : 64
Nov  7 12:50:05 daemon info syslog: Stateful address conf.    : No
Nov  7 12:50:05 daemon info syslog: Stateful other conf.      : No
Nov  7 12:50:05 daemon info syslog: Router preference        : medium
Nov  7 12:50:05 daemon info syslog: Router lifetime           : 1800 seconds
Nov  7 12:50:05 daemon info syslog: Reachable time           : 0 milliseconds
Nov  7 12:50:05 daemon info syslog: Retransmit time          : 0 milliseconds
Nov  7 12:50:05 daemon info syslog: Prefix                   : 2a02:390:xxxx:5e05::/64
Nov  7 12:50:05 daemon info syslog: Valid time               : 2592000 seconds
Nov  7 12:50:05 daemon info syslog: Pref. time               : 604800 seconds
Nov  7 12:50:08 daemon info email[12327]: eMail: SMTP_SERVER:smtp.fastmail.com SMTP_USER:xxxxxxxx@fastmail.net SMTP_PASS:xxxxx SENDER_MAIL:xxxxxxxx@fastmail.net PORT:587 USE_TLS:true
Nov  7 12:50:08 daemon info email[12327]: eMail: Subject:WAN IP Change (new IP:91.135.10.56)
Nov  7 12:50:13 daemon info syslog: dhcp6c restart..
Nov  7 12:50:17 daemon warn radvd[11665]: poll error: Interrupted system call
Nov  7 12:50:17 daemon warn radvd[11665]: Exiting, sigterm received.
Nov  7 12:50:17 daemon info radvd[12449]: version 1.8 started
Nov  7 12:50:17 daemon warn radvd[12449]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:18 daemon warn radvd[12449]: poll error: Interrupted system call
Nov  7 12:50:18 daemon warn radvd[12449]: Exiting, sigterm received.
Nov  7 12:50:18 daemon info radvd[12494]: version 1.8 started
Nov  7 12:50:18 daemon warn radvd[12494]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:18 daemon warn radvd[12494]: poll error: Interrupted system call
Nov  7 12:50:18 daemon warn radvd[12494]: Exiting, sigterm received.
Nov  7 12:50:18 daemon info radvd[12503]: version 1.8 started
Nov  7 12:50:18 daemon warn radvd[12503]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:18 daemon warn radvd[12503]: poll error: Interrupted system call
Nov  7 12:50:18 daemon warn radvd[12503]: Exiting, sigterm received.
Nov  7 12:50:19 daemon info radvd[12533]: version 1.8 started
Nov  7 12:50:19 daemon warn radvd[12533]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:33 daemon info email[12327]: eMail: Send Finish
Nov  7 12:50:34 daemon info email[11953]: eMail: Send Finish
Nov  7 12:50:35 daemon warn radvd[12533]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:51 daemon warn radvd[12533]: received RA from fe80::6203:47ff:fe4b:xxxx

billion_fan
Posts: 5205
Joined: Tue Jul 19, 2011 4:30 pm

Re: 8900AX-1600R2 - intermittent WAN connection failure

Post by billion_fan » Thu Nov 07, 2019 5:08 pm

Pete B wrote:
Thu Nov 07, 2019 4:31 pm
Hi, unfortunately I'm still in trouble with this WAN connection dropping issue. Since last posting I have tried various configurations...

1. Used both statically & dynamically configured 'ULA Prefix Advertisement' prefixes.

2. Run with and without MLD snooping (default was on with this router)

3. Router & VDSL modem (DrayTek Vigor 130) rebooted. The DrayTek is quoted as IPv6 compatible in its specification and is running their latest firmware.

I've had multiple WAN dis/reconnects. It can and does often run for several hours without issue, then I'll see 2 or 3 WAN connections failures within the space of 2 to 3 minutes (if there are 3 consecutive failures, I will typically see the first 2 in rapid succession followed by a 3rd around 20 minutes later), there's almost a pattern to this behaviour. Worst case seen, router and network totally unreachable (resolved only by router's power switch :roll: )... best case, it all still works after the upheaval. So. usable but really unreliable. FWIW the only conclusion I reached is that it's IPv6 related but I think we knew that ;) Would seriously appreciate more advice / ideas on how to proceed and get out of this situation.

I have attached another section of syslog which shows the build up to a typical WAN disconnect (slightly edited for IPs). Hope it may help...

Code: Select all

Nov  7 12:50:04 daemon crit syslog: PPP session established.
Nov  7 12:50:04 daemon info radvd[11665]: attempting to reread config file
Nov  7 12:50:04 kern warn kernel: netdev path : 
Nov  7 12:50:04 kern info kernel: ppp2.1 -> eth4.1 -> 
Nov  7 12:50:04 kern info kernel: eth4
Nov  7 12:50:04 daemon notice syslog: pppd:Using interface ppp2.1
Nov  7 12:50:04 daemon notice syslog: pppd:Connect: ppp2.1 <--> eth4.1
Nov  7 12:50:04 daemon notice syslog: pppd:Couldn't increase MTU to 1500.
Nov  7 12:50:04 daemon err syslog: pppd:Couldn't increase MRU to 1500
Nov  7 12:50:04 daemon info radvd[11665]: resuming normal operation
Nov  7 12:50:04 daemon warn radvd[11665]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:04 daemon err syslog: pppd:Couldn't increase MRU to 1500
Nov  7 12:50:04 daemon crit syslog: PPP LCP UP.
Nov  7 12:50:05 daemon notice syslog: pppd:Couldn't increase MTU to 1500.
Nov  7 12:50:05 daemon err syslog: pppd:Couldn't increase MRU to 1500
Nov  7 12:50:05 daemon err syslog: pppd:Couldn't increase MRU to 1500
Nov  7 12:50:05 daemon crit syslog: PPP LCP UP.
Nov  7 12:50:05 daemon info radvd[11665]: attempting to reread config file
Nov  7 12:50:05 daemon notice syslog: pppd:local  LL address fe80::742d:b416:96e9:c98f
Nov  7 12:50:05 daemon notice syslog: pppd:remote LL address fe80::02a3:8eff:feca:ae80
Nov  7 12:50:05 daemon info radvd[11665]: resuming normal operation
Nov  7 12:50:05 daemon warn radvd[11665]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:05 daemon notice syslog: pppd:local  IP address 91.135.xxx.xxx
Nov  7 12:50:05 daemon notice syslog: pppd:remote IP address 212.69.xxx.xxx
Nov  7 12:50:05 daemon notice syslog: pppd:primary   DNS address 212.69.40.23
Nov  7 12:50:05 daemon notice syslog: pppd:secondary DNS address 212.69.36.23
Nov  7 12:50:05 daemon crit syslog: Received valid IP address from server.  Connection UP.
Nov  7 12:50:05 daemon info syslog: Hop limit                : 64
Nov  7 12:50:05 daemon info syslog: Stateful address conf.    : No
Nov  7 12:50:05 daemon info syslog: Stateful other conf.      : No
Nov  7 12:50:05 daemon info syslog: Router preference        : medium
Nov  7 12:50:05 daemon info syslog: Router lifetime           : 1800 seconds
Nov  7 12:50:05 daemon info syslog: Reachable time           : 0 milliseconds
Nov  7 12:50:05 daemon info syslog: Retransmit time          : 0 milliseconds
Nov  7 12:50:05 daemon info syslog: Prefix                   : 2a02:390:xxxx:5e05::/64
Nov  7 12:50:05 daemon info syslog: Valid time               : 2592000 seconds
Nov  7 12:50:05 daemon info syslog: Pref. time               : 604800 seconds
Nov  7 12:50:08 daemon info email[12327]: eMail: SMTP_SERVER:smtp.fastmail.com SMTP_USER:xxxxxxxx@fastmail.net SMTP_PASS:xxxxx SENDER_MAIL:xxxxxxxx@fastmail.net PORT:587 USE_TLS:true
Nov  7 12:50:08 daemon info email[12327]: eMail: Subject:WAN IP Change (new IP:91.135.10.56)
Nov  7 12:50:13 daemon info syslog: dhcp6c restart..
Nov  7 12:50:17 daemon warn radvd[11665]: poll error: Interrupted system call
Nov  7 12:50:17 daemon warn radvd[11665]: Exiting, sigterm received.
Nov  7 12:50:17 daemon info radvd[12449]: version 1.8 started
Nov  7 12:50:17 daemon warn radvd[12449]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:18 daemon warn radvd[12449]: poll error: Interrupted system call
Nov  7 12:50:18 daemon warn radvd[12449]: Exiting, sigterm received.
Nov  7 12:50:18 daemon info radvd[12494]: version 1.8 started
Nov  7 12:50:18 daemon warn radvd[12494]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:18 daemon warn radvd[12494]: poll error: Interrupted system call
Nov  7 12:50:18 daemon warn radvd[12494]: Exiting, sigterm received.
Nov  7 12:50:18 daemon info radvd[12503]: version 1.8 started
Nov  7 12:50:18 daemon warn radvd[12503]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:18 daemon warn radvd[12503]: poll error: Interrupted system call
Nov  7 12:50:18 daemon warn radvd[12503]: Exiting, sigterm received.
Nov  7 12:50:19 daemon info radvd[12533]: version 1.8 started
Nov  7 12:50:19 daemon warn radvd[12533]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:33 daemon info email[12327]: eMail: Send Finish
Nov  7 12:50:34 daemon info email[11953]: eMail: Send Finish
Nov  7 12:50:35 daemon warn radvd[12533]: received RA from fe80::6203:47ff:fe4b:xxxx
Nov  7 12:50:51 daemon warn radvd[12533]: received RA from fe80::6203:47ff:fe4b:xxxx
Can't really see anything other then the PPPoE connection between modem and router has dropped.

As the Billion is in router mode and using PPPoE it shouldn't drop the connection unless there is a issue on the line or with the Draytek.

Are you able to login to the Draytek and check the logs or DSL uptime, this should help to pin point the issue.

Another test would be to use the 8900 in modem/router mode (using the DSL port) and see if the same issue occurs.

I don't think its IPv6 related , if the IPv6 connection drops the IPv4 connection should carry on working, but that is not the case for your issue,

Also attached is the latest firmware 2.52.d2, with this firmware once upgraded a factory reset will be needed, and manual re-configuration will also be needed.

Do not restore settings from previous firmware builds (as this newer firmware is on a newer code case)
You do not have the required permissions to view the files attached to this post.

Pete B
Posts: 24
Joined: Tue Sep 15, 2015 3:15 pm

Re: 8900AX-1600R2 - intermittent WAN connection failure

Post by Pete B » Thu Nov 07, 2019 6:41 pm

Are you able to login to the Draytek and check the logs or DSL uptime, this should help to pin point the issue.
Yes, I accessed the DrayTek's logs. I found little information which I could understand but it did appear that what I could see corresponded timewise to the first WAN disconnect time seen on the Billion. However, due to clumsiness on my part :roll: I then forced a reboot on the DrayTek which wiped the log, so I can't truly verify this right now. I need to see further WAN disconnects, then try and correlate the DrayTek/Billion log timings. It's unfair to ask you to look at DrayTek log extracts but I can of course post them anyhow ;) , I guess I could still end up talking to DrayTek support after all that :lol: One thing I do know definitely is that there has been no actual VDSL connection downtime, it has been solid, in fact running for over a 1000 hours until I rebooted it the first time.

I will post back with any WAN disconnect, timing correlation info when I get it.
Another test would be to use the 8900 in modem/router mode (using the DSL port) and see if the same issue occurs.
I'll just hang fire on this one until I get better data from above. As for being an IPv6 issue, I guess I just (incorrectly) assumed that because I only saw this issue after enabling IPv6 :) I will also update the firmware in due course, so thanks for that. I have a lot of manual config, such a loads of MAC addresses for WiFi MAC restriction, static IPs and virtual servers. Not a task I take on lightly, so I'll save a day for it :lol:

Meanwhile, back in due course and thanks again.

Post Reply