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

Packet Loss and Latency/Jitter on PPPoE Interface.

Scheduled Pinned Locked Moved General pfSense Questions
30 Posts 3 Posters 11.5k 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
    marrold
    last edited by Aug 6, 2013, 3:59 PM

    No, Virgins modem provides a public IP via DHCP on my WAN1 interface. I dont have any of the jitter/packet loss issues with my Virgin Media connection.

    For the sake of testing, Ive setup another pfSense box on a slightly more modern CPU (And a different NIC) and Im still seeing a lot of jitter on the connection. The odd thing is, if I remove pfSense from the equation and just use the Technicolor, it's stable with no jitter.

    It looks as though its an issue with pfSense, or the combination of pfSense and my connection.

    Can you confirm your MTU for me?

    Cheers

    1 Reply Last reply Reply Quote 0
    • S
      senser
      last edited by Aug 6, 2013, 4:34 PM

      OT: Why don't you guys just copy your rrd-graph images? No need to take screenshots from them. :)

      We use the mighty pf, we cannot be fooled.

      1 Reply Last reply Reply Quote 0
      • M
        marrold
        last edited by Aug 6, 2013, 4:58 PM

        @senser:

        OT: Why don't you guys just copy your rrd-graph images? No need to take screenshots from them. :)

        I think I did it because it's not possible to copy graphs from smoke ping, thanks for pointing that out though.

        1 Reply Last reply Reply Quote 0
        • S
          stephenw10 Netgate Administrator
          last edited by Aug 6, 2013, 7:53 PM Aug 6, 2013, 7:49 PM

          My PPP settings are all default, I never had to do any tuning, so it's 1492.

          $ ifconfig pppoe1
          pppoe1: flags=88d1 <up,pointopoint,running,noarp,simplex,multicast>metric 0 mtu 1492
          	inet6 fe80::290:7fff:****:****%pppoe1 prefixlen 64 scopeid 0x13 
          	inet 81.152.***.*** --> 217.32.***.*** netmask 0xffffffff 
          	nd6 options=43<performnud,accept_rtadv></performnud,accept_rtadv></up,pointopoint,running,noarp,simplex,multicast>
          

          There's nothing to suggest that my connection wouldn't look the same as yours if I tested it externally. I am lucky enough to live very close to the exchange so my connection is close to optimal. Though with FTTC that shouldn't be such as issue as long as your green cabinet is relatively close.
          I would guess that pfSense does not prioritise ping response in anyway and perhaps the Technicolor router does. That doesn't explain why your Cable connection is so much better though.  :-\

          I note that in your original comparison graphs from smoke ping you are not comparing like with like. The pfSense graph is several days where as the Technicolor graph is 40mins. Do similar time spans still show disparity?

          @senser:

          OT: Why don't you guys just copy your rrd-graph images? No need to take screenshots from them. :)

          Good question. Didn't think of it I guess, too used to taking a screen shot to show settings etc.   ::)

          Steve

          1 Reply Last reply Reply Quote 0
          • M
            marrold
            last edited by Aug 9, 2013, 1:13 PM

            @stephenw10:

            I note that in your original comparison graphs from smoke ping you are not comparing like with like. The pfSense graph is several days where as the Technicolor graph is 40mins. Do similar time spans still show disparity?

            I only tried the Technicolor TG582 for about an hour, hence why its a smaller section. I appreciate its not a great comparison, but there is definitely something weird going on with PPPoE.

            I investigated the possibility that ICMP traffic may be being prioritized differently, but I ran some iperf UDP tests, and there is definitely packet loss going on.

            Thanks

            1 Reply Last reply Reply Quote 0
            • S
              stephenw10 Netgate Administrator
              last edited by Aug 9, 2013, 2:51 PM

              Hmm, not sure what to say about the packet loss.
              I'm running a smoke ping test against my FTTC connection from here: http://www.dslreports.com/smokeping. I'll report back when it starts giving results.

              Steve

              1 Reply Last reply Reply Quote 0
              • M
                marrold
                last edited by Aug 15, 2013, 7:48 AM

                Any luck Stephen?

                1 Reply Last reply Reply Quote 0
                • S
                  stephenw10 Netgate Administrator
                  last edited by Aug 15, 2013, 9:48 AM

                  Ooops, totally forgot about that! Doesn't seem to be showing anything now. Started again. The graph should appear here:
                  http://www.dslreports.com/r3/smokeping.cgi?target=network.e6c1442a6598dd4e26a0fa816f137954&r=33

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • M
                    marrold
                    last edited by Aug 15, 2013, 2:50 PM

                    Thanks for your help. Do you mind if I add you IP / Domain to my monitoring? You can PM me if you wish, but I understand if you would rather not.

                    1 Reply Last reply Reply Quote 0
                    • S
                      stephenw10 Netgate Administrator
                      last edited by Aug 16, 2013, 5:58 PM

                      Moving this back to the forum where it could help others.
                      Your tests results seem to show this isn't an inherent pfSense/FreeBSD problem. Do you have the HG612 vdsl modem?

                      Steve

                      1 Reply Last reply Reply Quote 0
                      • M
                        marrold
                        last edited by Aug 18, 2013, 9:41 AM

                        For clarity for other users, here are the graphs.

                        My own, showing lots of packet loss/jitter-

                        stephenw10's graph, showing no packet loss and a steady connection-

                        I have the newer ECI  B-FOCuS V-2FUb/R Rev.B VDSL2 FTTC modem, so I am unable to 'hack' it to get the line stats, but I intend on ordering a HG612 next week. I've asked my ISP (which funnily enough I work for) for the line stats, but our upstream provider is taking their time.

                        So far, it remains a mystery.

                        1 Reply Last reply Reply Quote 0
                        • S
                          stephenw10 Netgate Administrator
                          last edited by Aug 18, 2013, 10:34 AM

                          @marrold:

                          I've asked my ISP (which funnily enough I work for)

                          Ha, no excuses then.  ;D
                          Interesting that your base ping time is lower than mine by quite a bit. Is your smoke ping test box within the ISPs network?

                          Steve

                          1 Reply Last reply Reply Quote 0
                          • M
                            marrold
                            last edited by Aug 18, 2013, 11:22 AM Aug 18, 2013, 11:00 AM

                            Unfortunately we are essentially a reseller so I am still relying on a third-part for the info.

                            The smokeping box is indeed in the ISP's network, only a few hops away from the Broadband End Point (The 'LNS' I believe, I have to admit Im not an expert on the finer details). I have monitored another colleagues FTTC connection using the Technicolor TG582, and again, his connection looks fine.

                            I will push for the line stats tomorrow. Until then, there isn't much else I can try.

                            I find it bizarre the problem has been present on both the ADSL and VDSL service, as the wiring, modems, filters, and pfSense box have all been changed with no effect, hence my first hunch was it must of been pfSense's PPPoE implementation, but it doesn't look like that is the case.

                            1 Reply Last reply Reply Quote 0
                            • S
                              stephenw10 Netgate Administrator
                              last edited by Aug 18, 2013, 11:04 PM

                              I assume you aren't seeing any errors or collisions on the WAN NIC? Can you switch the pppoe connection to another NIC? Do you have another box you can load pfSense onto for a test?

                              Steve

                              1 Reply Last reply Reply Quote 0
                              • S
                                stephenw10 Netgate Administrator
                                last edited by Aug 19, 2013, 12:08 AM

                                Just re-reading this: http://forum.pfsense.org/index.php/topic,64786.msg354161.html#msg354161
                                Definitely check for a duplex mismatch between the modem and pfSense box.

                                Steve

                                1 Reply Last reply Reply Quote 0
                                • M
                                  marrold
                                  last edited by Aug 19, 2013, 8:55 AM

                                  @stephenw10:

                                  I assume you aren't seeing any errors or collisions on the WAN NIC? Can you switch the pppoe connection to another NIC? Do you have another box you can load pfSense onto for a test? Steve

                                  There are currently 0 errors/collision on the WAN NIC. I've had the same issues with other NIC's / boxes with a variety of NICs

                                  @stephenw10:

                                  Just re-reading this: http://forum.pfsense.org/index.php/topic,64786.msg354161.html#msg354161
                                  Definitely check for a duplex mismatch between the modem and pfSense box.
                                  Steve

                                  I have forced the speed and duplex on the pfSense box but I am unable to force it on my OR modem unfortunately.

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    stephenw10 Netgate Administrator
                                    last edited by Aug 19, 2013, 3:59 PM

                                    You should only force the speed/duplex if the modem-pfSense connection is not negotiating correctly. Was it negotiating to full speed full duplex? It seems this is not the first time it's happened with that modem:
                                    http://forum.mikrotik.com/viewtopic.php?f=3&t=70166

                                    Try putting a switch between the modem and pfSense box. Return everything to auto-negotiation.

                                    Steve

                                    1 Reply Last reply Reply Quote 0
                                    • M
                                      marrold
                                      last edited by Aug 20, 2013, 9:23 AM

                                      pfSense was auto-negotiating correctly, so I shall return it back to normal. The OR modem is currently hooked up to a switch, and then VLAN'd to the pfSense box, but I still get the same latency/jitter when connecting directly.

                                      Im still waiting on the line stats from the upstream provider, I really need to get a 'hacked' box.

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        stephenw10 Netgate Administrator
                                        last edited by Aug 20, 2013, 9:28 AM

                                        It looks like there are some hacking options for that box too but they involve soldering so it's really non-reversible. BT will know if they come round to fix it and charge you accordingly!
                                        Since it's the modem that seems to be suspect in negotiating the connection speed/duplex can you find out if it's doing so correctly with the switch?
                                        If it was just a line problem why does it not happen with the SOHO router you have? I suspect the line stats will show you nothing.  :-\

                                        Steve

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          marrold
                                          last edited by Aug 20, 2013, 11:18 AM

                                          I have the newer hardware revision which has limited hacking options unfortunately. The Huawei HG612 seems to the most established hacked box, so I don't mind grabbing one off Ebay for modifications, as you say, BT will charge if I damage their supplied equipment.

                                          Speed and Duplex is being correctly negotiated by the switch.

                                          I also suspect the line stats will be inconclusive, but Its literally my last hope! I could do with taking my pfSense box to another location with FTTC, but they are few and far between in my area. I was the very first customer in my cabinet!

                                          Thanks again for your help, even though it doesnt look as though a resoloution is in sight.

                                          1 Reply Last reply Reply Quote 0
                                          26 out of 30
                                          • First post
                                            26/30
                                            Last post
                                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                                            This community forum collects and processes your personal information.
                                            consent.not_received