Results 1 to 2 of 2
  1. #1
    Newbie
    Join Date
    Jul 2010
    Posts
    5

    Default Routing Issues Multiple Subnets Behind Single Untangle Interface

    I have a ProCurve 2824 with 3 VLans that need access to the internet.

    VLan 200 is the server network (10.10.1.0/24) where the Untangle internal interface sits at .254. The ProCurve gateway for the server VLAN is at .253. This network routes properly to all subnets with no issues with all hosts on the network using the procurve as their gateway.

    VLan 400 is the PC network (192.168.0.0/24). Hosts from this network cannot get outside of the Untangle. They can ping the untangle, they can access the web gui of the untangle, but cannot get outside.

    Packet traces show my pings to google from the pc network hit the untangle interface (proof is wireshark on the Untangle box logs the packet) and I'm assuming they are dropped because there is no attempt from Untangle to forward the request through it's external interface.

    I can ping both the internal and external interfaces of the Untangle from the PC network, but can get no further.

    My routes are setup correctly so it seems like a NATing problem. I have a nat rule that says 0.0.0.0/0 uses a specific static ip. I've also tried this with specific subnet entries and the results are the same. At this point I suspect this may be a software bug. I'm hoping you can prove me wrong.

  2. #2
    Untangler
    Join Date
    Dec 2010
    Location
    Wisconsin Dells, WI
    Posts
    86

    Default

    On your Internal Interface, add a NAT policy for 192.168.0.0/24. Leave the source address auto and also leave the default 0.0.0.0/0 rule there. If you already created a static route for the subnet you should now be set.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

SEO by vBSEO 3.6.0 PL2