I have upgraded, reset to defaults and went to the wizard - the magic 1 is back. I will slide the slave into production and keep this one online for you if you want to have a peek around in it. You can find me in #pfsense unless I am messing with firewall hardware. On a similar note, it seems that packages don't get un-installed when reset to factory defaults, however their listing on the installed packages page is removed.

@jimp: The weight setting is for load balancing, not failover. It lets you set the approximate bandwidth ratio of the links, relative to each other. For example, I have 3Mbit DSL and 10Mbit cable, so I use a weight of 1 for DSL, and 3 for Cable, so for every 4 connections, 3 will use cable. The traffic that is being blocked is likely due to it being out of state traffic, which is probably happening due to the asymmetric routing you have going on. Under advanced options, you may want to try checking the option to "bypass firewall rules for traffic on the same interface" which can improve the situation in your case. interesting, I've enabled the bypasss fw rules for traffic on same iface, and it seems to have improved the vpn traffic, although I did enable and start playing with the traffic shaping at the same time. thank you.

Auto update was broken until a few days ago. Do a console update by URL and feed it a snapshot link, or download an update and use the manual upload.

Yep, working now.  Many thanks.

sullrich fixed the installer and it should work again on the next new snapshot.

Sorry if I was unclear. Will wait for the next build and try it.

If it reboots itself without any errors on the console or warning at all, it's likely hardware related in some way.

@sjorge: Fixed in latest build  :D Oops, seems the auto update installed the i368 veriant not the amd64. After some more testing, it seems amd64 was the problem :(

tried it on the 22nd may snap and restore works fine and even reboots fine now, thanks

@jjstecchino: Should I file a bug about this? One already exists: http://redmine.pfsense.org/issues/88

there's a ticket open on it

@jimp: What type of WAN do you have? Or do you only have DNS which you configured by hand? I've got a 2.0 NanoBSD VM running that same snapshot and I have the symlink. I have DHCP for WAN, though. I think this must be related to me powercycling my test box during the startup process.  My serial connection was borked, so I just hit the power button to see if that would fix it. I was using DHCP for wan, and when I looked under /var/etc/ the correct files and data was there, but /etc/resolv.conf wasn't pointing to anything, so there was no local dns resolution, or for any of the clients via dnsmasq. I will try reinstalling and see if it happens again.  Josh

Thanks for the reply! Newer? This was today snap pfSense-2.0-BETA1-20100520-0344.iso

@pieter64: Thanks dusan, I have now setup the gateways…see below. Name Interface Gateway Monitor IP Description WANGW (default)  WAN  192.168.0.5  192.168.0.5  Main_ADSL        OPT1GW  OPT1  192.168.0.3  192.168.0.3  Backup_ADSL I have then gone into the Groups ..... Group Name LoadBalancing Gateways WANGW OPT1GW Priority Tier 1 Tier 1 Description Load Balancing But it still is using the wan and never going to opt1. Have I missed something??????? Probably missing (policy-based) routing rules. Checkout you Firewall -> Rules -> LAN tab to be sure there are rules with gateway=LoadBalancing. If every rule is with gateway=* (where * means the default gateway) then all traffics go out via the default gateway (WAN).

Go to Diag > Command and run: ps ax|grep choparp and make sure it's actually running. If so, then get a packet capture when it's not working and see if your upstream is actually sending ARP requests that aren't getting replies.

There are no "standard" rules really. You can run whatever you want, whatever is right for the traffic you expect on your network.

hi, i can give you the file of course ;) but I have to remove all passwords and usernames <system><optimization>normal</optimization>   <hostname>pfsense</hostname>   <domain>whitebear.lan</domain>   <timezone>Asia/Shanghai</timezone>   <timeupdateinterval><timeservers>0.pfsense.pool.ntp.org</timeservers> <webgui><protocol>http</protocol>   <port><auth_method>session</auth_method>   <backing_method>htpasswd</backing_method></port></webgui>   <disablenatreflection>yes</disablenatreflection>   <dnsserver>8.8.8.8</dnsserver>   <dnsserver>4.4.4.4</dnsserver> <firmware><alturl><enable><firmwareurl>http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_HEAD/.updaters</firmwareurl></enable></alturl></firmware> <group><name>admins</name>   <description>System Administrators</description>   <scope>user</scope>   <home>index.php</home>   <gid>2000</gid>   <member>0</member></group> <group><name>all</name>   <description>All Users</description>   <scope>system</scope>   <gid>1998</gid>   <member>0</member></group> <user><name>admin</name>   <fullname>System Administrator</fullname>   <scope>system</scope>   <password></password>   <uid>0</uid>   <priv>usershellaccess</priv>   <md5hash></md5hash>   <nthash></nthash>   <expires><authorizedkeys></authorizedkeys></expires></user> <user><name></name>   <fullname></fullname>   <scope>user</scope>   <expires><md5hash></md5hash>   <authorizedkeys></authorizedkeys></expires></user> <user><name></name>   <fullname></fullname>   <scope>user</scope>   <expires><md5hash></md5hash></expires></user> <user><name></name>   <fullname></fullname>   <scope>user</scope>   <expires><md5hash></md5hash></expires></user> <user><name>test</name>   <fullname>test</fullname>   <scope>user</scope>   <expires><md5hash></md5hash></expires></user> <user><name></name>   <fullname></fullname>   <scope>user</scope>   <expires><md5hash></md5hash></expires></user> <user><scope>user</scope>   <password></password>   <md5hash></md5hash>   <nthash>***</nthash>   <name>bear</name>   <fullname>Whitebear</fullname>   <expires><authorizedkeys><uid>2000</uid></authorizedkeys></expires></user>   <nextuid>2001</nextuid>   <nextgid>2001</nextgid>   <enablesshd></enablesshd></timeupdateinterval></system>

Hi, OK, I understand, you already done a great job. I am not a good programmer and don't understand everything on how pfSense is working (on developpement side) but I really need such feature so I will try to take some time to try to implement it (perhaps only for the packages that I need (incorporating it into pfSense base on my firewall) if I don't find a global solution, …). For my case I only need to add a user management page under the captive portal (only for users of captiveportal group), so I will begin with this and try to do the pkg selector after this because I will be more interested to use Radius than local user manager, ... For this I need some informations : Where is located the list of "system privilegies" on the filesystem? Is the informations below used for managing this on php files of pfSense : 1.   ##|+PRIV   ##|*IDENT=page-package-settings   ##|*NAME=Package: Settings page   ##|*DESCR=Allow access to the 'Package: Settings' page.   ##|MATCH=pkg.php   ##|-PRIV 2.   if (isAllowedPage("system_usermanager")) {} How to add a menu item on pfsense (not using package)? How to add a tab on a page ?   I have seen that it seems to be hardcoded using this "$tab_array = array();", so it says that I must modify every pages of captive portal. Is this right?