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

Strangest problem - unstable firewall

Scheduled Pinned Locked Moved General pfSense Questions
3 Posts 2 Posters 772 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.
  • Q
    Q22
    last edited by Sep 29, 2016, 12:36 PM

    Hello there,

    Recently, I'm having to deal with a very strange problem. At my workplace, we've changed our WAN link. Same IP, same ISP. However, after that change, many machines here are having trouble to communicate with the firewall. The internal network is answering to ping requests just fine.

    In these machines, if the IP is changed, be it via DHCP to static IP, or via one static IP address to another, or any other way, it tends to work. The exact method varies by machine. The problem is that after some time these machines stop communicating with the firewall again, and we have to repeat this process. We can even put the machine to the IP address that was previously being used to make it work.

    We also have 2 WAN links, and there is a rule that sets the default route, which was also changed when the new link was set up, since it was faster.

    Anyone have any clue of what this could be?

    1 Reply Last reply Reply Quote 0
    • D
      Derelict LAYER 8 Netgate
      last edited by Sep 29, 2016, 5:34 PM

      The problem is that after some time these machines stop communicating with the firewall again

      This could be 1000 different things. Need to do some basic connectivity troubleshooting and see exactly what is failing.

      https://doc.pfsense.org/index.php/Connectivity_Troubleshooting

      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
      • Q
        Q22
        last edited by Oct 3, 2016, 12:50 PM

        Here are some more characteristics rrom this problem. The WAN connectivity doesn't actually stop. What is actually stopping is the e-mail manager program, such as Thunderbird and Outlook, and only for certain machines. Thunderbird, for example, stops at the SMTP connectivity process. Whenever the e-mail managers aren't working, the firewall machine won't answer to ping requests. The Internet  is always fine though.

        Reconnecting the network cable fixes the problem (ping and e-mail managers) for some time, but then it comes back. Changing the IP does the same thing.

        Any clues?

        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