Hi Scott, PFSense Version Beta2 Full Install 2WAN + Lan
Myself being a MultiWan and Load Balancing User I thought that you may appreciate some feed back. I first did the CVS update on the 19th or 20th March when you announced the changes. PFSense box already configured, as a working load balance. I created the Static Routes and checked to use the Interface as a GW. (I remembered seeing this available in the Snapshot Releng 03-10-2006, it didn’t work for me then). I had to reinstall to be able to continue business for the following day. I retried the newer CVS update 03-20-2006 and re-setup the Static routes for the Interfaces and DNS addresses per Interface. But it made no difference to being able to Fail-Over DNS. I associated this to be a conflict with my working DualWAN (Round Robin). Reinstalled for next work day. 23Mar06. 3.30AM I reinstalled PFSense and did an update via cvs_sync.sh releng_1. This produced a couple of errors at the end of the update, failed to open debug in path /usr/local/lib/php/extensions/no-debug-non-zts-20020429/.... I went looking for the file manually via the CVSTrack but found that the reason why it could not open the file is that it had not been updated. I presumed that this was known and I continued ignoring the error MSG. SETUP Load Balance + Failover I first setup the Interfaces to allocate IP Addresses. I then setup the Load Balance I setup the Static Routes allocating the Wan and Opt interfaces as Gateways I then configured the NATs for all interfaces Then the Firewall Rules for All Interfaces Results: There was a Failover of sorts, the remaining interface would not resolve the URL immediately but with coaxing a couple of times it would eventually find the page. Modifying NATs and Rules made no positive differences to the viewing of any page. I then left the PFSense configured with the DualWan Load Balance + FailOver ready for work at 5.15AM. When Staff began work at 7.15AM the PFSense box was not passing traffic in any direction and could not ping any outside IP or host from the console. A restart was performed and tried again. Again the traffic only flowed for a short time period before stalling. To continue operations for the day, a complete reinstall was done reconfigured by using a restore of the working config, but this did not pass traffic (seems to be a problem in Beta2 for some reason as I have tried this a number of times with the same results, it unsuccessfully restores). Another reinstall was done and manually configured DualWan Load Balanced, NATTED and Ruled in 20 minutes. If it is any help, when I next do a DualWan Load Balance + Failover I can send you a copy of the config in File.txt. I don’t think that it would tell you anything that you would not already be aware of though. But it may confirm in my mind that I have not forgotten or overlooked something. In case this has been an oversight, the Subnet in the Rules pages are Max of 31 not 32 as in all other events of the subnet. So a Static Internet IP is unable to be selected to create rules for. If it is intentional, then you must have a reason for it. Anyway, thanks for a great Firewall. BTW, Endian announced their release yesterday and the Features are not half as good as PFSense. I looked at theirs before I discovered PFSense. Now that I'm here, I wont use anything else. www.efw.it Kindest Regards, Craig Roy Horizon IT Consultants [EMAIL PROTECTED] -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.1.384 / Virus Database: 268.2.6/288 - Release Date: 22/03/2006 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
