Navigation

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

    2.4.0 -> 2.4.1: WAN PPPOE cannot connect

    Installation and Upgrades
    4
    6
    895
    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
      segfooled last edited by

      Just did the maintenance update 2.4.0 -> 2.4.1 now the WAN interface cannot connect.
      Gateway Log says:

      dpinger 		send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 0 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr [ISP_IP] bind_addr [MY_IP] identifier "WAN_PPPOE " 
      

      Syslog has a series of:

      Oct 25 09:24:28 	ppp 		[wan_link0] Link: reconnection attempt 25 in 4 seconds
      Oct 25 09:24:28 	ppp 		[wan_link0] LCP: Down event
      Oct 25 09:24:28 	ppp 		[wan_link0] Link: DOWN event
      Oct 25 09:24:28 	ppp 		[wan_link0] PPPoE connection timeout after 9 seconds
      Oct 25 09:24:19 	ppp 		[wan_link0] PPPoE: Connecting to ''
      Oct 25 09:24:19 	ppp 		[wan_link0] Link: reconnection attempt 24 
      

      I have not changed any of the configs and my previous upgrade 2.3.4 -> 2.4.0 went smoothly.

      Any ideas?

      EDIT: Ok I realize this is due to the PPPOE/VLAN naming bug newly introduced in 2.4.1 (VLAN naming change breaks something). I need to dial up using VLAN ID 10 and PPPOE.

      I'm a bit put off I must say that such a big change is done in a maintenance update that I thought was primarily meant to fix KRACK. Murphy's law struck, as for the first time since years I did not read the release notes.

      So new question: Can I fix this in 2.4.1 through some config change, e.g. redo VLAN10 for the ISP or reassign WAN? Alternatively, how do I roll back to 2.40 or slightly forward to pre-2.4.2 where it seems fixed? Could not find 2.4.2.

      Thanks!

      1 Reply Last reply Reply Quote 0
      • Grimson
        Grimson Banned last edited by

        Are you using PPPOE over a VLAN interface, if yes: https://forum.pfsense.org/index.php?topic=138804.msg758710#msg758710

        1 Reply Last reply Reply Quote 0
        • S
          segfooled last edited by

          Thx! Annoying but good to see it confirmed

          1 Reply Last reply Reply Quote 0
          • N
            NineX last edited by

            @Grimson:

            Are you using PPPOE over a VLAN interface, if yes: https://forum.pfsense.org/index.php?topic=138804.msg758710#msg758710

            if you have pppoe on vlan
            there is a quick fix

            edit your config.xml
            and replace iface.vlan with interface_vlan
            reboot
            it's a bug in mpd and it's fixed in 2.4.2 development snapshot already.

            1 Reply Last reply Reply Quote 0
            • S
              segfooled last edited by

              @NineX:

              @Grimson:

              Are you using PPPOE over a VLAN interface, if yes: https://forum.pfsense.org/index.php?topic=138804.msg758710#msg758710

              if you have pppoe on vlan
              there is a quick fix

              edit your config.xml
              and replace iface.vlan with interface_vlan
              reboot
              it's a bug in mpd and it's fixed in 2.4.2 development snapshot already.

              Yep -thx, have seen and done as per the thread in the snapshot section of the forum. Worked and I had to rename just the VLAN that does PPPOE. It's back online.

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

                same problems here

                3 VLAN Wans
                1 of them static ipv4 was connected
                2 of them could not connect per pppoe

                Upgrade to latest Snapshot has fixed, without renaming anything.

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