I have just upgrade from 84.6 to 85.2 (on wrap),
modifying a firewall rule I got this error
Warning: touch(): Unable to create file /filter_dirty because Read-only
file system in /etc/inc/filter.inc on line 57
regards
Rodolfo
My view is that wireless can be considered in the same way
The Net it. Unsafe. Howver generally people on it are uninterested in the data
passing across it just because of sheer volume. If you have data that is
sensitive or you just don't want people to view it use tunneling, that's what
Ipsec
Just some more info:
cpu usage stay at 100% (it's the backup firewall), here is top output:
last pid: 81653; load averages: 1.61, 1.50, 1.36up 0+00:59:28
09:47:25
23 processes: 1 running, 22 sleeping
CPU states: 0.7% user, 0.0% nice, 1.4% system, 1.4% interrupt, 96.6%
idle
Mem:
0.50.2? I guess you are talking about 0.85.2, if not upgrade! ;-)
I only have experienced such problems if the carpinterfaces didn't match the
real ip/subnet-range of the real interface the carp interface is running on.
Another thing to try is to manually disable and enable CARP at
Hello,
Maybe this is a stupid question, in that case im sorry.
But where can i find the latest image for a wrap system.
And what size does my compactflash card has to be?
I am new to pfsense, so forgive me my question.
Greetz,
Michiel de Jager
On Mon, 2005-09-26 at 09:51 +0200, Rodolfo
Go to http://pfsense.com/index.php?id=22 and follow the link New Installs.
Choose a mirror near you and download the embedded image (like
http://pfsense.iserv.nl/downloads/pfSense-Embedded-0.85.2.img.gz ). Once you
have a version Installed you'll find mini wrap upgrades in the
downloadsection
Just a question (and maybe something I've overread in your original mail). You
have pppoe on WAN. Is your CARP-Interface for WAN or for LAN? pppoe and dchp
interfaces won't work together with CARP. You need at least 3 static IPs on WAN
for this to work (1 for the master, 1 for the backup and 1
Holger Bauer wrote:
After reboot (third), carp interface goes up (as backup).
The interface is a wan interface, but I have a router in front of it and
not a modem
Take care that this was an upgrade from 84.6 (working nicely) to 85.2
Now primary is a 84.6, secondary is 85.2
regards
Rodolfo
Can you try to upgrade the second machine to 0.85.2 as well? I doubt that the
latest changes (not only pfsense related changes but freebsd carp as well)
prevent two machines with different versions to sync properly but this is
something you should try next.
Holger
-Ursprüngliche
Holger Bauer wrote:
H, the second machine is master
I have tried adding a rule to master and backup got this rule without
problem,
I am not sure if carp sync works well, I tried rebooting the master and
backup became master without problem, but cpu remained at 100%
regards
Rodolfo
Can
Scott Ullrich wrote:
# cat platform
wrap
regards
Rodolfo
This is not correct. WRAP's should be running on a memory mounted /tmp/
What does /etc/platform say?If it does not say wrap, pleae change
it and reboot.
Scott
On 9/26/05, Rodolfo Vardelli [EMAIL PROTECTED] wrote:
I have
Oddly I haven't seen this on my wrap installs :-/
There was a broken commit of /etc/filter.inc that would have exhibited
this behavior on a wrap, but that didn't make it into 0.85.2 (just
confirmed on one of my installs)
Warning: touch(): Unable to create file /filter_dirty makes me think
we
I'm still running 80.2 and thought I would mention my issue - in the
unlikely event that the VPN code has not been updated since that
release. So, If this hasn't already been spotted and resolved, keep
this in mind when you are working on VPN components.
I have 2 IPSEC VPN tunnels which run
Try checking System - Advanced - Prefer old IPsec SAs
The IPSEC code has been sync'd with m0n0wall since that version.
Scott
On 9/26/05, Ted Crow [EMAIL PROTECTED] wrote:
I'm still running 80.2 and thought I would mention my issue - in the
unlikely event that the VPN code has not been
Yep, there was a small typo in filter.inc. It's fixed now.
Scott
On 9/26/05, Bill Marquette [EMAIL PROTECTED] wrote:
Oddly I haven't seen this on my wrap installs :-/
There was a broken commit of /etc/filter.inc that would have exhibited
this behavior on a wrap, but that didn't make it
update_file.sh /etc/inc/filter.inc
On 9/26/05, Rodolfo Vardelli [EMAIL PROTECTED] wrote:
Scott Ullrich wrote:
Where? So I can fix on my board
regards
Rodolfo
Yep, there was a small typo in filter.inc. It's fixed now.
Scott
On 9/26/05, Bill Marquette [EMAIL PROTECTED] wrote:
N...don't do that :) I split the shaper code off into another
file, you will break if you simply follow this.
/etc/rc.conf_mount_rw
touch /etc/inc/shaper.inc
/etc/rc.conf_mount_ro
update_file.sh /etc/inc/shaper.inc
update_file.sh /etc/inc/filter.inc
--Bill
On 9/26/05, Scott Ullrich [EMAIL
Bill Marquette wrote:
Now I get this:
Parse error: parse error, unexpected T_IF in /etc/inc/shaper.inc on line 129
regards
N...don't do that :) I split the shaper code off into another
file, you will break if you simply follow this.
/etc/rc.conf_mount_rw
touch /etc/inc/shaper.inc
OK, here is what I have hardware wise:
CPU: AMD Duron 950 Mhz
RAM: 256 MB not sure of the brand
Hard Drive: Maxtor 5T02oH2 20GB
Motherboard: Soyo with a Via Chipset
WAN NIC: Onboard Realtek (I think it's a RealTek) on a Soyo
LAN NIC: Linksys LNE100TX unused interface
Opt 1 (DMZ) NIC: FA310TX
update_file.sh /etc/inc/shaper.inc
There was a missing ;
On 9/26/05, Rodolfo Vardelli [EMAIL PROTECTED] wrote:
Bill Marquette wrote:
Now I get this:
Parse error: parse error, unexpected T_IF in /etc/inc/shaper.inc on line 129
regards
N...don't do that :) I split the shaper code
Please gather that John requested and send to the list.
Thanks.
On 9/26/05, Mojo Jojo [EMAIL PROTECTED] wrote:
OK, here is what I have hardware wise:
CPU: AMD Duron 950 Mhz
RAM: 256 MB not sure of the brand
Hard Drive: Maxtor 5T02oH2 20GB
Motherboard: Soyo with a Via Chipset
WAN NIC:
Just to be clear, if the boxes goes down again run those commands again
without rebooting the box.
-Original Message-
From: Scott Ullrich [mailto:[EMAIL PROTECTED]
Sent: Monday, September 26, 2005 10:35 AM
To: support@pfsense.com
Subject: Re: [pfSense Support] Argg! My PfSense just died!
Did you send in your config.xml?
BTW add this to the list of commands to run (at the top).
( ifconfig -a ; echo ) /usr/crash.info;
-Original Message-
From: Mojo Jojo [mailto:[EMAIL PROTECTED]
Sent: Monday, September 26, 2005 10:24 AM
To: support@pfsense.com
Subject: Re: [pfSense
I have not received anything.
On 9/26/05, Fleming, John (ZeroChaos) [EMAIL PROTECTED] wrote:
Did you send in your config.xml?
BTW add this to the list of commands to run (at the top).
( ifconfig -a ; echo ) /usr/crash.info;
-Original Message-
From: Mojo Jojo [mailto:[EMAIL
I agree with you 100%. If you have sensitive data then yet it should either be
going over a wired connection or a secure tunnel/vpn when going over a wireless
connection.
My point was that adjusting the TX power does serve a purpose though. In many
situtation were you want to try to prevent
Not yet guys, tryin' to keep up, had a real busy day and night :)
I will try to get all this together soon and send it. Just wanted to get you
the hardware info while I was in front of it this morning.
Todd
- Original Message -
From: Scott Ullrich [EMAIL PROTECTED]
To:
Dear Team,
I currently am having miscellaneous issues with your software which did not
occur until just recently. I believe my NIC died, and so I lost connection
with my ISP via my WAN. I replaced my cable modem since I thought itwas this,
which is fine, but I also replaced the NIC, and now it
This file was introduced after 0.85.2. Are you sure you didn't update
filter.inc ?
Scott
On 9/26/05, Dan Swartzendruber [EMAIL PROTECTED] wrote:
I was unable to connect to my pfsense a few minutes ago. Running
0.85.2. The webGUI got a strange error about being unable to create
a pipe.
This was fixed after 0.84. Please upgrade to the latest version.
Scott
On 9/26/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Dear Team,
I currently am having miscellaneous issues with your software which did not
occur until just recently. I believe my NIC died, and so I lost connection
Awesome man thanks for the update, what is the most recent 0.85.4?
-Jaimie
Quoting Scott Ullrich [EMAIL PROTECTED]:
This was fixed after 0.84. Please upgrade to the latest version.
Scott
On 9/26/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Dear Team,
I currently am having
Yes, thats the current Full Update version.
Scott
On 9/27/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Awesome man thanks for the update, what is the most recent 0.85.4?
-Jaimie
Quoting Scott Ullrich [EMAIL PROTECTED]:
This was fixed after 0.84. Please upgrade to the latest version.
31 matches
Mail list logo
