THIS IS A TEST INSTANCE. Feel free to ask and answer questions, but take care to avoid triggering too many notifications.
Ask Your Question

Revision history  [back]

Revision 2
grahamb's avatar
23.8k
grahamb
updated 2023-05-19 08:08:01 +0000

Same notebook - same server to contact - different behavior – different setting parameter [conversation completeness]

Hi everyone, I have a notebook and two different networks, in two different places, connected with a same server (server.xxxxx.com ) by two different IPSEC. Here a summary of the two networks experience. When the same notebook starts the conversation with the server, I noted the differences setting between the Wireshark parameter Conversation completeness 

-> Notebook -> Network # 1 -> IPSEC #1 -> server.xxxxx.com -> [Conversation completeness: **Incomplete, DATA (15)**] -> **works fine** 

-> Notebook -> Network #2 -> IPSEC #2 -> server.xxxxx.com -> [Conversation completeness: **Complete, WITH_DATA (47**)] -> **doesn’t work**

So, if I simply change the network, I don’t know where and why the same notebok really acquires the different setting of Conversation completeness parameter, for beginning the communication with the server. Can you help me to resolve that network enigma? Many thanks in advance for your collaboration. Felix

Revision 1
Felix's avatar
1
Felix
asked 2023-05-18 21:22:14 +0000

Same notebook - same server to contact - different behavior – different setting parameter [conversation completeness]

Hi everyone, I have a notebook and two different networks, in two different places, connected with a same server (server.xxxxx.com ) by two different IPSEC. Here a summary of the two networks experience. When the same notebook starts the conversation with the server, I noted the differences setting between the Wireshark parameter Conversation completeness 

-> Notebook -> Network # 1 -> IPSEC #1 -> server.xxxxx.com -> [Conversation completeness: **Incomplete, Incomplete, DATA (15)**] (15)] -> **works fine** 
works fine 
-> Notebook -> Network #2 -> IPSEC #2 -> server.xxxxx.com -> [Conversation completeness: **Complete, Complete, WITH_DATA (47**)] (47)] -> **doesn’t work**
doesn’t work

So, if I simply change the network, I don’t know where and why the same notebok really acquires the different setting of Conversation completeness parameter, for beginning the communication with the server. Can you help me to resolve that network enigma? Many thanks in advance for your collaboration. Felix