Inbound load balance is ok ! but outbound only using wan
-
The tittle speaks for itself, after some brainstorm i finally manage to make (thanks Gruens ;D) inbound load balance to work.
(I´m having some issues with download speed not using all the different speed avaliable, but i think this is solved setting multiple times the same wan connection correct ?)
But now what concerns me is the outbound, in this case i´m using uTorrent, and the its using only the wan connection to seed :'(
The oubound rules generation is set to automatic ! is this right ? Information abou this topic is really scarce on the forums.
Thanks for the help ;D
-
You do have to create some rules and some pools for outbound load balancing. This excellent document lays it out pretty well.
http://doc.pfsense.org/index.php/MultiWanVersion1.2
db
-
Bittorrent, seeding and multiWAN wont work together.
You would have to announce two IP's to the tracker which is afaik in no client possible.It will only work if you establish outbound, balanced, a connection to a peer.
-
You could run a couple instances of bittorrent, or two BT programs if necessary, and have each bind to a different WAN. The trick is to be able to use pfsense's firewall to distinguish traffic from the two running instances and filter them each to its own WAN. This would be simple enough for seeding, as each could listen on a different port and be filtered by that.
For downloading however, you may have to create an alias for your torrenbox's LAN IP address, or get a second NIC or a second torrent box. Bind each instance of BT to a different LAN IP and pfsense can direct the outgoing connections thereby.
db
-
For downloading however, you may have to create an alias for your torrenbox's LAN IP address, or get a second NIC or a second torrent box. Bind each instance of BT to a different LAN IP and pfsense can direct the outgoing connections thereby.
Well i dont see much of a problem for downloading with a single bt client on a single LAN IP.
If you create an outbound connection with an IP unknown to a peer/seed, he will just add it to its list of clients.
Even if he doesnt know about this peer from the tracker.
To the remote peer/seed it would just seem like a new peer connected.Or what is your idea behind having multiple LAN IPs?
-
You're probably right about downloading, outbound loadbalancing should do the trick.
As for seeding, on second thought, if you run a couple instances of bittorrent and get them to independently announce your separate WAN IPs then you should be able to utilise both WANs for incoming.
db
-
As for seeding, on second thought, if you run a couple instances of bittorrent and get them to independently announce your separate WAN IPs then you should be able to utilise both WANs for incoming.
Yeah this will most probably work.
I read a bit up on the various bt client forums and this question has come up.
The general consensus is to run two instances of the client.
