firmware 2.52

[Pete-B]

Router has now been up for 2D 2H 9M 10S.

The firmware being tested includes:
DSL PHY and Driver Version A2pvI042j1.d26q_rc1a
Wireless Driver Version 7.14.164.20.cpe4.16L05.0-kdb

[picbits]

I'm having a similar issue - random reboots. Three today so far.

I've got remote logging enabled on a Linux server so have posted below the moment it all rebooted this afternoon.

I'm also getting a lot of IP6 messages even though I don't use IP6 on my network.

2018-09-22T15:45:46.629237+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T15:46:41.051929+01:00 radvd[932]: received RS from fe80::417:fd76:81be:7ec3 received RS from fe80::417:fd76:81be:7ec3
2018-09-22T15:46:41.052556+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T15:47:46.362530+01:00 radvd[932]: received RS from fe80::417:fd76:81be:7ec3 received RS from fe80::417:fd76:81be:7ec3
2018-09-22T15:47:46.376029+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T15:48:20.773281+01:00 radvd[932]: received RS from fe80::417:fd76:81be:7ec3 received RS from fe80::417:fd76:81be:7ec3
2018-09-22T15:48:20.774278+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T15:55:41.596131+01:00 radvd[932]: received RS from fe80::417:fd76:81be:7ec3 received RS from fe80::417:fd76:81be:7ec3
2018-09-22T15:55:41.600317+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T15:59:19.551170+01:00 kernel: icmpv6_send: no reply to icmp error icmpv6_send: no reply to icmp error
2018-09-22T16:02:33.607751+01:00 radvd[932]: received RS from fe80::417:fd76:81be:7ec3 received RS from fe80::417:fd76:81be:7ec3
2018-09-22T16:02:33.609999+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:13.841824+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:13.869851+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:13.870832+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:16.946115+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:16.958943+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:16.962502+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:17.266064+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:17.300897+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:17.303664+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:18.035931+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:18.049598+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:18.053086+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:18.274218+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:18.276355+01:00 kernel: device wl0 entered promiscuous mode device wl0 entered promiscuous mode
2018-09-22T16:04:18.293844+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:18.296942+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:18.321200+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:18.332645+01:00 kernel: br0: port 5(wl0) entered forwarding state br0: port 5(wl0) entered forwarding state
2018-09-22T16:04:18.334476+01:00 kernel: br0: port 5(wl0) entered forwarding state br0: port 5(wl0) entered forwarding state
2018-09-22T16:04:18.336821+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:18.339988+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:18.343497+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:18.358203+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:18.360704+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:18.362721+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:18.372721+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:18.374663+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:18.376206+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:18.386911+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:18.388207+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:18.671490+01:00 kernel: No device name wl0 found in Ethernet driver No device name wl0 found in Ethernet driver
2018-09-22T16:04:18.710983+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:18.719715+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:18.720394+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:18.918095+01:00 kernel: device wl0.1 entered promiscuous mode device wl0.1 entered promiscuous mode
2018-09-22T16:04:18.918754+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:18.925842+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:18.929349+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:18.958784+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:18.967615+01:00 kernel: br1: port 2(wl0.1) entered forwarding state br1: port 2(wl0.1) entered forwarding state
2018-09-22T16:04:18.968847+01:00 kernel: br1: port 2(wl0.1) entered forwarding state br1: port 2(wl0.1) entered forwarding state
2018-09-22T16:04:18.980071+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:18.982575+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:18.984494+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:19.004086+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:19.006168+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:19.008985+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:19.027119+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:19.029905+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:19.035009+01:00 radvd[932]: attempting to reread config file attempting to reread config file
2018-09-22T16:04:19.054783+01:00 radvd[932]: resuming normal operation resuming normal operation
2018-09-22T16:04:19.057788+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:19.204865+01:00 kernel: No device name wl0.1 found in Ethernet driver No device name wl0.1 found in Ethernet driver
2018-09-22T16:04:22.812893+01:00 radvd[932]: received RS from fe80::1a74:2eff:fee4:f8eb received RS from fe80::1a74:2eff:fee4:f8eb
2018-09-22T16:04:22.815100+01:00 radvd[932]: received RA from fe80::6203:47ff:fe3c:ae3c received RA from fe80::6203:47ff:fe3c:ae3c
2018-09-22T16:04:28.509280+01:00 kernel: Line 0: VDSL G.993 channel analysis Line 0: VDSL G.993 channel analysis
2018-09-22T16:04:30.374294+01:00 radvd[932]: received RS from fe80::d638:9cff:fe72:4df9 received RS from fe80::d638:9cff:fe72:4df9

[gerdesj]

Three out of my four BiPACs have gone into a reboot cycle again, right now. The one that hasn't is running the older firmware (2.50). So if you need stability, do as billion_fan suggests and run that firmware. As I have discovered by testing, you must factory reset when going backwards in firmware version, so document your settings first.

[Pete-B]

System Up-Time 4D 1H 37M 32S

[billion_fan]

System Up-Time 4D 1H 37M 32S

Attached is the test firmware, please feel free to test it, and let us know if you experience any reboots

[ZicoUK]

Thanks for posting. I've downloaded it but will wait until tomorrow to update.

[ZicoUK]

Well as if by magic, not more than 10 minutes after I posted, the router restarted. I quickly pulled the DSL cable and have now factory reset and flashed the test firmware. Fingers crossed for the next day.

[gerdesj]

System Up-Time 4D 1H 37M 32S

Attached is the test firmware, please feel free to test it, and let us know if you experience any reboots

OK, line in sand 8) I have four BiPAC 8800NL R2s, let's call them say billion1 to 4 and note firmware and uptimes:

Code: Select all

billion1 2.52.d3     0D 1H 32M
billion2 2.52.d3     0D 1H 37M
billion3 2.52.d10_t1 0D 0H 6M
billion4 2.50a.d13   1D 11H 24M

3 was only just updated to this firmware, 4 has stayed up since I reverted the firmware to an old one, 1 and 2 have had regular problems. I've removed the seconds

[billion_fan]

System Up-Time 4D 1H 37M 32S

Attached is the test firmware, please feel free to test it, and let us know if you experience any reboots

OK, line in sand 8) I have four BiPAC 8800NL R2s, let's call them say billion1 to 4 and note firmware and uptimes:

Code: Select all

billion1 2.52.d3     0D 1H 32M
billion2 2.52.d3     0D 1H 37M
billion3 2.52.d10_t1 0D 0H 6M
billion4 2.50a.d13   1D 11H 24M

3 was only just updated to this firmware, 4 has stayed up since I reverted the firmware to an old one, 1 and 2 have had regular problems. I've removed the seconds

I would upgrade 1 and 2 also to the newer firmware 2.52.d10_t1 as the results I have seen have shown 6 days uptime so far

[ZicoUK]

Not quite a full day for me yet. If it's good through to midnight then hopefully we're onto a winner.