Re: [pfSense] pfSense version 2.1.1 has been released

2014-04-07 Thread Jeremy Porter
What hardware is this running on, and what auto-update URL was  your 
system previously set to?

What variant are you using, Nano/Full Install?

If you have a config file, from prior to the upgrade, just install 2.1.1 
of your preference, and upload your config.

The config file contains the RRD data.

Changing cpu architectures involves replacing system binaries, as well, 
which is why the RRD data doesn't work across variants,

so just changing the kernel back would not be sufficient.


On 4/6/2014 11:39 AM, Josh Karli wrote:

I think I've found a potentially serious bug in the upgrade process.

I'm not getting this error but I am seeing something rather 
disturbing: before the update I was running 2.1-release amd64 and the 
update seems to have switched it to 2.1.1-release i386! All the normal 
things that happen in the UI when switching architectures are there: 
RRD can't graph the data due to error 1 (data is from another 
architecture), and a shell command sysctl hw.machine returns i386.


I updated using the autoupdate feature with automatic rebooting.

So basically your x64 2.1.1-release update is the wrong kernel 
version. I have a config file and can install 2.1.1-release x64 from 
scratch but I'd rather not lose the RRD data. Is there a way to undo 
this update so I can get my 64 bit kernel back? I can provide logs if 
it helps tracking this bug down.


-- Original Message --
From: Jeppe Øland jol...@gmail.com
To: pfSense Support and Discussion Mailing List 
list@lists.pfsense.org

Sent: 4/5/2014 14:13:47
Subject: Re: [pfSense] pfSense version 2.1.1 has been released


On Fri, Apr 4, 2014 at 8:58 AM, Jim Thompson j...@netgate.com wrote:

 Please see the blog post
 https://blog.pfsense.org/?p=1238


Hmmm... mine gives an error that it can't verify the image signature...
(I'm on 4gb 2.1 nano vga 64bit)

Regards,
-Jeppe
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list


___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list


___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] 2.1.1 and OpenVPN Client Export

2014-04-07 Thread Peder Rovelstad
Reinstalled  package, fixed.

 

From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Peder
Rovelstad
Sent: Saturday, April 05, 2014 7:49 AM
To: 'pfSense support and discussion'
Subject: [pfSense] 2.1.1 and OpenVPN Client Export

 

I'm seeing a 404 when going to the Client Export tab.  Do I need to delete
my OVPN server and recreate to be able to export a new install package?
Using Mr. Wizard, I get port in use stepping through the process.  Or is
this even necessary?  It does connect OK with the old client.  Thanks much.

 

Peder

 

___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] pfSense version 2.1.1 has been released

2014-04-07 Thread Pete Boyd
The 2.1.0 to 2.1.1 upgrade on nanobsd (4g) on ALIX failed for me with
Something went wrong when trying to update the fstab entry. Aborting
upgrade.

I got the same issue when using auto update, and when using local upload
of pfSense-2.1.1-RELEASE-4g-i386-nanobsd-upgrade.img.gz.

The log has 2 instances of this:
php: /system_firmware.php: The command '/sbin/mount -u -w -o
sync,noatime /cf' returned exit code '1', the output was 'mount: not
currently mounted /cf'

On bootup it already has this issue in the log:
php: rc.bootup: The command '/sbin/mount -u -r -f -o sync,noatime /cf'
returned exit code '1', the output was 'mount: not currently mounted /cf'

Does anyone have any thoughts on how to remedy this please?


-- 
Pete Boyd

Open Plan IT - http://openplanit.co.uk
The Golden Ear - http://thegoldenear.org


___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list


Re: [pfSense] pfSense version 2.1.1 has been released

2014-04-07 Thread Jim Pingle
On 4/7/2014 8:38 AM, Pete Boyd wrote:
 The 2.1.0 to 2.1.1 upgrade on nanobsd (4g) on ALIX failed for me with
 Something went wrong when trying to update the fstab entry. Aborting
 upgrade.
 
 I got the same issue when using auto update, and when using local upload
 of pfSense-2.1.1-RELEASE-4g-i386-nanobsd-upgrade.img.gz.
 
 The log has 2 instances of this:
 php: /system_firmware.php: The command '/sbin/mount -u -w -o
 sync,noatime /cf' returned exit code '1', the output was 'mount: not
 currently mounted /cf'
 
 On bootup it already has this issue in the log:
 php: rc.bootup: The command '/sbin/mount -u -r -f -o sync,noatime /cf'
 returned exit code '1', the output was 'mount: not currently mounted /cf'
 
 Does anyone have any thoughts on how to remedy this please?

What does the output of mount show while booted and running?

If your /cf slice is missing/corrupt/not there, that would explain the
symptoms. No easy fix for that short of a reimage or using a new card.

Perhaps you used an image that was slightly too large for the card and
didn't see the error when imaging, or never noticed that you didn't
actually have a /cf partition.

Jim
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list


[pfSense] 2.1 to 2.1.1 upgrade throughput issue

2014-04-07 Thread Maine Techie
Hello all,

