tunneled to local bridged

  • 0
  • 1
  • Question
  • Updated 3 months ago
  • Answered

Hi

  the current setup is with 2x rfs7000 with mixture of AP7131 and 7532, theWIFI networks  are set to tunnel at present, I would like to test a new setup with one AP/WIFI network to be locally bridged on the AP.

The port of the AP will connect to on the network switch and the port  set to be a trunk port, The AP is set to allow 1,4096 vlans so the network switch hold the allows VLAN information.

Will it work ? having just this one AP / wifi network to locally bridged ? or is it an all or nothing setting ? 

Photo of Phil storey

Phil storey

  • 1,254 Points 1k badge 2x thumb

Posted 3 months ago

  • 0
  • 1
Photo of Andy Holden

Andy Holden, Employee

  • 1,472 Points 1k badge 2x thumb

Hi


The short answer is yes. However you cannot have a vlan that is both tunneled and locally bridged.


Son on this single AP you would need to have a new set of WLANs that are locally bridged and using VLANS that have not been assigned to a previously created WLAN that was TUNNELING traffic

Photo of Christoph S.

Christoph S., Employee

  • 3,230 Points 3k badge 2x thumb
Hello Phil, 

  • Change the WLAN from tunnel to local
  • Make sure the VLANs are configured on the AP (Interfaces >> Virtual Interfaces)
  • Make sure the VLAN is mapped to the WLAN (Vlan Assignment >> VLAN)
  • Trunk only if you have more than one vlan is configured on the AP or else no need to trunk the port. 
  • If more than one VLAN exists, make sure they are also allowed through the switchport the AP is connected to.
  • Make sure that the wireless clients get the correct DHCP IP address information assigned to them (DGW, DNS, etc...)
  • Test 
This way, traffic will be routed by the AP (local) versus the controller (tunnel). 
Photo of Michael (Misha) Elin

Michael (Misha) Elin, SE

  • 476 Points 250 badge 2x thumb
Hello Phil,
  In addition to what is recommended already:
1. Try to keep allowed vlans list reasonable. With "mint mlcp vlan" (default) MiNT link creation protocol (MLCP) will send discovery to all allowed vlans - i.e. to 4096 vlans. Which creates some CPU load.
2. Having same VLAN tunelled and availabe in trunk as well will potentially create loops. For instance client's dhcp request will be tunneled to controller, bridged there to target vlan than reach AP's LAN interface. So as recommended - filter all tunneled vlans in AP trunk

Misha