Multiple Internal Network Setup

Multiple Internal Network Setup

I would like to configure an Untangle router to handle 3 different internal networks.
I have read http://wiki.untangle.com/index.php/How_Do_I... and I think I have the general idea down.

First off, I have a dual core Xeon with 6GB of memory and 4 onboard Ethernet interfaces. (Asus P5M2-E/4L) I plan on using the 64bit ISO for installation.

I would like the following…

Internal network A (192.168.76.0) – Office network with desktops and servers, DNS & DHCP provided by my internal Windows servers
Internal network B (192.168.81.0) – Public WiFi, Ideally… DHCP provided by Untangle and DNS by the Windows servers on network A
Internal network C (192.168.117.0) – DMZ for web servers that will be available to clients on A, B and the Internet. I suppose I don’t really need DHCP on the DMZ network if that makes a difference.

Network_Diag.png

I currently have two separate Untangle installations (one for internal and one for WiFi) but would like to consolidate to a single server for two reasons.

One… QOS, I need my VOIP traffic prioritized over all other traffic.
Two… At some point in the future, I may want to use the web caching application and don’t want to pay for it twice.

I am thinking that I will use the “Internal” interface for network B, the “DMZ” interface for network C and the “ethX” interface for network A. Is that a sensible plan?

I am not quite sure about the DHCP & DNS. Is it possible to enable Untangle’s DHCP on only a particular interface, or is packet filtering the recommended way to control it?

Can I configure the DHCP clients on B & C to obtain the address of my DNS servers on A via Untangle’s DHCP?

Attached Images

• Network_Diag.png (51.5 KB)