From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id kC/3Ata+NmS94AAASxT56A (envelope-from ) for ; Wed, 12 Apr 2023 16:23:18 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id yCfbAta+NmSihwAAauVa8A (envelope-from ) for ; Wed, 12 Apr 2023 16:23:18 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id BF0F93EF13 for ; Wed, 12 Apr 2023 16:23:17 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pmbN6-0003aF-0f; Wed, 12 Apr 2023 10:22:52 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pmbN4-0003Zc-2b for help-guix@gnu.org; Wed, 12 Apr 2023 10:22:50 -0400 Received: from koszko.org ([93.95.227.159]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pmbN1-0007Gq-8X for help-guix@gnu.org; Wed, 12 Apr 2023 10:22:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=koszko.org; s=mail; h=Content-Type:MIME-Version:References:In-Reply-To:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=rVoPAFAwzhSf2givE1fQXwgYpSfTdTHZ8BwUAX8l/nI=; b=up6GUUdu9BgSqmXEcThZZUaycO FPEmqo4IOzRaSE8kyVc3MM9lAWJcfElbLK/JcBeU8k717+AV/gfOKAqFF/0tGZQ/fgka15BD6++pm tR3d+BPF/5ILSXIWP3ibrPpBWF2GAVlqLIn2oscZcpBlR+ZQ8pRvpslWi3+0j5dkptnVKk+G/nmdG ZE2t2AvEYnZTrS+8j6RMZTACrt7egrYdMKd1Ygms0FO1vZG4AJVJVdu/eOXOJyjRxG1q8f2Iv6Qgt t8zTDnmee2pEfPPDIQGldsR+Qwmlq9tedmAvcT8XYHcBKv7wakmsggmGn1VY+/LBDaph6bbuyIB4w 0PQBjjEo2xiuccDB6v8UpE+OHa9AN60VYnbkACSLF5NXZ0RQhhYvj3/9Js7Nr1xJ5ND4r/LGRDdr8 2RaOXnj1T10XgFwIeRcjiL592Gx29MqA1tRTCPBqifNmG1LN0SvbNtsH/y/p1UKyhjwTbLwTf37HP delH95+/rP9Sbq8c0NWrEg7kVq/dhSRO9RYSURI2sVH4KdxnhbZQsanMIPYZPCXcc/mcsPrBFivwG IA3p3eEST/SYC6PTsLFjdISRNr41KHOjO4v0tEgio1JGUH6qLDzKjBvZy7/C2aBkPAeeFUS5cl8zM OWM0A7SPSZhnCj2BFkmEQfKjhKYGAt/7nZIlCr7lU=; Received: from [77.252.47.222] (helo=koszkonutek-tmp.pl.eu.org) by koszko.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pmbMs-00010g-4V; Wed, 12 Apr 2023 16:22:38 +0200 Date: Wed, 12 Apr 2023 16:22:33 +0200 To: Gottfried Cc: help-guix@gnu.org, ds-ac@nanein.fr Subject: Re: internet connection freezes Message-ID: <20230412162233.235c6b93.koszko@koszko.org> In-Reply-To: References: <96f803f7-2736-8558-e470-77b58d733289@posteo.de> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/J6ZUWrWZoHq_6OCuSFhLTG+"; protocol="application/pgp-signature"; micalg=pgp-sha256 Received-SPF: pass client-ip=93.95.227.159; envelope-from=koszko@koszko.org; helo=koszko.org X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-to: Wojtek Kosior From: Wojtek Kosior via Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: help-guix-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Seal: i=1; s=key1; d=yhetil.org; t=1681309397; a=rsa-sha256; cv=none; b=GPRe6fAQybwZOrI6s6uCIVkgwjW7fxRZ6Z9aj/U7Ped+/nIMgmjZu83YTLq+3hZqheJKuC lUuMS09jtW5UeGfECMDBVH+VJe3jKFexPlNyu3XlKxA5kKhfVP3TdNN+MF5EBKJnRRE21d dDPmYOTIFjoO7F1SBJX43iyCarIVLVPy5JT+i808gNp+ZABeHiY9FWwvaslC4oQykIMvIp wRfNGLLfonWsQlg16/YWTbSba0+JG/0gfEly4y2rnMSK0UJG0Yr+2zuypFk2TPmCdBfamD uQ9SMh6ldSP33lPxAjsql1ibhuiRUJA7tzd1of3CZmJm6pXGbAur2KvnOf3HCA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=koszko.org header.s=mail header.b=up6GUUdu; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gnu.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1681309397; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=rVoPAFAwzhSf2givE1fQXwgYpSfTdTHZ8BwUAX8l/nI=; b=pZ7bu8TLv2LDtRYEE5cl4C+sBwuGmzshqmc+KyyIt+MazfDTBbcIELpO93EXg5g5upg8pY 3cqPEMoOvwguZtG8aKT3mSh8I1VBMKdZXl8qywNO83SvqdadKZq7HY68XZ702X/QI5PizB DteTyTBxHlywCNLtQOfslKV9Nfl7I2SvoayRhYaPMfC9onLO1Q0IejyYMaEdp5bzawGliQ /qEjrkmD8xs4HqK/w8nlEhygxMzyZs7LoP861pN6taZfzEIo5KaFLZgKpn/FjpuvmVxm6A cQGAZ28G/oqj6LAi4eBm1uEZ12z0SLLPfJkTxLt10T02W+Pe3OAlYfQlZ5pNHg== X-Migadu-Queue-Id: BF0F93EF13 Authentication-Results: aspmx1.migadu.com; dkim=fail ("headers rsa verify failed") header.d=koszko.org header.s=mail header.b=up6GUUdu; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gnu.org X-Migadu-Scanner: scn0.migadu.com X-Migadu-Spam-Score: -6.92 X-Spam-Score: -6.92 X-TUID: gKYArPzK/kJX --Sig_/J6ZUWrWZoHq_6OCuSFhLTG+ Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Gottfried, Sorry, this command I suggested (`sudo herd restart network-manager`) was incorrect. The one given by Paren, `sudo herd restart networking`, is the right one. Try it. > I connect my laptop via ethernet cable, LAN, to a router And I assume you already tried re-plugging it? > gfp@Tuxedo ~$ `nmcli connection down \ > && nmcli connection up ` >=20 > -bash: command substitution: line 1: syntax error near unexpected > token `newline' > -bash: command substitution: line 1: `nmcli connection down > name> ' =20 >=20 > .................................................................... > 9. > gfp@Tuxedo ~$ `nmcli connection down \ > && nmcli connection up `. >=20 > -bash: command substitution: line 1: syntax error near unexpected > token `&&' -bash: command substitution: line 1: `nmcli connection > down name> && nmcli connection up ' =20 > -bash: .: filename argument required > .: usage: . filename [arguments] >=20 > I am not sure how the command should look like. Arnaud surely wanted you to replace the "" part with the name of an actual connection on your system. It seems a bridge (aka a virtual connection) under the name "virbr0" somehow got created on your system. You could try running nmcli connection down virbr0 && nmcli connection up enp53s0 Alternatively, you could even try sudo ip link del virbr0 to remove this mysterious virtual bridge instead of disabling it > There is no possibility shown to enable networking again, no button > to click.... Not even a button to turn it off? Perhaps there's at least some helpful context menu available when right-clicking? > 5. > nmcli g > STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN > connected (local only) limited missing enabled missing enabled >=20 >=20 > Does this mean WIFI is on my lapttop enabled? > If yes, how can I switch it off? I guess it tells you that WiFi is enabled in software but also that no WiFi hardware is available to Network Manager. Which means it's not going to use WiFi anyway. If you want to also disable WiFi in software (only practically useful when Network Manager has access to some WiFi hardware), you can run nmcli radio wifi off as per nmcli's manpage. Wojtek -- (sig_start) website: https://koszko.org/koszko.html PGP: https://koszko.org/key.gpg fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A =E2=99=A5 R29kIGlzIHRoZXJlIGFuZCBsb3ZlcyBtZQ=3D=3D | =C3=B7 c2luIHNlcGFyYXR= lZCBtZSBmcm9tIEhpbQ=3D=3D =E2=9C=9D YnV0IEplc3VzIGRpZWQgdG8gc2F2ZSBtZQ=3D=3D | ? U2hhbGwgSSBiZWNvbWUg= SGlzIGZyaWVuZD8=3D -- (sig_end) On Wed, 12 Apr 2023 10:54:20 +0000 Gottfried wrote: > Hi, > thanks for help, >=20 > sorry , I forgot to say that: >=20 > I connect my laptop via ethernet cable, LAN, to a router > --------------------------------------------------------------------- > 1. > gfp@Tuxedo ~$ nmcli > virbr0: connected (externally) to virbr0 > "virbr0" > bridge, 52:54:00:16:E9:74, sw, mtu 1500 > inet4 192.168.100.1/24 > route4 192.168.100.0/24 metric 0 >=20 > enp53s0: unavailable > "Realtek RTL8111/8168/8411" > ethernet (r8169), D4:93:90:07:A2:AD, hw, mtu 1500 >=20 > ---------------------------------------------------------------------- >=20 > 2. > Use "nmcli device show" to get complete information about known devices a= nd > "nmcli connection show" to get an overview on active connection profiles. >=20 > Consult nmcli(1) and nmcli-examples(7) manual pages for complete usage=20 > details. >=20 > .........................................................................= .. > 3. > gfp@Tuxedo ~$ nmcli device show > GENERAL.DEVICE: virbr0 > GENERAL.TYPE: bridge > GENERAL.HWADDR: 52:54:00:16:E9:74 > GENERAL.MTU: 1500 > GENERAL.STATE: 100 (connected (externally)) > GENERAL.CONNECTION: virbr0 > GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/3 > IP4.ADDRESS[1]: 192.168.100.1/24 > IP4.GATEWAY: -- > IP4.ROUTE[1]: dst =3D 192.168.100.0/24, nh =3D= =20 > 0.0.0.0, mt =3D 0 > IP6.GATEWAY: -- >=20 > GENERAL.DEVICE: enp53s0 > GENERAL.TYPE: ethernet > GENERAL.HWADDR: D4:93:90:07:A2:AD > GENERAL.MTU: 1500 > GENERAL.STATE: 20 (unavailable) > GENERAL.CONNECTION: -- > GENERAL.CON-PATH: -- > WIRED-PROPERTIES.CARRIER: off > IP4.GATEWAY: -- > IP6.GATEWAY: -- >=20 > ...................................................................... >=20 >=20 > 4. > gfp@Tuxedo ~$ nmcli connection down \ > && nmcli connection up > -bash: syntax error near unexpected token `&&' > ----------------------------------------------------------------------- > gfp@Tuxedo ~$ nmcli --version > nmcli tool, version 1.41.2 > ........................................................................ >=20 > 5. > nmcli g > STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN > connected (local only) limited missing enabled missing enabled >=20 >=20 > Does this mean WIFI is on my lapttop enabled? > If yes, how can I switch it off? >=20 > .........................................................................= ... > 6. > `nmcli connection down \ > && nmcli connection up `. >=20 > Do I have to include the "dot" at the end? > I guess it shows the end of the sentence. >=20 > ........................................................................ > 7. > gfp@Tuxedo ~$ nmcli c > NAME UUID TYPE DEVICE > lo 7a147fe2-d819-4316-8fc3-5048760b8449 loopback -- > virbr0 3806cfd9-88d8-4640-b159-171587357668 bridge virbr0 > Wired connection 1 84733337-c8dc-3c39-8b73-c05ae193c799 ethernet -- >=20 > .........................................................................= ..... >=20 > 8. > gfp@Tuxedo ~$ `nmcli connection down \ > && nmcli connection up ` >=20 > -bash: command substitution: line 1: syntax error near unexpected token=20 > `newline' > -bash: command substitution: line 1: `nmcli connection down name> ' =20 >=20 > .................................................................... > 9. > gfp@Tuxedo ~$ `nmcli connection down \ > && nmcli connection up `. >=20 > -bash: command substitution: line 1: syntax error near unexpected token `= &&' > -bash: command substitution: line 1: `nmcli connection down name> && nmcli connection up ' =20 > -bash: .: filename argument required > .: usage: . filename [arguments] >=20 > I am not sure how the command should look like. > ....................................................................... >=20 > gfp@Tuxedo ~$ sudo herd restart network-manager > Password: > herd: service 'network-manager' could not be found >=20 > I am using MATE desktop >=20 > clicking the icon network in the menu line > shows >=20 > ethernet: > device: enp53s0 > MTU: automatic >=20 > There is no possibility shown to enable networking again, no button to=20 > click.... >=20 >=20 >=20 > Kind regards >=20 > Gottfried >=20 >=20 >=20 >=20 > Am 11.04.23 um 17:48 schrieb Arnaud: > > Hi, > >=20 > > It depends on how you connect to the Internet. > >=20 > > On a laptop and with the default configuration, you are probably using= =20 > > Network Manager (which you can check by running `nmcli`). > >=20 > > If you use Network Manager, you can probably use the following instead > > of rebooting: > > `nmcli connection down \ > > && nmcli connection up `. > >=20 > >=20 > > Hope that helps, > >=20 > > --=20 > > Arnaud =20 >=20 >=20 --Sig_/J6ZUWrWZoHq_6OCuSFhLTG+ Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQTpcnBg48VjfIpPS0JLxSIcWnn9GgUCZDa+qQAKCRBLxSIcWnn9 GoZrAP0cyRBVvqFO2Cla5TtToP1tjPWAGduBOSPgHh8B2d8fGAEAqOjEH+WEWa0f 5xvywuFyXx8Xtqt/4PfOdqIYoRYc9gM= =3eHr -----END PGP SIGNATURE----- --Sig_/J6ZUWrWZoHq_6OCuSFhLTG+--