From nobody Thu Dec 08 01:03:24 2022 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4NSG9x4d0Bz4kKrr for ; Thu, 8 Dec 2022 01:03:33 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from holgerdanske.com (holgerdanske.com [184.105.128.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "holgerdanske.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4NSG9w5mD2z4NH7 for ; Thu, 8 Dec 2022 01:03:32 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=holgerdanske.com header.s=nov-20210719-112354 header.b=17qXWrGm; spf=pass (mx1.freebsd.org: domain of dpchrist@holgerdanske.com designates 184.105.128.27 as permitted sender) smtp.mailfrom=dpchrist@holgerdanske.com; dmarc=pass (policy=none) header.from=holgerdanske.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=holgerdanske.com; s=nov-20210719-112354; t=1670461405; bh=E1TEOmyjnKa+0gcwEEOOxQZzwPN06O8QQT2MGkGXhxo=; h=Received:Message-ID:Date:MIME-Version:User-Agent:Subject:To: References:Content-Language:From:In-Reply-To:Content-Type: Content-Transfer-Encoding; b=17qXWrGm1vDHHE1r9ds4/tPasXg/cOBjzk8KnRwgzcwKdvdZ7qw9CRRMAxQarWUbE KeQ/EThmBQC2XTC9ytt8wfHQQm+hn53jpsGTLaraz4sIi5SDKRwUz4uvHNBZKqpZ1C OMVfTcH4FpM6/2T6pdyTPgv5ceXs3+jJMX8KoFnY5lg/AZp49QZ32SyV0CoOJ9JFB+ z3ou+N3wPmGsB7Lg5OjcwM3Iw/w5V9tYEEPvRR6f/bmlFj/8LehBpBNMBvETZvMJ4h NvzES7PK2d4/PfBQCIO8cwKwvgD0tNuWrFIdA5jO7r+bxxqRvwP1/2ztUxZqdqV+5l PRYigS8B5kEy+O3uH7HLHnT6JY8ueBL9Q48Ptbnjva4DGYTliS0FYtB/4Kv6nZmOMc fZd9dIY3nekLsCygIwIzMRGjVs+3UGY9ybrod3Ytc2by1t+wtpPfwZ0XBTKIW5+/pu l/bOl5u0H4Fz5qGH73abYjeQMaDs30w6BxSphu7rVb8oODSYNj54CVGCvj7hz7Hb1d ETFVOqx1+mlRPbujEafV4d+xqOthoNlVRlu3SzvLf8ycFMb14E7+VMbgt0aC9vu1p5 1cfqwuHe6QFcEdO+055RkGvwWLSgRhITOo6LvzFrmflftnbNHWd9QHvR1mZ5ZQRCQq AmZgpYHqPkR1YiI2Am6JePhk= Received: from 99.100.19.101 (99-100-19-101.lightspeed.frokca.sbcglobal.net [99.100.19.101]) by holgerdanske.com with ESMTPSA (TLS_AES_128_GCM_SHA256:TLSv1.3:Kx=any:Au=any:Enc=AESGCM(128):Mac=AEAD) (SMTP-AUTH username dpchrist@holgerdanske.com, mechanism PLAIN) for ; Wed, 7 Dec 2022 17:03:25 -0800 Message-ID: <1eacf9a2-d466-62bb-067a-4d886aa53382@holgerdanske.com> Date: Wed, 7 Dec 2022 17:03:24 -0800 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: FreeBSD keep loosing ethernet connection To: questions@freebsd.org References: Content-Language: en-US From: David Christensen In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; DMARC_POLICY_ALLOW(-0.50)[holgerdanske.com,none]; R_SPF_ALLOW(-0.20)[+a]; R_DKIM_ALLOW(-0.20)[holgerdanske.com:s=nov-20210719-112354]; MIME_GOOD(-0.10)[text/plain]; DKIM_TRACE(0.00)[holgerdanske.com:+]; ASN(0.00)[asn:6939, ipnet:184.104.0.0/15, country:US]; MLMMJ_DEST(0.00)[questions@freebsd.org]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4NSG9w5mD2z4NH7 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On 12/7/22 16:21, iio7@tutanota.com wrote: > I have recently changed one of my long running boxes from Arch Linux > to FreeBSD 13.1, after which I see this in the log during file transfers: > > > Dec  8 01:01:41 foo kernel: re0: watchdog timeout > Dec  8 01:01:41 foo kernel: re0: link state changed to DOWN > Dec  8 01:01:45 foo kernel: re0: link state changed to UP > Dec  8 01:01:51 foo kernel: re0: watchdog timeout > Dec  8 01:01:51 foo kernel: re0: link state changed to DOWN > Dec  8 01:01:55 foo kernel: re0: link state changed to UP > Dec  8 01:02:02 foo kernel: re0: watchdog timeout > Dec  8 01:02:02 foo kernel: re0: link state changed to DOWN > Dec  8 01:02:06 foo kernel: re0: link state changed to UP > Dec  8 01:02:18 foo kernel: re0: watchdog timeout > Dec  8 01:02:18 foo kernel: re0: link state changed to DOWN > Dec  8 01:02:22 foo kernel: re0: link state changed to UP > Dec  8 01:02:30 foo kernel: re0: watchdog timeout > Dec  8 01:02:30 foo kernel: re0: link state changed to DOWN > Dec  8 01:02:34 foo kernel: re0: link state changed to UP > Dec  8 01:02:45 foo kernel: re0: watchdog timeout > Dec  8 01:02:45 foo kernel: re0: link state changed to DOWN > Dec  8 01:02:49 foo kernel: re0: link state changed to UP > Dec  8 01:03:01 foo kernel: re0: watchdog timeout > Dec  8 01:03:01 foo kernel: re0: link state changed to DOWN > Dec  8 01:03:05 foo kernel: re0: link state changed to UP > Dec  8 01:03:14 foo kernel: re0: watchdog timeout > Dec  8 01:03:14 foo kernel: re0: link state changed to DOWN > Dec  8 01:03:18 foo kernel: re0: link state changed to UP > Dec  8 01:03:26 foo kernel: re0: watchdog timeout > Dec  8 01:03:26 foo kernel: re0: link state changed to DOWN > Dec  8 01:03:30 foo kernel: re0: link state changed to UP > Dec  8 01:03:47 foo kernel: re0: watchdog timeout > Dec  8 01:03:47 foo kernel: re0: link state changed to DOWN > Dec  8 01:03:51 foo kernel: re0: link state changed to UP > Dec  8 01:03:57 foo kernel: re0: watchdog timeout > Dec  8 01:03:57 foo kernel: re0: link state changed to DOWN > Dec  8 01:04:01 foo kernel: re0: link state changed to UP > Dec  8 01:04:31 foo kernel: re0: watchdog timeout > Dec  8 01:04:31 foo kernel: re0: link state changed to DOWN > Dec  8 01:04:35 foo kernel: re0: link state changed to UP > Dec  8 01:05:09 foo kernel: re0: watchdog timeout > Dec  8 01:05:09 foo kernel: re0: link state changed to DOWN > Dec  8 01:05:13 foo kernel: re0: link state changed to UP > Dec  8 01:13:39 foo kernel: re0: watchdog timeout > Dec  8 01:13:39 foo kernel: re0: link state changed to DOWN > Dec  8 01:13:41 foo kernel: . > Dec  8 01:13:42 foo kernel: , 52791. > Dec  8 01:13:43 foo kernel: > Dec  8 01:13:43 foo kernel: re0: link state changed to UP > Dec  8 01:13:44 foo kernel: . > > > During which I eventually loose connection completely and have to > manually reboot the box. > > When I run Linux on the box all runs well, so I don't suspect the > ethernet card. > > The card is setup with a static IP address: > > ifconfig_re0="inet 192.168.1.3/24" > > So it really should NOT change the state like this. > > Any advice? > > Kind regards. My SOHO server has a static IP and works reliably: 2022-12-07 16:59:38 toor@f3 ~ # freebsd-version ; uname -a 12.3-RELEASE-p9 FreeBSD f3.tracy.holgerdanske.com 12.3-RELEASE-p6 FreeBSD 12.3-RELEASE-p6 GENERIC amd64 2022-12-07 17:00:43 toor@f3 ~ # grep 192.168.5 /etc/rc.conf | grep -v alias defaultrouter="192.168.5.1" ifconfig_em0="inet 192.168.5.13 netmask 255.255.255.0" I do not see a 'defaultroute' in your post. I do not see a 'netmask' in your post. I would try adding them and rebooting. David