I just upgraded this weekend and I noticed a significant drop in bandwidth
(throughput).  So I spent a day testing and making sure it wasn't something
on my side.

Here is the environment:

Residential cable modem service
running on x86 platform (Intel Pentium 4 CPU 3.06GHz
2 CPUs: 1 package(s) x 1 core(s) x 2 HTT threads)
4GB memory
1 quad 10/100 NIC (sis0-3)
1 dual 10/100 NIC (fxp0-1)
all 6 interfaces used (different segments of network - wifi, VPN, DMZ, LAN,
WAN, etc)

Here is what I found:

Prior to upgrade (on stable 2.1) bandwidth test to various servers on
various bandwidth sites gives me an average of 12-15mbps download and 1 -
1.5mbps upload on standard residential cable modem service.

After I upgraded (2.1.1) bandwidth dropped to 2-3.5mbps download and
512-768kbps upload again on the same residential cable service.

So I bypassed the pfSense box and I am right back to the original 12-15mbps
download and 1 - 1.5mbps upload.

I am hoping someone has experienced the same issues and has a solution
(apart from a full wipe and reinstall).

Thanks in advance for the help!!

Regards
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list

[pfSense] Packages didn't install after upgrade from 2.0 to 2.1.1

2014-04-07 Thread Walter Parker
I upgraded my ALIX system running 2.0 to 2.1.1. The base upgrade appeared
to go fine, I got the screen that said the system was upgrading all of the
packages, but after the system restarted, none of the pacakges on the old
system were listed as installed on the new system.

But the service screen shows the old packages and the menus still have menu
items for the old packages (clicking on one causes a php error). Installing
the package from the package manager menu does work and the package then
starts working (but in the case of vnstat2, it now appears in the menu
twice).

What do you recommend I do to fix the problem between what package used to
be installed and what is currently installed.




-- 
The greatest dangers to liberty lurk in insidious encroachment by men of
zeal, well-meaning but without understanding.   -- Justice Louis D. Brandeis
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] Network Traffic Monitoring w/o Webgui

2014-04-07 Thread Brian Caouette

What about using mrtg to graph the various interfaces? Does PF support this?

On 4/7/2014 12:54 PM, Jim Pingle wrote:

On 4/7/2014 12:29 PM, James Caldwell wrote:

Happy Monday list...

Does anyone have a preferred way of monitoring over all traffic throughput for 
various interfaces via shell/putty instead of having to remain logged in to the 
webgui?  I have several alix based appliances that have had their ISP 
connections upgraded and I am trying to remain outside the web interface as 
much as possible due to the load that it puts on the system.

Any thoughts or experience is appreciated.

The iftop package is great for this.

Install it from the GUI and then from the shell run it like so:

iftop -nNpPi vr0

(Serving suggestion, salt to taste)

Jim

___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list


___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list


Re: [pfSense] pfSense version 2.1.1 has been released

2014-04-07 Thread Brian Caouette
I noticed everything stopped working after update. After a few days 
pulling hair I've found that disabling captive portal allows me to surf 
the net again. Problem being we no longer have security without the 
Captive Portal.


On 4/4/2014 11:58 AM, Jim Thompson wrote:


Please see the blog post
https://blog.pfsense.org/?p=1238

or changelog
https://doc.pfsense.org/index.php/2.1.1_New_Features_and_Changes

for details.

Happy upgrading.

Jim



___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list


___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] pfSense version 2.1.1 has been released

2014-04-07 Thread Brian Caouette
I love the CP. Have some nice customs screens made up for it. Not sure 
what happen.


On 4/7/2014 1:26 PM, Ryan Coleman wrote:
Good to know - we're pushing the CP at the pub in a few weeks and this 
would be troubling.



On Apr 7, 2014, at 12:25 PM, Brian Caouette bri...@dlois.com 
mailto:bri...@dlois.com wrote:


I noticed everything stopped working after update. After a few days 
pulling hair I've found that disabling captive portal allows me to 
surf the net again. Problem being we no longer have security without 
the Captive Portal.


On 4/4/2014 11:58 AM, Jim Thompson wrote:


Please see the blog post
https://blog.pfsense.org/?p=1238

or changelog
https://doc.pfsense.org/index.php/2.1.1_New_Features_and_Changes

for details.

Happy upgrading.

Jim



___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list


___
List mailing list
List@lists.pfsense.org mailto:List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list




___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list


___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] Network Traffic Monitoring w/o Webgui

2014-04-07 Thread Brian Caouette

What is Cacti? FOSS?

