How do I generate a random MAC address from the Linux command line?
I search for a solution that only requires standard tools commonly found on the Linux command line.
The MAC address will be used for a guest KVM.
Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up.
Sign up to join this communityI use
macaddr=$(echo $FQDN|md5sum|sed 's/^\(..\)\(..\)\(..\)\(..\)\(..\).*$/02:\1:\2:\3:\4:\5/')
The benefit of this method, over a completely random number, is that it's possible to reliably reproduce the MAC address based on the FQDN of the machine, which I find useful sometimes. The 02
for the first octet just sets the "locally assigned" bit, which makes it obvious that it's not a vendor-provided MAC address, and guarantees that you won't collide with a real NIC's MAC address.
If you need to generate multiple MAC addresses per host, I used to concatenate the FQDN with the name of the bridge to connect the interface to; this did a good job of spreading things out for different NICs.
tr -dc A-F0-9 < /dev/urandom | head -c 10 | sed -r 's/(..)/\1:/g;s/:$//;s/^/02:/'
The posted scripts are good, but I want to add a warning: Mind the Birthday (paradoxon)!
It comes from the fact that even if you have just 23 people, the chance is already 50% that 2 of them have birthday on the same day.
It depends on your scenario how you use it, but if you generate the MACS randomly, at approx 1 million your chance for a mac number clash is 40% at 2 million it is already 87%!
If you need just a couple this is ok, but when you maintain a server farm with hundreds of servers, each of them hosting tens of virtual machines, or if you use the macs as index in some db for bookkeeping and you need uniques be careful!
These variants work as well.
longer:
openssl rand -hex 6 | sed 's/\(..\)\(..\)\(..\)\(..\)\(..\)\(..\)/\1:\2:\3:\4:\5:\6/'
or shorter:
openssl rand -hex 6 | sed 's/\(..\)/\1:/g; s/:$//'
The load consumption of both variants is very similar according to quick measuring with time.
fold -w2|paste -sd: -
instead of sed
. The sed
solution is probably easier to remember as it uses a more familiar tool – though I learned more from his/her answer.
Sep 26, 2016 at 13:21
03:00:00:00:00:00
locally, they'll get RTNETLINK answers: Cannot assign requested address
, because the second bit must be set, but not the first. In other words, 00000011
fails, while 00000010
is correct. 03
octet fails; 02
octet is correct. Actually, in a broadcast address, the user would see 11111111
(255), 255.255.255.255
. To make a long story short, the first octet should represent an even number, not an odd.
Jun 10, 2021 at 17:11
myserver% perl -e 'for ($i=0;$i<6;$i++){@m[$i]=int(rand(256));} printf "%X:%X:%X:%X:%X:%X\n",@m;'
55:C2:A5:FA:17:74
Ah, the ol' Swiss Army Chainsaw rides again. And by way of version 0.2, I'm unashamedly stealing womble's excellent point about the first octet being 02:
myserver% perl -e 'for ($i=0;$i<5;$i++){@m[$i]=int(rand(256));} printf "02:%X:%X:%X:%X:%X\n",@m;'
02:8E:94:A3:47:26
I know this post is old, but for future visitors, if you want a cryptographically secure pseudorandom MAC address, without being limited to 0x02 as the OUI, here is a fast mostly platform agnostic generator:
$ printf '%02x' $((0x$(od /dev/urandom -N1 -t x1 -An | cut -c 2-) & 0xFE | 0x02)); od /dev/urandom -N5 -t x1 -An | sed 's/ /:/g'
tr
instead of but cut
and sed
: printf '%02x' $((0x$(od /dev/urandom -N1 -t x1 -An | tr -d ' ') & 0xFE | 0x02)); od /dev/urandom -N5 -t x1 -An | tr ' ' ':'
Mar 14, 2022 at 19:30
Here are five other options, all of which use random bits for the least significant bit of the most significant byte that indicates if the address is unicast or multicast and for the second-least significant bit of the most significant byte that indicates if the address is universally or locally administered.
jot -w%02X -s: -r 6 1 256
openssl rand -hex 6|fold -w2|paste -sd: -
od -N6 -tx1 -An /dev/random|awk '$1=$1'|tr \ :
god -N6 -tx1 -An /dev/random|cut -c2-|tr \ :
hexdump -n6 -e'/1 ":%02X"' /dev/random|cut -c2-
jot
comes with OS X and BSDs but not with most Linux distributions. In jot
-w
changes the format, -s
changes the separator, and -r
generates random numbers.
od
is in POSIX but hexdump
is not.
OS X's od
(/usr/bin/od
below) uses a different output format than GNU od
:
$ /usr/bin/od -N6 -tx1 -An /dev/random|tr ' ' :
:::::::::::d9::b9::d7::da::5f::96::::::::::::::::::::::::::::::::::::::::
$ god -N6 -tx1 -An /dev/random|tr ' ' :
:f5:6d:0a:3b:39:f9
In OS X's od
options placed after an argument for an input file are treated as the names of input files, so the command in the answer by Aaron Toponce reads from /dev/urandom
indefinitely with OS X's od
.
Here's another one, based on wombie's answer:
macaddr=$(dd if=/dev/urandom bs=1024 count=1 2>/dev/null|md5sum|sed 's/^\(..\)\(..\)\(..\)\(..\)\(..\)\(..\).*$/\1:\2:\3:\4:\5:\6/')
echo $macaddr
You could just add a $RANDOM after $FQDN and this would give you random mac addresses every time you run it. This is especially helpful for poeple who want to create backup vms using snapshots or clones of vms.
macaddr=$(echo $FQDN$RANDOM|md5sum|sed 's/^\(..\)\(..\)\(..\)\(..\)\(..\).*$/02:\1:\2:\3:\4:\5/')
Python one-liner:
python3 -c 'import os; print(":".join(["{:02x}".format(x) for x in b"\02x" + os.urandom(5)]))'
Just for fun, here is a pure bash version, tested against Bash 4.4.12(1)-release:
read -N6 b </dev/urandom
LC_ALL=C printf "%02x:%02x:%02x:%02x:%02x:%02x\n" "'${b:0:1}" "'${b:1:1}" "'${b:2:1}" "'${b:3:1}" "'${b:4:1}" "'${b:5:1}"
First line reads 6 characters from /dev/urandom
; then using the C character set print the 0-filled hex value of each character separated with a colon (the newline is optional but useful to print out the value).
Since you can print directly to a variable with printf -v myvar
there is no fork/subshell needed to capture the result.
Extracting the value of a character using printf is defined in POSIX printf documentation:
If the leading character is a single-quote or double-quote, the value shall be the numeric value in the underlying codeset of the character following the single-quote or double-quote.
NB: read
will not block on /dev/urandom
, so it may return early causing the last bytes of the MAC to be all 0's. This will be particularly noticeable if run in a thigh loop or if another application is doing heavy reads at the same time from /dev/urandom
.
If you're an idiot^H^H^H^H^Hnaive like I was and don't do the local/unicast right, I found the following works to patch six random bytes. And of course you can use one of the simple schemes here and feed it into this.
echo -n "01:23:45:AB:CD:EF" | sed 's/^\(.\)[013]\(.*\)/\12\2/' | sed 's/^\(.\)[457]\(.*\)/\16\2/' | sed 's/^\(.\)[89B]\(.*\)/\1A\2/' | sed 's/^\(.\)[CDF]\(.*\)/\1E\2/')
If there's a shorter variant, I'd love to see it.
Locally administered unicast address randomizing all the remaining bits:
python3 -c 'import os;print(":".join(f"{os.urandom(1)[0]&~m|m*2:02x}" for m in [1]+5*[0]))'
(the ~m
mask is used to clear bit 0 of the leftmost byte; the m*2
mask is to set bit 1)
Why posting one more solution here: wanted something short and readable without the bad feeling of leaving some bits wasted (regardless the practical importance of these extra 6 bits of address space).