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

    Network interface stops working

    General pfSense Questions
    2
    4
    744
    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.
    • C
      CM350
      last edited by

      Hi All,

      We are on pfsense 2.3.4-RELEASE (amd64).

      Virtualized trough KVM (Proxmox v5.1).

      We changed our firewall setup from 5 firewall(s) to only 2 since this weekend  ;).

      Our main firewall now has 8 network interfaces.

      This morning round 11:00 AM GMT+1 1 of our interfaces stopped working. Could not ping to devices connected on that vlan. Devices could not ping firewall.

      Disabled the interface, applied changes, enabled the interface again, applied changes and after that, it started working again.

      We have this version running with a lot of customers and it never failed. So since we did a configuration-change I suppose we made a mistake. :)

      Nothing to see in system log or firewall log.

      Can you help us with this for future outage(s)? (We are hosting a few servers for our customers)

      1 Reply Last reply Reply Quote 0
      • C
        CM350
        last edited by

        up?

        Somebody?

        1 Reply Last reply Reply Quote 0
        • GertjanG
          Gertjan
          last edited by

          @CM350:

          We are on pfsense 2.3.4-RELEASE (amd64).

          Not related, but : Old version.

          @CM350:

          Virtualized trough KVM (Proxmox v5.1).

          So : probably wrong forum section. All your interface are 'virtual' - this might be an important factor.

          @CM350:

          We changed our firewall setup ….
          Our main firewall now has 8 network interfaces.
          This morning round 11:00 AM GMT+1 1 of our interfaces stopped working. Could not ping to devices connected on that vlan. Devices could not ping firewall.
          Disabled the interface, applied changes, enabled the interface again, applied changes and after that, it started working again.
          We have this version running with a lot of customers and it never failed. So since we did a configuration-change I suppose we made a mistake. :)

          No way to go back ?
          What I mean : when x (lower then 8) works well on your virtual host (VM) and 8 gives problems now, I exclude (I did not test)  pfSense, which is known to handle far more the 8 LAN's, VLAN, virtual LAN's using a VM.

          Check also if there are enough resources available (CPU power) to handle all these vitual NIC's.

          No "help me" PM's please. Use the forum, the community will thank you.
          Edit : and where are the logs ??

          1 Reply Last reply Reply Quote 0
          • C
            CM350
            last edited by

            We had the same problem with our smaller pfsense (2nics) firewall (on the same server).

            So we tried with virtio instead of e1000 and now everything looks running fine.

            Has nothing todo with pfsense though :).

            Just wanted to update this thread instead of someone has this problem too.

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