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

    Strange routing problem

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 1 Posters 1.7k 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
      marton
      last edited by

      Hello.
      We have 2 pfsense firewalls running in two houses. Each of the houses has their own WAN connection, but we have a direct gigabit connection between the houses. Everything has worked perfectly until my firewall rebooted unexpectedly yesterday. After that it stopped working, "one way". Everything works from House A to House B but not the other way. This is a complex issue so it is not easy to explain.
      Please remember that this has worked fine the last 2-3 months.
      NOTE1 Here is a interesting note. If I ping 192.168.2.50 from my network, it replies. If I ping 192.168.3.50 from House B network, I get no replies. But if I ping 2.50 from 3.50, then ping works both ways. Strange or what?
      NOTE2 If I ping from House B to House A. We get no reply. We can see the connection states in the diagnose->states on House B's pfsense, but nothing shows in the Diagose->states on House A's pfsense.

      192.168.3.0/24 is House A network
      192.168.2.0/24 is House B network

      Config:

      HouseA:
      LAN: 192.168.3.1/24
      WAN: DHCP address
      HtoH: 172.16.0.3/24
      Static route: HtoH 192.168.2.0/24 172.16.0.2
      FWrules-LAN:

      • LAN net * * * *
        FWrules-HtoH:
      • 192.168.2.0/24 * 172.16.0.3 * *
      • 192.168.2.0/24 * LAN net * *
        FW-rules-WAN: Not nessesary to list here

      HouseB:
      LAN: 192.168.2.1/24
      WAN: DHCP address
      HtoH: 172.16.0.2/24
      Static route: HtoH 192.168.3.0/24 172.16.0.3
      FWrules-LAN:

      • LAN net * * * *
        FWrules-HtoH:
      • 192.168.3.0/24 * 172.16.0.2 * *
      • 192.168.3.0/24 * LAN net * *
        FW-rules-WAN: Not nessesary to list here

      We now run latest 1.2 RC3 on both servers

      1 Reply Last reply Reply Quote 0
      • M
        marton
        last edited by

        This issue is now solved..
        It was the Captive portal that was enbled on the interface..  ;D

        /MartOn

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