Good day all, I've been trying to follow the existing guides on how to configure a new metal AC52 as a wifi station/client to connect to the existing non-mikrotik wifi at the rv campground. The AC52 is running OS 7.21.4.
Specifically I want to connect to a remote wifi AP, then feed the internet connection via the ethernet port to my rv's router.
None of the setup guides that I have found online seem to match what I see on the screen.
Sorry, I'm stumped and after a week of searching really frustrated.
You change the mode of the wifi interface corresponding to the frequency of the campground wifi to station-pseudobridge, add SSID and password, bridge it with ether1 and you're done
Possible wifi connection using ac52 device.
(Sorry about the amount of text)
Assumes it's default configuration is much the same as a map lite device
(also a single wifi, single ethernet device)
Default configuration of this device is ethernet is WAN, and wifi is
attached to a bridge and is LAN. wifi is open (no password)
Initial configuration changes need to be done via wifi.
Tasks:
Login to the guest wifi with laptop, and check the ip address received from guest wifi.
If it is in range 192.168.88.0/24 will need to alter IP address on ac52 later.
Download and use winbox from mikrotik.com/download
Need ethernet port on laptop, USB adapter if necessary.
Leave ether1 on ac52 unconnected (except poe injector powering it)
Connect to the ac52 via wifi. (Device should show up as mikrotik_SomeHexValues) Note: You may need to fight the laptop a little here, as it might not
want to stay connected as it cant get to the internet. Just keep
reconnecting to the ac52, it should eventually stick.
Login using winbox
Configure password on device (if it doesn't have one)
Ensure RouterBoot is same version is RouterOS
system / routerboard, upgrade if needed, restart and reconnect.
Reset device to factory defaults, (but keeping users)
system / reset configuration
Connect via wifi again.
Go into the firewall
Check there are filter rules defined.
If in the first part above, the ip address received by the laptop was 192.168.88.0/24
use quickset to change the internal IP address and dhcp range of the ac52 to something different,
perhaps 192.168.84.1, and 192.168.84.30-192.168.84.230. Apply,
Then disconnect and reconnect back to the wifi.
In bridge screen, choose the ports tab and add ether1 to the bridge.
Plug laptop into ac52 ethernet port (data side of poe injector)
Disconnect from the wifi, and ensure you can now login using the ethernet cable.
In the interface/interfaces screen, disable the wireless lan device (devices?)
(Is 2.4GHz called wlan1 and 5GHz called wlan2 maybe, I have assumed wlan1 change as required,
you could setup both)
In the bridge/Ports Screen, disable the wlan device(s).
In the interface/interface lists screen, Change the WAN entry from ether1 to wlan1
In the ip dhcp-client screen, change the default dhcp client interface from ether1 to wlan1
In the wireless screen.
Choose the security profiles tab.
Add a suitable entry for the wifi you want to connect to.
Name it so it indicates the ssid it is for.
Mode is hopefully dynamic keys
Choose wpa2 psk
Enter the wpa2 pre-shared key.
Save it.
Note: In settings at top of winbox, you can allow it do display passwords.
Open the Wifi interfaces tab of the wireless screen.
Open the wlan1 entry.
Enable advanced mode.
Change mode to be station
SSID to be the SSID you want to connect too.
security profile: The one you setup above
Frequency Mode: regulatory-domain
Country: Your country
Installation: any
WMM support: enabled
Station Roaming: enabled
Default Authenticate: Yes
Enable the interface
(enable button at RHS or in general tab on newer winbox)
You should see device searching for ESS, and hopefully it will connect.
In the Log, it should show you what happened.
And the current IP address.
You might with luck now have internet access.
Some things that might still cause issues:
You may need login into the guest network.
They may watch the ttl's of packets and block you if they change.
(change indicating you are using a router)
In this case you can perhaps add the following mangle rule which might
help
/ip firewall mangle
add action=change-ttl chain=postrouting comment="force outbound ttl to 65 (except when tracert)" new-ttl=set:65 out-interface=wlan1 ttl=\
greater-than:35