Jump to content

trogne

Active Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

trogne's Achievements

Newbie

Newbie (1/14)

  1. Nothing wrong in the VM, since all VMs react the same. I already tried changing the MAC. As you say, it's a "limitation of virtual machines and internal wireless cards". When connecting using USB wifi adapter, MACs are good. I begin to think that EVERYONE have my problem.
  2. No. The problem in simpler. Look : For any VMs (linux/windows/mac, on vmware/vbox) using the wireless interface for connectivity (in bridged mode) : Doing "arp -a" on a physical machine on the same network (but NOT the vmware/vbox host) : this shows the VM mac address equals to the vmware/vbox host VM .
  3. I think digip does not understand. I mean the onboard wifi. And it's not the attacking wireless interface, it's just the one used for bridging. Forget about arpspoof or any attack. What I mean, is that when using the onboard wireless interface as the vbox/vmware bridged interface, then when I'm "arp -a" from another physical machine (on the same network), I see that the MAC of host PC (on which kali vm is) AND the kali VM are same (equals to the host PC MAC).
  4. It's the same for both on virtualbox and vmware. At least it works on my physical kali (an old pc) with the included wireless adapter. Note that I'm not talking about the extra wireless usb adapter (like alfa). I'm talking about the pc's wireless adapter used as a bridged adapter for the VMs. That adapter's MAC is no more showing on arp command from another physical pc on same network. Instead it shows the the host pc's MAC address. To sum up : Host PC on 192.168.1.10, mac ending with 68 Guest Kali VM on 192.168.1.11 (running on host .10), mac ending with 52 "arp -a" command on physical pc on 192.168.1.123 : Both .10 and .11 have the same MAC (ending with 68).
  5. It works if I changed the virtualbox adapter, used by Kali vm, to the ethernet adapter instead of the wireless one. Any idea why it's not working anymore with the wireless adapter ? It was working before ?
  6. Let's forget about arpspoof for a second. What's weird is that, on the remote physical machine, "arp -a" shows that the guest vm mac address is the same as the hosts mac address. It was not like this before. What's missing so that the guest vm mac address is the right one ? Clearing out the arp didn't helped.
  7. Today, if I want to arpspoof a physical machine form a VM, I have to arpspoof from the physical adapter (wlan0), not from the virtual eth0. Before (like one month ago), I was able to arpspoof a physical machine even when I arpspoof from the virtual eth0. Why does it not work today ? I've tried with my old snapshot and it's not working. I tried on vmware and virtual box too.
×
×
  • Create New...