from fakeap import * ap = FakeAccessPoint("mon0", "testap") ap.run()
I have this interface
sudo iw dev wlo1 interface add mon0 type monitor sudo ip link set mon0 up
I have the same issue as MrSentex (Issue #10 )
I haven't any more information. I looked at the process ressource consumption in top, and everything seems to be ok. Maybe a driver issue (iwlwifi), i have several errors in kernel.log
When I started a FakeAccessPoint it does not stop getting errors of this style:
Could not find IP 117.208.55.170 in ARP table.
Could not find IP 239.255.255.250 in ARP table.
Could not find IP 239.255.255.250 in ARP table.
Could not find IP 239.255.255.250 in ARP table.
Could not find IP 239.255.255.250 in ARP table.
I saw that for sending packets the project uses the sendp method from scapy.
I've read in another issue that this project is not necessarily an efficient AP implementation but is rather focusing on versatility.
Despite that, sendp is a slow method for injecting packets, especially if it is a lot of packets. This is because for every sendp call scapy opens a new socket, sends packets and then closes the socket again. Opening and closing sockets is time consuming.
Alternatively you can open an L2socket at the very start of the program and use only that socket for sending packets.
Radio_tap_header is gnerated by the receiver wireless card . I tried this function and found no use . Infact the reciever wireless card recieves the radio_tap_header according to properties of the sender wireless card like channel , transmission rate etc . Please explain the use of get_radiotap_header and correct me if i am wrong ?
This is not an issue, Iām just wondering if this is possible via a custom callback, Iām interested in testing out what passwords were used to access the ap.
Not sure if it's still supported, and i had to change many things. But now that everything looks good I cant connect to the AP nor just see it from other devices
Unknown error at monitor interface: NameError("global name 'EAP' is not defined",)
Unknown error at monitor interface: NameError("global name 'EAPOL' is not defined",)
Fixed them by adding this line in callbacks.py from scapy.layers.eap import EAPOL, EAP
Hey there,
Is the AP that is created under the scapy TCP/IP stack or the Native TCP/IP stack? If it is under the scapy stack then how can I reject packets to the AP? And if it is not, is there a way to create an AP under python which can be integrated with the native tcp/ip stack and can reject packets acting like a traditional firewall?
Have you noticed that the packet loss rate is a little high?
Many ICMP (ping) packets between station and the fakeap may be lost, for me, more than 50% sometimes. And I am sure it's not the wifi-adapter's problem.
If I use airbase-ng to setup an AP, then the situation will be much better.
I am not an expert in the network field.
So, I am just curious about that whether it is the problem of scapy or the way you handle dot11 packets?
When I starting the fakeap, tun interface created successfully but I am not able start dhcp server for that interface. Root cause is mac address is not assigned when fakeap is created. When I try to assign mac address using "ip link", it throwed errors.
I am using isc-dhcp-server in ubuntu to assign ip address for the clients connecting to fakeap
Wifiphisher is released under the MIT license though while scapy-fakeap is GPLv2. This would lead to releasing all of wifiphisher's next versions under GPL.
Do you consider switching to MIT or BSD for scapy-fakeap so we can avoid that?