I have a working carp config at home. Have failed over several times the last
days, with 0.85.2 and 0.85.4 no session was dropped (I even was tunnelling from
a client behind the carpmachines to the office). DNS and DHCP is configured for
failover as well. I haven't seen any issues so far.
At 11:56 PM 9/26/2005, you wrote:
This file was introduced after 0.85.2. Are you sure you didn't update
filter.inc ?
i probably did. i think i was trying to pick up a bugfix. probably
not a good idea.
-
To
I am just curious why you failed over twice.. Why did your primary go down?
Todd
- Original Message -
From: Holger Bauer [EMAIL PROTECTED]
To: support@pfsense.com
Sent: Tuesday, September 27, 2005 6:41 AM
Subject: AW: [pfSense Support] 050.2 CARP won't go Master or Backup
I have a
Probably not when certain people split a dozen or so functions out
into their own file :) 0.85.4 has all the latest fixes. At this
time, there isn't much patched post 0.85.4 (unless you try running
ipv6 tunneling :)), I'd recommend moving to it.
--Bill
On 9/27/05, Dan Swartzendruber [EMAIL
At 09:28 AM 9/27/2005, you wrote:
Probably not when certain people split a dozen or so functions out
into their own file :) 0.85.4 has all the latest fixes. At this
time, there isn't much patched post 0.85.4 (unless you try running
ipv6 tunneling :)), I'd recommend moving to it.
already did,
Only problems I've had with carp recently weren't actually due to
carp, but the dhcp daemon. There's a hold down timer somewhere that
won't let it come up as primary for 300 or 360 seconds (my bet is
there two different timeouts, a 60 second timeout and a 300 second
one). So if you're running a
Ivan, aren't you running carp with PPPoE? If so, this will not work correctly.
Scott
On 9/27/05, Bill Marquette [EMAIL PROTECTED] wrote:
Only problems I've had with carp recently weren't actually due to
carp, but the dhcp daemon. There's a hold down timer somewhere that
won't let it come
Just wanted to update you guys on my situation looks like 0.85.4 may have
fixed my problem, been running successfully for about an hour now, will post
additional updates later, thanks for the headsup!!
-Jaimie
-Original Message-
From: Scott Ullrich [mailto:[EMAIL PROTECTED]
Sent:
OK, now it appears to still be dropping my connection but in interfaces it
still shows I have an IP address in the WAN, but if I do release, then renew
it works for about 5mintues.
-Jaimie
-Original Message-
From: Jaimie E. O'Neill [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 27,
HI
PPPoe is on WAN .. CARP is on LAN with carp sync on OPT1.
OK so you guys are going to laugh at me. I do feel stupid. As a fault finding
procedure and just to get connectivity back I halted router2, which is UTP
crossed over connected to router 1 on OPT1. So OPT1 (carp sync) is down. (no
On 9/27/05, Frimmel, Ivan (ISS South Africa) [EMAIL PROTECTED] wrote:
PS .. what does the update_files.sh thing do?
It's a script that pulls down the latest version of a file. It can
also be passed the -all flag to update all known files.
It's basically a upgrade mechanism for a single file to
On 9/27/05, Frimmel, Ivan (ISS South Africa) [EMAIL PROTECTED] wrote:
HI
PPPoe is on WAN .. CARP is on LAN with carp sync on OPT1.
OK so you guys are going to laugh at me. I do feel stupid. As a fault finding
procedure and just to get connectivity back I halted router2, which is UTP
The error is not on TF wizard..
I try clone rule for MS-RDP ( port 3389 ) to a another service
RADMIN ( port 4899 )
but I select TOS low delay and to throughput for this rule I get
this error and if I not select it's work fine.
2005/9/27, Scott Ullrich [EMAIL PROTECTED]:
This just
Are both supposed to be selected? I suspect for this to work we'll
need to convert those to the hex values and do a bitwise AND on them.
I trust you'll be able to test any changes we make?
--Bill
On 9/27/05, William Armstrong [EMAIL PROTECTED] wrote:
The error is not on TF wizard..
I try
Hi Guys,
I am pulling my hair out trying to figure this out.
I have PFSense now running on several boxes in different locations.
I am building a new firewall for a client and during the install I am
getting the following error on versions 80.0, 80.4, 85.0 and 85.2.
The error is as follows:
Try a different CD-ROM Reader. I've got this problem at work on a
machine as well.
Scott
On 9/27/05, Mike [EMAIL PROTECTED] wrote:
Hi Guys,
I am pulling my hair out trying to figure this out.
I have PFSense now running on several boxes in different locations.
I am building a new firewall
Return Receipt
Your [pfSense Support] CDROM Version Install
document:
Thanks for the fast response Scott. I will give that a try right now.
Mike
-Original Message-
From: Scott Ullrich [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 27, 2005 6:08 PM
To: support@pfsense.com
Subject: Re: [pfSense Support] CDROM Version Install
Try a different CD-ROM
FreeBSD is having love issue (see no) with your cdrom. It could be..
1. bad cdrom drive
2. bad cdrom
3. bad cable
4. sucky IDE chipset.
5. FreeBSD bug.
If you get a chance try a default install (just for testing) of FreeBSD
Beta 5 (or whatever the lastest beta of 6.0 is) and see if you get the
I'm seeing this problem since 0.85.2. the same cd-rom reader was working ever
since pfsense 0.20 for me :-/
Holger
-Ursprüngliche Nachricht-
Von: Fleming, John (ZeroChaos) [mailto:[EMAIL PROTECTED]
Gesendet: Mittwoch, 28. September 2005 00:12
An: support@pfsense.com
Betreff: RE:
Yes, s0ren changed tha ATAPI CDRom code recently. :/
Scott
On 9/27/05, Fleming, John (ZeroChaos) [EMAIL PROTECTED] wrote:
If you get a chance try a default install (just for testing) of FreeBSD
Beta 5 (or whatever the latest beta of 6.0 is) and see if you get the
same issues.
:)
ok, I have experienced some strange problems bringing up CARP-Interfaces here
as well (quite reproducable but also a bit sporadic). Scott did several changes
and he finally came up with something that now is running on my systems without
any problems any more (my systems are also syncing via a
The only thing left to try is:
http://wiki.pfsense.com/wikka.php?wakka=BootTroubleShooting
Scott
On 9/27/05, Mike [EMAIL PROTECTED] wrote:
OK I have tried 3 CDROMS and 3 floppy drives with no luck. All the CDROMS
and Floppy drives are good with 1 new of each in that mix.
I have tried a
Anyway, I downgraded to 70.4 and all is well. Manual upgrade to 85.4
and I have the same issue of not getting a DHCP address and the same
errors. Also, after the 85.4 update if I go to Manual Update I get
Unable to Receive Version Info. I'll look into this DHCP error a little
later, as I have seen
On 9/27/05, Jeff Quinonez [EMAIL PROTECTED] wrote:
Anyway, I downgraded to 70.4 and all is well. Manual upgrade to 85.4 and I
have the same issue of not getting a DHCP address and the same errors. Also,
after the 85.4 update if I go to Manual Update I get Unable to Receive
Version Info. I'll
25 matches
Mail list logo
