The first issue should be fixed in the latest snapshots.

Fixed thanks

@kaarposoft: "noasync" should make no difference, since this is the default. Emphasis on "should" - better safe than sorry when you're testing. :) @kaarposoft: YES, everything should be "noatime". Why did I not think of that? Why does pfSense not do this by default? Not sure. It's been brought up before but I don't recall why it hasn't been done. It may just be that nobody has taken the time to make the changes.

Thx

My setup had some errors…. wrong path to cert files... wrong cert type for peer... Now it works and I am even more flabbergasted :S Why does it work? As far as I can tell the pfSense box does not have the others public key!

I found today that not only SMTP but also HTTP and maybe all TCP protocols are affected; and, not only the IP 118.x.y.z but also 80.254.71.228 (IP address of the web server of m0n0wall project) and maybe many, many IP addresses are affected. This serious problem can be reproduced easily. Create a firewall rule that routes every web-browsing traffic to some non-default interface, then visit http://m0n0.ch to see that it actually goes through the default interface.

http://redmine.pfsense.org/issues/show/441

This is working fine now with March 19th snap.

See also: http://redmine.pfsense.org/issues/show/439 http://redmine.pfsense.org/issues/show/440

Thanks for your reply and your information! :-) Best regards, Chris

Same here since 17. Trying to get multiwan, single lan shaper to work

im on the 20th march snapshot and pppoe still has issues reconnecting if connection gets dropped for some reason and to make it reconnect i have to reboot the alix, pressing connect under interfaces also doesnt make it come up and system log keeps showing the stuff below Mar 21 09:27:29 mpd: [wanL1] PPPoE: Connecting to '' Mar 21 09:27:38 mpd: [wanL1] PPPoE connection timeout after 9 seconds Mar 21 09:27:38 mpd: [wanL1] Link: DOWN event Mar 21 09:27:38 mpd: [wanL1] LCP: Down event Mar 21 09:27:38 mpd: [wanL1] Link: reconnection attempt 1 in 1 seconds Mar 21 09:27:39 mpd: [wanL1] Link: reconnection attempt 1 Mar 21 09:27:39 mpd: [wanL1] PPPoE: Connecting to '' Mar 21 09:27:48 mpd: [wanL1] PPPoE connection timeout after 9 seconds Mar 21 09:27:48 mpd: [wanL1] Link: DOWN event Mar 21 09:27:48 mpd: [wanL1] LCP: Down event Mar 21 09:27:48 mpd: [wanL1] Link: reconnection attempt 2 in 4 seconds Mar 21 09:27:52 mpd: [wanL1] Link: reconnection attempt 2 Mar 21 09:27:52 mpd: [wanL1] PPPoE: Connecting to '' Mar 21 09:28:01 mpd: [wanL1] PPPoE connection timeout after 9 seconds Mar 21 09:28:01 mpd: [wanL1] Link: DOWN event Mar 21 09:28:01 mpd: [wanL1] LCP: Down event Mar 21 09:28:01 mpd: [wanL1] Link: reconnection attempt 3 in 3 seconds Mar 21 09:28:04 mpd: [wanL1] Link: reconnection attempt 3 Mar 21 09:28:04 mpd: [wanL1] PPPoE: Connecting to '' Mar 21 09:28:10 mpd: caught fatal signal term Mar 21 09:28:10 mpd: [wan] IFACE: Close event Mar 21 09:28:10 mpd: [wan] IPCP: Close event Mar 21 09:28:12 mpd: [wan] Bundle: Shutdown Mar 21 09:28:12 mpd: [wanL1] Link: Shutdown Mar 21 09:28:12 mpd: process 37623 terminated Mar 21 09:28:15 mpd: Multi-link PPP daemon for FreeBSD Mar 21 09:28:15 mpd: Mar 21 09:28:15 mpd: process 50493 started, version 5.5 (root@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org 17:05 19-Mar-2010) Mar 21 09:28:15 mpd: [wan] Bundle: Interface ng0 created Mar 21 09:28:15 mpd: [wanL1] Link: OPEN event Mar 21 09:28:15 mpd: [wanL1] LCP: Open event Mar 21 09:28:15 mpd: [wanL1] LCP: state change Initial --> Starting Mar 21 09:28:15 mpd: [wanL1] LCP: LayerStart Mar 21 09:28:15 mpd: [wanL1] PPPoE: Connecting to '' Mar 21 09:28:24 mpd: [wanL1] PPPoE connection timeout after 9 seconds Mar 21 09:28:24 mpd: [wanL1] Link: DOWN event Mar 21 09:28:24 mpd: [wanL1] LCP: Down event Mar 21 09:28:24 mpd: [wanL1] Link: reconnection attempt 1 in 3 seconds Mar 21 09:28:27 mpd: [wanL1] Link: reconnection attempt 1 Mar 21 09:28:27 mpd: [wanL1] PPPoE: Connecting to '' Mar 21 09:28:36 mpd: [wanL1] PPPoE connection timeout after 9 seconds Mar 21 09:28:36 mpd: [wanL1] Link: DOWN event Mar 21 09:28:36 mpd: [wanL1] LCP: Down event Mar 21 09:28:36 mpd: [wanL1] Link: reconnection attempt 2 in 2 seconds Mar 21 09:28:38 mpd: [wanL1] Link: reconnection attempt 2 Mar 21 09:28:38 mpd: [wanL1] PPPoE: Connecting to '' Mar 21 09:28:47 mpd: [wanL1] PPPoE connection timeout after 9 seconds Mar 21 09:28:47 mpd: [wanL1] Link: DOWN event Mar 21 09:28:47 mpd: [wanL1] LCP: Down event Mar 21 09:28:47 mpd: [wanL1] Link: reconnection attempt 3 in 3 seconds

