Results 1 to 3 of 3
  1. #1
    Newbie
    Join Date
    Nov 2011
    Posts
    4

    Default Cant see internal network

    Hi,
    I'm pretty new to routing and VPN so I appologise if this is a stupid question. I am having trouble seeing machines on my internal network when connected to my VPN. Here is my setup...

    My UT box is sitting between my modem and a switch. It is in router mode. The external IP is dynamic, and the internal IP is static (192.168.2.1). My switch has the following settings:

    External IP (Static) - 192.168.2.2
    Subnet - 255.255.255.0
    Default Gateway - 192.168.2.1
    DNS - 192.168.2.1
    -----
    Internal IP (Static) - 192.168.3.1
    Subnet - 255.255.255.0
    -----
    DHCP Server = Enabled
    Address Range: 192.168.3.100 - 192.168.3.149


    My OpenVPN settings are:
    Status - VPN Server
    Client Address Pool IP - 172.16.16.0/255.255.255.0
    Export DNS = True
    Server Port = 1194
    DNS Override = False
    Exported Networks/Hosts: Internal Network (192.168.2.1/255.255.255.0)

    Problem Description:
    I can successfully connect to the VPN, and I am able to ping the Internal NIC on my UT box. I can also successfully ping the external IP on my switch (192.168.2.2). I can NOT ping the internal IP on my switch though (192.168.3.1) or anything past that. I have a feeling that I need to add a static route somewhere, but I'm not sure where. I am also not able to ping from inside the network to a machine on the VPN.

    I hope I gave enough information. Any help or pointers would be great.
    I have also checked and made sure that there are no firewalls blocking any traffic.

    Thanks

  2. #2
    some dude hlarsen's Avatar
    Join Date
    Jul 2010
    Location
    sfba
    Posts
    1,318

    Default

    you should get rid of the double NAT if possible - does Untangle know that .3.0/24 is behind .2.2?
    Attention: Support on the Untangle Forums is provided by volunteers and community members.
    If you need official Untangle support please call or email support@untangle.com.

  3. #3
    Newbie
    Join Date
    Nov 2011
    Posts
    4

    Default

    Oh I didn't realize I was double NAT'ing. What would you suggest?
    When I first read your post the untangle box did not know about the 3.0/24 network was behind .2.2. I tried adding a static route on the untangle box:
    Destination: 192.168.3.0/24
    Gateway: 192.168.2.2
    And I still have issues. Did I set up the route wrong?

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