I've searched/read all threads about multi-wan within the forum/wiki/howto. Many posts concern 1.2.x. Also, it seems all of them are concerned with squid running in transparent mode. I've started a new thread on this old topic to try and:
a) summarize the current state of what works and what doesn't.
b) determine if multi-WAN will behave differently under squid (not transparent)?It seems the general consensus is that:1) 2.0 Multi-WAN + firewall + loadbalance + failover:
Works great 2) 2.0 Multi-WAN + firewall + failover + squid (transparent):
Seems to work for most users, others experience problems after some time (down link not coming back up again etc), yet others can't get it to work altogether (probably due to weird scenarios or wrong settings). 3) 2.0 Multi-WAN + firewall + failover + loadbalance + squid (transparent):
Found one post that claims it works,
others experience problems after some time (yet it seems these cases weren't tested properly to ascertain that the setup worked in the first place)
, yet most users can't get it to work altogether. Problem seems to be squid always using the default WAN, thus balancing doesn't work for HTTP data. Or, squid not understanding balancing? However, it seems very logical to me that floating rules should solve this? 4) 2.0 Multi-WAN + firewall + squid (not transparent) (loadbalance + failover):
Any comments? Anyone tried this? How would this behave differently than squid (transparent)?
In my scenario I can't use squid transparently. I'd like to add load balancing to a working server, but can't get much down time on it, thus will have small window within which to deploy it. Thus, any pre-knowledge would be of great help.