Update happens once per month. What makes you think it does not?

Take a look in the Multi-WAN forum

@blak111: I'm not sure if the factory restore clears this directory, but check /conf/backup. Looks like it does. All my config.xml files are current rule sets. Thank you anyways, Ive pretty much been piecing it back together for the past few hours watching what is blocked and tracing it to the source and determining what the traffic is. I know that I will be backing up my config this time. Thanks again for the help!

Quote so when i added my vlans, LAN1 could talk to LAN2. these were all various nanobsd installs. Did you make sure that you didnt mix tagged and untagged traffic on the same NIC? probably, 1 of the physical nics is untagged and the 2nd nic has 4 x tagged vlans on it. i haven't tried crossing from 1 vlan to another vlan. i would assume that this wouldn't work. i'll dig a little deeper tonight i think.

After some investigation I came to the conclusion my Wan an Lan were switched. That was the reason the ports were open. Thx for the response. this can be closed.

Take a look there: http://doc.pfsense.org/index.php/FTP_Troubleshooting

Hello again. It seems that NAT reflection was the problem. I was just so sure I tested the ports from my home-computer, which has a different WAN IP and not in any way connected to the pfsense LAN. Well it worked, and I'm very grateful :) Thanks, Sune W.

Thank you! :)

@timurx: Why can't pfsense rules be formulated based on url references? Because pfSense uses pf and not ipfw. (except the CP and shedules).

FINALLY!!! I got it to work! The solution: I used OPT1 or OPT3 for the incoming connections, change this to WAN All devices connected where configured with static IP addresses, configure for DHCP and set up DHCP-server on LAN Make some NAT and firewall rules to LAN & WAN +> Problem solved! Eugene thanks for the support so far!

Sounds like a problem with your Squid configuration, but from your lack of useful information (eg, phrases like "etc etc") it's hard to help you. How about you start by providing the version of pfSense and Squid you've installed, along with details for all the other packages.  A note of all the settings you changed from the defaults for squid will be rather important too.

no don't have anything listening. (wouldn't even know how to setup a ftp server lol). ive checked the box on the wan side but no matter what i do cant close the port… dono what to do guys, im at a loss . is there not maybe something else im doing wrong? - cards are bridged? thank u again for ur help guys

I have played around with this and I still can't get the system to block browsing access after hours. I will continue to try but I then realized that if I block browsing access will these also block me from being able to RDP into the domain? I have set the schedule and created the rule but still no block, has anyone here successfully stopped browsing access according to schedule?

Hi I'm having some issues setting this up ifconfig gif0 create ifconfig gif0 tunnel lan.ip.1.1 broker.ip.here.142 up ifconfig interface0 inet6 IPv6:Prefix:here::1 prefixlen 64 alias route add -inet6 default fe80::%gif0 where lan.ip.1.1 is that my lan interfaces ip(192.168.0.1) or the computers ip(192.168.0.5)? where interface0 is that my lan interface or my wan interface? where IPv6:Prefix:here:: do i set that too the Client IPv6 address i got from tunnelbroker.net? does anything need to be changed in the last line? and… netsh interface ipv6 6to4 set state disabled netsh interface ipv6 set privacy disabled netsh interface ipv6 add v6v4tunnel mytbs 192.168.1.1 202.157.186.227 netsh interface ipv6 add address "Local Area Connection" 2001:db8:ff:ff::1 netsh interface ipv6 add route 2000::/3 mytbs publish=yes where  192.168.1.1 do i put my computers ip or my lan interface ip? do i use  2001:db8:ff:ff::1 or do i replace that with my Client IPv6 address i got from tunnelbroker.net?

I had the same problem once but it was related to bogon networks, my file with non-allocated reanges was not uptodate. Packets dump would definitely help here.

A reboot did the trick! :) Sorry, I just installed it and so I am still learning… Thanks, Jens