Inter-VLAN connection not working correctly

Hi guys,

I am trying to set up my network with VLAN on my hAP ax3 to achieve the set up below:

The network has no switches, all devices are connected via Wifi and ethernet cable directly

VLANs
- 100: Management - 192.168.100.1/24
    - Tag Mgmt_2/5
    - Tag ether_5

- 10: Main devices - 192.168.10.1/24
    - Tag Main_2/5

- 20: Main IOT - 192.168.20.1/24
    - Tag IOT
    - Tag ether3_Verisure_hub
    - Untag Main

- 30: Unsecured IOT - 192.168.30.1/24
    - Tag IOTx
    - Untag Main

- 40: Guest - 192.168.40.1/24
    - Tag Guest

- 50: Servers - 192.168.50.1/24
    - Tag ether2_NAS
    - Untag Admin

Here is my full configuration https://pastebin.com/JFju0uA8.

In my understanding, I can only have 2 wifi interfaces due to the hardware limitation, so I set 2 “master”| Wifi “TL_Mgmt_5/2” cards and other “slave” cards to derive the settings from it, in order to get the different SSID

From the configuration above, I can connect to different SSIDs just fine, the IP addresses are leased correctly, with a few problems I would like to ask for your inputs:

  • I cannot set a static IP address to the “ether_2” port with the DHCP → Leases → Set static. Every time I tried it, it kept the status at Wating or Offer, and when I ping, it is unreachable.
  • Machine A connect to TL_IOT using Windows, machine B connects to TL_Mgmt_5 using MacOS. At the moment, A can ping B, but not the other way around (I never been able to use Mac OS to ping my network before for some reason, even in the same subnet, so it could be something with the computer). But I would like to set up so that B can reach A but not the other way around.
  • I cannot connect to Winbox anymore with this set up, even though I can ping 192.168.88.1 just fine. Scan neighbors discovered nothing and trying connect via IP address doesn’t work. The only port that allow the connection currently is “ether3”.

Maybe related, maybe not, Windows (I am presuming Windows 10 or 11) does normally not respond to pings (if the network is categorized as Public, it should work if Private, but sometimes it is needed to change a firewall rule on windows).
See:
https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-Window-10-computer-does-not-reply-to-ping/ta-p/286927

Thank you! I will try that out.

Do you have some input for my config as well?