@heavy1metal:

The only thing I've noticed is after renewing it etc.. and I go to the lightsquid report, i have to refresh the actual page.

Did that too.

It's always happened, no way to add those users without doing so and it warns you there on that page.

@TooMeeK:

1000 miles? Just always use 2 routers, one as backup for remote management.
If this is a REALLY server it should has Remote Access card, like Dell PowerEdge or Fujitsu-Siemens Primergy has, and public IP reserved for this management card.

It's RC status not a stable release so you have to expect problems.
Yes it is "safe" to run the update on a live system but end users will experience disconnection while it reboots.
I can't comment on other hardware but the use of remote management on HP servers will not allow the media to mount correctly. I'm not sure why as it will mount both Current and Release versions of FreeBSD.

Thanks

That solved the problem

Finally got some time to sit down and scratch on this problem.

I am able to use openvpn to log into other location and ping target IP via Dyndns. ICMP returns are seen and are also seen in pftop.
Then, I used radmin at other location, again, via openvpn, and attempt to log into system here, where I am. No connection error seen at remote location. However, pftop see's the attempt.

I then uninstall Commodo firewall, restart, and re-try. Again, no connection error, pftop see's attempt.

I then, using windows 7, navigate to windows firewall and check the permissions. I almost mistake radmin viewer as the correct program, but this is incorrect as I am looking for rserver, which is located, in my system, inside the syswow64 folder.

Rserver is not listed as allowed. Rserver added as allowed and… bread, butter and cheese..it works!

So, I apologize for being too quick to hit RC2. She has had some rough days in the past, but this young lady is maturing nicely.  :)

Thanks for replaying…I've already fix the problem this morning by restoring to factory default, maybe it's just a misconfiguration on my side... thank you again.

Hi mdima,

I'm not using CARP. To me, the problem seems to happen randomly….

If someone needs more info, i'm willing to help

Regards,
Raclure

http://tinyurl.com/3b2uo93

i installed the PFsense version and not the PFhacom and it works !

so don't install the nanobsd pfhacom version.

For clarification, the problems I've been having with VMware have been for Workstation 7.1.4 (running on Windows 7 x64) I have just uninstalled this and installed VMware 6.5.5 and it looks to be working as it should, the wireless USB device also now connects correctly using USB 2.0.

Although I still need to do some more tests its looking promising  :)

Cheers,

Gareth

OK, that fixed it for us. thanks.

anyone knows what is the default queue size?

Should be fixed, looks like it was a case of not having anything in the <filter>portion of the config, it was trying to unset a value that assumed that section existed.

https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/d2903c0cabbcef2a324835ebee9e62c8852a58f7</filter>

Solved. Today I upgraded to 2.0-RC1 (i386) built on Thu Apr 14 10:42:41 EDT 2011. The error message is now gone. Thanks developers!

@GruensFroeschli:

Yes.
Create a virtual IP of "alias" type.

Damn wouldn't you know I just came here to post that I got it.

I was staring right at the "IP Alias" the whole time but never checked it.

After getting the IP what I had to do was define a gateway entry that pointed to that alias IP, then set a route for the subnet to use that gateway.  Finally obviously is adding a LAN rule to allow the networks to talk to each other.

Thx Gruens.

THere was a issue fixed lately which could cause memory starvation if you had dns hostnames in aliases.
Latest snapshots should have that fixed.

Otherwise check with others suggestions.