Connect Netgear Orbi to TZ350W as separate network
beachbum
Newbie ✭
So a business partner - our main vendor - requires that we purchase and install a showroom information / display system that includes a Netgear Orbi Pro router and satellite.
Their tech document contains errors and conflicting information: they say that their system creates an entirely new WiFi network but it doesn't. It's clear from the details and from the way that their installer tried to set it up that it simply extends our existing WiFi. Their materials aren't even clear on the distinction between a router and an access point but it's clear that they want the Orbi set up as access points and their demand is that we change the Sonciwall firewall to accommodate this. They say they've never run into a problem before.
We have an existing TZ350W that runs our wired office LAN, our credit card terminal and our office WiFi - which is totally separate from our wired LAN.
We want to setup the Netgear Orbi as a totally separate system, thought process being that it will be in router mode and distribute IP addresses to the retail showroom network and not on either our wired LAN or our Sonicwall provided WiFi. Unfortunately we no longer have anyone in-house fully qualified to do this but what we were thinking is to connect the Orbi router to X2 on the Sonicwall set up in the DMZ zone.
Assuming that this is the right way to do what needs to be done what information needs to be in the Orbi configuration page to make it function as a completely separate network getting its internet connection through the Sonicwall and our Comcast business gateway? Or is there some better way to do this that we haven't thought of?
Thanks in advance for any assistance and sorry for the lengthy post but it seemed better to give as much detail up front as possible.
Answers
You're on the right track. Utilize a free, non-LAN (DMZ) zone interface for the 'Orbi'.
Connect the Orbi WAN interface to the configured Sonicwall interface. Make sure to setup a DHCP reservation for it.
(Skip the 'Add Dynamic' section in the above KB, Add a static for the MAC Orbi WAN interface MAC address.)
Then test the devices connected through the Orbi.
Or just tell them you won't do it unless they provide additional information and security details. It's an unknown device to your company, why should you trust it?
It's also an absolute pile of stinking garbage. At least 3 times during the process of configuring it to our liking I've experienced it completely refusing to accept the known sign-in credentials each time requiring a total factory reset despite the recover lost password feature built-in to it. Also, immediately after a factory reset showing me a LAN interface configured on 10.x.x.x. when the factory default is 192.168.1.1 and I've never inputted any 10. info into it ever.
I (briefly) had it working the way I thought it should work as far as the Sonicwall side of things but repeated losses of access to the management side of the Netgear means that, brand-new or not, it's heading for a landfill and I'm ordering something better.