Not really. You can add the same IP to the pool multiple times to sort of get that effect. But you may be better off using a package like HAproxy that supports actual weight parameters.

Have same problem here. When I dissable Gateway Monitoring it works. I have tried a high down ping time, ms and packetloss but with same problem. I am running 2.0.3

Hi all. i am new to pfs. i am trying to block all ports and only allow the neccesary ports that i need on our network such as port 80,443, pop3, smtp etc. its about the rule under Firewall. how is the sequence work with the floating rules? is it reading from top to bottom or bottom to top? pls help. rikki

I can only guess, but I assume that traffic is not going to your WAN1 connection because of a misplaced or misconfigured firewall rule. So when you enable these other two rules (WiFi<->LAN) and (OpenVPN<->LAN) either or both of those rules come before (higher on the list) the (WAN<->LAN) rule. I'd need to see how your VLAN, and Firewall rules are set up.  How are you creating the bridges?

sounds like a combo of port forwarding and manual outbound NAT. Setup IP Alias,CARP, or ProxyARP VIP for each that you are going to use. Setup portforwards to forward the traffic into the correct server. Then test to make sure that works. Once that is working, then go to outbound NAT. Switch it to manual. At the top (since it works top down) add each server with any port as the source with destination any. Set the NAT Address to the corresponding VIP.

Once you assign the VPN interface – Interfaces  > (assign), add the interface, then enable it with an IP type of 'none' and restart that VPN instance -- you'll get a gateway entry automatically. Once you have the gateway entry, you can craft a firewall rule to catch the traffic from the IP you want and force it to use that VPN gateway. You will have to make sure that NAT will apply to that traffic, either locally as it leaves the VPN interface, or remotely at the other side of the VPN, or it won't make it out to the Internet.

With NAT disabled, the upstream router needs to have a static route on it that points the LAN subnet back to the WAN address of the firewall. Otherwise you'd need a bridged setup, not a routed setup.

Hello dear PFSENSE Forum The Problem was not Pfsense and Loadbalancing issue. It was that the Managed Switch by the technical instance was 100mbit/s… Not the give me today a new Line in my House... Now is working with 150mbit/s... Thank you all for your help... Divotion

No one has any thoughts on this?

Turns out that: It is not hard, and I did know what I was doing the ports had not been configured correctly or there was some patching issue. Sigh, so many wasted hours :) Thanks anyway

try in this step http://forum.pfsense.org/index.php/topic,60977.0.html

In cases such as this, I always start with the firewall logs (Status > System Logs > Firewall) tab. IF you haven't setup any rules yet the traffic is probably getting blocked. If this is the case, you will want to visit the rules (Firewall > Rules) and add rules which all traffic out of the different LAN interfaces.

What virtual platform are you using? Vmware, VirtualBox, Hyper-v? It sounds like you don't want your pfsense box to be behind the host computer. If this is the case you will need to go into the networking configuration of your virtual environment and bridge the pfsense WAN interface to the physical hosts external interface. You will then want to create another virtual switch/network and connect the pfsense LAN interface to that. Anything you connect to the new virtual network will be behind the pfsense firewall.

I have to agree, if set to DHCP, it should be able to pull an IP address. I would think that perhaps the nic/cable/switch port might have something wrong with it. Traffic is probably getting to WAN2, but because of its issue will not get any farther.  If you can start with the easiest, change ports, then change cable, and then change the NIC out.

Sorry, it works for IPV4, don't use IPV6 yet. But you may want to check on your other routers in the network. TCP:SA is usually a valid block and you may be doing some criss-cross routing. (It's healthy to know where your packets go  :) )

Anyone ? We still have this problem also after having upgraded to 2.0.3 release.

It still is not multi-wan capable, even on 2.1. It will go via the WAN/default gateway no matter what you try, since we assume the WAN interface as external. If we offer an external interface choice it will still only work on one WAN, but you'd get to choose which WAN that is. Though I suspect it would still only really work on the WAN containing the default gateway. It's not a quick/easy fix or we'd have done it by now.