@geeknik: @blewis: I guess you are like in my shoes, I needed multi-wan but pfsense has not so great Traffic Shaping, so I threw a 3rd party firmware supported router of myr choice in front of pfsense to do the traffic shaping. Yeah, I'm just tempted to put something like NetBalancer or CfosSpeed on my Windows machines and let the software handle the QOS instead of the router.  Doesn't help me where the Xbox is concerned, but I'll survive. ;) Actually if you use something like Tomato (highly recommended), dd-wrt, or openwrt, and connect those items, such as your xbox or any game console to it, and let Tomato/etc do the QoS then you wouln't need cfos/netbalancer.

OK. That's what I was thinking. So the button shouldn't appear after adding a new alias.

Confirmed. The Fri Mar 19 23:39:43 EDT snapshot returned it to normale.

also get this on the 20th march nanobsd snapshot which sued to come from the past few snapshots Mar 20 15:04:37 php: : The command 'route add -host 195.229.252.33' returned exit code '1', the output was 'route: writing to routing socket: Invalid argument add host 195.229.252.33: Invalid argument' Mar 20 15:04:37 php: : The command 'route add -host 195.229.252.33' returned exit code '1', the output was 'route: writing to routing socket: Invalid argument add host 195.229.252.33: Invalid argument'

I haven't tried it. But I would try creating a limiter with a mask set to none and apply it to a rule for an entire interface and see if those are the results you are looking for. Dan

Fixed. Actually you just need to load shmop module.

@seabra: Hello. I found some posts but nothing conclusive about this topic. Is layer7 working or not? If not when is it expected to work? Kind Regards, Seabra while I am not using it myself, a friend of mine is and he tells me he has had to write many rules but that its stable and is doing wonders for 60 subs on a ten meg cable modem (100 bucks a month) These are 60 heavy users that he diverted from his fiber connection.

+1 Me too. If I follow the uninstall URL : http://192.168.254.40/pkg_mgr_install.php?mode=delete&pkg=Open-VM-Tools Then, just below the next uninstall screen , I get this error : Warning: require_once(/usr/local/pkg/open-vm-tools.inc): failed to open stream: No such file or directory in /etc/inc/pkg-utils.inc on line 748 Fatal error: require_once(): Failed opening required '/usr/local/pkg/open-vm-tools.inc' (include_path='.:/etc/inc:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg') in /etc/inc/pkg-utils.inc on line 748