search

alobbs / macchanger

GNU MAC Changer
http://www.gnu.org/software/macchanger
GNU General Public License v3.0
581 stars 112 forks source link

Network driver didn't actually change to the new MAC! ! #37

Open TommyToo opened 7 years ago

TommyToo commented 7 years ago

Every time I run macchanger I get this error

root@kali:~# macchanger -r wlan0 Current MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.) Permanent MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.) New MAC: 76:9f:ed:09:77:fc (unknown) Network driver didn't actually change to the new MAC!!

Before running macchanger I am running ifconfig wlan0 down

After macchanger I'd finish by using ifconfig wlan0 up If the darn thing would work.

I am using a USB Wifi adapter inside virtualbox. The adapter is made by Ourlink and has a Realtek rtl8192eu chipset. I have installed the driver using several different methods. I can use the wifi adapter and connect to the internet but when I run airmon-ng I get this.

root@kali:~# airmon-ng

PHY Interface Driver Chipset

null wlan0 ?????? Realtek Semiconductor Corp.

Someone please help, I have about 18 hours of researching and testing with this issue to no avail. I am going insane. Thank you in advance. You'll be my hero for the month!

Sabyextremo1234 commented 6 years ago

I've got the same darned issue and I think that it all owes to Realtek Semiconductor corp. cause I've been toiling for the same bloody issue and I have a leoxys adapter running the same chipset . Let me tell you this : Never buy a stupid adapter that runs a Realtek chipset cause I can't enable monitor mode or change my Mac address or do anything for that matter. I suggest you get another adapter for this.

YerongLi commented 6 years ago

I am using a Realtek Semiconductor corp adapter I found actually we can spoof the MAC address by following the process here: https://www.youtube.com/watch?v=-orY4fCoze4

1) First generate a new MAC address with macchanger.

# macchanger -r wlan0
Current MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.)
Permanent MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.)
New MAC: 76:9f:ed:09:77:fc (unknown)
Network driver didn't actually change to the new MAC!!

2) Then copy and paste the New MAC to the cloned MAC of the connected wifi:76:9f:ed:09:77:fc 3) Then disconnect with the wifi. (IMPORTANT, Don't miss this)

4) Reboot the machine and check the current MAC address:

# macchanger  -s wlan0
Current MAC:   76:9f:ed:09:77:fc (unknown)
Permanent MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.)

This works, but this is very inconvinent though. I would be very happy if anyone could find a way to finish the MAC change without a reboot.

ghost commented 6 years ago

@YerongLi Can you please elaborate step number? I'm not sure what the cloned MAC is referenced to.

TTTristan commented 6 years ago

@YerongLi Could you show step 2 as it would be typed in linux? Just getting into linux and not quite getting step 2 with that way of explaining it.

MAsghar11 commented 5 years ago

@YerongLi @maxrugen can anyone please explain what you mean by step 2?

bddarknight commented 5 years ago

I am using a Realtek Semiconductor corp adapter I found actually we can spoof the MAC address by following the process here: https://www.youtube.com/watch?v=-orY4fCoze4

  1. First generate a new MAC address with macchanger.
# macchanger -r wlan0
Current MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.)
Permanent MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.)
New MAC: 76:9f:ed:09:77:fc (unknown)
Network driver didn't actually change to the new MAC!!
  1. Then copy and paste the New MAC to the cloned MAC of the connected wifi:76:9f:ed:09:77:fc
  2. Then disconnect with the wifi. (IMPORTANT, Don't miss this)
  3. Reboot the machine and check the current MAC address:
# macchanger  -s wlan0
Current MAC:   76:9f:ed:09:77:fc (unknown)
Permanent MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.)

This works, but this is very inconvinent though. I would be very happy if anyone could find a way to finish the MAC change without a reboot.

Tried in Kali, Did not work.

vijay2701 commented 5 years ago

I am using a Realtek Semiconductor corp adapter I found actually we can spoof the MAC address by following the process here: https://www.youtube.com/watch?v=-orY4fCoze4

1. First generate a new MAC address with macchanger.
# macchanger -r wlan0
Current MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.)
Permanent MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.)
New MAC: 76:9f:ed:09:77:fc (unknown)
Network driver didn't actually change to the new MAC!!
1. Then copy and paste the **New MAC** to the cloned MAC of the connected wifi:`76:9f:ed:09:77:fc`

2. Then disconnect with the wifi. (IMPORTANT, Don't miss this)

3. Reboot the machine and check the current MAC address:
# macchanger  -s wlan0
Current MAC:   76:9f:ed:09:77:fc (unknown)
Permanent MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.)

This works, but this is very inconvinent though. I would be very happy if anyone could find a way to finish the MAC change without a reboot.

what is cloned mac bro?

saiko85 commented 5 years ago

I faced the same issue with REALTEK external-wifi dongle (maybe it has something to do with its inability to swap modes or any form of malleability) however

1) macchanger works on any eth port with no issue- and for wifi- 2) i switched over to RALINK device (via my ALFA network dongle- supports Monitor mode etc) The macchanger command worked on that-

maybe try (#crontab -e) command and put (@reboot macchanger -a wlan0) at the end - and then reboot and see if that helps- tbh its a lil bit of a hail mary- but worth a shot

vikas-k-sharma commented 4 years ago

I am also facing the same issue on my end. The

I am using a Realtek Semiconductor corp adapter I found actually we can spoof the MAC address by following the process here: https://www.youtube.com/watch?v=-orY4fCoze4

1. First generate a new MAC address with macchanger.
# macchanger -r wlan0
Current MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.)
Permanent MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.)
New MAC: 76:9f:ed:09:77:fc (unknown)
Network driver didn't actually change to the new MAC!!
1. Then copy and paste the **New MAC** to the cloned MAC of the connected wifi:`76:9f:ed:09:77:fc`

2. Then disconnect with the wifi. (IMPORTANT, Don't miss this)

3. Reboot the machine and check the current MAC address:
# macchanger  -s wlan0
Current MAC:   76:9f:ed:09:77:fc (unknown)
Permanent MAC: 00:e0:4c:10:ed:53 (REALTEK SEMICONDUCTOR CORP.)

This works, but this is very inconvinent though. I would be very happy if anyone could find a way to finish the MAC change without a reboot.

I was trying to do this method and to see the step 2, i thing of using the given video link. On opening it, getting video unavailable message. is anyone aware of how to perform the step 2?

Keenonthedaywalker commented 4 years ago

Has anyone actually figured it out yet?

monickverma commented 4 years ago

Did any of you get it fixed??

monickverma commented 4 years ago

Did any of you get it fixed??

Did You figure it out?

Stevedmg commented 3 years ago

did you figure out this : Then copy and paste the New MAC to the cloned MAC of the connected wifi - ???

Stevedmg commented 3 years ago

https://www.youtube.com/watch?v=-orY4fCoze4 - this video is not available -

saiko85 commented 3 years ago

So long as the drivers not the issue and is updated- and mine I got it working-

esp when i used the #chrontab-e to schedule the machchanger upon startup

@reeboot macchanger-a wlan0

This was the workaround that worked for me- chrontab was the answer to my predicament

On Mon, Feb 22, 2021 at 10:43 AM Stevedmg notifications@github.com wrote:

did you figure out this : Then copy and paste the New MAC to the cloned MAC of the connected wifi - ???

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/alobbs/macchanger/issues/37#issuecomment-783086718, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMNXHTNRS5BPMXVEKSAZQDTTAHRXRANCNFSM4C72IBGA .

zacky56 commented 1 year ago

step number two is unclear