IP Range to Omada Customers

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

IP Range to Omada Customers

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
IP Range to Omada Customers
IP Range to Omada Customers
2020-05-19 17:38:33
Model: EAP110  
Hardware Version: V4
Firmware Version: 3.1.0 Build 20180418 Rel. 74719
Good afternoon,

I'm from Brazil

 

I come through this forum, because I have a problem with my network controlled by Omada Controller. He currently manages 4 EAP, however, our internal network is in DHCP, in which any device that is placed on the network, acquires automatically. However, workstations, servers and the Omada Controller itself and the EAPs are with fixed IPs. 

Now the problem is that when connecting a Cellular Device or Printer to the Wifi network, it acquires an IP from a machine that is fixed or from some equipment that is momentarily off.

 

 

What I wanted to know is whether Omada is able to restrict an IP range so that all connections made in the EAPs are attributed only to what we call.

 

Example..
We set the range in OMADA: 192.168.1.0 to 192.168.1.99
And so all connections made on it were within that range.

Is there a possibility?

Thank you.
  0      
  0      
#1
Options
2 Reply
Re: IP Range to Omada Customers
2020-05-19 20:39:34

Hello @Prevencardio,

 

Neither the EAP nor the Omada Controller (software or OC-200) will do what you are asking.  You need something with Layer-3 control like a Layer-3 switch or router.  You would then need to link your Wifi clients SSID to a VLAN tag.  Then route that tag (on the Layer-3 swtich to the subnet (or portion of a subnet) of your choosing.

 

Similarly, DHCP services are provided by your own DHCP server/service/appliance (like your router or higher end Layer3/4 switches) separately from the the EAP/Omada equipment.

 

-Jonathan

  0  
  0  
#2
Options
Re: IP Range to Omada Customers
2020-05-20 00:22:09 - last edited 2020-05-20 00:22:56

 

Prevencardio wrote

He currently manages 4 EAP, however, our internal network is in DHCP, in which any device that is placed on the network, acquires automatically. However, workstations, servers and the Omada Controller itself and the EAPs are with fixed IPs. 

 

Omada controller does not assign IPs via DHCP, it's your DHCP server which does this.

 

Solution is to configure a limited DHCP address pool in your DHCP server, from which IPs are being served. For example:

Base (start) IP: 192.168.1.20

Last (end) IP: 192.168.1.249

 

Then you can use the spare IPs from 192.168.1.1 to .19 and .250 to .254 as static IP addresses.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  1  
  1  
#3
Options

Information

Helpful: 0

Views: 2113

Replies: 2

Related Articles