Is this an upgraded system or a fresh install? I haven't seen this on a fresh installed system but I have seen this once on an upgraded system already. If it is upgraded, can you please reinstall it? I would suggest using one of the images from  http://pfsense.com/~sullrich/BETA2-BUGVALIDATION3/ .

Get a spinrite bootdisk and check your dirve when this happens. My bet is that your HD/CF is borked.
Spinrite fixes tons of issues and is well worth the money imo.

Thanks for all suggestions guys.
I solved it. Off course, I know about the possibilities of typing the IP address, but that's not an option for wife and kids.
Anyway, I solved it by editing the hosts file on each machine. It still wouldn't work untill I disabled the damned WinXP firewall on each machine. I wonder why M$ call windows user-friendly, aargh.
I feel great, outwhitting M$ for a change  ;D

@wjoyce:

What are the issues?  I would like to help out on this front if I am capable.

Well…1.0 isn't released yet.  Can't release 1.1 until that's out.  Then comes some amount of time for development of new features (this would be one of them - albeit developed already).  Then people test, eventually we get to beta, then release.

Three ways to help.  Write code, test and give good bug reports, donate something to help get the devs stuff they want/need for other pfsense work.

--Bill

Guess you're the only one to use this feature.  I can attest that none of the devs do.

–Bill

My 4801 locks up from time to time also.  It's got a wireless board in it too.  From what I've seen the 4801's ship with supplies barely big enough to handle the unit itself assuming the supply is 100% in spec.  I've seen low voltage supplies lock up 4801's with great consistency before.  This is probably power related.

–Bill

@sullrich:

When its ready.

LOL ;D

http://www.networksorcery.com/enp/protocol/igmp.htm

running the full install version here even without swap for month now and haven't seen issues due to that either.

block bogon is already unchecked, block private is checked.

can you clarify which you meant please?

Yeah, that's where I'm confused. sullrich seemed like he was implying that 'net.inet.icmp.icmplim: 200' was the reason this was happening. But it sounds like you're saying that this is happening because of something in pfsense. The thing I was mainly curious about is the reason 25152 is the limit, as opposed to another number.

@submicron:

Yeah, I only intend to use it for testing, but since it seems like I'm re-installing pfSense ever day or two for various testing, having a couple of VMWare images would be very helpful.

I make heavy use of workstations snapshotting and cloning features.  Very useful.

–Bill

I know the OSI model pretty well(layer 4 and lower). I just wanted to see if I understood this particular situation correctly.

Ok…how I'm able to run the script and I have IPv6 connectivity on the pfSense PC.

What is the best rule, for security reasons, to allow IPv6 traffic?

He's not talking about a firmware update but the new version of this specific file. Check http://cvstrac.pfsense.com/timeline or http://pfsense.com/cgi-bin/cvsweb.cgi/ or wait for the next release.

I agree, later down the road would be great for 1.0 I'm more concerned with the stability and scalability of the current feature-set.

That makes sense as this way the pfsense can't detect the linkdown and the pfsense is not killing the pppoe right after the first timeout. Should be no issue though.

That kind of spam appears about every week several times. We're trying to keep up with deleting them, however most of the things that are porsted as question to the faq don't belong there either.

Afaik there is no way to view the entries in a chronological order.