VLANs and NAT

[Hyper-W]

I did a search but was unable to come up with a concrete solution.

I have two VLANs of which one contains my Untangle box. I am unable to get past the untangle box from the other VLAN.

I believe this is a NAT issue but I am not certain.

Background:
Network topology is attached.

My Untangle box does our NAT Routing and has a public address on the external interface.
The internal interface has the ip address 192.168.200.253(/24).

My L3 Switch (Nortel ERS 4500) has a routing interface with IP address 192.168.200.254 on VLAN 200 and 192.168.202.1 on VLAN 202.

All of my network devices look to the ERS as their first hop router (default gateway). The ERS has a default route built pointing to Untangle (192.168.200.253).

All traffic to Untangle is untagged and on VLAN 200.

Untangle has a route built to access 192.168.202.0/24 through 192.168.200.254.

Untangle's first hop/default gateway is my WAN Router (208.X.35.153).

Behavior:

All traffic on VLAN 200 works like a champion.

From VLAN 202, I can ping Untangle's internal interface (192.168.200.253) and external interface (208.X.35.154).

I cannot ping the WAN router (208.X.35.153) from VLAN 202.

My thoughts:

I know from my research that Untangle does not handle VLANs. All traffic to Untangle is untagged. From VLAN 202, I can talk to Untangle directly (responds to ping, http, etc.) but I cannot get 'beyond' Untangle. I believe I am missing something with my NAT settings on Untangle but it could also be that what I am doing is impossible. While I'm fairly decent with IP and static routing, NAT is far from my specialty.

I would really appreciate any help.

[dmorris]

I would try changing the netmask to /16 on the untangle internal interface.
/24 does not contain all of your networks.

If that does not work I would add an alias on the internal interface of 192.168.202.2/24

welcome to the forums!

[Hyper-W]

I would try changing the netmask to /16 on the untangle internal interface.
/24 does not contain all of your networks.

If that does not work I would add an alias on the internal interface of 192.168.202.2/24

welcome to the forums!

Thanks, I'll give that a shot after-hours and post back with an update.