Snapshots are back!
-
Are they stable enough now for home use, without crashing or any major problems?
-
Are they stable enough now for home use, without crashing or any major problems?
Basically, yes, but if you depend on specific packages or features there may be the one or other thing not working as expected.
-
Since we moved the builds to a blazingly fast new box, I went ahead and enabled nanobsd+vga builds for each snapshot run. enjoy!
-
Is your blazingly fast new build boxes dumping update files to a new location also? Reason I am asking is that I have an IPv6 only firewall that cannot get to update. Some troubleshooting shows that snapshots.pfsense.org is not resolving a AAAA record.
-
Yeah the snapshots site moved to our colo at NYI (the builds are done in yet a different place), the NYI site doens't have IPv6 yet, but will soon.
-
N00b question but still, what windows program should I use to burn the 4g image to my ssd?
-
It's on the wiki, but either physdiskwrite or win32 disk imager.
-
Thanks :)
-
AAAA is back for snapshots.pfsense.org so getting updates over IPv6 will work again.
-
Thanks. That is good news.
-
Wow, it's that I need, thank you!
-
Where should I look for changes in these snapshots? In here ?
-
There and also here: http://redmine.pfsense.org/activity
-
Hello
I am on a clean 2.0.1 (i386) and try to update to 2.1. Enabling development repo, and allowing unsigned images.
When done it says:
The image file is corrupt.
Update cannot continueShould it be possible to upgrade using the GUI? Or is something else needed for first time upgrade to 2.1?
BR. Anders
-
That should be enough.
It's possible your system is downloading a bad or corrupt image somehow (perhaps a proxy or something else in between?)
If it's still giving the same message after a new snapshot run (check back tomorrow), start a fresh thread for the issue.
-
Will do, thanks.
-
are there 64-bit builds? I'm looking for a nanobsd to run from USB but all I see are i386. Possibly I'm missing something.
-
There are separate links for i386 and amd64, but all are under http://snapshots.pfsense.org
e.g. http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_RELENG_2_1/?C=M;O=D
-
There are separate links for i386 and amd64, but all are under http://snapshots.pfsense.org
e.g. http://snapshots.pfsense.org/FreeBSD_RELENG_8_3/amd64/pfSense_RELENG_2_1/?C=M;O=D
Thanks! Hey, look at that. Right there in the body of the OP. Sorry for the momentary illiteracy.
-
Hi jimp,
I am experiencing issues reaching snapshots.pfsense.org from last two days:
Maybe it can be a temporary / network issue?
[luzemario@acer ~]$ tracepath snapshots.pfsense.org
1: 192.168.X.Y 0.129ms pmtu 1500
1: mysite.no-ip.org 2.123ms
1: mysite.no-ip.org 1.982ms
2: ispinternalrouter 11.607ms
3: mygateway.com.br 12.756ms
4: embratel-T0-6-5-0-tacc01.rjoen.embratel.net.br 30.328ms
5: ebt-T0-2-0-0-tcore01.rjo.embratel.net.br 155.039ms asymm 7
6: ebt-Bundle-POS1211-intl01.nyk.embratel.net.br 154.490ms
7: ae59.edge2.NewYork1.Level3.net 158.892ms asymm 15
8: vlan60.csw1.NewYork1.Level3.net 162.673ms asymm 18
9: ae-81-81.ebr1.NewYork1.Level3.net 163.354ms asymm 17
10: ae-2-2.ebr1.Newark1.Level3.net 169.491ms asymm 17
11: ae-1-51.edge2.Newark1.Level3.net 167.495ms asymm 16
12: THE-NEW-YOR.edge2.Newark1.Level3.net 221.790ms asymm 17
13: cs20.cs59.v.jfk.nyinternet.net 165.389ms asymm 18
14: no reply
15: no reply
16: no reply
17: no reply
…