Wan Optimization Support

Technical => Features => : hkaiser January 04, 2017, 10:05:48 PM

: Please explain how deduplication works in bridge mode
: hkaiser January 04, 2017, 10:05:48 PM
Hi,
Could you explain me how deduplication in brigde mode works? thanks in advance.

with best regards
HK
: Re: Please explain how deduplication works in bridge mode
: ahenning January 05, 2017, 10:21:37 AM
Hi,

Deduplication works the same in both bridge and tunnel mode:

The datastore is like a large dictionary. The English language dictionary has about 170k words, but the Wanos byte dictionary will have many millions or many hundreds of millions of words.

When data is sent across the WAN, Wanos will look for these words in the packets and replace the byte-word in the packet with the location in the dictionary, e.g. Page 100 Line 40. The short code might look something like 100,40. The receiver then looks in the dictionary on this location and finds the data and replace the dictionary location code with the original byte-word data. Once it is complete, the packet payload is a 100% match of the original.
: Re: Please explain how deduplication works in bridge mode
: hkaiser January 05, 2017, 11:27:07 PM
So you need in bridge mode also two wanos appliances to do deduplication? thanks in advance.
: Re: Please explain how deduplication works in bridge mode
: ahenning January 06, 2017, 10:29:54 AM
Yes, the dictionary needs to be on both sides. The sender uses the dictionary to compress the data and the receiver uses the dictionary to decompress.
: Re: Please explain how deduplication works in bridge mode
: hkaiser January 06, 2017, 10:33:33 PM
But how each other side get to know that they have to exchange data? Where I can configure this?
: Re: Please explain how deduplication works in bridge mode
: ahenning January 09, 2017, 12:25:59 PM
On a point to point link, defaults should be enough, because all traffic is sent to the one remote site. Once peer status is up, they will start to exchange data.

On a meshed or multisite network, add the remote subnets in the multisite config and traffic policies. Then bypass all other traffic with a default bypass rule #99. Note from v.4 onward these steps are no longer required.