From owner-freebsd-questions@freebsd.org Thu Oct 10 14:00:51 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 8553F1394C3 for ; Thu, 10 Oct 2019 14:00:51 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (mx32.harte-lyne.ca [216.185.71.32]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mx32.harte-lyne.ca", Issuer "CA_HLL_ISSUER_2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 46pt5s3n24z41lT for ; Thu, 10 Oct 2019 14:00:49 +0000 (UTC) (envelope-from byrnejb@harte-lyne.ca) Received: from mx32.harte-lyne.ca (localhost [127.0.32.1]) by mx32.harte-lyne.ca (Postfix) with ESMTP id 7EE0C21CB4; Thu, 10 Oct 2019 10:00:39 -0400 (EDT) X-Virus-Scanned: amavisd-new at harte-lyne.ca Received: from mx32.harte-lyne.ca ([127.0.32.1]) by mx32.harte-lyne.ca (mx32.harte-lyne.ca [127.0.32.1]) (amavisd-new, port 10024) with ESMTP id aY1tOsR1eN8D; Thu, 10 Oct 2019 10:00:29 -0400 (EDT) Received: from webmail.harte-lyne.ca (webmail.hamilton.harte-lyne.ca [216.185.71.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx32.harte-lyne.ca (Postfix) with ESMTPSA id 348AC21CA9; Thu, 10 Oct 2019 10:00:25 -0400 (EDT) Received: from 216.185.71.44 (SquirrelMail authenticated user byrnejb_hll) by webmail.harte-lyne.ca with HTTP; Thu, 10 Oct 2019 10:00:26 -0400 Message-ID: In-Reply-To: References: Date: Thu, 10 Oct 2019 10:00:26 -0400 Subject: Re: Intermittent connectivity loss with em(4) From: "James B. Byrne" To: nervoso@k1.com.br Cc: =?iso-8859-1?Q?=22Morgan_Wesstr=F6m=22?= , "FreeBSD Questions" Reply-To: byrnejb@harte-lyne.ca User-Agent: SquirrelMail/1.4.23 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Rspamd-Queue-Id: 46pt5s3n24z41lT X-Spamd-Bar: -------- X-Spamd-Result: default: False [-8.47 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[harte-lyne.ca:s=dkim_hll]; RCVD_COUNT_FIVE(0.00)[5]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+ip4:216.185.71.0/26]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; REPLYTO_ADDR_EQ_FROM(0.00)[]; HAS_REPLYTO(0.00)[byrnejb@harte-lyne.ca]; TO_DN_SOME(0.00)[]; DWL_DNSWL_LOW(-1.00)[harte-lyne.ca.dwl.dnswl.org : 127.0.4.1]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; RCVD_IN_DNSWL_MED(-0.20)[32.71.185.216.list.dnswl.org : 127.0.4.2]; DKIM_TRACE(0.00)[harte-lyne.ca:+]; HAS_X_PRIO_THREE(0.00)[3]; DMARC_POLICY_ALLOW(-0.50)[harte-lyne.ca,quarantine]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:12021, ipnet:216.185.64.0/20, country:CA]; IP_SCORE(-3.77)[ip: (-9.90), ipnet: 216.185.64.0/20(-4.93), asn: 12021(-3.94), country: CA(-0.09)] 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: Thu, 10 Oct 2019 14:00:51 -0000 On Tue, October 8, 2019 09:07, Sergio de Almeida Lenzi wrote: > Em ter, 2019-10-08 às 10:51 +0200, Morgan Wesström escreveu: >> That is almost correct. The cable modem is a SagemCom 2864 with >> tailored >> firmware for my ISP and it has a setting to switch between >> NAT/bridge >> mode. I've put it in bridge mode and the ISP provides 4 public >> IP-addresses through DHCP. > > Hello... in Brazil I solved the problem when I put a small 5 port > switch between the modem and the FreeBSD machine.. > one cable FreeBSD -> small switch -> modem instead of : Freebsd -> > modem > since than no connection drop at all > > I do not know why this happens.. must be something about hardware, > timing... > It the host with the problem has an Intel Atom mainboard then the BIOS might be set to power off the NIC chip if there is no traffic on the port for an extended period. The hub might be generating enough heartbeat traffic to keep the timeout from happening while the cable modem does not. We had this happen with some of our gateways built on Atom board systems. The BIOS was factory set to use this feature as a power-saving device on laptops. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3