yandex drivers are out now so no more guarddogs were the yandex supposed to be better performance?

Yeah upgrading to latest version or check that you have the right password and the same port on both boxes.

I've tried that several times in the past and had lots of problems afterwords.  it might work with a simple config but I would definitely not recommend it!  also, 1.2.3 has PPTP limitations that m0n0wall does not. Roy…

Yes, I am using the Local User Manager for authentication, with the users added at the System/User Manager menu. However, I have only the first box checked. The second is not checked. This is the opposite of what you recommend, although the result appears to be the same (ie. after login the user mac address gets added to the passthrough list with a message like 'auto added mac for user bobby'). Perhaps PfSense has a fallback mode whereby it includes the username when it is present. Anyhow, I will try switching the checkboxes at some convenient quiet time and experiment some more with a view to finding any potential subtle differences or misunderstandings. If I spot anything I will write again. In the meantime, thank you again for your help. Michael.

Solved. Added the GW from "System > Routing" instead. Thakns!

Here is the relevant devwiki page: http://devwiki.pfsense.org/SubmittingPatches …assuming it is up-to-date. Jason.

Thanks.  I almost hit the upgrade button but decided to check the forums.  Glad I did! I'm running "2.0-RC1 (amd64) built on Fri Mar 18 18:32:14 EDT 2011"  – no crashes but the watchdog timeout messages from yandex are annoying.

Try a firewall rule on the DMZ interface blocking (with logging) anything from DMZ subnet to DMZ address port 80 (http). Add a rule on the DMZ interface blocking (with logging) anything from DMZ subnet to DMZ address port 443 (https). Reset firewall states (Diagnostics -> States, click on Reset States tab, click on Reset button). Test, check the access attempts are logged in the firewall log (Diagnostics -> System Logs, click on Firewall tab) and then (if desired) go back and edit these rules to disable logging. Adjust rules appropriately if you have chosen to configure a custom port number for access to web configurator.

No, the PPTP proxy was completely removed since it was still causing some other issues.

Might be that you have this Captive Portal option enabled (ticked): "Enable Pass-through MAC automatic additions", or you have manually added the user to the mac-pass-through list. I recently discovered that pass-through users are not included in the status list with the 2.0 RC1.

@ermal: You can disable the user! Furthermore, the macs are disabled by default so its kinda confusing having this option there. The problem is that i have a lot of users without "username" but in certain times i need to disable the access to them. Nothing specific, just for example disable access for 10macs two days, no problem in doing it manually. Give them usernames and passwords is not an option right now, because changing the rules of how they connect its a problem at user  level  ;) I know that this can be done with squid but i don't want to install packages and i need in the same box the wanbalance (not compatible with squid)

yes this is a solution heper, bt with havp as a parent for squid (on localhost) it is not feasible! 127.0.0.1 is already in use! and also this solution dont access on any 2.0 version ;) thanks therefore

@tsk: Just get rid of the second subnet line (or comment it out) and it should boot up fine. Thanks. Doesn't seem to cause any boot problem.