Displaying 3 results from an estimated 3 matches for "mryg3a".
2017 Sep 05
3
Packet capture to analysis the tinc connection close
...0.0.102/32
IndirectData = yes
Port = 8102
Server side configure:
tinc.conf:
Name = abc
AddressFamily = ipv4
PingTimeout = 10
abc:
Address = 47.152.x.x(public address, 172.31.x.x as the private real NIC address)
Subnet = 10.0.0.16/32
Port = 443
IndirectData = yes
As you saw from https://ibb.co/mRyG3a <https://ibb.co/mRyG3a>, the connection get drop and re-establish very frequently, and the one highlighted as yellow, it’s the connection we’ll go into deep dive, which happens on 07:41:35, when you cross check this with https://ibb.co/b740UF <https://ibb.co/b740UF>, you’ll find that ev...
2017 Sep 07
0
Packet capture to analysis the tinc connection close
...t the connection was not stable to cause this issue, and BTW, I’ve set the PingTimeout to 10 seconds already, but this situation still happens a lot sometimes, but when the connection drop happens, the connection recovery pretty fast, normally in a minutes.
[...]
> As you saw from https://ibb.co/mRyG3a <https://ibb.co/mRyG3a>, the connection get drop and re-establish very frequently,
It looks like it happens almost exactly 10 minutes after a connection
was established. I suspect that there is a firewall or NAT device in
front of the client that drops any TCP connection after 10 minutes,
re...
2017 Sep 07
2
Packet capture to analysis the tinc connection close
...nection was not stable to cause this issue, and BTW, I’ve set the PingTimeout to 10 seconds already, but this situation still happens a lot sometimes, but when the connection drop happens, the connection recovery pretty fast, normally in a minutes.
> [...]
>> As you saw from https://ibb.co/mRyG3a <https://ibb.co/mRyG3a>, the connection get drop and re-establish very frequently,
>
> It looks like it happens almost exactly 10 minutes after a connection
> was established. I suspect that there is a firewall or NAT device in
> front of the client that drops any TCP connection...