Compressing/decompressing traffic & cache & unchanged ip

John-Mark Gurney gurney_j at resnet.uoregon.edu
Fri Sep 2 20:49:44 GMT 2005


Oleksandr Samoylyk wrote this message on Fri, Sep 02, 2005 at 23:02 +0300:
> I've a "strange" idea. Here I've outlined the plan:
> 
> ========================================================
> 
> Compress traffic   Uncompress traffic   Compress traffic
>        here              & cache               here
>   ___________          _________          ___________
>   |          |         |        |         |          |
> --|  Router  |         |  Our   |         |  Router  |--
> --| in city1 |-------->| ROUTER |<--------| in city2 |--
>   |__________|         |________|         |__________|
>                           |
>                           |
>           ________________|________________
>           |       |       |       |       |
>                      Our clients
> 
> ========================================================
> 
> So, let me describe the situation. We have our central router and 
> several router in different places. Unfortunately, we haven't got a good 
> connection to them. Our physical "link" to them is quite "narrow". 
> Nevertheless, our "external" routers are good connected to the "world" 
> (they have megabit uplinks). We can't at the moment got a better 
> connection between them and our central router :(.
> The ultimate aim is to speed up bandwidth for our clients by means of 
> software :)
> We had been using a transparent cache-server (Squid) for some time, but 
> it has the problem (as all proxies have). It changes ips of clients.
> I'd a sort of brain-wave :) and thought out the following:
> - On those routers we compress traffic (how?)
> - On our main router we decompress it and cache it (how?)
> - Moreover, it should be done transparently and without substitution of ip for client. So client even don't "feel" that he/she is behind proxy or so...  So everywhere should be ip of user not Squid one. (how?)
> - In addition to that it would be good to do this with HTTP and FTP as well...

ipsec has a layer that will do packet compression...   look at
-C calgo parameter to setkey(8), one of which is deflate..

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."


More information about the freebsd-net mailing list