Public Static IP on OC300 Not connecting to Internet
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Public Static IP on OC300 Not connecting to Internet
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
We have tried, unsuccessfully, to get a stand-alone OC300 Controller to connect to Internet through our existing router (non-TP-Link brand) by connecting the OC300 directly to our router and assigning the Controller a public static IP address. This connection was tested with a PC having the same static IP address and the connection worked to the Internet without issue. The OC300 just does not complete the connection. We have set the "Gateway Model" type to Universal, since wer are not using a TP-Link branded Router, but still no connection. We have been back and forth with TP-Link support to try to get this resolved with no luck. Where are we going wrong here?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thanks, good suggestions but the OC300 is located in a data center, racked and connected to our ISP Network feeds. I can probably get to this during the week, but frankly don't expect to get any positive results from this. It's like the OC300 interface is not taking on the IP, SNMask, or gateway entries for the WAN port that is connected. Is there any specific WAN designation for the ports on the OC300 that I might be missing? The documentation is not very specific about Identifying specific port designations on this device, just generalities, like ports can have both LAN and WAN IPs and uses.
- Copy Link
- Report Inappropriate Content
The OCXXX hardware controllers are single-port devices, the 2-ports are just a 2port ethernet switch. The controller port is designed to connect to a LAN environment, and there is no WAN/LAN ability whatsoever.
- Copy Link
- Report Inappropriate Content
So, the designations below only refer to the WAN ports on a connected gateway?
- Copy Link
- Report Inappropriate Content
@DanoH I don't see an image above, but the hardware Controller ports are neither WAN nor LAN, they simply connect to a port with access to the management VLAN/subnet.
The Omada stack is simple and rigid, a typical layout below especially if powering the controller via POE:
GATEWAY
vv
SWITCH <--> Controller
vv
AP OR USERS
The controller can attach directly to a LAN port of the Gateway (router) or a switch port with access to the management VLAN.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 1214
Replies: 14
Voters 0
No one has voted for it yet.