N/A Gateway from OMADA SDN DashBoard / NO Gateway in All Client Device Properties
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have a concern related to all Client devices under my hotspot using OMADA SDN OC200 Controller and Outdoor EAP225. From the Below picture, I noticed no gateway specified on each device where I understand N/A Gateway from the dashboard of my omada account is particular for hardware compatible gateway on very few available models only.
My question is since I'm using a gaming router ASUS RT-AX88U connected to the SG-TL1008MP 8 POE Port switch, all my client properties don't have the gateway. I noticed gateway from my gaming home router don't have a specific gateway define (key in) as per the attached screenshot. Is the gateway from my router directly related to the properties of clients in the Omada environment? I have also attached a screenshot of my dhcp gateway router field. I understand default gateway of router is the main Ip address of router. doing ipconfig/ all shows me my default gateway and dhcp server is the IP of my router which is 192.168.50.1 on this scenario.
Please advise.
Hi JhonneL,
I don't want to sound harsh, but if you don't believe me, then please at least RTFM (Read The Fine Manual):
Again: Ignore any function which shows the warning message »Gateway required« if you don't have an Omada Gateway.
You cannot use all those nifty functions such as setting a fixed IP address for a client through SDN Controller if the SDN Controller does not manage an Omada Gateway. And no, Asus routers will almost certainly never be supported as an Omada Gateway. The message is not related to your client device or to a default gateway setting on the Asus router, it is related to the »Use Fixed IP Address« setting of this particular configuration menu.
Omada SDN Controller does not interfere with the data flow between clients and the router, it does not interfere with any services such as DHCP, DNS etc. It even does not notice that kind of traffic, it just does not see any traffic flowing between a client and a router. It collects only data from Omada devices to learn about clients and their usage, nothing else.
It's not that difficult to understand: every network needs 1) a router, 2) a DHCP server and 3) a DNS server at least. Most home routers are all-in-one devices, thus the Asus router provides all those services and it is fully functional for your home network.
Omada Controller does only see messages directed from Omada EAPs, Omada switches and Omada gateways to the controller and it does not even care about any settings or the traffic of your DHCP server, DNS server or the Asus router.
If you want to set a fixed IP for your Galaxy client device, manually define this IP in the Galaxy itself (if possible at all). You cannot define its IP through the SDN Controller unless you have a full SDN network (Omada SDN router, Omada SDN switches, Omada SDN EAPs). This is what SDN is all about: a completely SDN-enabled network. Using any other non-SDN enabled router or non-SDN enabled switch is no problem at all, but those devices cannot be managed by the Omada SDN controller.
Hope this helps to understand the concept of an Omada SDN Controller better.
Hi JhonneL,
I don't want to sound harsh, but if you don't believe me, then please at least RTFM (Read The Fine Manual):
Again: Ignore any function which shows the warning message »Gateway required« if you don't have an Omada Gateway.
You cannot use all those nifty functions such as setting a fixed IP address for a client through SDN Controller if the SDN Controller does not manage an Omada Gateway. And no, Asus routers will almost certainly never be supported as an Omada Gateway. The message is not related to your client device or to a default gateway setting on the Asus router, it is related to the »Use Fixed IP Address« setting of this particular configuration menu.
Omada SDN Controller does not interfere with the data flow between clients and the router, it does not interfere with any services such as DHCP, DNS etc. It even does not notice that kind of traffic, it just does not see any traffic flowing between a client and a router. It collects only data from Omada devices to learn about clients and their usage, nothing else.
It's not that difficult to understand: every network needs 1) a router, 2) a DHCP server and 3) a DNS server at least. Most home routers are all-in-one devices, thus the Asus router provides all those services and it is fully functional for your home network.
Omada Controller does only see messages directed from Omada EAPs, Omada switches and Omada gateways to the controller and it does not even care about any settings or the traffic of your DHCP server, DNS server or the Asus router.
If you want to set a fixed IP for your Galaxy client device, manually define this IP in the Galaxy itself (if possible at all). You cannot define its IP through the SDN Controller unless you have a full SDN network (Omada SDN router, Omada SDN switches, Omada SDN EAPs). This is what SDN is all about: a completely SDN-enabled network. Using any other non-SDN enabled router or non-SDN enabled switch is no problem at all, but those devices cannot be managed by the Omada SDN controller.
Hope this helps to understand the concept of an Omada SDN Controller better.
