NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Orbi aggressive DHCP?
My Orbi router has been assigned a network IP adderess and attached to a 12 port switch to provide its internet access though our provider. It and its 5 satellites have been inplace for months withou...
AllanA wrote:Anything attached to that 5 port switch receives a 10.50.1.x address which is not compliant with the 192.168.1.x IP scheme used on the local network.
As assumed, you are operating two different networks, with two different subnetworks.
A. The network from your ISP router, with the five port switch, and the connection to the Orbi Pro router WAN/Internet interface, and the 10.50.1.x subnet.
B. The network served by the Orbi Pro with its wireless and its LAN ports with the Orbi Pro default LAN subnet on 192.168.1.0/24.
This makes clear why the devices on the "A" network can't reach the "B" network, because of the Orbi Router does default to operate as a router, does NAT, and has a by default closed firewall for WAN/Internet->LAN.
You need to run only one internal network. To achieve this goal, you have two to options:
- Either let the ISP router do it's routing/NAT/firewall/whatever job and re-configure the Orbi Pro as a pure Wireless Access Point system - so the only DHCP server on your network is the ISP router, or
- If possible re-configure the ISP router to pure bridging mode (one might hope there will be a public IP address available then - you might want to talk to your ISP), continue to operate the Orbi Router in router mode with the complete feature set, and only connect one cable from the ISP port to the Orbi WAN/Internet interface, while all additional switches are connected only to the Orbi Pro LAN port(s), ideally on the router.
Afraid, not a Netgear or Orbi Pro issue after all....
The Orbi is connected to a 5 port switch with a static IP address (192.168.1.31) to maintain its connection to the ISP provided router.
DHCP is on assigning 10.50.1.x addresses to Wifi clients 24/7 and some wifi connected mini-computers & printers. By distributeable IP, I mean DHCP addresses that are defined to be given out on request.
Anything attached to that 5 port switch receives a 10.50.1.x address which is not compliant with the 192.168.1.x IP scheme used on the local network.
(I inherited the IP scheme and its a bit too far down the path to make an all out change now)
AllanA wrote:Anything attached to that 5 port switch receives a 10.50.1.x address which is not compliant with the 192.168.1.x IP scheme used on the local network.
As assumed, you are operating two different networks, with two different subnetworks.
A. The network from your ISP router, with the five port switch, and the connection to the Orbi Pro router WAN/Internet interface, and the 10.50.1.x subnet.
B. The network served by the Orbi Pro with its wireless and its LAN ports with the Orbi Pro default LAN subnet on 192.168.1.0/24.
This makes clear why the devices on the "A" network can't reach the "B" network, because of the Orbi Router does default to operate as a router, does NAT, and has a by default closed firewall for WAN/Internet->LAN.
You need to run only one internal network. To achieve this goal, you have two to options:
- Either let the ISP router do it's routing/NAT/firewall/whatever job and re-configure the Orbi Pro as a pure Wireless Access Point system - so the only DHCP server on your network is the ISP router, or
- If possible re-configure the ISP router to pure bridging mode (one might hope there will be a public IP address available then - you might want to talk to your ISP), continue to operate the Orbi Router in router mode with the complete feature set, and only connect one cable from the ISP port to the Orbi WAN/Internet interface, while all additional switches are connected only to the Orbi Pro LAN port(s), ideally on the router.
Afraid, not a Netgear or Orbi Pro issue after all....
Thanks for the logic check. My gut told me the same but I thought it better to get a second opinion. I'm relieved to know its not the Orbi. When I asked (?) errant DHCP was the only thing, no matter how unlikely, I could figure.
Thanks for your help
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
