topic Re: Hub2 Log filling up. in My Router

Hub2 Log filling up.

Mark-J — Sat, 24 Feb 2024 18:30:48 GMT

Hi all,

I have recently moved over to full fibre and using the Hub 2.

Everything is running great but looking at the Log entries I see that the log is filling up with the following:-

2.4G client Mac: BC:6E:76:25:EF:73 Deauthentications (Reason:Deauthenticated because sending station is leaving (or has left) IBSS or ESS)

I have not had this before. Even when I turn off the 2.4G WiFI I am still getting these entries.

Anyone know what is going on.

Thanks.

Re: Hub2 Log filling up.

Dan_the_Van — Sat, 24 Feb 2024 18:41:21 GMT

@Mark-J welcome to the community

The MAC address BC:6E:76:25:EF:73 appears to registered to Green Energy Options Ltd.

It could be it's not getting a connection to the Hub and repeatedly retries.

Re: Hub2 Log filling up.

Mark-J — Sat, 24 Feb 2024 18:44:45 GMT

Hi,

Yes I did a MAC lookup and found the info, but it is not a device belonging to me. Its just filling up the log ever few seconds and can't stop it.

Re: Hub2 Log filling up.

MisterW — Sat, 24 Feb 2024 18:51:40 GMT

From what I can see, it's likely a WiFi module in a Smart Meter IHD

https://geotogether.com/product/wifi-module/

Re: Hub2 Log filling up.

jab1 — Sat, 24 Feb 2024 18:52:30 GMT

If it is anything like the one in my (now re-boxed) IHD, it is as much use as a chocolate kettle.

Re: Hub2 Log filling up.

Dan_the_Van — Sat, 24 Feb 2024 19:46:54 GMT

When you started using the Hub two did you copy the wireless name and password from your previous Hub? This would explain why it is trying to connect if it is set for that network.

It would only attempt to connect to a wireless network it has been configured for.

Re: Hub2 Log filling up.

Mark-J — Sun, 25 Feb 2024 01:20:19 GMT

No, changed the name. New Hub New name. The device trying to connect is unknown to me. BUT I do have a smart meter which is what I thought it might be but do not understand why its trying to connect to me so persistently. I have switched back on my old WiFi unit and it does not try connecting to that !

It could be a neighbours I suppose. Guess I'll just have to live with the Hubs Log filling up with junk.

Re: Hub2 Log filling up.

MisterW — Sun, 25 Feb 2024 07:44:37 GMT

BUT I do have a smart meter which is what I thought it might be but do not understand why its trying to connect to me so persistently

Its not a Smart meter per se, it's likely an IHD (In home display). If you have one with a wifi module, it will likely have been configured with the wifi name and password of the odl router. It will need reconfiguring with the the name/password of the new hub wifi.

Re: Hub2 Log filling up.

Champnet — Sun, 25 Feb 2024 08:26:45 GMT

Interesting, I always thought smart meter configurations or in home displays were completely independant of any home networks.....

Re: Hub2 Log filling up.

MisterW — Sun, 25 Feb 2024 09:11:22 GMT

The meter and the basic IHD's are independant. The later ones have the option to connect to your wifi network to allow you to use an App to get the data from the IHD.

Re: Hub2 Log filling up.

Mark-J — Sun, 25 Feb 2024 12:08:49 GMT

I have reprogrammed the Indoor Display Unit to my new network but I still get these log messages. I have unplugged the Indoor Unit completely and no still change. The display unit does not have the same MAC address that is showing up on the log entries.

Looks like I will just have to live with it.

Re: Hub2 Log filling up.

greygit1 — Mon, 26 Feb 2024 00:06:57 GMT

Its the same network 'modelling' as used by a lot stuff.

Local device ->. local wireless network -> internet connection -> a server on the internet (but no capability of accessing the local devide within the local network)

Solution?

Local device (mainly a internet-connected 'smart phone', also connected to the local wireless network) -> app -> a server on the internet - pulls back the info put back onto the internet.

Re: Hub2 Log filling up.

Champnet — Mon, 26 Feb 2024 08:01:11 GMT

@Mark-J wrote:
Looks like I will just have to live with it.

Both iPads and iPhones can randomise their MAC addresses. If you have any then check their wifi settings.

Re: Hub2 Log filling up.

Mark-J — Mon, 26 Feb 2024 16:41:56 GMT

Hi All,

Just thought I would update everyone regarding my Hub2 Log filling up with an unknown WiFi device.

Yesterday the Hub2 Log had an entry saying the logs for the 2.4G WiFi had reached its maximum !

So I took the steps of resetting the Hub2 back to Factory defaults. Reloaded my configuration and everything came back as expected minus the unwanted WiFi alerts in the log page.

So far its been running for over 6 hours now and not a single entry. Whatever the device was trying to connect to my Hub2 has gone away and is no longer bothering me. Maybe the Hub2 got confused at some point, who knows!

Thanks for everyone's input.

Re: Hub2 Log filling up.

Anonymous — Mon, 26 Feb 2024 17:00:59 GMT

@Mark-J wrote:

Maybe the Hub2 got confused at some point, who knows!

That would be my guess, because the last statement in your original post shouldn't be possible, and made no sense -

@Mark-J wrote:

I see that the log is filling up with the following:-

2.4G client Mac: BC:6E:76:25:EF:73 Deauthentications (Reason:Deauthenticated because sending station is leaving (or has left) IBSS or ESS)

@Mark-J wrote:

Even when I turn off the 2.4G WiFI I am still getting these entries.

Re: Hub2 Log filling up.

Champnet — Mon, 26 Feb 2024 17:05:32 GMT

@Anonymous It’s possible the unknown device gave up when the router was re-booted, It’s even possible the unknown device has now connected to the correct router which may have had a weaker signal…

Re: Hub2 Log filling up.

greygit1 — Mon, 26 Feb 2024 22:13:11 GMT

Who was visiting at the time?

Could the device be a i-something with a MAC which you don't recognise? I've seen similar when one of my offspring has visited and they've configured their i-thing to use a MAC which is something not recognised outside of their own local network. They've had the wireless key to here so they can still access the wireless network when they've visited (for their own convenience). And the hub2 doesn't have any MAC filtering. Such entries disappeared when the visitor left the ranges of wireless network. Sometimes the device would generate multiple entries as it fell in and out of the ranges of the two wifi networks (as they wandered around the house and garden).

Re: Hub2 Log filling up.

bobpullen — Tue, 27 Feb 2024 01:36:03 GMT

The Hub Two will rotate its logs at a sensible interval anyway I imagine, so even when 'full', it's unlikely to have any impact on your Internet connection.

Reassuring that the errant entries have gone away though I guess.

Re: Hub2 Log filling up.

Dan_the_Van — Tue, 27 Feb 2024 07:42:57 GMT

@greygit1

Such entries disappeared when the visitor left the ranges of wireless network. Sometimes the device would generate multiple entries as it fell in and out of the ranges of the two wifi networks (as they wandered around the house and garden).

I do not recognise this behaviour with the Hub Two I've used.

A MAC address can only be listed once, it will show up as connected to either 2.4 or 5GHz (or LAN port), when not connected it will detail which frequency it was last connected to.

The only condition when a device name (hostname) can be listed more than once is when the device has used two different MAC addresses, this being either a LAN or multiple wireless MAC addresses due to a device using randomised MAC address for privacy reasons. New wireless devices use randomised MAC address is the default setting.

The Hub also displays devices that have previously connected from months ago, in a disconnected state

Re: Hub2 Log filling up.

greygit1 — Thu, 29 Feb 2024 21:05:16 GMT

"The Hub also displays devices that have previously connected from months ago, in a disconnected state"

That'd be in the "devices" section, and not in the log?

Perhaps I should have been clearer - in the case I was remembering it was entries in the log, and the entries in the log ceased to re-appear. I also remember log entries which mentioned "self-roaming" for the device.