@Enoque 

 

Hey

 

So the article you are reading is for creating an Management VLAN, this is not what you are after.

 

Management VLANs in short are a specific VLAN that the Omada system can use to communicate to eachother away from the default network.   Basically a segmented network for ONLY Omada traffic, which is not what you want.

 

You can indeed create VLANs without an Omada router, but you will need some router capable of VLANs to accomplish this as it will be providing the seperate networks for you.   You can then pass these networks onto the Switch and APs.   What hardware do you have in place at the moment?  If you dont have full Omada or use a mix this may be more complicated, bear in mind your switch and APs also need to support VLANs.

 

  @Philbert 

 

Hello,

 

Thank you very much for the reply. I see that now, I thought it was to have my LAN connected. I have a OC200. 1 TL-SG2008 and 1 EAP225. The issues I am mostly Is my normal VLANs are able to get to the router(internet). But when I create the VLAN/interface(and wireless network) with a IP range, my device gets assigned an IP (e.g. 192.168.10.55) in that range, its just the gateway ip is the subnet gatway ip(192.168.10.1), I need it to be able to connected to the internet which is VLAN1(192.168.1.1).

 

Since the TL-SG2008 is a Layer 3 Switch, i thought i wouldnt need the gateway and could just use my ISPs router.

 

Adding a diagram of how its connected: 

The 10 and 100 VLANS are able get their respective IP correctly but cant get internet from the 1.1 router. 

  @Enoque 

 

Hey

 

Yeah the problem is that the Interface VLAN you are creating is expecting to see an IP address of the Default Gateway (192.168.10.1) on the network somewhere, this would be located on the router, which sadly in your case has a different IP.  

 

Ideally you would need to change your default gateway to 192.168.1.1 but as this is an SDN solution that isnt possible.     The way I have got this working before with 3rd party routers is to create just VLANs and not Interfaces, that way its just chucking the data down to the 3rd party router and it handling DHCP and interfaces.    Honestly this is very likely not a capability of your ISP router, its designed for just one VLAN (the default one) and thats it.

 

After rattling my brain here for an hour considering this for you, honestly dont see an easy way to do this without some VLAN capable router in place, be that 3rd party or Omada.

 

Unless someone can think of something I cant, to do this you will likely have to consider a router of some description.   A lot of people use Mikrotek Routers and they are feature rich devices, however if spending money it would be wise to consider the Omada router as its fairly reasonably priced and will work seamlessly for you.

 

Thank you very much for looking into it. I was thinking the same. Pushing down to the gateway. What I found most frustrating is that all the VLAN stuff was working fine in standalone mode. It looks like adding the controller removes a ton of L3 config. Since I havent been able to get it working since adding the controller. I got the controller to control mt EAPs. Its almost as if (tin foil hat goes on) they want me to buy THEIR router/gateway(ER605).

  @Enoque 

 

Tin Foil hat at the ready!

 

 

Yeah this is one of the limitations of an SDN solution like this, it very much requires you to be onboard with that one vendor, Ubiquiti is virtually the same in that regard.

 

They are a funny type of layer 3 switch, in that they are but are not lol.  They are software aware of the gateway, but ultimately its not programmed on the switch, instead rather the router making this really just  layer 2 switch which is layer 3 aware?  As said Ubiquiti is pretty much identical in their setup and it also doesnt play well with 3rd party stuff.  Its one of the big caveats of using a simpler SDN implementation, what you gain in simplicity, you lose in control / flexability.

 

One advantage is that the Omada 605 router is pretty cheap and in fairness does what it says on the tin, been running it a for a year now without issue (touch wood)