Synology RT6600AX with mesh (switch from Bridge to Router mode)
After a suspected attack event , purchased a Purple and after reading reviews two Synology RT6600AX for my network. The second synology router operates in bridge mode as a Wifi Mesh Extender and backhauls over the LAN back to the Synology router operating in router mode. The Synology router features are really robust and can do some things that I want to keep, I wanted to keep those features so I wound up installing Purple in Bridge mode.
Simplistically network flows like this
ONT -> Purple (Bridge ) -> Synology Router -> Devices
I realize now that Purple in Router mode would offer more protection and would like to switch from Purple in Bridge mode to router mode
I am hesitant to just try to hack something together since the config took a long time to get where its at now, if I break the network.
I want to avoid a situation where devices can't be routed out due to purple router and synology router "not agreeing on network table".
I would assume that purple operating in router mode would work over my existing network if: Purple was not assigning DHCP addresses , and somehow settings allowed NAT to either work twice , or purple just allowed the router behind it to perform the NAT.
I am looking for Purple router mode configuration advice.
Thank you for reading and giving your input
-
One synology is in router mode, one synology is an access point for WiFi mesh and it backhauls data from the AP to the synology router to then pass traffic to the wan.
What I mean by multiple network tables , is in the past when I’ve had routers behind routers: they can’t find clients at the different layers because they each have different IP addresses in their own respective routing tables.
What I’m after is aside from turning off DHCP on the firewalla router , what else in Firewalla would I need to change for both the Firewalla in router mode and the existing router to allow traffic to flow in and out through the multiple layers of routers.
Please sign in to leave a comment.
Comments
2 comments