From nobody Sun Nov 19 16:41:08 2023 X-Original-To: freebsd-net@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 4SYGcM0CPSz511fC for ; Sun, 19 Nov 2023 16:41:23 +0000 (UTC) (envelope-from ozkan.kirik@gmail.com) Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SYGcL5gW8z4GGQ; Sun, 19 Nov 2023 16:41:22 +0000 (UTC) (envelope-from ozkan.kirik@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-x131.google.com with SMTP id 2adb3069b0e04-507a5f2193bso3763459e87.1; Sun, 19 Nov 2023 08:41:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700412080; x=1701016880; darn=freebsd.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Z2Pxx/TGzs+W0tbo6rYMjxZ3ArjiqX30qFC+R2/RCxE=; b=bxdtJUfsLcM6fkp4taVYSu3WpKUBjjNIcqvxG0BrZtnIlavKK4Xu/k4YZUTuK2rNoL BQu+6QR1LNSF3wWZ+ftUP1HgFXZBVgjAof9V77gvss9JGevV0FTMf5lHc5FpSfuoTeZZ KR/7SDq8m+Zaag9akwdjzCsGypb0FmxLljLK3Tt5dmzJm/bi1FArSnpSq0zWS3Uxk96N 7u5TtdtPdv6Awyf8vNHN2GT84snNuSPPo0CxV0Y41lF7sUZN/PVov0saDBaioXFKp5tK SnwH0B1Sxa7Le4+sWwvkqtOOhVTedo3DHHIdj2hshJlReUkfnrLHaVKIEOOiDV4EQotn u2Dw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700412080; x=1701016880; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Z2Pxx/TGzs+W0tbo6rYMjxZ3ArjiqX30qFC+R2/RCxE=; b=Ef9pnV5ZQOaWPpcAADN98pRGg8aFiut/0gexXotmclq3/PTf2NIBTlEhEmcRyP6MWE vYgOXHH0nKWVZ/maYsgN0RJ6ssi5bg7WwGUeAxj91pZKotXgBjQkPGA48xsppFWzaR18 yuqztXLDbT0dA/0l38AmaSkmLpka7+O2E6ZRlezIUh3p0801/PfWMd2WnkJPgXyRfkWv RlxzzlaLliNEy3G4zK4mdESXLZmeEbQwlqig5aczrbl95k8bU2XBYCMO5G7+QbyIRjkb sxmWiodFQp+U5whRanPY2zLyfLKI7Y8+sh/zKvHJV2QqwIEX7invsAKEfmyl4DqTl/0Y OsPg== X-Gm-Message-State: AOJu0Yz/ufzq/7/dYp2SLlJmUh0pkjrcdKsVxyt0ManDee7IImewXZTF hO5/Svl7RJdKQzX9BbaQWO4tIe2eMgM2otA8MkYW4FyBxH8= X-Google-Smtp-Source: AGHT+IG00pE9SnzfUG3AjJGECIggDhoCf2gim1u4g2Av9LlEbfRL7SutV0EKmtLCx7BQADwF1cYoR8v3Kv3gGSKMy/Q= X-Received: by 2002:a19:ee14:0:b0:504:7d7e:78dd with SMTP id g20-20020a19ee14000000b005047d7e78ddmr1507898lfb.23.1700412079362; Sun, 19 Nov 2023 08:41:19 -0800 (PST) List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 References: <9eef5488-e8da-4edd-bc00-baeb5aaf4a23@FreeBSD.org> In-Reply-To: From: =?UTF-8?B?w5Z6a2FuIEtJUklL?= Date: Sun, 19 Nov 2023 19:41:08 +0300 Message-ID: Subject: Re: How to tell if a network interface was renamed (and from what) To: =?UTF-8?Q?Mina_Gali=C4=87?= Cc: Kyle Evans , freebsd-net@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Queue-Id: 4SYGcL5gW8z4GGQ Hi Mina, Let's explain with a small example: In this scenario, we are going to add two alternate names for the "lo" interface. And then we can access to the interface using all of the names: lo, test1, test2 # ip link show lo 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 # ip link property add dev lo altname test1 # ip link property add dev lo altname test2 # ip link show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 altname test1 altname test2 2: enp4s0: mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether b0:7b:25:31:6c:92 brd ff:ff:ff:ff:ff:ff # ip link show lo 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 altname test1 altname test2 # ip link show test1 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 altname test1 altname test2 # ip link show test2 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 altname test1 altname test2 # ping -I test2 127.0.0.1 ping: Warning: source address might be selected on device other than: test2 PING 127.0.0.1 (127.0.0.1) from 127.0.0.1 test2: 56(84) bytes of data. 64 bytes from 127.0.0.1: icmp_seq=3D1 ttl=3D64 time=3D0.023 ms By the altname feature, the interface name doesn't change, but you can assign many altnames. So you can access them using these altnames. Mina Gali=C4=87 , 19 Kas 2023 Paz, 17:36 tarihinde =C5= =9Funu yazd=C4=B1: > > > Hi =C3=96zkan, > > > It would be better if FreeBSD could have "interface altname feature" > > like Linux has. > > even tho I'm writing this email from a Linux laptop, and often > have to understand Linux specific code to see how I can (or if I > need to) replicate that on FreeBSD, I'm not familiar enough > with Linux. > > Can you describe the altname feature, and how it works? > > Kind regards, > > Mina