Unknown AP on WRT1900ACSv2

Installing and Using OpenWrt
1

Hello,

I just upgraded the Linksys wrt1900acsv2 from 18.xx to the latest version (24.10). I know much has changed since then (DSA support and more) so I chose to reset the settings to factory (I think I was even forced to do that).

So I configured the device as usual. But now I have an extra AP on the 2.4G wifi network, overlapping with the configured 2.4G. It's clearly linked to this device because when I disable both radios, that AP disappears too. If I configure the 2.4G radio to another channel, that extra AP follows it. Even more, when I disable both radios, and I do a configuration change on one of the radio's, that AP returns while the 2 configured AP remain disabled !

The unknown AP is named "E_433_433" and follows the channel of the configured 2.4G AP.

How do I get rid of this AP ? It is nowhere to be found in any configuration file...

Yves

2

and you don't have a wifi extender somewhere ?

3

No I don't have wifi extenders.

4

Also it looks like it has a randomized/custom MAC address "F6:3C:3B:06:21:BB"

5

OpemWrt does not magically start random ap after reset.

6

I ran mvebu targets for many years and never seen or heard of that. Double check you are running the latest 24.10.1, check you are not on the 2nd parition on some old build remember to install the luci-app-advanced-reboot package for your target since it's supported there. Finally consider starting over with a wipe/clean config with firstboot && reboot.

7

What does iwinfo say about the radio configuration?

8

I did a factory reset and reconfigured and it is gone now.

I wonder if this would be some kind of security breach attempt so that I would try to connect to it and give it my password ? I'm unsure if anyone of the family tried that so I changed the credentials to be on the safe side.

Yves

9

if they've managed to set up their own AP on your device, they've already go your password.

10

The thing is, nowhere in any configuration file could I see this AP configured. It might still be an external AP from the neighbor doing this.