Controller with 3rd Party gateway: Can't connect to WLAN with VLAN

Controller with 3rd Party gateway: Can't connect to WLAN with VLAN

Controller with 3rd Party gateway: Can't connect to WLAN with VLAN
Controller with 3rd Party gateway: Can't connect to WLAN with VLAN
a week ago - last edited Monday
Model: OC300   EAP653  
Hardware Version: V1
Firmware Version: 5.14.32.56

Hi,

I'm sorry, this is my 2nd day with the OC300 Controller and I have a very strange problem, which is probably due to my lack of experience with the controller software.

 

I'd like to seperate my WLAN networks by VLAN:

My default network (172.1.0.0/16) is VLAN 1, with the SSID "Internal". Connected from Port 1 to my switch, managed by a firewall. If I connect to the internal WLAN, i get an internal IP address and everything works fine.

 

My second network (172.18.0.0/16) is VLAN 18, with the SSID "guest". Connected from Port 2 directly to my firewall. If I connect to the guest WLAN, my Computer can establish a connection but don't have network or web access. I tried it with and without DHCP. If I switch the VLAN config from V18 to default, I can establish a connection to my internal network.

 

I can ping the 172.18.0.1 gateway from the controller and I also can directly connect my computer to the firewall port and have web access, so in my opinion my fault is somewhere on the controller configuration I made.

 

LAN Network:

Name: Guest

Purpose: Interface

VLAN: 18

Gateway/Subnet: 172.18.0.1/16

 

Switch Profile:

Name: Guest

Native Network: Guest(18)

Untagged Networks: Guest(18)

 

WLAN:

SSID: Guest

Device: EAP

....

Advanced Settings:

VLAN: Custom

Add VLAN: By Network - Guest(18)

 

What did I do wrong and where is the error in my config?

 

EDIT: I tried this guide but it doesn't work: https://support.omadanetworks.com/in/document/13319/

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:Controller with 3rd Party gateway: Can't connect to WLAN with VLAN-Solution
a week ago - last edited Monday

  @Pungini 

 

If i am reading this right, you have two different uplink ports for each vlan to the firewall?

 

On the AP side of things, it should be connected to a port with untagged vlan 1, tagged vlan 18, otherwise the traffic on the AP on the second SSID cant go anywhere

Main: ER8411 x1, SG3428X x1, SG3452 x1, SG2428LP x1, SG3210 x1, SG2218P x1, SG2008P x1, ES205G x2, EAP650 x6 Remotes: ER605 v2 x3, SG2008P x2, EAP650 x2 VPN Server: ER7206 v2 Controller: OC300
Recommended Solution
  0  
  0  
#2
Options
4 Reply
Re:Controller with 3rd Party gateway: Can't connect to WLAN with VLAN-Solution
a week ago - last edited Monday

  @Pungini 

 

If i am reading this right, you have two different uplink ports for each vlan to the firewall?

 

On the AP side of things, it should be connected to a port with untagged vlan 1, tagged vlan 18, otherwise the traffic on the AP on the second SSID cant go anywhere

Main: ER8411 x1, SG3428X x1, SG3452 x1, SG2428LP x1, SG3210 x1, SG2218P x1, SG2008P x1, ES205G x2, EAP650 x6 Remotes: ER605 v2 x3, SG2008P x2, EAP650 x2 VPN Server: ER7206 v2 Controller: OC300
Recommended Solution
  0  
  0  
#2
Options
Re:Controller with 3rd Party gateway: Can't connect to WLAN with VLAN
a week ago

Hi  @Pungini 

 

We need understand your topology first. Can you please share a topology like in the article?

Please include the mentioned switch&gateway port number.

 

When connecting to the guest network with DHCP, will they clients obtain an IP address from the second network(172.18.0.0/16)?  If not, what IP address will they get? some IP in default network (172.1.0.0/16), or an invalid IP 169.254.x.x?

  0  
  0  
#3
Options
Re:Controller with 3rd Party gateway: Can't connect to WLAN with VLAN
Monday

  @GRL 

 

Damn it, you are right. I thought all the traffic goes through the controller and in to the firewall, but the APs manage the traffic, so they need the tagged VLANs, not the controller.

 

Thank you very much

  0  
  0  
#4
Options
Re:Controller with 3rd Party gateway: Can't connect to WLAN with VLAN
Monday
Great. This seems to be a common misconception when people start using SDN (controller based) network for the first time. The controller does absolutely nothing other than telling other devices what to do, it essentially lets you configure all supported devices without having to go into each devices GUI seperately Controllers themselves only need to exsit on the management vlan, and can even operate just fine on a 10mbit link since they are just sending and receiving config data!
Main: ER8411 x1, SG3428X x1, SG3452 x1, SG2428LP x1, SG3210 x1, SG2218P x1, SG2008P x1, ES205G x2, EAP650 x6 Remotes: ER605 v2 x3, SG2008P x2, EAP650 x2 VPN Server: ER7206 v2 Controller: OC300
  1  
  1  
#5
Options