To TapMyHed - did you have to manually input all the settings when you rolled back to d27? I would like to echo your comment about the timeout functionality which really gets annoying after a while
Thankfully the router hasn't hung yet but one more episode and I think I'll try d27
Cheers, Mike
Yes. To be absolutely sure everything was right. Billion fan recommends a clean set up after a firmware update.
Some of the earlier firmwares i used were ok, d23. D24 had issues with schedules on ssids and as usual billion fan sorted that right out with d27.
I didn't get a chance to use d27 instead leaving it ages and going straight to d41.
I'm really glad i put in d27 this week and put all the settings back in after a factory reset. It's been blindingly great and reliable and the webpage pops up so quick now so i can find tune the kids connections.
Let's face it, i really like the billion simply because managing kids devices and QoS is brilliant.
Many thanks for that - from reading other posts on the forum, I think firmware pre d36 has to be manually configured if rolling back. Ah well - I will only roll back if I experience more hangs or if I'm feeling particularly bored Cheers, Mike
My router hung again this evening in the same way as described earlier (ie) it's lit up but no response to pings/loss of internet
The last few messages recorded in the log were:
Aug 29 17:46:39 192.168.27.1 kernel: Intrusion -> TCP packet from [ptm0.1] 87.251.70.79:65534 to 92.3.32.223:5905
Aug 29 17:50:50 192.168.27.1 radvd[27899]: received RA from fe80::6203:47ff:fe17:bf06
Aug 29 17:56:52 192.168.27.1 kernel: br0: received packet on eth0.0 with own address as source address
Aug 29 18:00:11 192.168.27.1 kernel: Error - can't find the requested ARL entry
followed by:
Jan 1 00:01:17 192.168.27.1 kernel: ptm0.1 MAC address set to xx:xx:xx:xx:xx:xx [my 'x's)
Jan 1 00:01:17 192.168.27.1 kernel: netdev path : ptm0.1
Jan 1 00:01:17 192.168.27.1 kernel: ->
Jan 1 00:01:17 192.168.27.1 kernel: ptm0
etc.
A zipped copy of the log is attached.
Please let me know if this helps in any way or if there's any further info I can provide.
You do not have the required permissions to view the files attached to this post.
nightcustard wrote: ↑Sat Aug 29, 2020 8:33 pm
My router hung again this evening in the same way as described earlier (ie) it's lit up but no response to pings/loss of internet
The last few messages recorded in the log were:
Aug 29 17:46:39 192.168.27.1 kernel: Intrusion -> TCP packet from [ptm0.1] 87.251.70.79:65534 to 92.3.32.223:5905
Aug 29 17:50:50 192.168.27.1 radvd[27899]: received RA from fe80::6203:47ff:fe17:bf06
Aug 29 17:56:52 192.168.27.1 kernel: br0: received packet on eth0.0 with own address as source address
Aug 29 18:00:11 192.168.27.1 kernel: Error - can't find the requested ARL entry
followed by:
Jan 1 00:01:17 192.168.27.1 kernel: ptm0.1 MAC address set to xx:xx:xx:xx:xx:xx [my 'x's)
Jan 1 00:01:17 192.168.27.1 kernel: netdev path : ptm0.1
Jan 1 00:01:17 192.168.27.1 kernel: ->
Jan 1 00:01:17 192.168.27.1 kernel: ptm0
etc.
A zipped copy of the log is attached.
Please let me know if this helps in any way or if there's any further info I can provide.
Can you confirm which firmware version you are running?
nightcustard wrote: ↑Fri Sep 18, 2020 7:56 pm
Hi billion_fan - sorry about the late reply - my firmware version is 2.52.d41
Regards, Mike
Reported to our engineers
Hi Mike
Can you send us a backup of your config with admin password set to admin so our engineers can check your settings
(email it to support@billion.uk.com also if you can answer the following questions within the email)
1.How long does it take for the lock up issue to occur per cycle ?
2.Can you confirm if syslog Log Level and Display Level is set to = Debugging ?