Hi all, this is not the first time I use Mikrotik to do that but it’s first time I have to spend over some minor problems so let me explain. I need to provide connectivity to some equipment that I did insall in a rack and it’s not easy to pull a cat cable to it. In this case I bought an hac ac lite and after some try I start with a clean configuration:
create a bridge and add all 5 eth interface and the 2 wifi
connect to the existing wifi with station-pseudobridge
now from the eth port of the hap I can connect to the rest of the network but the hap have no IP adress. I try with DHCP client with no result. Considering that it’s not a real problem I set the hap with a static IP adress disabling the dhcp client.
Now the main problem is that I can’t reach the hap from the main network, also winbox can’t find the hap. Only if I’m connect to the eth port of the hap.
Some advice?
Thanks.
Hard to tell without seeing config.
Any station mode, other than “station-bridge”, has problems when transparent bridge between two wired islands is required. In particular: MAC address of wired computer is lost when frame is passing such wireless link and any service, which expects to see unique MAC address (DHCP server is often one of them, winbox in MAC connectivity mode is another one), has problems.
Read more about different wireless station modes: https://help.mikrotik.com/docs/spaces/ROS/pages/122388518/Wireless+Station+Modes
Solution: use device, made by same vendor[*], as main AP.
[*] in case of Mikrotik, with event of AX wireless devices (and AC when running new wifi drivers), there was a generation change and older wireless driver features are largely incompatible with new wifi driver features
# jan/02/1970 00:08:37 by RouterOS 6.49.17
# software id = 9SFQ-RWTJ
#
# model = RB952Ui-5ac2nD
# serial number = HG909VMACTJ
/interface bridge
add name=bridge1
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
add authentication-types=wpa2-psk mode=dynamic-keys name="****" \
supplicant-identity="" wpa2-pre-shared-key=**************
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-onlyg country=italy frequency=2437 \
mode=station-pseudobridge security-profile="****" ssid="****"
set [ find default-name=wlan2 ] band=5ghz-onlyac channel-width=\
20/40/80mhz-eCee country=italy disabled=no frequency=5200 mode=\
station-pseudobridge multicast-helper=dhcp security-profile="****" \
ssid="****"
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 interface=ether2
add bridge=bridge1 interface=ether3
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
add bridge=bridge1 interface=wlan1
add bridge=bridge1 interface=wlan2
/ip neighbor discovery-settings
set discover-interface-list=!dynamic
/ip address
add address=192.168.1.212/24 interface=wlan2 network=192.168.1.0
/ip dhcp-client
add interface=bridge1
That’s my configuration.
Added to discussion in my previous post I have another suggestion: when configuring wireless interface into any of station modes, don’t “pin point” radio settings to anything. If AP decides to change its own running values, station may not be able to follow those changes. In particular:
set [ find default-name=wlan2 ] band=5ghz-onlyac channel-width=
20/40/80mhz-eCee country=italy disabled=no frequency=5200 mode=
station-pseudobridge multicast-helper=dhcp security-profile=“PF service”
ssid=“PF service”
unset settings for band, frequency and channel width. Even if AP is set statically with this regard (e.g. frequency only 5200), it’s no use to set station statically. The only positive effect is when station searches for suitable AP, it’ll only use parameters configured … if they are correct, then initial connection will be faster (by a few seconds at most). Detrimental effects are much more serious though.
And an error: static IP address should be set on bridge1 interface … wlan2 is bridge port and should thus never be used as a stand-alone interface.
That’s explain why I can’t connect to the hap from the main network? I can’t ping it either.
From winbox only the frequency can erase.
I’ve no idea. It might be due to the fact that static IP address is set on wlan2 instead of bridge1?
You can set frequency=auto, band=5ghz-a/n/ac and channel-width=20/40/80mhz-XXXX, that’s as generic as it gets.
You can try to set station-roaming=disabled … it will make station not to try to find a better AP after it connects to first AP. It is useful if both AP and station are stationary and hence signal strength doesn’t change with time (hopefully station connects to best AP in case there are more than one). Also it’s good to set it if there’s only one AP and signal strength is not the best … station would try to find a better AP (and degrade service meanwhile) but if you know there is no other AP, then you can as well configure station not to try to roam.
So after some time spent over I say state that it can’t do what I want. The strange thing is that I did buy an hap (I remeber that was with the usb so a different version) that did work (after I change to bridge-pseudostation) now instead you can’t reach any of the ip that is connected to the hap but from the hap you can. The main goal to me is that from an app I have to control 2 machine after the hap but the can’t. But it did work, unbeliveble.
It happen that I have a TL-WR802N that I did configured to be a wifi client. With the wifi of the hap disabled and the tp link connected wia ethernet cable to the hap everythings works.