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

    PPPoE reconenction fix - mpd fix ($100)

    Scheduled Pinned Locked Moved
    Expired/Withdrawn Bounties
    24
    243
    165.0k
    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.
    • X
      xbipin
      last edited by

      further analysis shows it could be a freebsd issue coz when the isp modem is reset or rebooted, the link between pfsense and isp modem is in a half dead state so inspite of mpd saying its trying to reconnect, those packets never reach the isp modem thats y the connection never recovers, only bringing down the complete interface on the pfsense box and then back up again makes those mpd packets reach the isp modem. in half dead state its like the interface is up but nothing flows between end points, so some1 needs to figure out what causes this half dead state, could it be the interface drivers or something else

      1 Reply Last reply Reply Quote 0
      • D
        dhatz
        last edited by

        @xbipin:

        further analysis shows it could be a freebsd issue coz when the isp modem is reset or rebooted, the link between pfsense and isp modem is in a half dead state so inspite of mpd saying its trying to reconnect, those packets never reach the isp modem thats y the connection never recovers, only bringing down the complete interface on the pfsense box and then back up again makes those mpd packets reach the isp modem. in half dead state its like the interface is up but nothing flows between end points, so some1 needs to figure out what causes this half dead state, could it be the interface drivers or something else

        Well, those who experience this issue should then provide a more detailed report of hardware (which driver e.g. em/vr/rl/etc, which DSL modem in bridge mode, which provider DSLAM -if known-) and pfsense/FreeBSD software used when replicating the issue …

        It's quite fortunate that mpd is being actively developed, and if this issue is somehow related to mpd, we can expect a quick fix.

        1 Reply Last reply Reply Quote 0
        • X
          xbipin
          last edited by

          im using the alix 2d3, the FTTH modem is by Zhone technologies (ZNID-GPON-2520), also tried with huawei DSL and cisco cable connection devices, the DSLAM is provided by unisphere for all the isp i had this issue with, pfsense is the nanobsd 1g 2nd feb 2013 snap

          1 Reply Last reply Reply Quote 0
          • X
            xbipin
            last edited by

            will $200 be good to fix this?

            1 Reply Last reply Reply Quote 0
            • D
              dhatz
              last edited by

              @xbipin:

              im using the alix 2d3, the FTTH modem is by Zhone technologies (ZNID-GPON-2520), also tried with huawei DSL and cisco cable connection devices, the DSLAM is provided by unisphere for all the isp i had this issue with, pfsense is the nanobsd 1g 2nd feb 2013 snap

              Well, could you check the very same setup with a different pfsense NIC (e.g. Intel) or running pfsense in a VM, to see if you can replicate the issue ?

              But if it's some odd interaction between mpd and Unisphere DSLAM, I think your best bet would be the mpd developers …

              1 Reply Last reply Reply Quote 0
              • X
                xbipin
                last edited by

                the issue remains when trying windows dialup connection using a realtek nic to ftth modem by isp.

                i have tried contacting mpd developers a few times recently also but no reply.

                the only working fix as of now is bringing down the interface and then back up again and this was provided by wow a few pages back but it works in delayed fashion but probably some1 from pfsense can add this to pfsense in a more reliable manner so when pppoe disconnected, then kill mpd, bring down interface, wait few seconds, then bring back itnerface, wait few seconds and then launch mpd

                1 Reply Last reply Reply Quote 0
                • X
                  xbipin
                  last edited by

                  @TimAtHome:

                  After suffering from very similar logs and lots of googling I found a cure (well a cause) for me anyway.

                  If the router came up after pfSense (if it was powered off then on again), pfSense would not connect to it no matter what unless you power cycled it again or yanked the cable. What I found was happening was when the link first came up pfSense would grab the ip address from the router using DHCP and start sending its pppoe requests to it (producing the same logs about connecting posted earlier), it would never log in. Pulling the cable, waiting a bit then plugging it back in would then log in straight away.

                  What was happening was the first ip address it obtained from the router was a local 'admin' address (in my case 192.168.2.10), the router would then connect to whatever destination and sync, it would then change it's ip address to the correct WAN IP (In my case 217.155..), but as the link status stayed as 'up' pfSense would not grab the new ip address and keep sending it's pppoe junk to the original 192.168.2.10 address. No amount of ifconfig up/down would shift it.

                  The solution to my problem was just to disable the DHCP server in the router as it isn't required anyway (admin access can be got using a static ip). Now I can power on/off router or pull/reconnect cable and pfSense picks up the status and the correct ip address straight away with no rebooting or anything.

                  I hope this is of use to someone as googling this issue picks this post as the top one.

                  the above was posted by another user but he managed to login into his isp modem i guess but in my case i cant do that, its not giving me access in anyway nor is dhcp enabled on the modem so i dont suffer that issue

                  1 Reply Last reply Reply Quote 0
                  • X
                    xbipin
                    last edited by

                    @dhatz:

                    @xbipin:

                    im using the alix 2d3, the FTTH modem is by Zhone technologies (ZNID-GPON-2520), also tried with huawei DSL and cisco cable connection devices, the DSLAM is provided by unisphere for all the isp i had this issue with, pfsense is the nanobsd 1g 2nd feb 2013 snap

                    Well, could you check the very same setup with a different pfsense NIC (e.g. Intel) or running pfsense in a VM, to see if you can replicate the issue ?

                    But if it's some odd interaction between mpd and Unisphere DSLAM, I think your best bet would be the mpd developers …

                    it would be helpful if some1 could get me a proper mpd developer contact

                    1 Reply Last reply Reply Quote 0
                    • W
                      webdawg
                      last edited by

                      I am having this same problem.  I am going to purchase another device to mange my ppp connection and pass that interface forward.

                      1 Reply Last reply Reply Quote 0
                      • X
                        xbipin
                        last edited by

                        sooner or later more ppl will have this issue once isp switch to unisphere BRAS or they upgrade its software or they implement one session per id restrictions

                        bytheway i have posted this on mpd forum as well but just one reply where i was asked for logs
                        http://sourceforge.net/projects/mpd/forums/forum/44692/topic/6720934

                        1 Reply Last reply Reply Quote 0
                        • X
                          xbipin
                          last edited by

                          there was some progress on this matter with the mpd developers and one way they showed to delay sending the PADT when modem is down was by setting set link keep-alive to a higher number and i did that and before mpd could renegotiate a new connection that modem came up but still the connection wouldn't continue and this gives me a strong feeling its the interface drivers but for time being still coordinating with mpd developers

                          1 Reply Last reply Reply Quote 0
                          • X
                            xbipin
                            last edited by

                            the other ppl having this issue or had this issue in the past, can u confirm ur using a alix box as well?

                            1 Reply Last reply Reply Quote 0
                            • E
                              eri--
                              last edited by

                              Its not an mpd issue it is a netgraph issue.
                              I told you that my priorities are set and will come back to this when i can.

                              For the mpd developers tell them that seems ng_ether has this issues with attaching/detaching interfaces or ng_iface.
                              Though there are some patches specifc to pfSense that might be needed to be tested as well.

                              1 Reply Last reply Reply Quote 0
                              • X
                                xbipin
                                last edited by

                                ok fine, no1 was replying so i thought it was forgotten completely.

                                bytheway few suggestions on the mpd forum helped a bit,regarding PADT packet which used to be sent when modem was down so they said to increase set link keep-alive value and so i did but if alix was connected to modem directly it wouldnt help but if connected through a switch then mpd would continue connection once modem was up again and i also tried setting the standard value of 60 for it and in that case also it would connect but after some time and had to goto interface and hit connect in which case mpd was killed and a fresh instance started. i have generated log for both and will keep with me till required.

                                meanwhile ill reply on mpd forum about it not being a mpd issue

                                1 Reply Last reply Reply Quote 0
                                • X
                                  xbipin
                                  last edited by

                                  bytheway mpd developers replied this

                                  And what those pfSense-specific patches are? I personally run mpd as PPPoE client using stock FreeBSD 8.3-STABLE and vr1 interface at home and have no netgraph-related problems with it

                                  1 Reply Last reply Reply Quote 0
                                  • X
                                    xbipin
                                    last edited by

                                    they mentioned this as well

                                    Ethernet card driver vr(4) is known to have major problems with traffic restoration after physical link down/up. This problem have nothing to do with mpd/netgraph. You need to contact FreeBSD developers or replace your hardware to get other type of NIC. Also, read this:

                                    http://lists.freebsd.org/pipermail/freebsd-net/2012-August/033127.html

                                    1 Reply Last reply Reply Quote 0
                                    • Y
                                      YiyiMan
                                      last edited by

                                      How I fixed it:
                                      Changed my USB Ethernet adapter for a different chipset, PCI Ethernet adapter. Voila!

                                      Zentyal, ClearOS and even pfSense failed to reconnect while using a Linksys USB200M, but I've had this same problem using another USB adapter (Intellinet, different chipset… I don't remember which). Maybe it's tied to USB adapters?

                                      1 Reply Last reply Reply Quote 0
                                      • F
                                        flip2
                                        last edited by

                                        I just installed pfsense (2.1-BETA1-4g-i386-nanobsd-20130507-1652.img.gz) on my Alix2d3 and I'm experiencing the same issue. Any news on a fix or workaround?

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          maverick_slo
                                          last edited by

                                          Ummm OK, here is my experience…
                                          Yesterday my box crashed and burned :) So I build a new one from an old PC...

                                          It has 2 NICs. 1 realtek (vr0) and one Intel (em0).
                                          Now, if WAN is on Realtek card it will never reconnect. But if on Intel card (em0) it will reconnect with no problem at all...
                                          Before that I had 4 Intel 100 cards (fxp). It also worked like a charm.

                                          So my suggestion for pppoe user is, use Intel NIC for WAN and you should be just fine.
                                          I do believe this is NOT mpd bug but driver bug.

                                          My 2 cents…

                                          1 Reply Last reply Reply Quote 0
                                          • X
                                            xbipin
                                            last edited by

                                            so considering a driver bug, how much would it cost to fix it or do the drivers need to be fixed from chipset manufacturer or freebsd?

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post