Vlan-id configured, but interface does not support assigning vlans

Hi,

leider ist es mir nun doch nicht so einfach gelngen meinen Cap-AC ins Netz zu bringen. Wie alle Geräte
habe ich die FW und RB auf die neuste Version gebracht. Auf dem AC dann das wifi-package installiert und alles equivalent zum AX eingestellt. Sah eigentlich gut aus, bis o.g. Meldung " vlan-id configured, but interface does not support assigning vlans" kam, die ich nicht einordnen kann.

Hier mal die gekürzte config des hAP-AX. Danke für eure Hilfe !

# 2025-01-11 07:02:35 by RouterOS 7.16.2
# software id = 9L1W-G84H
#
# model = C52iG-5HaxD2HaxD

/interface bridge
add ingress-filtering=no name=bridge1 vlan-filtering=yes
/interface ethernet
set [ find default-name=ether1 ] name=e1-to-modem
set [ find default-name=ether4 ] name=e4-to-cap
set [ find default-name=ether5 ] name=e5-to-switch

/interface wifi
# vlan-id configured, but interface does not support assigning vlans

add channel.band=2ghz-g configuration.country=Germany .mode=ap .ssid=\
    PRIVAT-2G datapath.vlan-id=100 disabled=no name=cAP-AC-2G-Private \
    radio-mac=74:4D:28:4C:02:A4 security.authentication-types=\
    wpa-psk,wpa2-psk .encryption=ccmp
	
# vlan-id configured, but interface does not support assigning vlans
add channel.band=5ghz-ac configuration.country=Germany .manager=local .mode=\
    ap .ssid=Private-5G datapath.vlan-id=100 disabled=no name=\
    cAP-AC-5G-Private radio-mac=74:4D:28:4C:02:A5 \
    security.authentication-types=wpa-psk,wpa2-psk .encryption=ccmp

add channel.band=2ghz-ax configuration.country=Germany .mode=ap .ssid=PRIVAT \
    datapath.vlan-id=100 disabled=no name=cAP-AX-2G-Private radio-mac=\
    D4:01:C3:00:06:42 security.authentication-types=wpa-psk,wpa2-psk \
    .encryption=ccmp
add channel.band=5ghz-ax configuration.country=Germany .manager=local .mode=\
    ap .ssid=PRIVAT .tx-chains="" datapath.vlan-id=100 disabled=no name=\  
    cAP-AX-5G-Private radio-mac=D4:01:C3:00:06:41 \
    security.authentication-types=wpa-psk,wpa2-psk .encryption=ccmp
	

/interface vlan
add interface=bridge1 name=vlan1 vlan-id=1
add interface=bridge1 name=vlan10 vlan-id=10
add interface=bridge1 name=vlan20 vlan-id=20
add interface=bridge1 name=vlan100 vlan-id=100
add interface=bridge1 name=vlan111 vlan-id=111


/interface list
add name=LAN
add name=WAN
/ip pool
add name=dhcp_pool-GUEST ranges=192.168.10.10-192.168.10.254
add name=dhcp_pool-IoT ranges=192.168.20.10-192.168.20.254
add name=dhcp_pool-Privat ranges=192.168.100.10-192.168.100.254
add name=dhcp_pool-SIP ranges=192.168.111.10-192.168.111.254
add name=dhcp_pool-MGMT ranges=10.0.0.60-10.0.0.254
/ip dhcp-server
add address-pool=dhcp_pool-GUEST interface=vlan10 lease-time=1d name=\
    dhcp-guest
add address-pool=dhcp_pool-IoT interface=vlan20 lease-time=1d name=dhcp-IoT
add address-pool=dhcp_pool-MGMT interface=vlan1 lease-time=1d name=dhcp-mgmt
add address-pool=dhcp_pool-Privat interface=vlan100 lease-time=1d name=\
    dhcp-private
add address-pool=dhcp_pool-SIP interface=vlan111 lease-time=1d name=dhcp-sip
/interface bridge port
add bridge=bridge1 frame-types=admit-only-untagged-and-priority-tagged \
    ingress-filtering=no interface=ether2
add bridge=bridge1 ingress-filtering=no interface=ether3
add bridge=bridge1 ingress-filtering=no interface=e4-to-cap
add bridge=bridge1 ingress-filtering=no interface=e5-to-switch



/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface bridge vlan
add bridge=bridge1 tagged=bridge1,e4-to-cap,e5-to-switch vlan-ids=1
add bridge=bridge1 tagged=bridge1,e4-to-cap,e5-to-switch vlan-ids=10
add bridge=bridge1 tagged=bridge1,e4-to-cap,e5-to-switch vlan-ids=100
add bridge=bridge1 tagged=bridge1,e4-to-cap,e5-to-switch vlan-ids=20
add bridge=bridge1 tagged=bridge1,e4-to-cap,e5-to-switch vlan-ids=111
add bridge=bridge1 untagged=wifi11-IoT-5G vlan-ids=20

/interface list member
add interface=bridge1 list=LAN
add interface=vlan1 list=LAN
add interface=vlan10 list=LAN
add interface=vlan20 list=LAN
add interface=pppoe-out1 list=WAN
add interface=e1-to-modem list=WAN
add interface=vlan100 list=LAN

/interface wifi cap
set discovery-interfaces=all enabled=yes


/ip address
add address=192.168.10.1/24 interface=vlan10 network=192.168.10.0
add address=192.168.20.1/24 interface=vlan20 network=192.168.20.0
add address=192.168.111.1/24 interface=vlan111 network=192.168.111.0
add address=192.168.100.1/24 interface=vlan100 network=192.168.100.0
add address=10.0.0.1/24 interface=vlan1 network=10.0.0.0

/ip dhcp-client
add disabled=yes interface=e1-to-modem use-peer-dns=no

Please also mark the comments that contributed to the solution of the article

Content-ID: 670645

Url: https://administrator.de/forum/vlan-id-configured-but-interface-does-not-support-assigning-vlans-670645.html

Printed on: January 14, 2025 at 07:01 o'clock

2 Comments

Latest comment

Die Meldung sagt es ja schon. Auf CAPs mit AC Chipsets kannst du keine VLANs dynamisch über den neuen CAPsMAN zuweisen, das musst du dann auf dem CAP selbst in der Bridge von Hand zuweisen ...

RTFM
Beispielconfig des CAPs: CAP using "wifi-qcom-ac" package

CAPs using "wifi-qcom" package can get "vlan-id" via Datapath from CAPsMAN, CAPs using "wifi-qcom-ac" package will need to use the configuration provided at the end of this example.

Um die Fehlermeldung weg zu bekommen musst du auch die vlan-id im CAPsMAN Datapath für diesen CAP entfernen

S. Hinweis ebenfalls aus o.g. Link

Passing datapaths "MAIN/GUEST" from the start of the example to "wifi-qcom-ac" CAP would be misconfiguration, make sure to use datapath without "vlan-id" specified to such devices.

Gruß gastric

@gastric ok, danke ... für die Hilfe.. werde es so mal versuchen
hat geklappt. War exakt die stelle im Manual die ich nicht gefunden hatte.

German solved Question MikroTik