On 4/7/2014 1:42 PM, Walter Parker wrote:
I'd expect that you should be able to enable SNMP, set a non default 
password (please don't use public) and add a firewall rule to allow 
UDP on port 161 to/from your mrtg server. I'd recommend using Cacti as 
your mrtg server (if you want a FOSS solution).



Walter


On Mon, Apr 7, 2014 at 10:23 AM, Brian Caouette bri...@dlois.com 
mailto:bri...@dlois.com wrote:


What about using mrtg to graph the various interfaces? Does PF
support this?


On 4/7/2014 12:54 PM, Jim Pingle wrote:

On 4/7/2014 12:29 PM, James Caldwell wrote:

Happy Monday list...

Does anyone have a preferred way of monitoring over all
traffic throughput for various interfaces via shell/putty
instead of having to remain logged in to the webgui?  I
have several alix based appliances that have had their ISP
connections upgraded and I am trying to remain outside the
web interface as much as possible due to the load that it
puts on the system.

Any thoughts or experience is appreciated.

The iftop package is great for this.

Install it from the GUI and then from the shell run it like so:

iftop -nNpPi vr0

(Serving suggestion, salt to taste)

Jim

___
List mailing list
List@lists.pfsense.org mailto:List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list


___
List mailing list
List@lists.pfsense.org mailto:List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list




--
The greatest dangers to liberty lurk in insidious encroachment by 
men of zeal, well-meaning but without understanding.   -- Justice 
Louis D. Brandeis



___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list


___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] pfSense version 2.1.1 has been released

2014-04-07 Thread A Mohan Rao
I also faceing same issue after update. Then i reset factory then i restore
my previous backup but backup is not restore properly. Like captive portal
is not restore alias is not restore etc..
Finally i format my core 2 duo 4 GB RAM with 260GB HDD firewall then
recreate all policy etc. I suggest b4 is upgrade ur live pfsense everyone
need to test with another pc.

Thanks now i feel good after 6  hours steuggling..
On Apr 7, 2014 10:55 PM, Brian Caouette bri...@dlois.com wrote:

  I noticed everything stopped working after update. After a few days
 pulling hair I've found that disabling captive portal allows me to surf the
 net again. Problem being we no longer have security without the Captive
 Portal.

 On 4/4/2014 11:58 AM, Jim Thompson wrote:


  Please see the blog post
 https://blog.pfsense.org/?p=1238

  or changelog
 https://doc.pfsense.org/index.php/2.1.1_New_Features_and_Changes

  for details.

  Happy upgrading.

  Jim



 ___
 List mailing 
 listList@lists.pfsense.orghttps://lists.pfsense.org/mailman/listinfo/list



 ___
 List mailing list
 List@lists.pfsense.org
 https://lists.pfsense.org/mailman/listinfo/list

___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list

Re: [pfSense] pfSense version 2.1.1 has been released

2014-04-07 Thread Chris L
Does “custom screens” mean customizations to index.php as well?

captiveportal.inc and index.php always get whacked in an upgrade.

On Apr 7, 2014, at 10:46 AM, Brian Caouette bri...@dlois.com wrote:

 I love the CP. Have some nice customs screens made up for it. Not sure what 
 happen.
 
 On 4/7/2014 1:26 PM, Ryan Coleman wrote:
 Good to know - we’re pushing the CP at the pub in a few weeks and this would 
 be troubling.
 
 
 On Apr 7, 2014, at 12:25 PM, Brian Caouette bri...@dlois.com wrote:
 
 I noticed everything stopped working after update. After a few days pulling 
 hair I've found that disabling captive portal allows me to surf the net 
 again. Problem being we no longer have security without the Captive Portal.
 
 On 4/4/2014 11:58 AM, Jim Thompson wrote:
 
 Please see the blog post 
 https://blog.pfsense.org/?p=1238
 
 or changelog
 https://doc.pfsense.org/index.php/2.1.1_New_Features_and_Changes
 
 for details.
 
 Happy upgrading.
 
 Jim
 
 
 
 ___
 List mailing list
 
 List@lists.pfsense.org
 https://lists.pfsense.org/mailman/listinfo/list
 
 ___
 List mailing list
 List@lists.pfsense.org
 https://lists.pfsense.org/mailman/listinfo/list
 
 
 
 ___
 List mailing list
 
 List@lists.pfsense.org
 https://lists.pfsense.org/mailman/listinfo/list
 
 ___
 List mailing list
 List@lists.pfsense.org
 https://lists.pfsense.org/mailman/listinfo/list

___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list


Re: [pfSense] pfSense version 2.1.1 has been released

2014-04-07 Thread Chris Buechler
On Sun, Apr 6, 2014 at 11:39 AM, Josh Karli josh.ka...@gmail.com wrote:
 I think I've found a potentially serious bug in the upgrade process.

 I'm not getting this error but I am seeing something rather disturbing:
 before the update I was running 2.1-release amd64 and the update seems to
 have switched it to 2.1.1-release i386! All the normal things that happen in
 the UI when switching architectures are there: RRD can't graph the data due
 to error 1 (data is from another architecture), and a shell command sysctl
 hw.machine returns i386.

 I updated using the autoupdate feature with automatic rebooting.

 So basically your x64 2.1.1-release update is the wrong kernel version.

Not true. If you ended up on i386 after upgrading, then your
auto-update URL was set to i386. If you originally were running i386
and manually set the update URL at some point, then restored that
config backup to amd64 without removing or changing the update URL, it
upgrading to i386 is the expected behavior. You weren't pointing at
the default stable amd64 updates URL if you ended up with i386.
___
List mailing list
List@lists.pfsense.org
https://lists.pfsense.org/mailman/listinfo/list