I'm working on setting up an untangle box to act as our router, firewall, and content filter. This server will sit at the edge of our network. The inside interface of the server will have an IP of 10.9.1.2 255.255.255.0, and it will connect to a core switch (at 10.9.1.4 255.255.255.0) which all of our organization's traffic will pass through to get to the Internet. This switch has dozens of VLANs on it, and all of our locations use several more. Some of these VLANs are:
10.60.20.0/24
10.60.30.0/24
10.125.0.0/16
10.130.0.0/20
And so on. Depending on what the VLAN is used for depends on how large it is. However, all VLANs are within the 10.0.0.0 network, and they will all pass through the core switch to get to the Untangle server.
I've read in the FAQ that Untangle does not support VLANs, and the suggested way to get everything working would be to create static routes for each VLAN pointing at the switch, and then create aliases as well.
My question though - with our network setup, would it be possible to just create a static route of:
Network 10.0.0.0 Mask 255.0.0.0 Gateway 10.9.1.4
And then an alias of 10.0.0.0/8 in untangle to get all the traffic flowing? Or will I have to create a route and alias for each individual VLAN?
10.60.20.0/24
10.60.30.0/24
10.125.0.0/16
10.130.0.0/20
And so on. Depending on what the VLAN is used for depends on how large it is. However, all VLANs are within the 10.0.0.0 network, and they will all pass through the core switch to get to the Untangle server.
I've read in the FAQ that Untangle does not support VLANs, and the suggested way to get everything working would be to create static routes for each VLAN pointing at the switch, and then create aliases as well.
My question though - with our network setup, would it be possible to just create a static route of:
Network 10.0.0.0 Mask 255.0.0.0 Gateway 10.9.1.4
And then an alias of 10.0.0.0/8 in untangle to get all the traffic flowing? Or will I have to create a route and alias for each individual VLAN?