Anyone got any idea on this? Have you got a similar config yourselves?

-configure the interfaces for net-A & B (ip / subnet / …) -create a firewall rules like this: on net-a interface: allow any-to-net-B on net-b interface: allow any-to-net-A be sure your clients use pfsense as a gateway done

sites would not work … what you could do is find out all the IP's youtube uses; create 1 alias for that set of ip's. then create a firewall rule any-->alias with gateway WAN1

Settings are attached as PDF: https://dl.dropbox.com/u/379598/pf_settings.pdf

By the given link I remove the two tick from the firwall/nat options please check below [image: up.jpg] [image: up.jpg_thumb]

Do a traceroute and see where it fails.  I suspect that the last device on your traceroute is not configured to route traffic from the originating subnet.

Any host based firewalls on those devices? Usually those allow only own subnet to contact not the neighbor.. Firewall ping is accepted, because by default firewall(/router) uses same subnet to contact those devices

possibly wrong configuration on the switch … did you set the PVID on the untagged ports on the netgear to the correct vlan-value ?

Just looking at this and it seems that despite having a Gateway group netstat -r is showing me that my default gateway is still the wan connection Routing tables Internet: Destination        Gateway            Flags    Refs      Use  Netif Expire default            192.168.22.1      UGS        0  374223    re0 a.resolvers.level3 192.168.20.1      UGHS        0    64291    re2 google-public-dns- 192.168.22.1      UGHS        0    69587    re0 google-public-dns- 192.168.21.1      UGHS        0    69611    re1 localhost          link#11            UH          0      102    lo0 192.168.17.0      192.168.17.2      UGS        0  293674 ovpns1 192.168.17.1      link#12            UHS        0        0    lo0 192.168.17.2      link#12            UH          0        0 ovpns1 192.168.20.0      link#3            U          0    1980    re2 192.168.20.250    link#3            UHS        0        0    lo0 192.168.21.0      link#2            U          0      267    re1 192.168.21.250    link#2            UHS        0        0    lo0 192.168.22.0      link#1            U          0    1185    re0 192.168.22.250    link#1            UHS        0        0    lo0 192.168.24.0      link#5            U          0  2617792    xl0 server1            link#5            UHS        0        0    lo0 resolver2.opendns. 192.168.20.1      UGHS        0      290    re2 obmr.btconnect.com 192.168.22.1      UGHS        0    4879    re0 [image: gw_groups.JPG] [image: gw_groups.JPG_thumb]

Thanks! I missed the point somewhere to enable sticky connections. After that, everything looks great! :) Best regards

of course ;)

I got the answer .This is nothing like same as usual set up …..make the both gateway together and make load balancing .If any body want to know this please ask me I will share it

That´s the point tim.mcmanus, as you can see in the captures routing table 1 and routing table 2, the default route disappear once the WAN interface goes down (the Tier1 in the gateway group) so.. how can the packets know where to go out if there are not a default route? Thank yu for your answer, BR Traxto

@robtoronto: Question is there a reason you would not want it to Load balance ? Gateways at the same priority to not only provide a redundant connection but also to provide a faster connection to your hosts? This has nothing to do with the OP, but in my particular setup I have a business WAN connection and a residential WAN connection.  My ISP worked with Spamhaus and declared their residential IP range as potential spammer addresses.  So if my mail server fails to the residential gateway all of my outgoing email will get flagged as spam.  So in my annoying situation the residential fails over to the business WAN but not the other way around.  I'd rather be hard down and haze the ISP then lose outgoing emails to being flagged as spam.

Now I don't want to sound like an ass because I'm new to this site myself…but the one thing I am not new to is the internet... [image: google-troll.jpg]

If (and only if) you use Sticky connections, which makes sure a given client always routes through a single gateway even when load balancing, then there is an additional tab under Diagnostics > States called "source tracking" that lists the relationships between a client and the gateway they're routing through. Sticky has other drawbacks but if you need your clients to "stick" to a particular WAN for all their traffic, and see what that WAN is, then it can be useful.

DSL lines are for aggregation. WIFIs represents 3g and 4g connections. The chart is list more WAN then i would really use.