Displaying 2 results from an estimated 2 matches for "explicit_congestion_notification".
2015 May 15
2
unreachable peer
....yy.yy.yy.https: tcp 0
15:58:12.746408 IP o.ff.i.ce.50902 > yy.yy.yy.yy.https: tcp 0
15:58:36.740454 IP o.ff.i.ce.50902 > yy.yy.yy.yy.https: tcp 0
15:59:24.728605 IP o.ff.i.ce.50902 > yy.yy.yy.yy.https: tcp 0
I tried to connect with a removed ecn bit [1]
[1] https://en.wikipedia.org/wiki/Explicit_Congestion_Notification
but this was not the solution.
Any ideas?
--
Thanks in advance!
LF
2015 May 16
3
unreachable peer
...902 > yy.yy.yy.yy.https: tcp 0
>> 15:58:36.740454 IP o.ff.i.ce.50902 > yy.yy.yy.yy.https: tcp 0
>> 15:59:24.728605 IP o.ff.i.ce.50902 > yy.yy.yy.yy.https: tcp 0
>>
>> I tried to connect with a removed ecn bit [1]
>>
>> [1] https://en.wikipedia.org/wiki/Explicit_Congestion_Notification
>>
>> but this was not the solution.
>>
>> Any ideas?
>
> That's not much information to go on. Can you run
> tcpdump on the "public peer system"? Does it receive
> the SYN packets from your office?
Well, the destination is not in my realm (d...