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

    Problems when update to 2.0.2

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    9 Posts 5 Posters 3.2k 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.
    • K
      kolomalo
      last edited by

      Since I updated to 2.0.2, Captive Portal and VoIP stop working correctly. Without change anything, the only way to work fine was revert to 2.0.1.

      VoIP seems that don't cross through pfsense. I haven't any rule to block it or any other configuration rather than some nat rules (on wan). VoIP come from an opt interface that has a "allow all trafic" rule on it. On 2.0.2 stop working, and reverting to 2.0.1 fix it.

      This is the topic for CP error
      http://forum.pfsense.org/index.php/topic,57785.0.html

      Many thanks

      1 Reply Last reply Reply Quote 0
      • K
        kolomalo
        last edited by

        pfsense full update 2.0      90 MB
        pfsense full update 2.0.1  90 MB
        pfsense full update 2.0.2  70 MB ??? ??? ??? ???  it's ok?? (all mirrors has the same file)

        1 Reply Last reply Reply Quote 0
        • chpalmerC
          chpalmer
          last edited by

          @kolomalo:

          pfsense full update 2.0      90 MB
          pfsense full update 2.0.1   90 MB
          pfsense full update 2.0.2   70 MB ??? ??? ??? ???  it's ok?? (all mirrors has the same file)

          I saw some posts where they cleaned up some un-needed files from the base OS.

          What is your VOIP config?

          Triggering snowflakes one by one..
          Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

          1 Reply Last reply Reply Quote 0
          • K
            kolomalo
            last edited by

            Sorry, I don't know anything about voip (it's "outsourced").

            Perhaps is not a pfsense fault, but reverting to 2.0.1 worked for me (and CP works again too).

            1 Reply Last reply Reply Quote 0
            • G
              gameoffuture
              last edited by

              Same kind of probles here. I have Bell business ADSL service and after upgrading to 2.0.2 it will not detect teh DNS from ISP anymore and sets it to 127.0.0.1.

              I have tried entering teh DNS manually, but no matter what I do I can't get connection going through. Basically I have lost the ability to surf the internet all toghether.

              Factory reset, restore settings from working 2.0.1 installation, no dice.
              Factory reset again, tried setting up PPPoE and the same issue, won't get DNS IPs and can't surf the web. I have verified my connection is working by connecting successfully via my laptop and desktop (just to be sure) to the DSL, and I can surf the web.

              I thought maybe something was wrong/corrupted on my installtion, so I downloaded the Live CD and booted from it, I can't even get it connected to my DSL anymore and it won't authenticate via the Live CD.

              I wiped teh HDD and tried installing from scratch from the live CD and it is stuck on the following command at 36%:

              /usr/local/bin/cpdup -vvv -I -o /usr /mnt/usr

              So it seems that I the live CD is broken or something is wrong with the install script or taht command? I have verified the iso and the disk so it is not a corrupted disk.
              Right now I can't even install the pfSense in my system at all… so I'm stuck...

              1 Reply Last reply Reply Quote 0
              • pttP
                ptt Rebel Alliance
                last edited by

                The "PPP-assigned DNS server problem " is a known issue, just check the Blog  and or do some "forum Search" about it ;)

                http://blog.pfsense.org/?p=676

                http://forum.pfsense.org/index.php/topic,57020.0.html

                1 Reply Last reply Reply Quote 0
                • G
                  gameoffuture
                  last edited by

                  Awesome :D Thanks for the reply… the only issue remains is I can't get 2.0.2 installed in my box anymore. The quick install and the custom install gets stock at the same 36% progress and that's as far as I can get. I did jump the gun whiping the drive to install the thing from scratch again.  -.-"

                  I had an image of the old pfsense, but I archived some of my backups since I was running out of space on my NAS and have to go dig it out now (sux having multiple back ups and still a pain to go back to them when you need it... that's life... )

                  1 Reply Last reply Reply Quote 0
                  • chpalmerC
                    chpalmer
                    last edited by

                    Give 2.0.3 a try.  :)

                    http://forum.pfsense.org/index.php/topic,58203.0.html

                    Triggering snowflakes one by one..
                    Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

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

                      Hi,

                      Just to report an upgrade problem : 2.0.1 + siproxy -> 2.0.2
                      I have lost the DNS, as described in the release notes (PPPOE problem).
                      But I have broken all the packaging system too. Siproxy was broken in the interface & not running.

                      Revert to previous 2.0.1 & waiting for stable 2.0.3, as I don't have issues for my needs.

                      If you are interested in, I have keep the update log file & the diff file from my previous user setup.

                      Thanks for the good job.

                      Phil

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