You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Macstealer performs the EAP and MSCHAPv2 handshake successfully. It then performs a DHCP broadcast and receives two different DHCP offers with a different IP in each offer from the DHCP service. Macstealer proceeds to respond with a DHCP request for each IP address which presumably confuses the DHCP server and the DHCP requests fail.
Offer 1: 10.218.144.69
Offer 2: 10.218.145.10
One DHCP request is sent for 10.218.144.69 and four DHCP requests are sent for 10.218.145.10.
Note: If I create basic wpa_supplicant.conf file and manually use wpa_supplicant followed by dhclient, I am able to connect and obtain an ip address as expected.
Great research - keen to try this out!
The text was updated successfully, but these errors were encountered:
When multiple different DHCP offers arrive, the script would reply to
all of them. This confuses some DHCP servers. Prevent this by only
replying to the first offered IP address.
This should fix#6
Hi, appreciate you looking into this but unfortunately I no longer have access to the testing environment. Therefore, I can't conclude whether your patch worked or not. Thanks again.
Macstealer performs the EAP and MSCHAPv2 handshake successfully. It then performs a DHCP broadcast and receives two different DHCP offers with a different IP in each offer from the DHCP service. Macstealer proceeds to respond with a DHCP request for each IP address which presumably confuses the DHCP server and the DHCP requests fail.
Offer 1: 10.218.144.69
Offer 2: 10.218.145.10
One DHCP request is sent for 10.218.144.69 and four DHCP requests are sent for 10.218.145.10.
Note: If I create basic wpa_supplicant.conf file and manually use wpa_supplicant followed by dhclient, I am able to connect and obtain an ip address as expected.
Great research - keen to try this out!
The text was updated successfully, but these errors were encountered: