Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13
  1. #11
    Untangle Ninja sky-knight's Avatar
    Join Date
    Apr 2008
    Location
    Phoenix, AZ
    Posts
    26,024

    Default

    RSears issue was just resolved on the phone. He's using an IPSec tunnel, not an L2TP tunnel.

    He needed the filter rule to indicate source address, instead of source interface. There is no source interface for IPSec, so changing tactics to using source address solved the problem.

    So, possible enhancement request / bugs?

    Why isn't there a virtual interface for source interface flagging for IPSec?
    Why isn't IPSec access to the Untangle Internal interface primary IP address on the encrypted administration port allowed by default?
    Rob Sandling, BS:SWE, MCP
    NexgenAppliances.com
    Phone: 866-794-8879 x201
    Email: support@nexgenappliances.com

  2. #12
    Untanglit
    Join Date
    Feb 2015
    Posts
    28

    Default

    I did the same thing srears did and I'm still unable to connect to the untangle box over the vpn. Attached is a screenshot.

    3-3-2015 1-34-18 AM.jpg

  3. #13
    Untangle Junkie dmorris's Avatar
    Join Date
    Nov 2006
    Location
    San Carlos, CA
    Posts
    17,747

    Default

    Thats a forward filter rule not an input filter rules.

    You need an input filter rules as those control access to the local processes.
    Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
    If you need Untangle support please call or email support@untangle.com

Page 2 of 2 FirstFirst 12

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