Ok, traced my steps *exactly* except I used VMware Server 1.0.3 and I get the exact same error. I also tried it on another physical machine running VMware server with the exact same results... So, it's not a Virtual Server issue or a hardware issue.
Where do we go from here? Dimitri Rodis Integrita Systems LLC -----Original Message----- From: Dimitri Rodis [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 17, 2007 3:31 PM To: support@pfsense.com Subject: RE: [pfSense Support] CARP, pfSense latest snapshot Ok, I can do VMware on that host machine also. I will give it a shot. For what it's worth, however, I have a number of fresh installations (meaning, I didn't attempt to upload a m0n0 config, but was set up from scratch) at other sites running just fine on VS 2005 R2. I'll post back later once I get it up in VMware server. Dimitri Rodis Integrita Systems LLC -----Original Message----- From: Chris Buechler [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 17, 2007 2:34 PM To: support@pfsense.com Subject: Re: [pfSense Support] CARP, pfSense latest snapshot Dimitri Rodis wrote: > > FWIW, this is running in a MS Virtual Server 2005 R2 SP1 virtual > machine, so it shouldn't have anything to do with the hardware, as > there are 10 other virtual machines running without issue. > MS VS is the hardware in this case, and can be extremely flaky with FreeBSD. It sounds like that might be what you're seeing. I'm pretty certain you won't be able to replicate that using the exact same config on real hardware or VMware. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
