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.

These are the official videos of the Whoppix release wich is now the Whaxx release (slackware live CD instead of knoppix). This distribution is the swiss army knife of the hacker or IT security profesional ;-)

Could also be the traffic shaper.  Disable the traffic shaper and give it another try.

Take a look at http://www.hamachi.cc that's all you need to crate a safe virtual network to play games with your friends without messing with the configuration you already have to access the school LAN.
BTW there are a lot of games community already set but you can always create your own.

@thinair:

I just installed 0.94.12, and my PPPoE DSL connection came up with no issues.  Anything you need to know in particular?

Nope, thats about all I needed to know.  Thanks

@sullrich:

@Jesse7:

Heh yeh,  but I don't post from that IP on these boards not that anyone could get my IP from these boards so no one has any way to find me :).

Not that anyone from here would aye??? :P

It's probably my short password that foiled whoever heh.

Ever heard of automated random ssh scripts?  Doesn't matter who or where you are.  If you leave yourself wide open, they will find you.

True,  it's probably what the above was,  I have fixed those two little problems anyways.  Thanks for the tips.

Any card marked with a+b+g 108mbit is atheros based. 3com pci card is atheros based. if you check out google and search for atheros based cards you will find loads of them. But as I said, any 108mbit a+b+g card is atheros based. The madwifi guys maintains a rather large list of supported cards: http://www.madwifi.org/wiki/Compatibility

Thanks for the tip Hoba ;).
Cheers

After I upgraded to 0.93.2 I got some issues with dhcp client, after doing some tests the problem was due the NIC, replacing the WAN Nic to other vendor not 3COM, the problem was solved.

I have to add that I'm running my 0.93.2 version since sunday with no problems, and the performance was really improved, I used to have a 60-80% CPU utilization with previous versions, but now it runs smoothly at 5-10% !!!

I'm running TrafficShapping, NTop, and squid on the box, and everything is working superb…

Congratulations again to the pfsense crew, outstanding job!!!

Emanuel Gonzalez
Guatemala

@torsten:

would like to see cvsup support.
anything planned?
Torsten

Say what?  We have our own upgrade infrastructure.

Never said it did  :)  All I said was that it was the last event in the system logs.  But thanks for the input!  Hey, can I make a suggestion for the wake-on LAN bit, where you use MAC addresses.  A timing option so you can say to all the machines in the list wake at 9am (as an example)

AIMsniff is also fairly limited and breaks almost everytime a new version of AIM comes out.  Also, if you look at the code for AIMsniff you'll see why its not really a good idea to run it on a critical network asset like a firewall.