Hello all,
Rather than rely on the rather obscure naming of network interfaces as
eth0, bond0, ath0, etc. I would like to give them more descriptive
and likely more portable names. For example, on many cloud or virtual
instances eth0 is configured to be on the private network. So, rather
than calling it eth0, I would like to have it named private0. To do
that I run a script with this at its core:
ip link show eth0 >& /dev/null && {
ip link set eth0 down
ip link set dev eth0 name private0
ip link set private0 up
}
I was just wondering what alternative solutions others have come up with.
Regards,
- Robert
--
Central West End Linux Users Group (via Google Groups)
Main page: http://www.cwelug.org
To post: [email protected]
To subscribe: [email protected]
To unsubscribe: [email protected]
More options: http://groups.google.com/group/cwelug
