I would like to get my new HAP AX2 into mode where it will give out IP addresses from the parent DHCP server (ATL LTE18 kit) to it’s Wifi connected and wired clients. So it would act as a "bridge"I guess. In my old router, I could choose between Router/Bridge mode -here I can’t somehow.
Would it be possible to achieve with some conf?
Or I got a wrong product for my need with its limitations?
My planned network [ATL LTE18 kit] ----- [HAP AX2] (garage, wifi and wired clients) ------ [Poe Switch] (house) ----- [AP]
Why not use ax2 as main router ? And put ATL in LTE pass mode ?
It’s possible to do what you want, you just use ax2 as simple switch/AP. There was tutorial by @anav here but i think it’s taken down.
Basically you need to remove default configuration so you have blank device, add all ports to a single bridge (including wireless interfaces), enable dhcp client on bridge.
Good practice is to reserve one port for off bridge mgmt so you don’t lock yourself out of the device.
I would stick to gigabytes plan to use the router as the proper router and the LTE devices strictly as an input WAN device.
However in terms of what you want is basically the AX as an AP/Switch.
highly recommend taking ether5 OFF the bridge for a separate and SAFE way to config the device!!
PS. this is a NON-capsman configuration, KISS !!!
PSS. this is a no vlan configuration and the base subnet is 192.168.88.0
/interface bridge
add ingress-filtering=no name=bridgeax vlan-filtering=no
/interface ethernet
set [ find default-name=ether5 ] name=OffBridge5
/interface list
add name=TRUSTED
/interface wireless security-profiles
/interface wireless
/interface bridge port
add bridge=bridgeax interface=ether2
add bridge=bridgeax interface=ether3
add bridge=bridgeax interface=ether4
add bridge=bridgeax interface=WLAN1-HOME comment=5GHz WIFI
add bridge=bridgeax interface=WLAN2-HOME comment=2GHz WIFI
add bridge=bridgeax interface=WLAN-MEDIA comment="virtual WLAN master is WLAN2-HOME"
add bridge=bridgeax interface=WLAN-GUEST comment="virtual WLAN master is WLAN1-HOME"
/ip neighbor discovery-settings
set discover-interface-list=TRUSTED
/ipv6 settings
set disable-ipv6=yes
/interface detect-internet
set detect-interface-list=NONE
/interface list member
add interface=bridgeax list=TRUSTED
add interface=OffBridge5 list=TRUSTED
/ip address
add address=192.168.88.X/24 interface=bridgeax=192.168.88.0
add address=192.168.55.1/30 interface=OffBridge5 network=192.168.55.0
/ip dns
set servers=192.168.88.1
/ip route
add dst-address=0.0.0.0/0 gateway=192.168.88.1 routing-table=main
/tool mac-server
set allowed-interface-list=none
/tool mac-server mac-winbox
set allowed-interface-list=TRUSTED
NOW if you lets say had three vlans coming from LTE ( the smart way to separate media deviced and guest from being able to access home users/devices )
Assuming on LTE 3 vlans created are:
vlan5-HOME - 192.168.88.0/24
vlan10-MEDIA
vlan20-GUEST
Thanks for the great tips @gigabyte091 and @anav - indeed handing wireguard tunnels and DNS and DHCP and everything else was maybe too much for this LTE18 board. After making it to serve only LTE modem functionality with the passthrough and moving everything else to HAP ax² the network is much more stable. Still figuring out my Wireguard based tunneling and routing between homes, but this is fun part and gives an opportunity to learn.
It looks like the HAP ax² does not have Back to Home functionality working well. It just gives a wrong hostname to the mobile app ( *.vpn.mynetname.net instead of *.sn.mynetname.net)