| 2021-06-26 11:57:45 +0000 | received badge | ● Popular Question (source) |
| 2019-12-16 10:37:47 +0000 | commented question | Wireshark trace - timeout problem just one notice. new lb that works is NLB while old one was classic load balancer in AWS |
| 2019-12-16 08:45:37 +0000 | commented question | Wireshark trace - timeout problem it seems that my colleague found what is wrong. There is a AWS load balancer in front of this ambassador pod, and when h |
| 2019-12-16 08:41:00 +0000 | commented question | Wireshark trace - timeout problem Sorry for that. public now. |
| 2019-12-15 20:24:49 +0000 | commented question | Wireshark trace - timeout problem Here are also traces on cloudshark: A dump (sending side - outside kubernetes) : https://www.cloudshark.org/captures/8cf |
| 2019-12-15 20:24:28 +0000 | answered a question | Wireshark trace - timeout problem Here are also traces on cloudshark: A dump (sending side - outside kubernetes) : https://www.cloudshark.org/captures/8cf |
| 2019-12-14 09:25:07 +0000 | commented question | Wireshark trace - timeout problem Tried that just now. Seems more-less the same. Here is updated image with all packets: https://prnt.sc/qap1zd Is it pos |
| 2019-12-13 15:08:25 +0000 | commented question | Wireshark trace - timeout problem B is in kubernetes. A is accessing it using this ambassador mapping service that is then forwarding it to the ambassador |
| 2019-12-12 09:54:04 +0000 | asked a question | Wireshark trace - timeout problem Wireshark trace - timeout problem I have following setup (as visible in the attached image): A (java process) -> B ( |
Copyright Wireshark Foundation, 2017-2020 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.