Ok thanks ill try this. Thanks for the heads up jigp Davao City 1.2.2

you but not the gtalk..gtalk wont log in imspector :( anyone? jigp Davao City 1.2.2

Whats the problem with double nating? Good morning jigp Davao City 1.2.2

Good morning :) How to install snort rules?Im not good in clit command…Anyone? jigp Davao City 1.2.2

I dont have squidguard. Imspector works in blocking msn. good morning jigp Davao City 1.2.2

Thanks, that resolved most of my blocked log issues. Meanwhile, can anyone help with my second question from the 1st post. Do Pfsense by default also limit each download thread to 4mbit?

Booyah!  Thanks for the link.  For some bizarre reason I knew about clicking on "save" in the interfaces menu but the subject line of that thread was so obtuse that I really don't even remember seeing it in my searches. So I'm only a little nuts.  Good. Just so long as others are aware and are working toward a fix. Thanks again.

@GruensFroeschli: MSN does work with the default settings. Version, hardware, setup, did you install any packages, what did you configure? (even if you say everything is on default, you had to do "some" configuration) Currently i'm using 1.2.3 RC2 based on FreeBSD 7.2 .. but previously I'm using 1.2.2 which also gave me the same problems as well Hardware Specification: Intel Pentium 4 3.0Ghz 1GB DDR400 Ram 2x Realtek Gigabit LAN card 1x Atheros Wifi card the only configuration i did was :- Bridging OPT1 with LAN Enabled Advanced Outbound NAT DNS Forwarder DynDNS Port Forward RDP,HTTP server ports Enabled uPnP

I definitely had to use AON and static ports with a client's VoIP system. The system would send out a UDP packet on (say) port 1234 and EXPECT the reply to come back on port 1235 - ie. (outbound_port + 1) Because pfSense would re-write the outbound packet to (say) 5678, the other party would reply on port 5679 - and it wouldn't go anywhere. By disabling outbound NAT for specific internal machines, the "send my a reply on the port I used, plus one" protocol (if you can call it that) remains intact.

Try a different web page over HTTPS. I had problem with mismatched MTU values which only showed up when HTTPS. If it fails on other HTTPS pages, double-check your MTUs.

Static port is only valid when using outbound NAT and with transparent bridge outbound NAT is not used.

n (put any number here) But the number of users isnt as relevant as how much bandwidth you want to push. Also you might run out of states. http://www.pfsense.org/index.php?option=com_content&task=view&id=52&Itemid=49 is a starting point how to size your pfSense.

Ok, i finally found the problem. There was no problem with the firewall, it was a problem of DNS.

Same as always: allow TCP from LAN net to any IP with port 80 destination (HTTP) and similar for HTTPS. If it doesn't work then you seem to have scrumbled a lot. Try a fresh and clean install instead.

Well i've managed to realise that the problem seems to occur during setup. After i've set up my internal and external VIP's, I configure Advanced outbound NAT (internal network –> WAN VIP). As soon as I do this, I lose connection to the internet (though I can still ping out?!). I hope this sheds some light...

Not sure if this is acceptable but: You basically want to access stuff on the LAN from the OPT. The problem is, that the server on the LAN doesnt know where to send the answer to. If you enable NAT from OPT to LAN, then the requests appear as if from the IP of the pfSense on the LAN side. Like this you dont need to change anything on the existing stuff. howto: enable advanced outbound NAT under "firewall" –> "NAT". there will be an autocreated rule for LAN-->WAN copy this rule and change it to OPT-->LAN