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

Pfsense Multiple Layers

Scheduled Pinned Locked Moved General pfSense Questions
xenservermultiple pfsens
3 Posts 3 Posters 621 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.
  • J
    jmcdiarmid_uk
    last edited by Feb 15, 2019, 2:46 PM

    Hi all.

    I have been using pfsense for a number of years successfully and have now come up against a problem that I cant seem to find the answer to.

    I have 2 pfSense routers both of which are in a Xen Virtual Server

    The first has our external facing IP and is used to connect the multiple buildings across the site. It has an address range of 172.16.0.1 /24 which buildings connect to.

    The second router is for the main office and is connected via a virtual network within the Xen Server. It has a WAN address of 172.16.0.9 and LAN in the range of 192.168.9.1 /24

    I can access the internet on all the devices on the 192.168.9 network however I cant access the 172.16.0.1 router from this network to manage it.

    Can anyone please help? Thanks in advance!

    1 Reply Last reply Reply Quote 0
    • R
      Rico LAYER 8 Rebel Alliance
      last edited by Feb 15, 2019, 2:50 PM

      For management access at WAN with RFC1918 address you first need to uncheck
      Interfaces -> WAN
      Block private networks and loopback addresses
      and setup your Rules for the management ports under Firewall -> Rules -> WAN

      -Rico

      1 Reply Last reply Reply Quote 0
      • S
        stephenw10 Netgate Administrator
        last edited by Feb 15, 2019, 3:53 PM

        That should not apply in this situation as 172.16.0.1 is the internal IP of the outer firewall so, presumably, does not have a gateway and hence also wouldn't have those rules.
        It doesn't apply to the inner firewall as that is outbound traffic from a device on the 192.168.9.X subnet which is always allowed.

        I assume you are NATing the outbound traffic in the inner firewall, the default configuration?

        I would run a packet capture first on the WAN interface of the inner firewall. Filter by host IP 172.16.0.1 and try to access the outer firewall from a client on the 192.168.9.X subnet.

        If you see traffic there try the same thing on the outer firewall LAN interface.

        Either the outer firewall is blocking that traffic deliberately or it has some touting problem that means it cannot reply. For example perhaps that traffic is not being NAT'd for some reason so it has no route back to 192.168.9.X. The packet cap should show what's happening.

        Steve

        1 Reply Last reply Reply Quote 0
        3 out of 3
        • First post
          3/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          This community forum collects and processes your personal information.
          consent.not_received