I encounter a strange behaviour using Pulse with other network-related software on clients sides.
Riverbed clients seems to be the one leading to my problem with Pulse.
We use SSL mode and not ESP.
As I know/read somewhere, Pulse allocates itself 100Bytes on total packet size, letting 1360 free.
In some case, using Riverbed client software, some packets are dropped througt the tunnel or at entry, probably because riverbed added some over-data to the header, which is now too long.
My question is quite simple but not easy to find:
- Do anyone can explain how much data Pulse in SSL mode adds to a packet?
- Is it possible to tune the 100B reserved by Pulse to avoid problems?(guess the answer is no but..)
Thanks for any help/advices on this one.
Solved! Go to Solution.