AP WLAN VLAN something wrong

RouterOS General
1

Trying to setup a hAP mini as AP for the main router as in http://forum.mikrotik.com/t/hosts-on-the-same-subnet-interface-cant-connect-eachother/164706/1
hAP mini is connected via it’s ether1 to the main routers ether3.
Routers can ping each other, I’m managing the mini through the main router.

Something is wrong with the WLANs of the mini. Any SSID associates but I get no IP assigned. Can’t figure why. Config should be as http://forum.mikrotik.com/t/using-routeros-to-vlan-your-network/126489/1
lak11.rsc (2.17 KB)

2

If you want to use it purely for AP/L2, then config should be like this:
http://forum.mikrotik.com/t/hap-ax-and-hap-ax-now-support-the-entire-5-ghz-range/164621/1

3

@darknate, stick to the harder stuff its where you excel, will never come close to 1/32 that you know but leave the easy pickings to the those that are used to mucking in the mud :wink:

At OP, Taking a look at your config it looks excellent!

(1) However needs slight adjustment on /interface bridge vlans for close to perfection.
You have
/interface bridge vlan
add bridge=BR1 tagged=BR1,ether1 vlan-ids=99

Needs to be
/interface bridge vlan
add bridge=BR1 tagged=BR1,ether1 vlan-ids=99
add bridge=BR1 tagged=ether1 untagged=wlan1 vlan-id=10
add bridge=BR1 tagged=ether1 untagged=wlan2 vlan-id=20
add bridge=BR1 tagged=ether1 untagged=wlan3 vlan-id=30

Note, you can leave out the untagged in this case, but I prefer to put in the config so
that they are visible in an export of the config and one can cross match easily with bridge ports to see what you have done (even more so if ever using hybrid ports)

/interface bridge vlan
add bridge=BR1 tagged=BR1,ether1 vlan-ids=99
add bridge=BR1 tagged=ether1 vlan-id=10
add bridge=BR1 tagged=ether1 vlan-id=20
add bridge=BR1 tagged=ether1 vlan-id=30

(2) Minor change… mac-server is not a secure access method and thus should not be utilized.
From
/tool mac-server
set allowed-interface-list=BASE
/tool mac-server mac-winbox
set allowed-interface-list=BASE

TO
/tool mac-server
set allowed-interface-list=NONE
/tool mac-server mac-winbox
set allowed-interface-list=BASE

(3) Add this line.
/ip dns
set allow-remote-requests=yes servers=192.168.88.1 comment=“dns through trusted subnet gateway”

4

thank you, that was the missing point

but

set allow-remote-requests=yes servers=192.168.88.1 comment="dns through trusted subnet gateway"

fails on the comment, might be because ROS was just 6.9

5

Dont know what you mean a comment is a comment bounded by "

6

As if 6.9 won’t support a comment on that command. Just upgraded to 7.8, can’t check anymore.

7

/ip dns is an array of properties with values. You can only change settings of existing (predefined) properties, you can’t add/invent new ones. comment does not exist … neither in 6.49.7 nor in 7.8.

Sometimes I wonder if @anav has something to do with ChatGPT (who is known to invent things) :laughing:

8

Good point LOL, I think its important to comment on every line of config, bad software habits.
MKX is correct, I didnt actually config that line I just wrote it, blindly assuming one could add a comment to that bit of code… LOL
THe DNS entry is not commentable if that is a word.
Truth be told that was more of - why are we adding this line… will adjust article. THANKS!!!

Not CHAT GPT, but I am flattered you equated me with AI :stuck_out_tongue_winking_eye:
But just to be sheite disturber I did fine one possibility

/ip dns static
add address=192.168.88.1 comment=“Hey look ma, i can comment on one type of dns entry ;-PPPPP” name=mkx_is_always_right