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)

@tunge2:

is it possible to add a tunX interface to the firewall (or is this not nessesary?) is it also possible to add a static route for the openvpn interface?

Routes are automatically added for whatever network you specify in the Remote Network field at either end as soon as the tunnel becomes active.  If you have more then one internal network on local end, then you can assign static routes at the remote end, and vise versa.

I haven't tried working with the summarization of networks, for example using a static route for 192.168.0.0/22 for subnets 192.168.0.0/24, 192.168.1.0/24, 192.168.2.0/24, 192.168.3.0/24.

http://wiki.pfsense.com/wikka.php?wakka=DeveloperBootStrapApfSenseDevelopersISOInstallation

LOL, I'll draw a nice gif to fill the emptyness again…  ;D

thanks scot, tahnks hoba.

@scan:

@hoba:

PPPoE happens on layer2, this means you don't need anything else at this interface allowed and it still will work after authentication. If you only want users to be able to pass through your firewall after they connected to PPPoE delete all rules at the Interface you run PPPoE on and disable the DHCP-Server for this interface.

how?

Let's say you run the PPPoE-Server at OPT1, delete all rules for OPT1 and don't set up a  DHCP-Server for this interface. Add pass-rules for your PPPoE Interface. Done.

Edit your /etc/sysctl.conf and add kern.timecounter.hardware=TSC. That's it.. problem solved!

@cheech:

I am "upgrading" some SonicWall equipment to pfsense. The SonicWall has settings for both TCP and UDP "Timeouts" (I can maybe understand TCP but isn't UDP stateless?) ANYWAY… I run terminal sessions via telnet over a VPN and I had to adjust the TCP Timeout on the SonicWall from a default of 15 mins to something like 60 mins otherwise users were getting dropped when they were idle. I don't see any settings like this in pfsense and am wandering if I might end up with a problem?

Thanks!

Default established timer is 24 hours using "normal" state timeouts.

–Bill