The snapshot server isn't meant to be navigated manually, and definitely not by people who have any doubt about what they're doing. :-)

The 2.0.x pages (your first links) are not meant to be linked anywhere right now except directly via the links in my forum thread for 2.0.3. We only have that on because of the problems people had with 2.0.2. Using 2.0.3 snapshots is safe, but it's best to follow the links there from the forum thread to read the explanation there.

@Abdsalem:

Interesting you mention squid rule creator, where have you seen this? I finally got multi-wan+squid+auto outbound NAT working (after switching the damned sticky conns off lol..with it on, only WAN was passing traffic) and looking to fine tune my squid rules or re-create them entirely.

I mean samekind of setup as watchguard (and similars) have, you just click porn and apply that, then you almost certain can't see any porn.

Thanks Jim, I got confused between the 2 now you've pointed it out.

I can see what you mean there would be no room for it under the menu banner.

I have a set of forums up and get hammered daily with spammers.  I've beaten them all using SMF, two addons, and logic questions.

I use httpBL and OS & Browser Detection as my two addons.  httpBL also leverages Project HoneyPot, which is real nice.  They're both stable and stop a majority of the spammers outright.

I also use a logic question that cannot be solved by bots.  In SMF you can ask questions and receive answers during registration.  One question can be something like "Write the answer to the first question here again."  A bot cannot understand that, and you can always change that question to ask for the second or third answer.  I've also asked for answers to be spelled backwards and numbers to be spelled out.  It stops 99% of the bots out there.  I think in the past year I haven't gotten a single spammer registered with a constant 50 attacks per day.

I'm running SMF 2.0.2 but I think the mods will work in your version.

I emailed you. Thanks!

It's now 3 days since I emailed wikiadmin@pfsense.org for a Wiki Account and have not heard as yet.

If something is actually relevant, someone can click 'report post' and ask a mod to unlock the topic. (Or start a fresh thread to ask about it, and link back to the old thread)

It's fairly rare, but we have had people come back months/years later to update a forgotten thread they started or were talking on to share a final resolution or workaround. In that case, one of us unlocks the thread and they can post in it no problem…

Occasionally we'll go back and edit a locked thread if it turns up high in Google searches for a particular topic as well, to lead people to better/more accurate info. In those cases if the thread were unlocked it would probably get a lot of irrelevant posts that would be better served by new threads.

Ok I have corrected the first entry.  And pointed to the tutorial from the tutorials section, that other link must of expired, ie no longer existed.

the other item doesn't make any sense - someone else must of edited the docs section already for what you were talking about.

Your best bet would probably be to contact the author of apinger (util used by pfSense to monitor gw up/down status)

@TooMeeK:

Does this server run in virtual env + snapshots?
Are there additional plugins?

Source for SMF 2.0:
http://download.simplemachines.org/

I see many queries to this server (because many people read / post), are You sure Your hardware is capable to serve it? And will with SMF 2.0?

This is a known problem with SMF 1.1.16…  It is not a problem with SMF 2.0.2 which I can confirm...

thanks, reported that to the admin of that site (I don't have an account there).

Cool. Didn't see that setting before. Thanks!

There have been a few such threads in the "General Discussion" board here, feel free to start a new one. Things change from time to time so people will probably chime in and show off what they've done.

The General Discussion board isn't so high-volume that we'd need to filter things like that out yet, so having a separate board wouldn't be a good idea (unless we start getting dozens and dozens of threads there about the same topic :-)

@cmb:

If you push it out to the branch level, that's easier, your description made it sound like you wanted to recreate Plixer's Scrutinizer product from scratch or something similar.

But in this situation i cant see traffic statistic per user in branch? Its not usable for me :(
I think in my case netflow collector are needed (on LAN interface before NAT), and need to combine login+logout time for user with timestamp+IP+data block size in netflow log.
AFAIK, it is possible to do by standard freebsd tools + some corrections is web scripts. Isn`t it?

Wurf!  I was thinking of holding off til the new release, but it looks as tho it might be a wee while yet.  Beaucoup de ta.

Just add the hostname to an alias and don't bother with the intermediate step. :-)

Ok, so no https there.
Thx for answer.