The scenario I had working until a few days ago at home, was like this:
- A hAP ac^2 was used as my 2nd AP.
- In an area where I had no LAN connectivity (actually I had but someone destroyed but that is another story), I had to connect a device so I used an RB951G-2HnD as a WiFi client.
This scenario was working (don't even remember exactly how I set it up, as it was few years ago), BUT I had lost any admin access to 951, both over WiFi and over LAN (tried connecting a laptop with a static IP, directly to it, on all it's LAN ports).
I let it be though, as it was simply working.
A few days ago, I replaced my ac^2 with another vendor device (sorry). I set up SSIDs etc. the same way, so everything (mobile devices and IoT devices) worked transparently like nothing changed.
EXCEPT the 951.
For some reason, it doesn't seem to work as a client to the new AP. It is not a WiFi issue, as the new AP reports the 951 connected and assigned IP (which is assigned by my router on the 951's MAC - but never actually had access to that IP as I said above, I just let the assignment be anyway).
Since I cannot have admin access, I cannot really see what the probelm is.
So I am looking solution for ANY of the following:
1- Gain admin access somehow without factory reseting it (possible?).
2- RE-configure from scratch (factory reset it), make it a client again, but in a way I still get admin access maybe over one of its LAN ports, for resolving issues, updating etc.
3- Replace it with ("retired") ac^2 but since ac^2 is dual band, somehow make it work also as a repeater (I need some further extension of WiFi range where the device is, anyway). Also I prefer to "over"-utilize ac^2 than retire it (prefer to retire 951).
4- A mix of #2 and #3, where 951 is just a client and ac^2 is connected to it as an AP, so it practically creates a repeater. But I hate this scenario (and has terrible WAF - remember this is at my house).
Best to worse: 3, 1, 2, 4.
Can someone point me to the right direction?
Thank you.