From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id A610571CB4 for ; Fri, 9 Apr 2021 13:21:13 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9A0E925C87 for ; Fri, 9 Apr 2021 13:21:13 +0200 (CEST) Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 4DBCA25C71 for ; Fri, 9 Apr 2021 13:21:10 +0200 (CEST) Received: by mail-lf1-x12a.google.com with SMTP id b14so9100709lfv.8 for ; Fri, 09 Apr 2021 04:21:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tecnetmza-com-ar.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=3NHL4cJjnOC0c3NDdJrdHdJVguOP2ATO2xbnapd3I74=; b=Eci0L62D8eRAex1Bdw9IFulLr6ZRIAr3XUyjj1aP1pef1Ie1llWvVi4YmFkE12VA31 Y8VZEomykYCqIvqOQEQvD871Xt9yfauUNkeKh1/2YvB5zcZ6an6vjl/Glpn53E3N93w8 MPJqu/Jfw3c2rkI0NU41VzHtV/EQKS0uKxndyvzSAIdGEatUM0JTpdvTYInMKB7xIAGS q2HAnGh2HdLABkb2RHEu4Pq12m+GHIMwjPSS0g9uUJoR4xJfVnmDsJYMHg/oav1xX13M A+vtN/IXVNgxy7OxxVvBg/rQlcA5aTdB2TfxrGhkA6qJw6GOZ+47Unsl+y4LuKYE/opM 9Q5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=3NHL4cJjnOC0c3NDdJrdHdJVguOP2ATO2xbnapd3I74=; b=qr5GoPrKVAQfDYb7oD82IzXDJlcfgklCPRTVNsAWMwpVZmgH7jlQHVNFyGpWIRSaTx P5rg/4689wPxD+sdZltX7vmoKqfiTWvRKd32kurut2lsdgAbkr+3QDns+gkhQuGZpTY+ bTES8oN1emh3fcTLLq/xYrE9MoHEl7yPZiF0RlI8eMh9vSlyPjE+kO+YJ7K54Nv287f4 G1UB2Cj2C5jnp62jzDkiyL9PzrWMEPJx4BxNUVF15px++nWNd8u0ZcIgjYUA3IV/uoJb RQqZOTe20M8DWl6wylLEIZ4a2/rTq1Bw6cLtPCp33TYL9/n9dw9gXzItRr8uBD6ne0EH LIwQ== X-Gm-Message-State: AOAM53181KjdcNFUsIwsSkmUGJHQPDRR8ktTwovKR1gWKRD34r3J7DI6 GoLtFSBZA6himaOPXTFhlVQfhhvI/IUC+4w/cv44OVcj3Q== X-Google-Smtp-Source: ABdhPJxznGt+i5v3dtLGSfkvfFEyWVaVzjjgWYH3+BMl1yZpqOwMsWpxSyUT72fMZWx/niNYl6YZ925+ZaWpr1lykUs= X-Received: by 2002:ac2:51ba:: with SMTP id f26mr10120423lfk.207.1617967263478; Fri, 09 Apr 2021 04:21:03 -0700 (PDT) MIME-Version: 1.0 References: <20210407220319.snhtabanjxcjfl6w@percival.namespace.at> In-Reply-To: <20210407220319.snhtabanjxcjfl6w@percival.namespace.at> From: Leandro Roggerone Date: Fri, 9 Apr 2021 08:20:59 -0300 Message-ID: To: Proxmox VE user list X-SPAM-LEVEL: Spam detection results: 1 AWL 0.207 Adjusted score from AWL reputation of From: address DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature HTML_MESSAGE 0.001 HTML included in message RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_SOFTFAIL 0.972 SPF: sender does not match SPF record (softfail) T_REMOTE_IMAGE 0.01 Message contains an external image URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [deduktiva.com, proxmox.com] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] link down for network interface X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Apr 2021 11:21:13 -0000 Veeeery strange. After removing the vlan aware flag on the interface configuration could get the link up. Fortunately I have a second nic on this server so I will use it instead. Have not much time to debug this. Thanks. Libre de virus. www.avast.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> El mi=C3=A9, 7 abr 2021 a las 19:04, Chris Hofstaedtler | Deduktiva (< chris.hofstaedtler@deduktiva.com>) escribi=C3=B3: > * Leandro Roggerone [210407 17:25]: > > Hi guys ... > Please consider that more than one gender exists. > > > Yesterday was working on my datacenter cabling my new proxmox network > > interfaces. > > I connected a network port to my mikrotik router. > > Before coming home I checked network linked condition and physically wa= s > ok > > , both leds blinking on both side , router and server nic. (eno1) > > Now , working remotely can see that server interface has no link. > > Very strange since interface at router is up. > > Any idea ? I never seen something similar (one side link ok and the > other > > is down). > > > root@pve2:~# ip link > [..] > > 4: eno1: mtu 1500 qdisc mq master > vmbr2 > > state DOWN mode DEFAULT group default qlen 1000 > > link/ether 40:a8:f0:2a:18:80 brd ff:ff:ff:ff:ff:ff > > > > as you can see eno1 is down ... while can see link up on the other > > connected side. > > You did not tell us the brand and make or driver of that network > card. Some Intel cards are known to be extremely picky about autoneg > and power save settings, (short) cables, etc. > > Best luck, > Chris > > -- > Chris Hofstaedtler / Deduktiva GmbH (FN 418592 b, HG Wien) > www.deduktiva.com / +43 1 353 1707 > > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > >