Welcome to LinuxQuestions.org, a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features.
Registration is quick, simple and absolutely free. Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Jul 3, 2017 - In the “Ethernet Status” window, click the “Details” button. The “Network. You'll see your Mac's IP address next to “IP address.” Other details. To find your MAC address, head to Settings > General > About. Scroll down a bit and you’ll see your MAC address listed as “Wi-Fi Address.” Android. On Android, you can find this information in the Settings app. Pull down from the top of the screen and tap the gear icon or open your app drawer and tap the “Settings” app icon to open it.
Are you new to LinuxQuestions.org? Visit the following links: If you have any problems with the registration process or your account login, please. If you need to reset your password,. Having a problem logging in? Please visit to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter. For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration.
![How To Find Mac For Eth0 Windows How To Find Mac For Eth0 Windows](/uploads/1/2/5/3/125395141/698542035.jpg)
This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
To receive this Complete Guide absolutely free. Quote: So network cards are managed by a helper program called 'udev'. Udev is great because it can managed dynamically the removal/addition of hardware, but it's attributing names to devices in it's own kind of way. For network cards names need to be consistent from one boot to the next, so udev is associating the conventional interface name (eth.) to it's unique MAC address (MAC address is build inside the device itself). Those associations are stored in the folder /etc/udev/rules.d/ where you will find a ' yxpersistent-net.rules' file ('yx' are random numbers, depends on your system).
The 'rules' udev use to name the devices are of the form. Code: sudo /sbin/ifconfig -a ('-a' option lists even non configured devices), it will look like 'HWaddr 00:1d:20:55:cf:67', and write this MAC address in the udev rule corresponding to the conventional name that suites you (eth0 for instance). You can delete old rules, add new ones for other cards.
You will need root privileges to edit the 'yxpersistent-net.rules' file. Reboot when done (restarting the network should be enough though.) This way you will get consistent naming of the interfaces, and static one. This helps - appreciate it. A little more background as to what I was doing.
I just installed Slakware 12 and I have 4 ethernet ports all connected to a switch. Let's say each port is in the same VLAN. Then I config eth0 and can ping it from a different host in the same subnet.
Now I want to introduce VLANs into the scenario in order to put the other interfaces in different subnets for some testing with tcpreplay I plan to do. First I scratch my head and say okay which int is actually eth0. I figure I will do a continuous ping and pull each cable one at a time until the ping is interupted. This did not work as easily as I thought it would, as the ping would stop even when I pulled a cable on one of the other 3 unconfigured ports, and was slow to restart when I restored cables.???? The bottom line is it sounds like if I know what MAC address corresponds to each physical interface I can assign the label assigned to those ports, and this label is used in commands like ifconfig, etc. This assignment occurs in the file in the response to my initial post. Those associations are stored in the folder /etc/udev/rules.d/ where you will find a 'yxpersistent-net.rules' file ('yx' are random numbers, depends on your system).
Now getting the MAC address for each physical port and knowing which port it actually is may require an empirical approach if I do not have documentation on this. I could configure one at a time and determine the MAC address of each. Once assigned does the label stay attached to the physical interface for subsequent boots? Even if I remove a cable or two and perhaps switch others?
While I was testing it appeared eth0 was jumpoing around between the 4 interfaces. Finally, can you tell me the command to stop and restart the network service? Thanks - appreciate all the help.