8800axl buggy firmware or faulty hardware?

Discussions for BiPAC 8800 series: 8800NL, 8800NLR2, 8800AXL, 8800AXLR2
frogfoot
Posts: 67
Joined: Sat Jun 02, 2012 8:21 pm

8800axl buggy firmware or faulty hardware?

Post by frogfoot »

Hi,
I've been using my new Billion 8800axl for six days now and have not yet had a 24 hour period where the router did not need to be restarted to fix some error.
Having come from three trouble free years of owning an 7800n, where the router would only get a reboot when I had to change some firmware setting which forced a restart, it has been a somewhat disappointing start.
The problems so far are as follows.

SNMP buggy, regularly causing the SNMP service to crash. - (Seems slightly better if you stick to SNMPv1)
Setting up a Guest WiFi network isolated from the lan breaks DHCP causing all kinds of merry hell to break loose. - (I have since removed the Guest network!)
This morning the entire router locked up when it was idle, (no one changing settings, no telnet connection, just CACTI logging SNMP, and Syslog output to server) The Web GUI was unavailable, as was Telnet, No internet access from any devices (wired or wireless), LAN ports LEDs were flickering as was the DSL and Internet LED's, However 2.4GHz Wifi light was off and 5Ghz Light was On steady.
Could this be a WiFI related crash?

All in all I think this device needs some serious love on the firmware department, or I've got a flaky one.
Tom
billion_fan
Posts: 5398
Joined: Tue Jul 19, 2011 4:30 pm

Re: 8800axl buggy firmware or faulty hardware?

Post by billion_fan »

frogfoot wrote:Hi,
I've been using my new Billion 8800axl for six days now and have not yet had a 24 hour period where the router did not need to be restarted to fix some error.
Having come from three trouble free years of owning an 7800n, where the router would only get a reboot when I had to change some firmware setting which forced a restart, it has been a somewhat disappointing start.
The problems so far are as follows.

SNMP buggy, regularly causing the SNMP service to crash. - (Seems slightly better if you stick to SNMPv1)
Setting up a Guest WiFi network isolated from the lan breaks DHCP causing all kinds of merry hell to break loose. - (I have since removed the Guest network!)
This morning the entire router locked up when it was idle, (no one changing settings, no telnet connection, just CACTI logging SNMP, and Syslog output to server) The Web GUI was unavailable, as was Telnet, No internet access from any devices (wired or wireless), LAN ports LEDs were flickering as was the DSL and Internet LED's, However 2.4GHz Wifi light was off and 5Ghz Light was On steady.
Could this be a WiFI related crash?

All in all I think this device needs some serious love on the firmware department, or I've got a flaky one.
Tom
Do you still have a copy of the system log before the crash?? Also let me know the firmware version you are running.
a5ian300zx
Posts: 30
Joined: Mon Apr 30, 2012 9:23 pm

Re: 8800axl buggy firmware or faulty hardware?

Post by a5ian300zx »

I am on the same bought having come from a 7800N with no issues whats so ever and now the 8800AXL which i still can see devices on the wireless network 2.4 or 5Ghz and have tried all the firmwares avaiable now.

i have given up was about to buy another billion until i read the new Draytek is coming out at the end of the month which will support VDSL and Wireless AC Dual Band.

I have had a Draytek in the past and it was solid too, more expensive but I can't be bothered to mess about with it I just want it to work.

Thanks
frogfoot
Posts: 67
Joined: Sat Jun 02, 2012 8:21 pm

Re: 8800axl buggy firmware or faulty hardware?

Post by frogfoot »

There was nothing remarkable in the syslog (I only output Warnings or above) apart from wl0: received packet with own address as source address. which I seem to get regularly on the 8800.
Note how the Diskstation lost External IP but STUDY-PC still managed to access a network drive...

Maybe you can tell me why DHCP ACK and OFFER events are categorized as errors rather than informational?

STUDY-PC was booted up at 8:00 ish (connected to LAN 1)

Code: Select all

