Billion UK Forum

Update: I performed a factory reset and as you say, that seems to have resolved the issue. Surprising as previous firmware updates have installed perfectly without this. FYI; I'm running an iMac Retina late 2014 which has a Broadcom BCM43xx embedded wifi controller. Logs are coming up clean again.

Thanks again.

Not for me I'm afraid flashed the etec8900ax2400_2.52.d15 firmware my iPad and iPhone refused to connect so I flashed back to etec8900ax2400_2.52.d12 now works all OK again I will just ignore the statistics.

I spoke too soon.

I'm getting the following error in the logs 3-4 times per day:
Apr 10 06:54:40 kern warn kernel: ^[[0;33;41mFCACHEfc_transmit ERROR: ABORT UNKNOWN Tx L2TP h_proto 0x3a72^[[0m

Any clue what that might be?

Thanks!

mawheele wrote:I spoke too soon.

I'm getting the following error in the logs 3-4 times per day:
Apr 10 06:54:40 kern warn kernel: ^[[0;33;41mFCACHEfc_transmit ERROR: ABORT UNKNOWN Tx L2TP h_proto 0x3a72^[[0m

Any clue what that might be?

Thanks!

It seems with this firmware you will need to reset back to factory default settings, and manually reconfigure the device again from scratch. (note added to the official firmware link)

I haven't seen that log before, can you post a snippet of your logs, before this log occurred, also including this log.

Also are you running a L2TP connection on the router??

Hi there,

Yes. Definite factory reset required. So I did that, but since doing so I now get the following error. This is the entire log entry and it repeats itself 2-3 times per day. I've not changed anything from prior configurations.

I am a Zen internet customer; the only changes I make are to manually setup my account (username and pw), switch off UPNP, switch on IPV6 LAN and use Google DNS. Otherwise as per factory. Not really sure why L2TP is coming up or where to even check it.

Here it is again: Apr 14 05:22:56 kern warn kernel: ^[[0;33;41mFCACHEfc_transmit ERROR: ABORT UNKNOWN Tx L2TP h_proto 0x7b2c^[[0m

This is all there is. Sorry.

Definitely some kind of wireless issue introduced with Rev 15 of the firmware. Herewith the log and the last few lines following the reset:


Jan 1 00:01:21 daemon notice syslog: pppd:local LL address fe80::0000:0000:0000:0001
Jan 1 00:01:21 daemon notice syslog: pppd:remote LL address fe80::d2f0:dbff:fe7d:6000
Jan 1 00:01:31 daemon info syslog: initQmtWlancfg: failed to get lock acquire Lock again, ret=9809
Jan 1 00:01:34 daemon info syslog: initQmtWlancfg: failed to get lock acquire Lock again, ret=9809
Apr 16 09:14:49 daemon info syslog: Hop limit : 64
Apr 16 09:14:49 daemon info syslog: Stateful address conf. : No
Apr 16 09:14:49 daemon info syslog: Stateful other conf. : Yes
Apr 16 09:14:49 daemon info syslog: Router preference : medium
Apr 16 09:14:49 daemon info syslog: Router lifetime : 1200 seconds
Apr 16 09:14:49 daemon info syslog: Reachable time : 0 milliseconds
Apr 16 09:14:49 daemon info syslog: Retransmit time : 0 milliseconds
Apr 16 09:14:49 daemon info syslog: Source link-layer address :REDACTED
Apr 16 09:14:49 daemon info syslog: Prefix : REDACTED
Apr 16 09:14:49 daemon info syslog: Valid time : 18000 seconds
Apr 16 09:14:49 daemon info syslog: Pref. time : 1800 seconds
Apr 16 09:14:49 daemon info syslog: dhcp6c restart..
Apr 16 09:14:52 daemon info WLAN Schedule: WLAN Schedule Control on wl1 start
Apr 16 09:22:24 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 10:38:57 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 10:58:25 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 11:03:38 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 11:13:06 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 11:27:17 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 14:35:58 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 14:36:02 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 14:53:50 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 15:18:33 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 15:26:07 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 16:24:50 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 16:32:35 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 17:42:45 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 18:00:40 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 18:02:58 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 18:22:06 kern warn kernel: br0: received packet on wl0 with own address as source address
Apr 16 18:26:14 kern warn kernel: br0: received packet on wl0 with own address as source address

Ggggrrrrr - Now it won't let me downgrade the firmware. Not fun.

Managed to get D12 back on and I can report all issues have gone away. Strong recommendation to Billion_Fan to pull D15 from website until fixed.

Hi, I upgraded to d15, did a factory reset and the wireless is terrible, ipad, macbook refusing to connect, just garbage. tbh for £250 this router is a joke and I will be contacting amazon to return it.

the wireless is average and really cannot see how this router justifies the price tag it has.

Hi Zarf2007, I'd hold onto the router if I was you. Whilst d15 firmware clearly has some issues, I can assure you that having tried almost every top selling ADSL AC router over £140 on the market, this is the best available - at any price - for modem, router and wireless performance. Downgrade back to D12 and you'll get the best there is.
I've tried Zyxel Vigor 2860AC (not a great modem), Netgear D7000 (great modem, shocking router) Netgear D7800 (rubbish modem, rubbish router), TPLink 2600 (2 units that were both DOA) and I could list more...

Hold on in there. I'm sure they'll fix the D15 release in a few weeks.