Multi-WAN (pfSense 2.1.2): Can ping/tracert sites, but cannot browse web

[Eisenfaust]

Hi All,

First, I'd like to say that pfSense is awesome!

Anyway, I have a double DSL setup from different providers.

It looks like this:

DSL A –------|
                    | pfSense 2.1.2 Box --------| LAN
DSL B -------

DSL A (Default Gateway) = 192.168.2.0/24
DSL B = 192.168.3.0/24
LAN = 192.168.1.0/24

When I try to make a host (192.168.1.130) use DSL B as it's gateway (via LAN rule), the host cannot browse the web, but can ping and tracert sites successfully.
Other applications (Steam, Battle.net etc) don't work as well.

DNS Forwarder is enabled, my hosts use pfSense LAN IP address as the DNS server, nslookup works, browsing works for the other hosts on DSL A.

This has been bothering me for almost a week, and any insight would be greatly appreciated.

Please see attached if they are of any help.

Regards,
Mark

[Eisenfaust]

Update:

I tried changing the Default Gateway to DSL B, and changing the host's gateway to DSL A, and the same thing happens: ping and tracert to websites are successful, but I can't browse the web.

Any tiny nudge in the right direction would be great, TIA.

[timthetortoise]

Are you using squid?

[Eisenfaust]

Hi Sir,

No, I'm not, but I did.

I removed all other packages after upgrading to 2.1.2 (squid3, squid guard, sarg, ntop), in an attempt to lower resource usage on the VM (VirtualBox).

Thanks for your time. :)

[Eisenfaust]

Well.. It's working now, but I have no idea how…

I just enabled logging on the Load Balance LAN rule, and removed the Streaming and Bulk download enqueue floating rules..

Thanks timthetortoise for taking the time to reply.

I'm still stumped though.. :-[

[timthetortoise]

It'd make sense that those rules would take precedence and not give the result you wanted since they weren't set to use the correct gateway group.