Some fixes on add interface function #26
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch fixes the lack of device folder on added interface as seen on point 2 of issue11 also it gives the same mac address to the new mon interface, instead of 00:00:00:00:00:00.
So airmon-ng will create the virtual device correctly but it doesn't work yet... Also when running airmon-ng stop wlan0mon it deletes the wlan0mon interface but can't bring back the inteface wlan0. And if you run rmmod 8812au or remove the device It causes kernel seg fault.
However if you create a mon interface ussing iw:
iw dev wlan0 interface add mon0 type monitorand later you remove itiw mon0 deldoesn't cause seg fault on kernel but mon0 interface doesn't still work...A weird behaviour happened when I ran
airodoump-ng -c 1 wlan0during a while and then I ranaireplay-ng -9 mon0, in that case mon0 found one AP and triyed to inject packets...It could be a good approach to make this driver compatible with airmon-ng... but it needs more work.