insufficient permissions to change MAC address
I am attempting to change the MAC address of the Wi-Fi hardware of a laptop. When I attempt to change the MAC address using macchanger, I encounter an error:
>sudo service network-manager stop
>sudo macchanger --mac 28:27:c4:f6:ca:a5 wlp4s0
Current MAC: 28:27:c4:f6:ca:a5 (unknown)
Permanent MAC: 5a:ef:56:3d:dd:7e (Intel Corporate)
[ERROR] Could not change MAC: interface up or insufficient permissions: Device or resource busy
Here, the default MAC address of the hardware is 5a:ef:56:3d:dd:7e and the MAC address to which it should be changed is 28:27:c4:f6:ca:a5. How should I approach this error?
networking 16.04 permissions mac
asked Oct 25 '16 at 12:47
d3pd
1,59672948
add a comment |
I am attempting to change the MAC address of the Wi-Fi hardware of a laptop. When I attempt to change the MAC address using macchanger, I encounter an error:
>sudo service network-manager stop
>sudo macchanger --mac 28:27:c4:f6:ca:a5 wlp4s0
Current MAC: 28:27:c4:f6:ca:a5 (unknown)
Permanent MAC: 5a:ef:56:3d:dd:7e (Intel Corporate)
[ERROR] Could not change MAC: interface up or insufficient permissions: Device or resource busy
Here, the default MAC address of the hardware is 5a:ef:56:3d:dd:7e and the MAC address to which it should be changed is 28:27:c4:f6:ca:a5. How should I approach this error?
networking 16.04 permissions mac
asked Oct 25 '16 at 12:47
d3pd
1,59672948
1
try deactivating the interface:sudo ifconfig wlp4s0 down
– iñaki murillo
Oct 25 '16 at 12:50
add a comment |
I am attempting to change the MAC address of the Wi-Fi hardware of a laptop. When I attempt to change the MAC address using macchanger, I encounter an error:
>sudo service network-manager stop
>sudo macchanger --mac 28:27:c4:f6:ca:a5 wlp4s0
Current MAC: 28:27:c4:f6:ca:a5 (unknown)
Permanent MAC: 5a:ef:56:3d:dd:7e (Intel Corporate)
[ERROR] Could not change MAC: interface up or insufficient permissions: Device or resource busy
Here, the default MAC address of the hardware is 5a:ef:56:3d:dd:7e and the MAC address to which it should be changed is 28:27:c4:f6:ca:a5. How should I approach this error?
networking 16.04 permissions mac
asked Oct 25 '16 at 12:47
d3pd
1,59672948
I am attempting to change the MAC address of the Wi-Fi hardware of a laptop. When I attempt to change the MAC address using macchanger, I encounter an error:
>sudo service network-manager stop
>sudo macchanger --mac 28:27:c4:f6:ca:a5 wlp4s0
Current MAC: 28:27:c4:f6:ca:a5 (unknown)
Permanent MAC: 5a:ef:56:3d:dd:7e (Intel Corporate)
[ERROR] Could not change MAC: interface up or insufficient permissions: Device or resource busy
Here, the default MAC address of the hardware is 5a:ef:56:3d:dd:7e and the MAC address to which it should be changed is 28:27:c4:f6:ca:a5. How should I approach this error?
networking 16.04 permissions mac
networking 16.04 permissions mac
asked Oct 25 '16 at 12:47
d3pd
1,59672948
asked Oct 25 '16 at 12:47
d3pd
1,59672948
asked Oct 25 '16 at 12:47
d3pd
1,59672948
asked Oct 25 '16 at 12:47
d3pd
1,59672948
asked Oct 25 '16 at 12:47
d3pd
1,59672948
1,59672948
1
try deactivating the interface:sudo ifconfig wlp4s0 down
– iñaki murillo
Oct 25 '16 at 12:50
add a comment |
1
try deactivating the interface:sudo ifconfig wlp4s0 down
– iñaki murillo
Oct 25 '16 at 12:50
1
1
try deactivating the interface:
sudo ifconfig wlp4s0 down– iñaki murillo
Oct 25 '16 at 12:50
try deactivating the interface:
sudo ifconfig wlp4s0 down– iñaki murillo
Oct 25 '16 at 12:50
add a comment |
1 Answer
1
active
oldest
votes
On Kubuntu 14.10 This page has a procedure that works.
As root:
service network-manager stop; sleep 5
ifconfig wlan0 down
macchanger -b -a wlan0; sleep 5
ifconfig wlan0 up; sleep 5
service network-manager start
The sleeps may not be necessary, but that's what worked. Macchanger is in the repos. My attempts using ifconfig or ip link appeared to take but did not survive connecting to a network, because I didn't stop Network Manager. The burnt in MAC was reasserted.
This also works:
service network-manager stop; sleep 5
ifconfig wlan0 down; ifconfig wlan0 hw ether F8:27:93:01:02:03
ifconfig wlan0 up; sleep 5;
service network-manager start; sleep 5;
I have a feeling there are some little gotchas lurking:
In the Network Manager gui, clear the 'Restrict to Device:' field.
Also clear the 'Random' field.Use a MAC with a recognised vendor prefix, easily found on Goog. Many
routers can tell the difference. It also avoids any snafu with the
'locally administered' bit, WTH that is.- Start from a clean state, regarding the ifup & ifdown commands. They
only keep a record of changes they have made & can be inconsistent
with the true network state ( And no: I have no idea what I'm talking
about regarding these)
Easy. Once you know how.
edited Apr 13 '17 at 12:24
Community♦
1
answered Nov 23 '16 at 1:53
gryphonB
563
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f841608%2finsufficient-permissions-to-change-mac-address%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
On Kubuntu 14.10 This page has a procedure that works.
As root:
service network-manager stop; sleep 5
ifconfig wlan0 down
macchanger -b -a wlan0; sleep 5
ifconfig wlan0 up; sleep 5
service network-manager start
The sleeps may not be necessary, but that's what worked. Macchanger is in the repos. My attempts using ifconfig or ip link appeared to take but did not survive connecting to a network, because I didn't stop Network Manager. The burnt in MAC was reasserted.
This also works:
service network-manager stop; sleep 5
ifconfig wlan0 down; ifconfig wlan0 hw ether F8:27:93:01:02:03
ifconfig wlan0 up; sleep 5;
service network-manager start; sleep 5;
I have a feeling there are some little gotchas lurking:
In the Network Manager gui, clear the 'Restrict to Device:' field.
Also clear the 'Random' field.Use a MAC with a recognised vendor prefix, easily found on Goog. Many
routers can tell the difference. It also avoids any snafu with the
'locally administered' bit, WTH that is.- Start from a clean state, regarding the ifup & ifdown commands. They
only keep a record of changes they have made & can be inconsistent
with the true network state ( And no: I have no idea what I'm talking
about regarding these)
Easy. Once you know how.
edited Apr 13 '17 at 12:24
Community♦
1
answered Nov 23 '16 at 1:53
gryphonB
563
add a comment |
On Kubuntu 14.10 This page has a procedure that works.
As root:
service network-manager stop; sleep 5
ifconfig wlan0 down
macchanger -b -a wlan0; sleep 5
ifconfig wlan0 up; sleep 5
service network-manager start
The sleeps may not be necessary, but that's what worked. Macchanger is in the repos. My attempts using ifconfig or ip link appeared to take but did not survive connecting to a network, because I didn't stop Network Manager. The burnt in MAC was reasserted.
This also works:
service network-manager stop; sleep 5
ifconfig wlan0 down; ifconfig wlan0 hw ether F8:27:93:01:02:03
ifconfig wlan0 up; sleep 5;
service network-manager start; sleep 5;
I have a feeling there are some little gotchas lurking:
In the Network Manager gui, clear the 'Restrict to Device:' field.
Also clear the 'Random' field.Use a MAC with a recognised vendor prefix, easily found on Goog. Many
routers can tell the difference. It also avoids any snafu with the
'locally administered' bit, WTH that is.- Start from a clean state, regarding the ifup & ifdown commands. They
only keep a record of changes they have made & can be inconsistent
with the true network state ( And no: I have no idea what I'm talking
about regarding these)
Easy. Once you know how.
edited Apr 13 '17 at 12:24
Community♦
1
answered Nov 23 '16 at 1:53
gryphonB
563
add a comment |
On Kubuntu 14.10 This page has a procedure that works.
As root:
service network-manager stop; sleep 5
ifconfig wlan0 down
macchanger -b -a wlan0; sleep 5
ifconfig wlan0 up; sleep 5
service network-manager start
The sleeps may not be necessary, but that's what worked. Macchanger is in the repos. My attempts using ifconfig or ip link appeared to take but did not survive connecting to a network, because I didn't stop Network Manager. The burnt in MAC was reasserted.
This also works:
service network-manager stop; sleep 5
ifconfig wlan0 down; ifconfig wlan0 hw ether F8:27:93:01:02:03
ifconfig wlan0 up; sleep 5;
service network-manager start; sleep 5;
I have a feeling there are some little gotchas lurking:
In the Network Manager gui, clear the 'Restrict to Device:' field.
Also clear the 'Random' field.Use a MAC with a recognised vendor prefix, easily found on Goog. Many
routers can tell the difference. It also avoids any snafu with the
'locally administered' bit, WTH that is.- Start from a clean state, regarding the ifup & ifdown commands. They
only keep a record of changes they have made & can be inconsistent
with the true network state ( And no: I have no idea what I'm talking
about regarding these)
Easy. Once you know how.
edited Apr 13 '17 at 12:24
Community♦
1
answered Nov 23 '16 at 1:53
gryphonB
563
On Kubuntu 14.10 This page has a procedure that works.
As root:
service network-manager stop; sleep 5
ifconfig wlan0 down
macchanger -b -a wlan0; sleep 5
ifconfig wlan0 up; sleep 5
service network-manager start
The sleeps may not be necessary, but that's what worked. Macchanger is in the repos. My attempts using ifconfig or ip link appeared to take but did not survive connecting to a network, because I didn't stop Network Manager. The burnt in MAC was reasserted.
This also works:
service network-manager stop; sleep 5
ifconfig wlan0 down; ifconfig wlan0 hw ether F8:27:93:01:02:03
ifconfig wlan0 up; sleep 5;
service network-manager start; sleep 5;
I have a feeling there are some little gotchas lurking:
In the Network Manager gui, clear the 'Restrict to Device:' field.
Also clear the 'Random' field.Use a MAC with a recognised vendor prefix, easily found on Goog. Many
routers can tell the difference. It also avoids any snafu with the
'locally administered' bit, WTH that is.- Start from a clean state, regarding the ifup & ifdown commands. They
only keep a record of changes they have made & can be inconsistent
with the true network state ( And no: I have no idea what I'm talking
about regarding these)
Easy. Once you know how.
edited Apr 13 '17 at 12:24
Community♦
1
answered Nov 23 '16 at 1:53
gryphonB
563
edited Apr 13 '17 at 12:24
Community♦
1
edited Apr 13 '17 at 12:24
Community♦
1
edited Apr 13 '17 at 12:24
Community♦
1
1
answered Nov 23 '16 at 1:53
gryphonB
563
answered Nov 23 '16 at 1:53
gryphonB
563
answered Nov 23 '16 at 1:53
gryphonB
563
563
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f841608%2finsufficient-permissions-to-change-mac-address%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
try deactivating the interface:
sudo ifconfig wlp4s0 down– iñaki murillo
Oct 25 '16 at 12:50