Date: Sat, 6 Jul 2024 08:02:08 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: Andrea Venturoli <ml@netfence.it> Cc: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, Ronald Klop <ronald-lists@klop.ws>, freebsd-net@FreeBSD.org Subject: Re: OpenVPN suddenly working one way only Message-ID: <202407061502.466F28cR033040@gndrsh.dnsmgr.net> In-Reply-To: <0a73a3e3-ebfe-4392-a598-5d76108f74e5@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 7/6/24 02:17, Rodney W. Grimes wrote: > > Host A *still* has/had a port open, and that port can lingere > > for several reasons, and that can cause issues. > > > > Ok, good, check both A and B. > > I had checked this too: neither A nor B had the port still open. > > > > > MTU's? Have you manually checked path MTU to make sure that it > > can carry your payload correctly IN BOTH DIRECTIONS. I have > > seen asymetrical routes cause MTU issues due to it being smaller > > in one direction. > > That's the first thing I thought: however a simple ping does not get > through and that's a small packed. Are you pinging the inside or outside address of the vpn? If you cant even ping the outside IP of a VPN you have basic connectivity problems that must be fixed before even attempting a VPN. > bye & Thanks > av. -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202407061502.466F28cR033040>