Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Access to PFSense

    Scheduled Pinned Locked Moved General pfSense Questions
    3 Posts 2 Posters 1.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mirage-42
      last edited by

      Hi,

      I have this setup :

      LAN1–[VPNrouter1]~~~~[VPNrouter2]–PFBox--LAN2
      The FBox is connected to the LAN2.

      From LAN2 I can access the PFBox without trouble.
      From LAN1 I can access the PFBox via SSH, but not with webconfigurator. My browser is connected, but not loading the page whenever I try HTTP or HTTPS.
      When trying logging in with HTTPS and hitting the HTTP address, the redirection works (I got the 301 HTTP code).

      
      wget pfsense
      --2013-03-05 15:43:52--  http://pfsense/
      Resolving pfsense (pfsense)... 192.168.1.1
      Connecting to pfsense (pfsense)|192.168.1.1|:80... connected.
      HTTP request sent, awaiting response... 301 Moved Permanently
      Location: https://pfsense:443/ [following]
      --2013-03-05 15:43:52--  https://pfsense:443/
      Connecting to pfsense (pfsense)|192.168.1.1|:443... connected.
      
      

      Firewall rules are all open.
      I just can't get it…

      Any help please ?

      1 Reply Last reply Reply Quote 0
      • K
        Klaws
        last edited by

        Is the firewall really "open"? Are there maybe any blocks enabled on the interface configuration pages?

        1 Reply Last reply Reply Quote 0
        • M
          mirage-42
          last edited by

          The first rule (except antilockout rule on LAN interface and block bogon networks) of every interface is :

          id   proto   source   port   destination   port   gateway   queue   schedule
                *           *             *         *                    *        *             none

          When I set up the HTTPS port on a different port, WebUI is still unavailable.
          nc -t -l 443 on the pfsense box and nc -t 192.168.1.1 443 on the LAN1 works in both ways.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.