From owner-freebsd-questions@freebsd.org Mon Oct 26 18:14:24 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 625078892 for ; Mon, 26 Oct 2015 18:14:24 +0000 (UTC) (envelope-from sales@carbonfiber.com.cn) Received: from mail86.ufhost.com (mail86.ufhost.com [61.151.239.86]) by mx1.freebsd.org (Postfix) with ESMTP id F1E271F83 for ; Mon, 26 Oct 2015 18:14:22 +0000 (UTC) (envelope-from sales@carbonfiber.com.cn) Received: from [192.168.104.254] (unknown [187.54.192.26]) by mail86.ufhost.com (Postfix) with ESMTP id C4DCC4849F9 for ; Tue, 27 Oct 2015 02:09:32 +0800 (CST) MIME-Version: 1.0 Subject: Last Warning!!! To: freebsd-questions@freebsd.org From: "Email Alert" Date: Mon, 26 Oct 2015 16:12:26 -0200 Message-Id: <20151026180932.C4DCC4849F9@mail86.ufhost.com> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: Mail message body X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Oct 2015 18:14:24 -0000 Dear freebsd-questions@freebsd.org 1969MB 2000MB We noticed your e-mail account has almost exceed it's limit. And you may no= t be able to send or receive messages any moment from now Your E-mail Account will be closed if you fail to increase Storage capacity= Kindly Click here to increase your storage capacity by 30.00GB Free.. Click here to add up free 20GB storage. If not gotten from you in the next 24 hours, We shut down your E-mail Accou= nt, = Until after proper verification before you can access your E-mail Account A= gain....!!! = Thanks. Domain Security 2014/2015. From owner-freebsd-questions@freebsd.org Mon Oct 26 18:24:57 2015 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5038C8C48 for ; Mon, 26 Oct 2015 18:24:57 +0000 (UTC) (envelope-from terje@elde.net) Received: from rand.keepquiet.net (keepquiet.net [144.76.43.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "keepquiet.net", Issuer "PositiveSSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1439A15DE; Mon, 26 Oct 2015 18:24:56 +0000 (UTC) (envelope-from terje@elde.net) Received: from [10.130.11.109] (cm-84.210.87.28.getinternet.no [84.210.87.28]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: terje@elde.net) by rand.keepquiet.net (Postfix) with ESMTPSA id 390F0AB9; Mon, 26 Oct 2015 18:16:56 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: NIC naming From: Terje Elde X-Mailer: iPhone Mail (13B143) In-Reply-To: <562E551F.6060406@freebsd.org> Date: Mon, 26 Oct 2015 19:16:51 +0100 Cc: freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <0746B048-19AB-4AA6-8439-4DF7A08D10AE@elde.net> References: <562E4D92.3000308@gmail.com> <562E551F.6060406@freebsd.org> To: Matthew Seaman X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Oct 2015 18:24:57 -0000 > On 26 Oct 2015, at 17:30, Matthew Seaman wrote: >=20 > This probably doesn't solve your problem, which appears to be knowing > which of the ethernet ports on your machine is em0 -- the usual method > to do that is by ifconfig'ing everything else down and then testing with > a network cable until you find the working port. However it might help > clarify the system configuration. ifconfig will give you the MAC of the card. I'm not sure if there's a standa= rd tool for it, but it should be easy to do something like "rename the card w= ith MAC address X to Y" Personally, I've started renaming along the lines of renaming em0 to em_lan0= , em1 to em_wan1 and so on. Makes it a bit easier to see what's going on, bo= th for when another admin might inherit the box, and also for myself, if I h= aven't touched the box in a few years.=20 Sure, you could argue all of this should be documented somewhere as well - a= nd you wouldn't be wrong - but renaming makes things obvious where the next a= dmin will look, not just in some doc that might be somewhere he didn't.=20 Terje=