Date: Mon, 4 Mar 2019 13:19:08 +0100 From: "Patrick M. Hausen" <hausen@punkt.de> To: Eugene Grosbein <eugen@grosbein.net> Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: TCP-forwarding with netcat - weird failures ... Message-ID: <C0F379B2-540A-4D39-9390-964F64B5EFCF@punkt.de> In-Reply-To: <a9a82e56-f7a7-97dd-86ba-948d91704ca2@grosbein.net> References: <D3EF7ABA-7674-4F7B-8ED2-21CED3BFB975@punkt.de> <a9a82e56-f7a7-97dd-86ba-948d91704ca2@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Eugene, > Am 04.03.2019 um 12:21 schrieb Eugene Grosbein <eugen@grosbein.net>: > > 04.03.2019 17:43, Patrick M. Hausen wrote: > >> Needless to say: doesn’t work. And no, it’s not the obvious ARP caches. >> Connections can be established but then abort spontaneously without >> an observable pattern or reason. > > Each "abort" of TCP connection has its own distinct reason: > TCP FIN or TCP RST or ICMP unreach or timeout etc. > > You need to start collecting packet captures with "tcpdump -npw file.pcap" > Without such details, noone can tell you what's your reason out of hundreds possible. You are of course right. We’ll start running both VMs in parallel on Wednesday to do exactly that. Kind regards Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe info@punkt.de http://punkt.de AG Mannheim 108285 Gf: Juergen Egeling
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C0F379B2-540A-4D39-9390-964F64B5EFCF>