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

    Pfsense LAN connectivity issues

    Scheduled Pinned Locked Moved Virtualization
    6 Posts 3 Posters 1.0k 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.
    • K
      kjzero
      last edited by

      Hello,

      I have pfsense installed on a Xen hypervisor with two NICs. On pfsense LAN network, from a client, I can ping pfsense LAN IP, pfsense WAN IP, Gateway IP, 8.8.8.8, and www.google.com.

      I can view pfsense's web interface on both WAN/LAN IPs from the client inside the LAN.

      I cannot bring up any other web pages.

      I am right now allowing all traffic through from both the LAN and WAN.

      I do not know what is causing this issue

      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        Blocks upstream, like a cache or something else?

        I am right now allowing all traffic through from both the LAN and WAN.

        Sounds scary to me.  You normally don't let ANYTHING inbound on WAN except port forwards, for example.

        Post your network details for WAN, LAN, and the firewall rules for both.  Remove or obfuscate any public IP references such as your WAN IP.

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

          The WAN interface is not facing the internet. It is splitting my internal network in two right now.

          Interface.PNG_thumb
          Interface.PNG
          LAN.PNG
          LAN.PNG_thumb
          WAN.PNG_thumb
          WAN.PNG

          1 Reply Last reply Reply Quote 0
          • KOMK
            KOM
            last edited by

            Get rid of that Bogon rule on LAN.  LAN is almost always a private network, so blocking them is counterproductive.  Also get rid of that Allow Any rule on WAN.  The port forwards to your Wordpress box are fine.

            You should also be aware that since your WAN is also private network space, the Block Bogons rule is going to interfere with anything trying to reach your WP server via port forward.

            1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              Might be this:

              https://forum.pfsense.org/index.php?topic=88467.msg512128#msg512128

              An unfortunate but necessary step to using PV NICs on Xen/XenServer.

              Alternately you can use hw.xen.disable_pv_nics=1 in /boot/loader.conf.local and reassign your interfaces to the reX NICs.

              (Moving thread to Virtualization)

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

                Derelict your Xen NIC step seems to have fixed the issue. It looks like it is working perfectly now, thank you.

                Thank you as well KOM for you assistance.

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