Date: Tue, 8 Oct 2019 12:17:47 +0100 From: Harry Duncan <usr.src.linux@gmail.com> To: =?UTF-8?Q?Morgan_Wesstr=C3=B6m?= <freebsd-database@pp.dyndns.biz> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Intermittent connectivity loss with em(4) Message-ID: <CAHAPYVA7neGfe1a90-dMbf9MSLrB%2BiMCvuCtBYOkNMR7HsPyoA@mail.gmail.com> In-Reply-To: <8c532e7a-241d-ce49-27d4-46a587538c85@pp.dyndns.biz> References: <ba24db9b-6a34-76d4-7c95-4c2e64d0a5a0@pp.dyndns.biz> <94B563F6-55C4-46BC-BD79-5CC2AD86E6C1@mail.sermon-archive.info> <43f0decc-d459-4ded-dc46-c249bc8e24c9@pp.dyndns.biz> <094A1786-98A8-4CEF-A036-5809D9705EC8@mail.sermon-archive.info> <eaa4fb4e-308d-ae37-4ede-7901034e6644@pp.dyndns.biz> <A9E5F776-CACA-4C3D-8A75-D5EC483874FA@mail.sermon-archive.info> <8c532e7a-241d-ce49-27d4-46a587538c85@pp.dyndns.biz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 8, 2019 at 9:52 AM Morgan Wesstr=C3=B6m <freebsd-database@pp.dyndns.biz> wrote: > Thank you, Harry. No, Linux isn't an alternative. I run it on my clients > but I feel much more comfortable with FreeBSD protecting my network. The > Linux iptables/networking learning curve would be to much for me. :) With you all the way there. > Only what is currently the cable modem interface is experiencing this > behaviour. I connect one of the others to my LAN and ssh to the machine > that way and I never lose connection through ssh. Interesting.... ssh ... so if ssh is failing through the cablemodem, that points to something very very different. SSH is very fault tolerant, as long as you don't try data entry, you can take down networks and put them back up and have it resume as before. If ssh session failure is what sparked this, then it is more likely that you are falling victim to your ISP doing something like 4 to 6 NAT or 6 to 4 or even 4 to 4 NAT with RFC1913 on one side, and the far side of the NAT not maintaining a constant IP through some load balancing setup. I've had some really weird experiences recently with the whole ip4/ip6, like travelling to SE Asia and not able to connect into my static ipv4 office network until I got a native to call the ISP and then made some change, and I got onto the "whole" internet then. I didn't look into it when I got what I wanted, but put it down to 6 to 4 nat/ Harry.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHAPYVA7neGfe1a90-dMbf9MSLrB%2BiMCvuCtBYOkNMR7HsPyoA>