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

    Upgrade to 2.4.1 cant connect to pppoe wan over vlan

    Scheduled Pinned Locked Moved
    2.4 Development Snapshots
    23
    50
    14.9k
    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.
    • A
      Apo
      last edited by

      I've upgraded my SG-4860 to 2.4.1 and lost my internet connection.

      I tried to modify my config, renaming all igb1.11 to igb1_11 but this results in the system not coming up at all anymore. I had to factory reset and reload the original config to connect again.

      What else can I do to get my connection running again?

      1 Reply Last reply Reply Quote 0
      • P
        PiBa
        last edited by

        While its running run on console "ifconfig igb1.11 name igb1_11" then from webgui edit the pppoe interface to select the right interface to run on. That should afaik allow for internet access. Until reboot that is..
        Should probably be possible to upgrade to 2.4.2development which should fix the pppoe+vlan issue, though i am not 100% sure if it wont complain during boot then yet again.. due to the changed config for a then not existing interface with that name..

        1 Reply Last reply Reply Quote 0
        • A
          Apo
          last edited by

          @PiBa:

          While its running run on console "ifconfig igb1.11 name igb1_11" then from webgui edit the pppoe interface to select the right interface to run on. That should afaik allow for internet access. Until reboot that is..

          That did the trick, thank you very much!!!

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned
            last edited by

            @jwt:

            This "mvneta" name did not come from us, it came from Semihalf, via FreeBSD.
            Many people are misinformed about being able to get reload images for Netgate platforms.  You perpetuate the myth, and I think only to gain advantage.

            I perpetuate nothing. I responded to your email, sadly no response to that. So let me restate this in public - noone gives a horse shit about who's responsible for the interface naming brainfart. You are breaking stable releases because of this nonsense. 2.4.0 RC, 2.4.1, the 2.4.2 snapshots…

            WTH you keep threatening contributors to this project What kind of advantage am I supposed to gain from this? Being threatened here, being threatened via email, as a reward for contributing tens of thousand LOCs to the project?

            Go see a shrink doctor, ASAP. This paranoia is pathologic.

            1 Reply Last reply Reply Quote 0
            • ivorI
              ivor
              last edited by

              That's it, your continuous abuse ends now. You were warned many times.

              Need help fast? Our support is available 24/7 https://www.netgate.com/support/

              1 Reply Last reply Reply Quote 0
              • ?
                A Former User
                last edited by

                Just did a fresh install of 2.4.0 and restored my backup config… all up and running now.. waiting for 2.4.2 for now, or maybe 2.5.x ...

                still damn unhappy about how this all went down... such change in an Minor upgrade.. unbelievable

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

                  My solution workflow that got our 2.4.1 box with this issue back online…....

                  a) Had upgraded from 2.4.0 to 2.4.1
                  b) System came back up fine after the upgrade reboot, but no internet connection anymore with existing VLAN/PPPoE configuration.
                  c) Logged into WebGUI
                  d) Went to Diagnotstics --> Edit File --> Browse. Choose "Conf" folder. Choose Config.xml file.
                  e) Place cursor in text window. Go to the Web browser's menu to choose the "find" content facility. Search for each occurrence of "interfacename.vlannumber" in config.xml and change the . to _ then save the edited config.xml file. For example igb0.900 to igb0_900
                  f) Reboot PfSense.
                  g) System came back up without issue and connected the PPPoE connection immediately. Job done. 15 minutes work max.

                  Hope that helps as another interim solution option. I had to do this remotely (200+ Km away), with the keyboard assistance of an inexperienced person at the system's site. The pfSense system was installed at a Radiology practice, so the situation was business critical.

                  It was an inconvenience yes, but not a show stopper.

                  The bottom line in all this, is that I failed to appreciated the release notes content regarding the VLAN/PPPoE issue, in as much as I forgot that this problem configuration existed on the system I upgraded. So I have no one else to blame but myself. I see that some people are rather disguntled by the circumstances of their own demise with this issue. Yes one could sook that the upgrade was released broken I suppose, but it gets a bit rich to complain about this, when the release notes forewarn of the issue for a specific configuration and then that warning is not heeded.

                  Cheers

                  1 Reply Last reply Reply Quote 0
                  • E
                    epek
                    last edited by

                    @MAW: if I follow that advise, pfSense will have troubles assigning it's vlans (on that appliance: vtnet0., vtnet0_ respectively) to logical interfaces (OPT*) at reboot. If I only change that within the vlan and pppoe sessions, assignments still work, but pppoe still fails.

                    1 Reply Last reply Reply Quote 0
                    • jahonixJ
                      jahonix
                      last edited by

                      @MAW:

                      … I had to do this remotely (200+ Km away) ... at a Radiology practice, so the situation was business critical ... It was an inconvenience yes, but not a show stopper.

                      What?
                      A point release that kills functionality IS a show stopper. Period.
                      Work in the live entertainment industry like I do and you'll get this pretty soon. Or get fired before you even know why.

                      1 Reply Last reply Reply Quote 0
                      • A
                        alex17857
                        last edited by

                        I upgraded to 2.4.1 and lost my PPPOE WAN connection too. Whoever implemented this system breaking change smoked far too much crack.

                        1 Reply Last reply Reply Quote 0
                        • P
                          phil94130
                          last edited by

                          @chrcoluk:

                          this is a known issue, will be fixed in 2.4.2.

                          I dont know if its fixed in the current 2.4.2 dev branch.

                          Thank you for the information

                          1 Reply Last reply Reply Quote 0
                          • R
                            robi
                            last edited by

                            The biggest pain in the ass comes when you update remotely the box, through a VPN connecting via the PPPoE connection. You won't be able to fix anything until you go there physically. Which can cause severe downtime…

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

                              @robi:

                              The biggest pain in the ass comes when you update remotely the box, through a VPN connecting via the PPPoE connection. You won't be able to fix anything until you go there physically. Which can cause severe downtime…

                              directly upgrade to 2.4.2 dev from 2.4 and it will be fine, just skip the 2.4.1 update

                              1 Reply Last reply Reply Quote 0
                              • jahonixJ
                                jahonix
                                last edited by

                                @xbipin:

                                directly upgrade to 2.4.2 dev …

                                Stuntman is your main profession or just a hobby?  8)

                                Honestly, you don't update a remote machine some serious distance away to a dev snapshot. May I remind you that dev stands for development and may contain glitches and quirks.
                                And which snapshot timestamp are you talking about? There's probably a newer one already built while we post. Is that fine as well, did you test that on my infrastructure?

                                You can do so at home if you like but surely not in a remote session to a critical system not within walking reach.
                                If you are sane, that is.  ;)

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

                                  I think he meant for this specific case only.
                                  This is the only reasonable thing to do. Better 2.4.2 which is more stable than 2.4.1 at least IMO.

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

                                    well i too run many boxes which r located in different countries and after testing 2.4.2 dev locally upgraded all of them to it and all work fine, there isnt much changed between 2.4.1 and 2.4.2 dev so its fine, if the dev marking scares u then wait for the stable but for now the only way to solve this pppoe over vlan issue is to use the dev version

                                    1 Reply Last reply Reply Quote 0
                                    • V
                                      virusbcn
                                      last edited by

                                      Here one other Pfsense KO, i upgrade a 2.4.1 and my PPOE over vlan go out, where can i download the 2.4.2 version to put in my ko pfsense ???

                                      1 Reply Last reply Reply Quote 0
                                      • jahonixJ
                                        jahonix
                                        last edited by

                                        https://snapshots.pfsense.org/amd64/pfSense_master/installer/

                                        1 Reply Last reply Reply Quote 0
                                        • B
                                          bullet92
                                          last edited by

                                          I think i'm very unlucky. I have the same problem that PPP doesn't work on vlan so i first tried:
                                          @PiBa:

                                          While its running run on console "ifconfig igb1.11 name igb1_11" then from webgui edit the pppoe interface to select the right interface to run on. That should afaik allow for internet access. Until reboot that is..

                                          But this doesn't work for me, PPP still was down. So I tried the procedure below:

                                          @MAW:

                                          Choose Config.xml file.
                                          e) Place cursor in text window. Go to the Web browser's menu to choose the "find" content facility. Search for each occurrence of "interfacename.vlannumber" in config.xml and change the . to _ then save the edited config.xml file. For example igb0.900 to igb0_900
                                          f) Reboot PfSense.
                                          g) System came back up without issue and connected the PPPoE connection immediately. Job done. 15 minutes work max.

                                          And my firewall was stucked in a bootloop: it starts, answer me 5 or 6 pings then restart…. I was able to connect to SSH and restore a previous configuration in this time frame (i think max 5-6 sec). Firewall reboots correctyl and now I have the same problem: my PPP VLAN doesnt works.  Finally i've tried this:

                                          @xbipin:

                                          directly upgrade to 2.4.2 dev from 2.4 and it will be fine, just skip the 2.4.1 update

                                          And my firewall was stucked at boot, saying it cant find /boot/kernel/kernel.
                                          :'( :-X

                                          EDIT: Added IMG error of 2.4.2 from SSD and error from USB (tried 2.4.0. and 2.4.2) USB was the memstick img.gz file and was written by rufus

                                          EDIT2: FreeBSD 11.1 AMD64 Memstick boots fine EDIT3. Nope, it stucks just later.
                                          I've changed USB and now 2.4.2 starts!

                                          error1.jpg
                                          error1.jpg_thumb
                                          error2.jpg
                                          error2.jpg_thumb

                                          1 Reply Last reply Reply Quote 0
                                          • V
                                            virusbcn
                                            last edited by

                                            I have a 2.4.1 that not works after upgrade, i have ppoe over vlan, and now what is the best option to repair it?
                                            Upgrade to 2.4.2dev? How ?  Before i can upgrade offline but now i not have the option, boot from USB 2.4.2dev and upgrade?  Repair my 2.4.1?? How? I don't understand very well what i need to have internet

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