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

    [Solved] Draytek Vigor 166. Frequently dropped connection.

    Scheduled Pinned Locked Moved Off-Topic & Non-Support Discussion
    23 Posts 4 Posters 5.8k 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.
    • Y
      youngy @stephenw10
      last edited by

      @stephenw10 Steve, I just thought I'd close out this thread by doing a final update. Since Thursday midday(ish) I've been using the MT992 modem. The connection hasn't dropped at all, which suggests to me there's either a problem with the Vigor 166 or it's too sensitive to the noise on our line. Although I tried altering the SNR margin via the console, it had no effect on the SNR margin when the modem connected (~3 dB). Thanks for your suggestions. I hadn't heard about the MT992 modem before.

      RobbieTTR 1 Reply Last reply Reply Quote 0
      • RobbieTTR
        RobbieTT @youngy
        last edited by RobbieTT

        @youngy The V166 is very picky with its firmware and, depending on cabinet, may need the 'alternative' fw load.

        The Openreach modem has a 1520 MTU set out of the box, so a 1500 bytes plus the 8 byte PPPoE overhead will fit through the pipe with no issues. It is typical to set the V166 at 1508 MTU.

        In either case, on pfSense itself the physical WAN to modem interface should be set to 1508 MTU:

         2023-05-20 at 16.04.49.png

        With the PPPoE tunnel set at 1500 MTU:

         2023-05-20 at 16.04.28.png

        The Openreach supplied RJ11 cable is a bit rubbish and the plug can cause poor connections on the modem when there is any lateral load or twist on it. RJ45 plugs make a better connection, even if RJ11 plugs are supposed to work ok in RJ45 sockets.

        Glad you found a working equipment solution. 👍

        ☕️

        Y 1 Reply Last reply Reply Quote 1
        • Y
          youngy @RobbieTT
          last edited by

          @robbiett Thanks for this information, I'll try your suggestion. Any help is much appreciated. Draytek sent me an alternative firmware (marked as beta) but with it I couldn't connect to the internet at all. There are two modem codes as standard with the latest firmware and I've tried them both, to no avail. I've been using a cable that came with the Fritzbox supplied by Zen, which has a RJ45 connection at the modem and have tried an alternative too :-( At least the MT992 seems fine (fingers crossed).

          RobbieTTR 1 Reply Last reply Reply Quote 0
          • RobbieTTR
            RobbieTT @youngy
            last edited by

            @youngy
            Do you happen to know what street cabinet type you have, Huawei or ECI?

            ☕️

            Y 1 Reply Last reply Reply Quote 0
            • Y
              youngy @RobbieTT
              last edited by

              @robbiett Hi, this is the output from the Vigor 166. It says the DSLAM vendor is BDCM, which I think is Huawei with a Broadcom chipset. Is that right? It seems to me that the SNR margin is too low (3 dB), but altering the target via the Vigor console doesn't appear to have any impact on the SNR margin of the connection. I spoke to Zen about it and they said that it's not possible for them to adjust it for the line like they could with adsl.

              6ae9c70c-40fe-4c6c-9f36-c6d49f625ae4-image.png

              RobbieTTR 1 Reply Last reply Reply Quote 0
              • RobbieTTR
                RobbieTT @youngy
                last edited by RobbieTT

                @youngy Yep, it is a Huawei cabinet. If it was an ECI it would have a vendor <IFTN>. At least you got the better of the two.

                On those stats you had a heck of a delta set - I guess you were testing the limits. I also note that you were stuck on an interleaved profile.

                ☕️

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  Setting the PPPoE interface to 1500 should automatically set the parent to 8 bytes above that. When I tested that recently it did not actually show on the pppoe but it was able to pass large packets.

                  RobbieTTR 1 Reply Last reply Reply Quote 0
                  • RobbieTTR
                    RobbieTT @stephenw10
                    last edited by

                    @stephenw10 Ok, I didn't know that; I've just been setting it by hand. 👍

                    ☕️

                    Y 1 Reply Last reply Reply Quote 0
                    • Y
                      youngy @RobbieTT
                      last edited by

                      @robbiett I might be being a bit dim but, do you have your ONT interface because your fibre is connected directly into pfSense? I just have a WAN (pppoe0) interface set up, which I've tried at various MTU values (1500, 1492, 1452). It didn't make any difference.

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        Didn't make any difference to the dropped connections or to the MTU on the interfaces? It should at least change the mtu of the parent NIC. It probably wouldn't have made any difference to the drops. I doubt that's MTU related.

                        Y 1 Reply Last reply Reply Quote 0
                        • Dobby_D
                          Dobby_ @youngy
                          last edited by

                          @youngy

                          I tried swapping back to the Openreach modem, which remained stable. Lastly, my ISP has arranged to send a replacement router (Fritzbox 7530) to test the line, but it can't be put into bridge mode so I'll end up with double NAT.

                          Cool, take it, you will be able to see the whole sync process
                          visually and on top you may be able to open the LAN port
                          to your pfSense as "exposed host", then you will be aware of double NAT!

                          • Internet > DSL-Informationen
                            You may see there the problems better shown
                          • Internet > Permit Access > Port Sharing
                            Set up "Exposed host", but only on the port for the pfSense

                          #~. @Dobby

                          Turris Omnia - 4 Ports - 2 GB RAM / TurrisOS 7 Release (Btrfs)
                          PC Engines APU4D4 - 4 Ports - 4 GB RAM / pfSense CE 2.7.2 Release (ZFS)
                          PC Engines APU6B4 - 4 Ports - 4 GB RAM / pfSense+ (Plus) 24.03_1 Release (ZFS)

                          1 Reply Last reply Reply Quote 1
                          • Y
                            youngy @stephenw10
                            last edited by

                            @stephenw10 Yes, the mtu of the interface changed. But, as you suggest, the dropped connections didn't.

                            Y 1 Reply Last reply Reply Quote 1
                            • Y
                              youngy @youngy
                              last edited by

                              @youngy Just to round off this thread, I contacted Draytek again and they supplied two alternative firmware for the Vigor 166. One of them (r15597_791_9cf83135b_beta) has been running for > 2 days without a dropped connection. Fingers crossed, that's given me a usable modem. Thanks for all your contributions.

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