2.0 RC3
-
Not official but I dont believe RC2 was ever officially released either.
https://github.com/bsdperimeter/pfsense-tools/commit/e91c7ff3e0e9bb4d52e29c921918b3d8295fd266
-
rc2 to rc3 was short interval
staying on rc2 I think until RELEASE!
-
RC3 "official" is building now, if it checks out it will be signed and put on the mirrors.
The commit you saw was not any kind of official switch, it was something being worked on at the time. The real commits happened today.
photonman - that wouldn't be advisable. Keep moving forward, it's only getting better.
-
I dont have very demanding networks but both my atom box and ALIX are humming along nicely, great work guys.
-
photonman - that wouldn't be advisable. Keep moving forward, it's only getting better.
better how?
I went ahead and switched over to a 32-bit pfsense box with RC3
that is the cool thing about vm's, I can provision new builds so easily…
-
Better as in less bugs, more stable, etc.
-
RC3 "official" is building now, if it checks out it will be signed and put on the mirrors.
…when you say signed: I'm on RC2 (came from 1.2.3 Release via RC1 (manual update from snapshot) from there semiautomatically to RC2) and tried to update yesterday. I still have to "allow unsigned" to update - am I missing public keys and if yes, where do I get and where do I put them?
-
No, the official signed images are put on the mirrors, not the snapshot server. The auto update url for the snapshot server will never pick up a signed update image since those are always just snapshots, and they aren't signed.
-
No, the official signed images are put on the mirrors, not the snapshot server.
Understood - and is there a simple way to point auto update to the correct URL or do I have to reflash manually? I have seen the Auto Update Settings GUI and I can enter a URL there. So I guess that's the field I need to fill. But what's the "official" URL then?
-
On the firmware update settings there is a drop-down with update URLs. The official update url is there.
That is still on 1.2.3 now, once 2.0 is released that will be 2.0. That is only for official -RELEASE versions.
There isn't an update URL that just tracks official RCs.
-
There isn't an update URL that just tracks official RCs.
Right - also just had a look atthe mirror I normally use (http://www.fleximus.org/mirror/pfsense/updates) and it still offers 1.2.3 and now having read your post I understand why.
What I don't understand is how to get the signed RC3 now, would just feel more comfortable as opposed to the unsigned snapshot's I'm now using. On the other hand I'd like to do it via auto update cause that's always worked well for me and I'm too lazy to do a clean install just to get away from unsigned snapshots…
-
The official RC3 hasn't been uploaded that I see.
There is zero different between the signed RC3 and the snapshot from Sunday night (Unless cmb decided to use a more recent snapshot for it).
You don't have to do a clean install, just download the RC3 firmware update once it's posted.
-
The official RC3 hasn't been uploaded that I see.
You don't have to do a clean install, just download the RC3 firmware update once it's posted.ok, solved, thought that was online already. Will do, thanks!
-
And RC3 becomes official ;D
-
Nice! ;D
Running smoothly for me. Upgrade process also super slick.Steve
-
Using 2.0-RC3 (amd64), updated 23 hours ago, and all seems to be fine….
Using 4 interfaces: 2 Wan`s ( failover ), LAN and OPT ( connected to a Softswitch & using Siproxd 0.8.0_2 ).
Im really happy with pfSense !
-
;D Sweet!!!!!!!!!!!!!!!!!!!!!! Keep up the great work. Will be upgrading this weekend. How do I go about upgrading my current build manually?
-
;D Sweet!!!!!!!!!!!!!!!!!!!!!! Keep up the great work. Will be upgrading this weekend. How do I go about upgrading my current build manually?
Download the firmware upgrade file from one of the mirrors and then use System > Firmware to upload it and apply.
-
Don't forget to tell it to not worry about signatures, as the snaps don't have any. Go to System: Firmware: Settings, and turn on unsigned images.
-
Don't forget to tell it to not worry about signatures, as the snaps don't have any. Go to System: Firmware: Settings, and turn on unsigned images.
The RC3 image on the mirrors is signed, so no need for that.
You only need to check that if you're updating from the snapshots server.
-
The RC3 image on the mirrors is signed, so no need for that.
You only need to check that if you're updating from the snapshots server.Yup, just updated my i386 nanobsd on an Alix remotely through OpenVPN. Worked flawlessly with sig check = on. Great!
Keeps on looking for updates on the snapshot server though so told me straight away that I can update again (then obviously unsigned). I don't want to update every day though - my system works :-)
-
is pppoe working on this release without problem?
been using 2.0 rc1 but problem is pppoe
-
is pppoe working on this release without problem?
been using 2.0 rc1 but problem is pppoeYes no problem - but that worked in my RC1 install as well… modem/line issues? Have FTTB vdsl2 fibre over here and the connection is rock stable
-
PPPoE for me has always worked, and is still working, not a single problem with it.
-
Anything in recent builds that would have broken LAN interfaces on VMWare ESX hosts? I have a VM that was running great in previous builds, but now I so no traffic on my LAN interface. Both interfaces are brought in on virtual e1000 cards, with no VLAN tagging on the client side. The WAN interface works fine.
When I tcpdump the LAN interface, the only packet I ever see is an igmp query.
-
Not that I'm aware of, we have a ton of users that use ESX, and if there was a problem that major, there would be a lot more people complaining.
-
Not that I'm aware of, we have a ton of users that use ESX, and if there was a problem that major, there would be a lot more people complaining.
Never mind. My switch configs were changed at some point in the last week while I was out of town. I thought I checked that first, but I was wrong. Oh well. Waste of 2 hours. :)
