From owner-freebsd-questions@freebsd.org Mon Oct 7 15:56:15 2019 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 93FE7132F21 for ; Mon, 7 Oct 2019 15:56:15 +0000 (UTC) (envelope-from freebsd-database@pp.dyndns.biz) Received: from keymaster.local (ns1.xn--wesstrm-f1a.se [IPv6:2a00:d880:5:1b9::8526]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "keymaster.pp.dyndns.biz", Issuer "keymaster.pp.dyndns.biz" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46n4pQ2ZGWz4Cvy for ; Mon, 7 Oct 2019 15:56:13 +0000 (UTC) (envelope-from freebsd-database@pp.dyndns.biz) Received: from [192.168.69.69] ([192.168.69.69]) by keymaster.local (8.15.2/8.15.2) with ESMTP id x97Fu8Wi062337 for ; Mon, 7 Oct 2019 17:56:10 +0200 (CEST) (envelope-from freebsd-database@pp.dyndns.biz) Subject: Re: Intermittent connectivity loss with em(4) To: freebsd-questions@freebsd.org References: <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> From: =?UTF-8?Q?Morgan_Wesstr=c3=b6m?= Message-ID: Date: Mon, 7 Oct 2019 17:56:07 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 MIME-Version: 1.0 In-Reply-To: <094A1786-98A8-4CEF-A036-5809D9705EC8@mail.sermon-archive.info> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 46n4pQ2ZGWz4Cvy X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd-database@pp.dyndns.biz has no SPF policy when checking 2a00:d880:5:1b9::8526) smtp.mailfrom=freebsd-database@pp.dyndns.biz X-Spamd-Result: default: False [3.72 / 15.00]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; IP_SCORE(-0.09)[asn: 198203(-0.44), country: NL(0.02)]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_MEDIUM(0.84)[0.838,0]; RCVD_TLS_LAST(0.00)[]; NEURAL_SPAM_LONG(0.77)[0.768,0]; HFILTER_HELO_IP_A(1.00)[keymaster.local]; R_SPF_NA(0.00)[]; HFILTER_HELO_NORES_A_OR_MX(0.30)[keymaster.local]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:198203, ipnet:2a00:d880::/32, country:NL]; MID_RHS_MATCH_FROM(0.00)[]; DMARC_NA(0.00)[pp.dyndns.biz]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Oct 2019 15:56:15 -0000 On 2019-10-07 05:55, Doug Hardie wrote: > Forgot to include, I use a lot of bge devices and some rl. However, I just discovered one of the remote client's computers has 2 em nics. I am running the ping test now on it. I did find the following in messages: > > zgrep em /var/log/messages* > /var/log/messages.6.gz:Sep 29 15:22:33 brain kernel: em0: link state changed to DOWN > /var/log/messages.6.gz:Sep 29 17:08:14 brain kernel: em0: link state changed to UP > /var/log/messages.6.gz:Sep 29 17:09:46 brain kernel: em0: link state changed to DOWN > /var/log/messages.6.gz:Sep 29 17:09:49 brain kernel: em0: link state changed to UP > > The first outage was a complete outage to that site. I don't know what caused it or how it got resolved. I never noticed the second one. > > The client has not been really thrilled with this machine. He had a much better one, but it was too noisy and replaced it. > > Yet another idea: get mtr "my trace route". package mtr-nox11 and use it to go to google. It is traceroute and ping combined. You can use -i 60 with it also. > > -- Doug Thank you for your suggestions, Doug. My suspicions right now points to my cable provider. I have two identical machines. One of them is always hooked up as my router/firewall and while that one is in service I'm free to experiment on the other. Earlier this year I switched from an ADSL provider to a DOCSIS 3.0 Cable provider. The ADSL provider used to give me 5 external IPs and I never had any trouble running both machines simultaneously through the ADSL modem. My cable provider gives me 4 IPs but this is the first time I attempt to run both machines simultaneously through the cable modem. Tcpdump shows a peculiar behaviour which is why my suspicions now points to the cable provider. While connectivity is established on my test router, tcpdump properly shows all packets leaving and entering that machine. But as soon as connectivity is lost, tcpdump suddenly starts showing packets that are leaving the _other_ machine instead. It only shows the leaving packets though, not the incoming ones but regardless I believe this behaviour isn't normal. As soon as connectivity returns on my test machine, tcpdump once again returns to only show the packets from that machine. Connectivity is never affected on the main machine when this happens and at some point I'll have to unplug it and only have the test machine connected but I have quite a few services running on that machine so it's painful to disconnect it, even for a short time. My DOCSIS knowledge is very limited and I have no idea how I can test for proper functionality of my cable modem. There are very few settings in it, none that I find relevant to this problem and the logs don't show any errors so I'm lost for now. /Morgan