Redirect/proxy traffic using L7?

I have a client that is using software which uploads a fairly large amount of data to a web server. They currently have 10 bundled but not bonded DSL connections. So the upload for a single stream is limited to the speed of a single DSL line which is rather slow.
What I want to do is take traffic and direct it to a bonded EoIP tunnel to one of our locations, and then out from there to the destination site

So it looks somewhat like

..[||||||] ..[||||||] <---- Multiple slow connections ..[||||||] .....| <-------- Fast Fibre Connection .....|

But ONLY traffic going to this particular site, and not everything.
The process should be as transparent as possible so the client’s PC thinks its directly transferring to the website. We can’t match IP addresses as the site has so many IP’s it would be practically impossible to find them all. So it appears Layer 7 is the way to go. Problem is I have limited understanding of the syntax and appropriate mangle rules to make it work

Any help?

Hi ,
Of course your destination web server has many IP’s but it’s not so difficult to find them , 99% they are in a single subnet ,
if not at least you client application using one or two of them with , so you can find IP’s

L7 is not reliable feature and it’s completely dependent on HTTP headers and commands.

even i don’t recommend Bonding except for Back up and redundant links.

I suggest you to use Load Balancing over your DSL connections ,

http://wiki.mikrotik.com/wiki/Load_Balancing

http://mum.mikrotik.com/presentations/US12/steve.pdf

The individual Load balancing won’t work, as the entire purpose of this exercise is to increase the bandwidth for singular connections. The 10x ADSL connections are load balanced but that means when 1 user is uploading a large amount of data, it’s only going to go at approx 1mbit/s
We want to bond it so that 1 user can achieve up to 10mbit/s. Because we don’t control the ISP we can’t have a EoIP or bonded link directly, the best we can do is bond links to one of our sites which has plenty of bandwidth, and then upload from there

But as mentioned can only be for certain connections so we aren’t needlessly wasting bandwidth. Another issue is related to DNS. The servers that are involved have a mechanism in place whereby if a DNS query comes through from 1 IP and then the connection immediately after from another IP, it blocks the connection. Massive pain in the ass but nothing we can do about it. There are literally hundreds of individual IP’s in different subnets