Go to https://www.grc.com/x/ne.dll?bh0bkyd2 and hit proceed. Then click one of the desired scans. It will scan your from the internet and report back in a html page what's open, closed, stealth,…

http://whatsmyip.org/ports/ offers a similiar service.

you could also place some scripts in /usr/local/etc/rc.d/ to run after the system boots. Make sure to chmod +x the script. I had to do this because pfSense didn't seem to properly bring up my aliased IPs on my WAN interface.

Yep, this has been pointed out on both the mailing list and the cvstrac bug tracker.  Both places have the recommended fix.

–Bill

Please open a ticket at cvstrac.pfsense.com and include as much info as possible. Thanks!

Oops, forgot the javascript, lol.

// the routine for the info center upshrink echo ' '; //This is for the pop menus echo ' '; echo ' ';

That starts on line 144, it should anyway, highlight the lines all the way down to the tag and replace it all with the previous code.

@caps_phisto:

Noticed a quirk.  It seems that I was overrunning the default state table size.  I've noticed it for a while but didn't think anything of it until I read this post http://forum.pfsense.org/index.php/topic,71.0.html.  I have over 400 users here so I would assume based on what was posted there 10k States just isn't enough.  This also correlates with the times that the connection "goes down", as it normally goes down during high traffic periods(noon/after dinner).  I have reset the Max States to 1million.  As the post above stated it was under System -> Advanced.

Thanks.

Back to waiting…

10K -> 1 million is a helluva jump.  You might want to scale that back some…say to 100K or 200K? :)  This thread might be useful to you http://marc.theaimsgroup.com/?l=pfsense-support&m=114771925530407&w=2

–Bill

Thanks, this is fixed. Basically you have installed a package of some sort and on bootup the package is not found.  You may have to remove the package info from /cf/conf/config.xml and then delete /tmp/config.cache

Does anyone have a Script to share capable of monitoring task(s) something like this ? …

1. Verify T.1 Task(s) are active process(es) in good condition as far as can reasonably be determined, if not take T.2 action.
2. If any T.1 Task(s) are consuming over C% CPU, checked every I time interval, occuring R number of times in a row, then take T.2 action.
3. Check the system.log every I time interval for occurance(s) of L.1 string list, if found take L.2 action.
4. If ping times to P.1 host are above P.2 ms, checked every P.3 time interval, occuring P.4 number of times in a row, take P.5 action.

Example Constants I define: T.1=('olsr','dnsmasq') : T.2=('reboot', 'restart'), C=30 %, I=30 sec, R=3, L.1=('hardware failure','halted') : L.2=('reboot','reboot'), P.1='192.168.1.1', P.2=500 ms, P.3=30 sec, P.4=5, P.5='reset ath0'),  -- actions: 'reboot'=reboot, 'reset ath0'=reset interface, 'restart'=run /usr/local/etc/rc.d/'T.1'.sh but if restart or reset fails or is triggered again within 12hrs then reboot.

If not, I may post a small bounty.
Thanks,

Pete

Thanks for the answer and the alternative solution.

Today I saw it again, so i took a picture, then rebooted, and still remained the same.

Is there something I can send you, to help in the diagnose?

a section of 192.168.0.1/status.php for example?

Is there a reset, or cache clear, command for the queues?
192.168.0.1/status_queues.php?reset=true or something similar?

I don't mean to bother u guys with nonsense, i'm just curious. be well :-)

It's Automagically(I learned this neat word from billm) normal again! weird.

@rds_correia:

And also look at those short cable fixes.
I never knew why m0n0wall doesn't complaint about short cables on my system while pfSense always warns me about it.
Even because my cable ethernet cables are now both 5 meter long…
I would be much more relaxed if I didn't see those warnings once every 5 minutes but I gotta level it with you

That's probably because m0n0 isn't running RELENG_6_1.

–Bill

It pings the monitor IP of the link every 5 seconds. If the ping fails the link will be excluded from the pool until it comes back.

OK Different box, same hardware basically and on a HD, Firefox, and runs just fine. Very snappy!
Changing Time Zone took 4 seconds, not 25.
Whew, that's a relief!

and yeah, I could have using IE60SP0 yesterday, it's got that 'slow finish' . reproducing it now, but my benchmark, Time zone still doesn't take forever like it was.
I'll re-check that box Fri or Mon when it's plugged in on location.

On the floppy, seems like I noticed 98) even with a config'd floppy, and I thought it strange. But it might have been on a interface mismatch, but before reboot…
Yes, manually copying the file over is what I ended up doing.

Thanks for the comments.

Woow :)
Nice i will try it asap ;)

@sullrich:

Install the darkstat or ntop package from System -> Packages.

ntop and darkstat is a start of something… but It is not what I need....  have posted a bounty on this one :)

Ok, I updated to 1.0-RC3

It works  ;D

Auto-solved ^^

You probably should start with deciding how many zones you need. A typical setup to start with would be 3 nics in your pfSense (WAN,LAN,DMZ). Depending on usage a 4th nic for "home use" might make sense that is only able to connect to the internet but to none of the other subnets. Put the servers that should be available from the internet to the DMZ. The other trusted machines go to you LAN subnet. Untrusted machines go to the "home use". You can setup DHCP individually for each internal subnet at services>dhcp.

Now create the additional IPs you have at your WAN connection using firewall>Virtual IPs. You can use them then for portforwards to your servers.

Create firewallrules between the different subnets with appropriate rights at firewall>rules (like pass LAN-> DMZ; block DMZ -> LAN;…). Setting up aliases for ports/hosts can keep the amount of rules low and makes reading/changing firewallrules later easier.

You also should enable nat reflection at system>advanced as it usually makes using a DMZ from other subnets easier.

Can't reproduce this.

Modify the /etc/inc/system.inc file - the /etc/syslog.conf is build in there.