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

    Hugh packet loss via pfsense

    Scheduled Pinned Locked Moved General pfSense Questions
    17 Posts 7 Posters 5.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.
    • chpalmerC Offline
      chpalmer
      last edited by

      We need a whole lot more information to be able to even try and guess.  But guessing- you could have a bad interface, bad cable, bad hair day, ect.

      Are you seeing any errors on your interface from the dashboard widget?

      Triggering snowflakes one by one..
      Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

      1 Reply Last reply Reply Quote 0
      • A Offline
        arun_cdm
        last edited by

        Thanks for your support  :),

        I too have changed the NIC's and new cables,  :(

        Ref the screen shot.

        pfsense_drop.JPG
        pfsense_drop.JPG_thumb

        1 Reply Last reply Reply Quote 0
        • DerelictD Offline
          Derelict LAYER 8 Netgate
          last edited by

          Status > Interfaces

          in/out errors?

          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
          • A Offline
            arun_cdm
            last edited by

            Hi,
            in/out errors : 0/0

            Ref. Screen shot

            pfsense_drop_intf_status.JPG
            pfsense_drop_intf_status.JPG_thumb

            1 Reply Last reply Reply Quote 0
            • DerelictD Offline
              Derelict LAYER 8 Netgate
              last edited by

              Diagnostics > Packet Capture

              Interface: WAN
              Protocol: ICMP
              Count: 100

              Download the pcap and attach after it stops (Should only run for about a minute.)

              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
              • DerelictD Offline
                Derelict LAYER 8 Netgate
                last edited by

                What do you get if you ssh into pfSense and:

                ping -i .25 -c 100 122.165.128.1

                FWIW I get about 30% packet loss there too:

                –- 122.165.128.1 ping statistics ---
                100 packets transmitted, 70 packets received, 30.0% packet loss
                round-trip min/avg/max/stddev = 224.001/234.627/272.539/8.829 ms

                Looks like you're in a pretty dark corner of the internet.

                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
                • A Offline
                  arun_cdm
                  last edited by

                  Thanks for ur support, i'll check and update

                  1 Reply Last reply Reply Quote 0
                  • M Offline
                    marvosa
                    last edited by

                    Same results here.  I'm currently seeing 34-42% packet loss from your default gateway (122.165.128.1).

                    Use PingPlotter to gather evidence on exactly where the packet loss is and take it to your ISP (Assuming the issue is downstream).

                    You also are using DSL in India, which may or may not be an issue in and of itself, but I would switch broadband technologies if possible.

                    1 Reply Last reply Reply Quote 0
                    • DerelictD Offline
                      Derelict LAYER 8 Netgate
                      last edited by

                      if i directly connect my ADSL router to Switch, there is no packet loss.

                      Something tells me this is unreliable. Frustrating.

                      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
                      • A Offline
                        arun_cdm
                        last edited by

                        Thank U  all for giving support  :), i'll use the pinplotter.

                        If i connect any node directly to ISP' router and trigger continuous PING, there is no loss in packets.
                        That's what i tried to convey earlier.

                        Earlier, I raised issue to ISP provider, they came and checked the physical line, then hard reset the ASDL router and tried to ping, result= success without firewall (pfSense). couple of minutes later after connecting pfSense tried to ping, result=loss (partial).  :o

                        Now, i'll use this PinPlotter in both cases with/without pfSense and get back.

                        1 Reply Last reply Reply Quote 0
                        • DerelictD Offline
                          Derelict LAYER 8 Netgate
                          last edited by

                          Your internet sucks, friend. It's not pfSense.

                          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
                          • chpalmerC Offline
                            chpalmer
                            last edited by

                            2 hops away from your gateway-

                            Ping statistics for 182.79.220.190:
                                Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
                            Approximate round trip times in milli-seconds:
                                Minimum = 243ms, Maximum = 260ms, Average = 245ms
                            
                            

                            your gateway-

                            Ping statistics for 122.165.128.1:
                                Packets: Sent = 100, Received = 61, Lost = 39 (39% loss),
                            Approximate round trip times in milli-seconds:
                                Minimum = 244ms, Maximum = 375ms, Average = 249ms
                            
                            

                            Your gateway router is hammered!  Last time I saw pings like that the site had been struck by lightning.

                            Triggering snowflakes one by one..
                            Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

                            1 Reply Last reply Reply Quote 0
                            • M Offline
                              marvosa
                              last edited by

                              Thank U  all for giving support  :), i'll use the pinplotter.

                              If i connect any node directly to ISP' router and trigger continuous PING, there is no loss in packets.
                              That's what i tried to convey earlier.

                              Earlier, I raised issue to ISP provider, they came and checked the physical line, then hard reset the ASDL router and tried to ping, result= success without firewall (pfSense). couple of minutes later after connecting pfSense tried to ping, result=loss (partial).  :o

                              Now, i'll use this PinPlotter in both cases with/without pfSense and get back.

                              My guess is when the ASDL router is in use, it's using a different route (or gateway) to the internet, which is why everything appears fine when using their router.  Gather your evidence via PingPlotter and go from there.

                              1 Reply Last reply Reply Quote 0
                              • M Offline
                                mer
                                last edited by

                                Something connected to the router, do you have a switch in between the router and the client?  Client doing DHCP so it's getting address/gateway/DNS from the router or beyond?  If so, and the pfSense box is also doing DHCP you should be able to compare those values.  Don't forget to check link state;  make sure everything matches on Speed, Duplex and MTU.

                                1 Reply Last reply Reply Quote 0
                                • ? This user is from outside of this forum
                                  Guest
                                  last edited by

                                  Note: ADSL Router in Bridge Mode.
                                  I've tried Netgear DGN2200 ADSL2+ router too.

                                  Sometimes peoples are meaning that there ISP router is in the so called "bridge mode" and it is
                                  working likes an ordinary and pure modem and then also really often some other peoples are meaning
                                  they was bridging the WAN port of their pfSense box to that ISP router and also really then the goal or
                                  "benefit" is;

                                  • packet loss
                                  • packet drops
                                  • port flapping
                                  • unstable connection

                                  But all in all if the pfSense box is doing actively DHCP and the ISP router in front of this pfSense is also
                                  doing DHCP it could produce also this behaviors or creating this issues. And this is not rarely seen.

                                  1 Reply Last reply Reply Quote 0
                                  • S Offline
                                    sos
                                    last edited by

                                    My question: who is "Hugh", and why is he worried about packet loss via pfSense?

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