2015-04-22,09:23:09,info,DiskStation,user,Connection,Tom:	CIFS client [Tom] from [STUDY-PC(IP:192.168.1.10)] accessed the shared folder [video].
2015-04-22,09:12:15,err,DiskStation,user,System,SYSTEM:	System failed to get External IP.
2015-04-22,08:54:49,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,08:44:48,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,08:34:47,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,08:30:46,warning,192.168.1.1,daemon,kernel,wl0: received packet with  own address as source address
2015-04-22,08:24:46,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,08:16:30,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.105
2015-04-22,08:16:30,err,192.168.1.1,daemon,syslog,dhcpd:sending OFFER of 192.168.1.105
2015-04-22,08:14:45,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,08:06:36,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.115
2015-04-22,08:06:36,err,192.168.1.1,daemon,syslog,dhcpd:sending OFFER of 192.168.1.115
2015-04-22,08:06:25,warning,192.168.1.1,daemon,kernel,wl0: received packet with  own address as source address
2015-04-22,08:04:44,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,08:04:22,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.115
2015-04-22,08:04:22,err,192.168.1.1,daemon,syslog,dhcpd:sending OFFER of 192.168.1.115
2015-04-22,08:02:56,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.10
2015-04-22,08:02:53,info,192.168.1.1,daemon,kernel,br0: bridge group port 1(eth0) entering forwarding state
2015-04-22,08:02:53,crit,192.168.1.1,daemon,kernel,eth0 (switch port: 1) Link UP 1000 mbps full duplex
2015-04-22,08:02:50,info,192.168.1.1,daemon,kernel,br0: bridge group port 1(eth0) entering disabled state
2015-04-22,08:02:50,crit,192.168.1.1,daemon,kernel,eth0 (switch port: 1)  Link DOWN.
2015-04-22,08:02:39,info,192.168.1.1,daemon,kernel,br0: bridge group port 1(eth0) entering forwarding state
2015-04-22,08:02:39,crit,192.168.1.1,daemon,kernel,eth0 (switch port: 1) Link UP 10 mbps full duplex
2015-04-22,08:02:36,info,192.168.1.1,daemon,kernel,br0: bridge group port 1(eth0) entering disabled state
2015-04-22,08:02:36,crit,192.168.1.1,daemon,kernel,eth0 (switch port: 1)  Link DOWN.
2015-04-22,07:57:10,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.118
2015-04-22,07:54:44,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,07:44:42,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,07:42:26,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.110
2015-04-22,07:34:41,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,07:28:09,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.119
2015-04-22,07:24:40,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
I'm running the as shipped
2.32d.dh13 firmware
DSL driver A2pv6F039g1.d24m
Wireless Driver 6.30.102.7.cpe4.12L08.4
billion_fan
Posts: 5398
Joined: Tue Jul 19, 2011 4:30 pm

Re: 8800axl buggy firmware or faulty hardware?

Post by billion_fan »

frogfoot wrote:There was nothing remarkable in the syslog (I only output Warnings or above) apart from wl0: received packet with own address as source address. which I seem to get regularly on the 8800.
Note how the Diskstation lost External IP but STUDY-PC still managed to access a network drive...

Maybe you can tell me why DHCP ACK and OFFER events are categorized as errors rather than informational?

STUDY-PC was booted up at 8:00 ish (connected to LAN 1)

Code: Select all

