Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

How hard would it be to add enterprise connections to client mode? #106

Open
walletdude opened this issue Sep 10, 2017 · 4 comments
Open

Comments

@walletdude
Copy link

I love the client mode feature of the project, but I wish it supported modes other than WPA2. How hard would it be to support enterprise networks for client mode?

@Swiftb0y
Copy link
Contributor

It depends. The wpa config get generated here and here. As you can see, a temporary config gets created and appended to the existing networks from /etc/wpa_supplicant/wpa_supplicant.conf. If you know how to manually add an enterprise wifi there, you can just add it normally and remove the check here. This would be the easiest temporary hack I could think of, but you might brick your existing installation if you are not careful.
It should not be to difficult to implement a genuine solution, but other things have more priority right now.

@mame82
Copy link
Collaborator

mame82 commented Sep 18, 2017

Not planned at the moment (PR is an option, but code changes frequently)

@DeadPackets
Copy link

I might be able to work on this, what is exactly needed to be changed? I'm having trouble understanding what the scripts do exactly.

@Swiftb0y
Copy link
Contributor

As already stated, I suggest you read the wiki. The P4wnP1 core is a systemd service that calls boot/boot_P4wnP1 which is a bash script that includes the modules based on the settings. The wifi gets setup in boot/init_wifi.sh but what for an ok from mame before you modify the core.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

4 participants