Re: [pfSense] Upgrades to 2.4.3.x failing after updating metadata

2018-05-15 Thread John Kline
Many of us a e seeing this.

On Tuesday, May 15, 2018, 7:53 PM, Steve Yates  wrote:

I upgraded two routers from 2.4.2 to 2.4.3 and today to 2.4.3_1.  One is an 
SG-3100 and one is a PC.  On both, both times, the upgrade almost immediately 
fails, but if I try again it works.  I click the pending-update icon on the 
dashboard to go to System Update and it detects the update.  I start and I get:

">>> Updating repositories metadata... done.
2.4.3_1 version of pfSense is available"

Then a red bar at the top of the page, "System update failed!"

If I click the already-highlighted System Update tab again, confirm the update, 
it then immediately installs.

Is anyone else seeing this?


Steve Yates
ITS, Inc.

pfSense mailing list
Support the project with Gold!

pfSense mailing list
Support the project with Gold!

Re: [pfSense] Outbound NAT rule editing in 2.4

2017-10-25 Thread John Kline
I’m seeing the same thing adding or editing NAT rules (even after upgrading to 
   - Invalid characters detected fga9b0lcc6mv3=3=o4. Please remove invalid 
characters and save again.

On Wednesday, October 25, 2017, 1:43 AM, Doug Lytle  wrote:

On 10/24/2017 10:12 PM, Travis Hansen wrote:
> After updating to 2.4 I see this when opening all of my outbound NAT rules:
>    - Invalid characters detected "00". Please remove 
>invalid characters and save again.
> It shows that as soon as I open the rule for editing and also prevents me 
> from updating the rules.  Anyone else seeing this?
> ___

I see that 2.4.1 is now available, you may want to update and try it again.


pfSense mailing list
Support the project with Gold!

pfSense mailing list
Support the project with Gold!

Re: [pfSense] pfsense 2.2 (i386) - Soekris 6501-70 - Crashing once a day or so

2015-02-08 Thread John Kline

 On Feb 6, 2015, at 10:39 AM, Giles Coochey wrote:
 On 29/01/2015 12:47, Giles Coochey wrote:
 I was running pfsense 2.1.5 (i386) on my Soekris 6501-70 with an mSata disk 
 drive without any problems. 
 I recently upgraded to pfsense2.2 (i386) and it appears to be crashing once 
 a day or so. 
 Now that I've disabled read-only /var  /tmp it reports upon logging in 
 whether I want to send the crash dumps to the developers - for which I'm 
 saying 'yes' to. 
 Apart from that, I'm at a loss as to what the problem is, I can't read the 
 crashdump lingo, but I wonder if these crash dumps are being received, and 
 whether anyone else is experiencing an issue with Soekris 6501 hardware and 
 pfsense 2.2 (i386)? 
 Well... no response to the mailing lists, one offline response effectively 
 telling me that 2.2 is no good.
 My Soekris eventually crashed and did not manage to boot up again, so I'm 
 going to revert to 2.1.5.
 I have tried installing 2.2 i386 onto my mSata drive, but it doesn't even 
 post after the image is put to the mSata drive, so can only assume that 2.2 
 doesn't support the soekris 6501 hardware, or at least the mSATA ports.
 pfSense mailing list
 Support the project with Gold!
 pfSense mailing list
 Support the project with Gold!

For what it’s worth, I also have a Soekris 6501-70 with mSata.  My upgrade to 
2.2 went fairly smoothly.  I got no logs after the upgrade and had to 
clear/restart logging to get logs again.

Also, the reboot didn’t go well (I got the red error light) and I had to pull 
the power to get it to restart (possibly not related to the 2.2 upgrade).

pfSense mailing list
Support the project with Gold!