2015-04-22,09:23:09,info,DiskStation,user,Connection,Tom:	CIFS client [Tom] from [STUDY-PC(IP:192.168.1.10)] accessed the shared folder [video].
2015-04-22,09:12:15,err,DiskStation,user,System,SYSTEM:	System failed to get External IP.
2015-04-22,08:54:49,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,08:44:48,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,08:34:47,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,08:30:46,warning,192.168.1.1,daemon,kernel,wl0: received packet with  own address as source address
2015-04-22,08:24:46,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,08:16:30,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.105
2015-04-22,08:16:30,err,192.168.1.1,daemon,syslog,dhcpd:sending OFFER of 192.168.1.105
2015-04-22,08:14:45,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,08:06:36,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.115
2015-04-22,08:06:36,err,192.168.1.1,daemon,syslog,dhcpd:sending OFFER of 192.168.1.115
2015-04-22,08:06:25,warning,192.168.1.1,daemon,kernel,wl0: received packet with  own address as source address
2015-04-22,08:04:44,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,08:04:22,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.115
2015-04-22,08:04:22,err,192.168.1.1,daemon,syslog,dhcpd:sending OFFER of 192.168.1.115
2015-04-22,08:02:56,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.10
2015-04-22,08:02:53,info,192.168.1.1,daemon,kernel,br0: bridge group port 1(eth0) entering forwarding state
2015-04-22,08:02:53,crit,192.168.1.1,daemon,kernel,eth0 (switch port: 1) Link UP 1000 mbps full duplex
2015-04-22,08:02:50,info,192.168.1.1,daemon,kernel,br0: bridge group port 1(eth0) entering disabled state
2015-04-22,08:02:50,crit,192.168.1.1,daemon,kernel,eth0 (switch port: 1)  Link DOWN.
2015-04-22,08:02:39,info,192.168.1.1,daemon,kernel,br0: bridge group port 1(eth0) entering forwarding state
2015-04-22,08:02:39,crit,192.168.1.1,daemon,kernel,eth0 (switch port: 1) Link UP 10 mbps full duplex
2015-04-22,08:02:36,info,192.168.1.1,daemon,kernel,br0: bridge group port 1(eth0) entering disabled state
2015-04-22,08:02:36,crit,192.168.1.1,daemon,kernel,eth0 (switch port: 1)  Link DOWN.
2015-04-22,07:57:10,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.118
2015-04-22,07:54:44,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,07:44:42,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,07:42:26,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.110
2015-04-22,07:34:41,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
2015-04-22,07:28:09,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.119
2015-04-22,07:24:40,err,192.168.1.1,daemon,syslog,dhcpd:sending ACK to 192.168.1.2
I'm running the as shipped
2.32d.dh13 firmware
DSL driver A2pv6F039g1.d24m
Wireless Driver 6.30.102.7.cpe4.12L08.4
Can you try loading the dh65 firmware and see if the same issue occurs (lockup with the 2.4ghz light off)

I don't know why the DHCP ACK and offers show as errors, I think this is down to Broadcom coding

Also once loaded, change the syslog logging level to debugging, if the issue occurs again hopefully we can capture something

regarding the DHCP guest wifi network issue, that has been reported and our engineers are looking into it, SNMP issue should be resolved within the next firmware release
frogfoot
Posts: 67
Joined: Sat Jun 02, 2012 8:21 pm

Re: 8800axl buggy firmware or faulty hardware?

Post by frogfoot »

Ok, dh65 firmware flashed, completely set up from scratch, all up an working so far.

One immediate improvement I have seen is the DHCP ACK and OFFER events are now Informational rather than ERROR
billion_fan
Posts: 5398
Joined: Tue Jul 19, 2011 4:30 pm

Re: 8800axl buggy firmware or faulty hardware?

Post by billion_fan »

frogfoot wrote:Ok, dh65 firmware flashed, completely set up from scratch, all up an working so far.

One immediate improvement I have seen is the DHCP ACK and OFFER events are now Informational rather than ERROR
Thanks for the update frogfoot, keep me posted on the lock up issue (I want to get to the bottom of this, I'm hoping we capture what's needed and don't need a console capture)
frogfoot
Posts: 67
Joined: Sat Jun 02, 2012 8:21 pm

Re: 8800axl buggy firmware or faulty hardware?

Post by frogfoot »

I've set up the Router to forward all messages DEBUG and above to my NAS which is running a Syslog daemon. So even if the router locks up we may have something to work with.

On another note I am still getting wl0: received packet with own address as source address warnings, any idea what may be causing those?
billion_fan
Posts: 5398
Joined: Tue Jul 19, 2011 4:30 pm

Re: 8800axl buggy firmware or faulty hardware?

Post by billion_fan »

frogfoot wrote:I've set up the Router to forward all messages DEBUG and above to my NAS which is running a Syslog daemon. So even if the router locks up we may have something to work with.

On another note I am still getting wl0: received packet with own address as source address warnings, any idea what may be causing those?
Our engineers have looked at this before without much success (wl0: received packet with own address as source address), I have this logged within my 7800DXL at home, at it seems to be my AP repeater causing these logs (it does cause any issues, no lockup etc my router has been up for 68 days now) as soon as I turn off my wireless repeater the logs disappear
frogfoot
Posts: 67
Joined: Sat Jun 02, 2012 8:21 pm

Re: 8800axl buggy firmware or faulty hardware?

Post by frogfoot »

I have several Devolo Powerline adaptors, one of which is a 2.4GHz Wireless access point (on a different channel with the same SSID and password)
Post Reply