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

    Really weird case

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    4 Posts 1 Posters 1.1k 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
      maverick_slo
      last edited by

      Hi all!

      I use 2 pfsense boxes.
      1 at home other at work.

      I upgraded box at home to 2.4 (latest todays snap).
      At work it is: 2.3.2-RELEASE-p1 (amd64)

      Now to the problem.
      I can ping from 2.3.2 box to home box
      I can traceroute from 2.3.2 box to home box
      I CANt connect to any port from 2.3.2 box to 2.4 (mail on port 25 does not work, also 80 or 443 dont work)

      When I had 2.3.3 at home it worked flawlessly…
      Also IPv6 works even now without any problems.
      IPsec between boxes works as well.

      Ran wireshark and saw a tons of tcp retransmissions...
      Funny thing is, that if I access website behind 2.4 box from anywhere else it works OK. Also I can receive mail from everywhere BUT 2.3.2 box (mailserver behind it).

      Any idea what happened?

      Thanks!

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

        I forgot to mention that I have 2 WANS..

        1 DHCP
        1 PPPoE

        When I shut down PPPoE (on this link is also IPSEC) it starts to work…

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

          Huh found the problem…

          When traffic comes to my HTTP server is OK (DHCP WAN), but HTTP server sends it back via PPPoE WAN because of ipsec connection.

          But why this worked in 2.3.3 version?

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

            Yeah confirmed…
            Disabled Ipsec, rebooted only one box and all works as expected...

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