pfSense doesn't support interface alias in version 1.0, however this is already present in head.

You can add multiple VLANs to a physical interface. Each VLAN will become a seperate interface providing all the options/services you have for a real physical interface (unique IP/subnet, filtering, dhcpserver, …).

That fixed the problem. Thanks  ;D ;D

Nice Aldo, keep us updated how these values scale when you have the real 1500 user setup  ;D

"In a bridged setup all interfaces involved in the bridge have to be up, so you need a link at lan."

That's what was getting me…...I don't recall seeing that anywhere in the documentation.

Thanks.

Just out of curiousity, are you putting this capture device between the pfsense box and the modem, between the switch and your daughters computer, running a hub for your daughters computer, or spanning the switch port of your daughters computer?

The cheapest solution that I can see by far provided you don't need over 10Mbit is to get a cheap tiny hub, connect it between the wrap switch and your daughters computer, and instead of running a proxy just have the capture device in promiscuous mode to capture everything travelling though that hub.

At my last job we had an IDS and it was basically connected to a switch with a spanned port.  The port that was being spanned was the port of the default gateway.

chmod a+rx /usr/bin/cvs

You should be able to at least slow this down by using the advanced options for the firewall rule that is granting access to SSH (like new X connections/Y seconds, simultaneous connections/host, …).

Reinstall using http://www.pfsense.com/~sullrich/RELENG_1_SNAPSHOT-07-01-2006/

@Gertjan:

From what I understood, all your LAN stuff is hooked up to a switch - and the pFsense box is also on this switch.

That's correct.

Cable modem <-> pfSense box <-> switch <-> computers, nas devices etc.

I have now tested switching back the Netgear router/firewall to replace pfSense, and amazingly, all the problems described in the first post disappeared. Just to verify the causality of this, I switched back the pfSense box, and none of the problems reappered.

Conclusion: no idea what was causing this, probably I'll never find out. What matters is that everything works.

I think i understand the most now :). thanks for the help.

There are differnet ways ISPs are setting this up. Some give you PPPoE user and password and assign you always the same IP on dialin, others give you static IP/gateway/DNS to use at your end, others assign you parameters via DHCP. In all cases set the Modem to bridge mode and configure either PPPoE, Static or DHCP at your pfSense WAN with the settings your provider gave you.

I have fixed this and this was due to some packets now going through the PFsense so the connections got droped.  I solved this by changing the IP address of the internet router to a total different subnet.

I'am still getting the error "ERROR: FreeBSD route add command failed: shell command exited with error status: 1"  the UID en GID are root and wheel? wat i' am doing wrong

iám using version: 1.0-RC1a

Jun 23 11:50:12 pfsense openvpn[79636]: TUN/TAP device /dev/tun1 opened
Jun 23 11:50:12 pfsense openvpn[79636]: TUN/TAP device /dev/tun1 opened
Jun 23 11:50:12 pfsense openvpn[79636]: /sbin/ifconfig tun1 10.8.0.10 10.8.0.9 mtu 1500 netmask 255.255.255.255 up
Jun 23 11:50:12 pfsense openvpn[79636]: /sbin/ifconfig tun1 10.8.0.10 10.8.0.9 mtu 1500 netmask 255.255.255.255 up
Jun 23 11:50:12 pfsense openvpn[79636]: ERROR: FreeBSD route add command failed: shell command exited with error status: 1
Jun 23 11:50:12 pfsense openvpn[79636]: ERROR: FreeBSD route add command failed: shell command exited with error status: 1
Jun 23 11:50:12 pfsense last message repeated 5 times
Jun 23 11:50:12 pfsense openvpn[79636]: GID set to wheel
Jun 23 11:50:12 pfsense last message repeated 5 times
Jun 23 11:50:12 pfsense openvpn[79636]: GID set to wheel
Jun 23 11:50:12 pfsense openvpn[79636]: UID set to root
Jun 23 11:50:12 pfsense openvpn[79636]: UID set to root
Jun 23 11:50:12 pfsense openvpn[79636]: Initialization Sequence Completed
Jun 23 11:50:12 pfsense openvpn[79636]: Initialization Sequence Completed

try to at this rule to the PFsense server config?

route 192.168.210.0 255.255.255.0

Thank you very much, you have explained it perfectly (very important difference LAN-LAN –-- client-LAN)