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

    100% Packet Loss Need Help

    Routing and Multi WAN
    2
    8
    361
    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.
    • S
      StormGate
      last edited by

      Hello, I am trying to configure a second WAN interface, not for failover but actually to move the network over too but before I do I wanted to make it actually functioned before disconnecting equipment. So currently have WAN2 interface configured and active. I configured WAN1 with the static information provided by the ISP, and i get 100% packet loss . On the ARP table I noticed 2 entries to WAN1, the one ARP entry for the static IP is complete fulfilled with the hosts name and the mac address however the entry with the gateway IP is showing incomplete. On the logs dpinger is a continuous error 64. Now sure what kind of troubleshooting I have to further see where the issue is.

      Any help would be greatly appreciated.

      S 1 Reply Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @StormGate
        last edited by

        @StormGate A common pitfall is pfSense defaults new interfaces to a /32 mask, is your mask correct?

        This is two ISPs right?

        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
        Upvote ๐Ÿ‘ helpful posts!

        S 1 Reply Last reply Reply Quote 0
        • S
          StormGate @SteveITS
          last edited by StormGate

          @SteveITS Correct netmask is 29 and 2 isp's. We are going to try with a laptop today to see if it works.

          S 1 Reply Last reply Reply Quote 0
          • S
            SteveITS Galactic Empire @StormGate
            last edited by

            @StormGate

            Yes direct with a laptop is a good idea. Did you find https://docs.netgate.com/pfsense/en/latest/troubleshooting/gateway-errors.html#sendto-error-64 ?

            Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
            When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
            Upvote ๐Ÿ‘ helpful posts!

            S 1 Reply Last reply Reply Quote 0
            • S
              StormGate @SteveITS
              last edited by

              @SteveITS Ok so the laptop was successful, I did see that error thank you. So when setting up the laptop I used Subnet 255.255.252.0 for the test but in PFsense I used the netmask 255.255.255.248 or /29 for the static IP. Not sure if I am dealing with a hardware issue on PFSense or its software.

              S 1 Reply Last reply Reply Quote 0
              • S
                SteveITS Galactic Empire @StormGate
                last edited by

                @StormGate A wider subnet should be OK, a narrower subnet can essentially be saying to ignore the gateway if the gateway is outside the narrower subnet.

                Unlikely to be a software issue unless it's a NIC driver issue but if the NIC is detected I'd think it would be OK. Unless maybe if it's Realtek, people post about problems with Realtek on FreeBSD a lot, or used to.

                In Diagnostics/Ping can you choose WAN2 and ping the gateway IP?

                Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                Upvote ๐Ÿ‘ helpful posts!

                S 1 Reply Last reply Reply Quote 0
                • S
                  StormGate @SteveITS
                  last edited by

                  @SteveITS I just tried and yes ping was successful to that new gateway. Hmm

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    StormGate @StormGate
                    last edited by StormGate

                    @SteveITS I think this 6100 is faulty, this WAN port initially dropped the network in its first year and had to configure WAN2 combo, assumed it was a Spectrum issue but now believe after not able to get it to work on another system, its a faulty interface.

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