I haven't seen that behavior at all, but then I don't use blacklists with squidguard.

It may be that the squidguard package is removed (and the blacklist files with it) and then when it's reinstalled, it doesn't redownload the blacklist files without manual intervention. That may take some extra coding on squidGuard to make happen, I'm not sure.

Squid Package > Traffic managment

If you assign a mask to the limiter then it will be applied per IP address, otherwise, all traffic matching the rule.

I need bridge because of some F##### protocol like dlna/upnp between my wlan and my lan …
If i use different subnets, some hardware won't running properly...  >:(

Yes, latest snaps are working fine.

@jimp:

@clarknova:

Do your 2 WAN connections use the same gateway? I know this doesn't work in 1.2 but I'm not sure about 2.0. I'm thinking no after reading your post.

No, it doesn't work on 2.0 either.

After telling a few people this myself they tried anyways and it does indeed work. I'm now using this so I didn't have to put a router in to change the gateway. It does work but I'm not able to access one of the modems on it. Fine with me. Using Google DNS btw.

pfsense 1.2.3

pfctl -vsr

Just to let you know:

2.0-BETA4  (i386)
built on Tue Oct 19 20:04:27 EDT 2010
FreeBSD 8.1-RELEASE-p1

Squid 2.7.9_4
squid guard 1.4-2

No problems.

Many thanks ….

Same issue here:
Thanks to this topic, I've fastly found a weird <vr0>in the <interface>section. Removing it, solved the issue. ;D

on restart I keep getting Interface mismatch. I have tried to reconfigure this but it is caught in a permanent loop. I am running the 32bit version on a via system.

This also happened to me and because of the infinite loop I was forced to reinstall the pfense box  :'(

Here are the steps i've performed:
(10) update using the Web GUI
(20) Auto Reboot
(30) Shell says there is an "Interface missmatch" and ask to configure interfaces
(40) I correcty resetup the interfaces
(50) Shell says "writing config File"
(60) Goto 30  :'(

May i suggest a "(55)" step saying something like "I failed to write a valid config file, Would you like to

Reset the config file: Type X (or a way to go back to the Main Pfsense Menu) or try again: Type Return

This would avoid having to fully reinstall the pfsense box, whenever the config file get corrupted…. 8)

BTW May be there is a way to return to the pfSense console setup menu (to be able to reset the configuration to factory default), but I was unable to find it  ???

Best regards,</interface></vr0>

Sorry,

Still get this in the system log but it seems to be working though.

Oct 21 18:28:30 kernel: vip2: incorrect hash
Oct 21 18:28:30 kernel: vip1: incorrect hash

You don't provide anything close to a useful problem description there. No description of even what the problem is or what is happening, no log entries, etc. You need to give a lot more detail before anyone can even guess at a problem.

Sorry, I meant using a short snippets from that page as passwords, not the full 63 character long passwords. I use 8 character passwords that I hand pick from the "The 63 alphanumeric-only character subset" so that the passwords are still random enough but I'm still able to remember them without writing them down.

You're right, it started now. Thanks.

I set the Null service name and it came right up. Thanks for the help everybody.

Try again forgot to remove something while fixing others.

Nothing to switch on, bridged interfaces are still treated like separate interfaces and you can filter, do snort, etc. You just can't have a service listening on that interface since it has no IP address. Snort doesn't listen in that way, it does packet inspection, so it still works.

And I recieve this message using Filezilla client

Error: Connection timed out
Error: Failed to retrieve directory listing

Hello World!

Just upgraded my old V2-Version (September 18th) to the current one (nanobsd 2G, build Mon Oct 18 18:29:59 EDT 2010) and passive FTP (outbound) works again.

Setup:

–--------------
        (    Internet      )
        ----------------
          |                |
          |                |
      pppoe          pppoe/static
          |                |
  ------------          |
| DSL-Router |        |
  ------------          |
          |                |
          |                |
          ---------------
        |    pfSense      |
          ---------------
                    |
                    |
          ---------------
        (Internal Network)
          ----------------