Thank you very, VERY, much!! The "sloppy state" is the answer to my issue!

It's much easier to type it out than dictate this kind of material. The chances of someone interpreting the dictation wrong are near 100%, and fixing what they misinterpreted would probably just as long as doing it ourselves in the first place.

The only cure is time, really.

@jimp:

We will announce it on the blog when it's out. We're making progress on it, but not as much as we'd like. It will be out sometime this year, hopefully sooner rather than later, but finding time to update the content (and write all new stuff for IPv6) is a lot of work.

Ok I look forward to it, Thank you for your time.

Open to suggestions there. It's a fairly complicated topic though, hard to boil it down to a simple table these days.

You also have to consider pps, packet size, the NICs being used, etc.

The table is just a general guide but it could use a couple of intermediate steps (Such as ~400 Mbps can be done on an Atom)

If anyone has some solid data – from actual pfSense installs -- of throughput achieved and the circumstances (cpu type, nic, packet size, pps/bps) it would help.

Seeing a FreeBSD or Linux benchmark on the hardware isn't very useful of course, it would need to be data from traffic passing through pfSense.

Bonus points for VPN speed with several different ciphers. (As in http://forum.pfsense.org/index.php/topic,27780.0.html )

Amazon had flagged some formatting issues in the book, last I heard the publisher was working to fix it up and get it posted again. It looks like the Kindle version is available again now.

Processly that are run 'nicely' are low priority and do not steal cpu cycles from other important processes.
See: http://www.freebsd.org/doc/handbook/basics-processes.html

Steve

It's in the print copy. If you have a PDF copy missing images, contact the company you got the PDF from for an updated copy.

The only legitimate online sources of the PDF (BSD Perimeter for pfSense commercial support, and Applianceshop.eu) both have copies of the PDF with all images included.

It's not much of a wiki when it's overrun by spammers, either. :-)

If you really want an account, just mail us at wikiadmin@pfsense.org, but don't make any giant changes like reorganization without asking first.

It isn't really all that haphazard/random, though there could be some better distinction between How-Tos and FAQs.

Unfortunately, the new services (caller id on-screen and remote dvr) require more than port forwarding…the router reports its status (including WAN address) to VZ and if it's IP is not on the edge WAN (VZ provided routable IP) it won't provide those services.  There is a very good FAQ on dslreports about using another router with the Actiontec/Westell provided by Verizon:
http://www.dslreports.com/faq/verizonfios/3.0_Networking#16077

And a thread on the dslreports Verizon FIOS TV forum about putting your own router in front of the VZ router and retaining full functionality.  Bit of a kludge but reading through the thread, there are a couple of ways to do it:
http://www.dslreports.com/forum/r23764746-Re-FIOS-TV-Central-website-access-with-Non-AT-Router

None of this is limited to pfSense, of course.  And it only applies if you subscribe to VZ TV as well as internet.  If you only subscribe to VZ FiOS Internet, you can use any router you choose.

Any router other than the VZ-supplied one connected to the ONT will require an ethernet connection, as omegadraconis points out.  On the initial install, most techs will willingly activate the Ethernet port on the ONT if there's cat 5 available at the ONT location.  If not, calling the FSC as he details works.

I'm using pfSense behind the FiOS-supplied Actiontec (Actiontec LAN ---> pfSense WAN) with no problem, even though it's double NATted.  That said, I don't routinely do torrents or game, both of which can be adversely affected by this setup.  I do have ethernet to the ONT and plan to try putting the pfSense box in front when I can get everything in place and plan for some down time.

@bunny:

This doesn't seem to work atm with flash based ads and text based ads(google ads). It does not collapse most ads either. In other words, if you're using firefox then using the adblock plus plugin will work better than this even if they filter the same ads. The reason it doesn't work for everything is because it is not editing the html sent over the net. It is just blocking urls for anything that tries to pass through squid which is pictures. Anything that is dynamic like most flash ads or websites like, for example, hulu.com do not pass through squid. If anyone knows how to block flash ads, block the text type ads, and collapse blocked ads then please let me know!

Thanks for the tutorial!
Would using this setup along with Adblock solve the problem? Especially the collapse issue?

I'm not sure how MediaWiki handles this. It would be nice if you could just make the same page have an English and Russian version, but I haven't ever tried to do any multi-lingual stuff with it.

If that can't be done, it might be better to have it as a separate site, rather than one large mix of pages in multiple languages. The topic has come up before but I don't know if anything ever came of it. cmb might have some more insight.

People learn different ways. I for one, am a visual and hands on learner. However, if the instructions are clear and concise, I will be able to manage. Not to mention, reading instructions are quicker since I can scan for what I am looking for, skip parts I know i've already accomplished etc. I know where to go because I can see the instructions as a whole. I video is too linear.