01-30-2009
User with root privileges:
ifconfig -a
Should give you ip address and mac address for all interfaces in your system.
5 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am training to be support on our solaris based network and was wondering why solaris seems to assign the same mac address to all NICs placed in the machine regardless of how many NICs are in there, when i do a ifconfig -a all nics have same MAC.
Presumably this is a feature and there is... (1 Reply)
Discussion started by: hcclnoodles
1 Replies
2. UNIX for Dummies Questions & Answers
Hello all.
I have a large number of text files outputted from various Netstumbler Wireless Scans; from which I need to extract the MAC addresses of the various Access Points.
The Text files look like this:
# $Creator: Network Stumbler Version 0.4.0
# $Format: wi-scan summary with... (9 Replies)
Discussion started by: dhs23
9 Replies
3. UNIX for Dummies Questions & Answers
If a web search is done on this topic there are many links but no information included in the documents. So my questions are;
Why does a NIC card have it's own permanent ID. Why can't it share the host name? An ID is an ID.
Why does a computer need two ways to ID it.
If the network... (3 Replies)
Discussion started by: theKbStockpiler
3 Replies
4. Shell Programming and Scripting
I have a problem with a script , i want to see my devices there are up in my network. I want as output the ip addresses of the devices and also the mac address but I only had the ip addresses
#!/bin/bash
while ]
do
-mac)
Extension=5
shift
mac=$1
shift
;;
esac... (1 Reply)
Discussion started by: Roggy
1 Replies
5. Shell Programming and Scripting
Hy over there,
Lets make it simple :)
Using a bash script, how to grep only the ip address and the mac address and put them in a file:.
for example from the dhcp.conf file we got such things:
The script will end up with two columns IP's and MAC adresses as it is showed below:
... (9 Replies)
Discussion started by: hermouche
9 Replies
EPAIR(4) BSD Kernel Interfaces Manual EPAIR(4)
NAME
epair -- A pair of virtual back-to-back connected Ethernet interfaces.
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device epair
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_epair_load="YES"
DESCRIPTION
The epair is a pair of Ethernet-like software interfaces, which are connected back-to-back with a virtual cross-over cable.
Each epair interface pair is created at runtime using interface cloning. This is most easily done with the ifconfig(8) create command or
using the cloned_interfaces variable in rc.conf(5). While for cloning you only give either epair or epair<n> the epair pair will be named
like epair<n>[ab]. This means the names of the first epair interfaces will be epair0a and epair0b.
Like any other Ethernet interface, an epair needs to have a network address. Each epair will be assigned a locally administered address by
default, that is only guaranteed to be unique within one network stack. To change the default addresses one may use the SIOCSIFADDR ioctl(2)
or ifconfig(8) utility.
The basic intend is to provide connectivity between two virtual network stack instances. When connected to a if_bridge(4) one end of the
interface pair can also be part of another (virtual) LAN. As with any other Ethernet interface one can configure vlan(4) support on top of
it.
SEE ALSO
ioctl(2), altq(4), bpf(4), if_bridge(4), vlan(4), loader.conf(5,) rc.conf(5), ifconfig(8)
HISTORY
The epair interface first appeared in FreeBSD 8.0.
AUTHORS
The epair interface was written by Bjoern A. Zeeb, CK Software GmbH, under sponsorship from the FreeBSD Foundation.
BSD
July 26, 2009 BSD