dispatch-proxy only works with HTTP and Socks. Any other protocol will be untouched at its layer. Openwrt is for embedded network equipment. I cant verify this yet, but I believe they have completely rewritten the network stack. So each does their load balancing and proxying in completely different ways than you will.
On Wed, Oct 14, 2020, 9:21 AM Susmita/Rajib <bkpsusmi...@gmail.com> wrote: > ---------- Received message ---------- > From: Dan Ritter > Date: Wed, 14 Oct 2020 09:17:25 -0400 > Subject: Re: Have Debian developers contemplated means of faster > internet access, using in parallel multiple ISPs from Debian installed > Lap- /Desk- tops? > To: Susmita/Rajib <bkpsusmi...@gmail.com> > Cc: debian-user@lists.debian.org > > Susmita/Rajib wrote: > > > ... ... [snipped] ... ... [snipped] > ... ... > > Packets have the following characteristics, at a minimum: > > IP of the sender > port number of the sending process > IP of the destination > port number of the destination > > When a network interface connects to a network, it has an IP > address assigned to it. (This can be static or dynamic; it does > not matter here.) The network will only send packets that are > destined for that IP address. > > An interface connecting to network A gets an address from > network A; an interface on network B has an address from network > B. > > When your computer sends out a request, it can pick either > network A or network B, but the sender IP will always match the > network that it picks, and so the answer will come in on the > same network. > > You have some options: > > - you can pick one network as primary and the other as > secondary, and stop using the primary if it fails. > > - you can assign some of your traffic to each network, but > answers will come back over the same network and you do not > get an increase in bandwidth for any given session. > > - you might be able to set up a proxy on a well-connected > machine somewhere, and send all your traffic via that proxy, > which understands that there are two paths back to you. > However, those two paths are likely to be of different > latencies, and you will see many exciting problems including > out-of-order packets, dropped packets, and repeated packets. > > Does this help? > > -dsr- > > > Wow! Unbelievable, Dr. Ritter, but I understood your line of reasoning. > > Okay, but then some questions arise: > (1) How does "openwrt (https://openwrt.org/) able to achieve a > similar objective? If my original Debian Forums thread and posts have > been perused. > > (2) Again, how dispatch-proxy is able to achieve a similar > objective? My earlier post was here: > https://lists.debian.org/debian-user/2020/10/msg00118.html > Unfortunately, I received no reply for the post. Very well. Let us > continue to keep it dead, but use the information posted there. > > Your post provides me an opportunity to clear some of my doubts, which > are endless. Etenally. > > I must keep my questions very focussed so that I don't irritate or lose > you. > In general, cognitive elites shall choose to ignore queries posted by > nincompoops such as I. > > So, I thank you for choosing to reply to my query. > > Regards, > Rajib > >
