|
Post by alexl83 on Apr 14, 2016 0:02:38 GMT
Kali 2016.1, amd64 running in virtualbox 5.0.16, basic text-only installation from official kali mini iso. fruitywifi git, master branch - modules set: api - ap - mana - karma (all from github). hostapd-karma doesn't compile, installing libnl-genl-3-dev doesn't help hostapd-mana does compile (with libnl-genl-3-dev) but doesn't work, after clicking enable, it doesn't run; no useful log entry recoverable from the webinterface. This project really needs some testing/documentation; I lost hours trying to set it up, is there (at least) a known working kali/fruitywifi version combination available ? I tried deb packages, master branch, v2.4 branch, github modules, deb modules.... all to no avail. My objective is to build an headless kali solution, manageable via webif, just running fruitywifi: lack of documentation is making this project impossible. I don't know if I have to remove my interfaces from /etc/network/interfaces (as I might have read here on the forums), I don't get basic functionality working, I'm lost: it feels messy. This project is very interesting, but xtr4nge, I can't read your mind to understand how this software ticks, and it's no use reinventing the wheel, I can't dissect the source code just to understand how it works, it's infeasible. mana-toolkit is text only, it works oob, it took me 15 minutes to integrate in fedora (firewall etc), switching to it for the time being. Any help appreciated. Sorry for my frustration, mean no offense. Peace. Alex
|
|
|
Post by xtr4nge on Apr 14, 2016 8:20:28 GMT
Hi alexl83, FruityWiFi is very easy to understand after you play with it a little bit. The code is simple and is mainly using well known tools ( FruityWiFi is mainly a framework and a wrapper ). There is a lot of info on the forum, I created the forum to make it easy for people to track issue and solutions, and also I'm always replaying to questions as soon as I can. I spend a lot of my own time building this project, and It will be awesome if people start contributing to it at least with documentation and tutorials. FruityWiFi will be always open source, I do this because is fun and because I use it for my own purposes (projects, research, whatever..) but I don't get any benefit releasing this project more than the fun. I don't sell products, I don't sell a brand, nothing. The installers are easy to understand and they are doing all the job, the user only needs to run the installers. They only need to have a compatible/tested system and the supported hardware. Linux distros changes versions, codenames, packages on repositories, so time to time some adjustments are needed on the installers, but it is very easy to spot doing some extra research, or asking on the forum. well.. you can try this: Mana is on Kali linux repositories and you can run apt-get install fruitywifi-module-mana If you want to install it from GitHub you need to change a line on the installer. Check the NetHunter thread, you will find the solution there under MINOR CHANGES. fruitywifi.boards.net/thread/111/fruitywifi-v2-4again, you can always ask on the forum. I'm always trying to help. regards,
|
|
|
Post by alexl83 on Apr 14, 2016 11:30:44 GMT
Thank you for your support xtr4nge; applying nethunter modifications I was able to get karma/mana to compile and to behave (sortof); now, if I enable AP mode, I get client associating, but still they're not getting IP configuration from DCHP; kali repos appear to be down, may I be missing some packages/modules ?
I'm running a pretty barebone ap/api/karma/mana setup.
|
|
|
Post by xtr4nge on Apr 14, 2016 11:35:04 GMT
Hi alexl83, No prob at all.
There is a change on the main installer that removes and option on dnsmasq config file.
edit this file:
/usr/share/fruitywifi/conf/dnsmasq.conf and remove/comment the option server=
That option (with that setup) is not supported anymore by DNSmasq. That is why I created FruityDNS to replace the DNS server option provided by DNSmasq To switch from DNSmasq as DNS server to FruityDNS you need to modify the option from AP module on tab DHCP-DNS
Note: if you want to fix the installer (install-FruityWifi.sh) the same change that you performed on Mana and Karma installer is required.
let me know regards,
|
|
|
Post by alexl83 on Apr 14, 2016 11:37:39 GMT
Thank you, in my setup the 'server' option is already commented; client get stuck on obtaining ip.
|
|
|
Post by xtr4nge on Apr 14, 2016 11:42:40 GMT
OK, go to AP module and check if AP + DHCP + DNS are enabled (green)
Note: be sure that you don't have any instance of DNSmasq running before to start the AP, and also Network-Manager can give you some problems (kill both to test)
Tail the dnsmasq log to get more info:
tail -F /usr/share/fruitywifi/logs/dnsmasq.log You can also refresh the tab LogDHCP on AP module.
before to start using Mana and Karma modes, check if Hostapd mode is working ok. You can change the modes from MENU/Config
Be sure that the IN and OUT interfaces are OK (IN is the AP interface, OUT is the internet interface)
regards,
|
|
|
Post by alexl83 on Apr 14, 2016 11:43:46 GMT
Hi alexl83, No prob at all. There is a change on the main installer that removes and option on dnsmasq config file. edit this file: /usr/share/fruitywifi/conf/dnsmasq.conf and remove/comment the option server=That option (with that setup) is not supported anymore by DNSmasq. That is why I created FruityDNS to replace the DNS server option provided by DNSmasq To switch from DNSmasq as DNS server to FruityDNS you need to modify the option from AP module on tab DHCP-DNS Note: if you want to fix the installer (install-FruityWifi.sh) the same change that you performed on Mana and Karma installer is required. let me know regards, install-FruityWifi.sh is already fixed, I think I'm missing some kali package (perhaps dhcp server) that the installer couldn't pull due to repos being offline...
|
|
|
Post by xtr4nge on Apr 14, 2016 11:48:27 GMT
Check the previous comment about DNSmasq and Network-Manager (kill them) Also check that the wireless interfaces that you are using on FruityWiFi are not present on
/etc/network/interfaces regards,
|
|
|
Post by alexl83 on Apr 14, 2016 11:50:59 GMT
OK, go to AP module and check if AP + DHCP + DNS are enabled (green) Note: be sure that you don't have any instance of DNSmasq running before to start the AP, and also Network-Manager can give you some problems (kill both to test) Tail the dnsmasq log to get more info: tail -F /usr/share/fruitywifi/logs/dnsmasq.log You can also refresh the tab LogDHCP on AP module. before to start using Mana and Karma modes, check if Hostapd mode is working ok. You can change the modes from MENU/Config Be sure that the IN and OUT interfaces are OK (IN is the AP interface, OUT is the internet interface) regards, Network config is sound, AP/DNS/DHCP disabled; I had them enabled in a previous try, but with no effect; dnsmasq log empty. No dnsmasq/networkmanager instances present. only eth in /etc/network/interfaces. IT seems, after 2-3 minutes DHCP and DNS gets enabled, still clients can't connect.
|
|
|
Post by xtr4nge on Apr 14, 2016 11:56:16 GMT
- re-check network-manager
/etc/init.d/network-manager stop
- start AP module - verify that DNSmasq is now running - tail dnsmasq log
You need to have some events on the log, if not, FruityWiFi DNSmasq instance is not running.
Note: I just re-read your initial post. I never used FruityWiFi on VirtualBox. When I tried for first and last time on VirtualBox it was 2 years ago, and it wasn't working. It works fine on VMware Fusion.
regards,
|
|
|
Post by alexl83 on Apr 14, 2016 11:58:33 GMT
- re-check network-manager /etc/init.d/network-manager stop - start AP module - verify that DNSmasq is now running - tail dnsmasq log You need to have some events on the log, if not, FruityWiFi DNSmasq instance is not running. Note: I just re-read your initial post. I never used FruityWiFi on VirtualBox regards, I'm using a debian minimal installation, text-only; networkmanager is not installed. AP started, dnsmasq not running according to 'ps -e'.
|
|
|
Post by xtr4nge on Apr 14, 2016 12:00:20 GMT
If DNSmasq is not running then there is a problem there, as DNSmasq is the DHCP server (and the default DNS server).
regards,
|
|
|
Post by alexl83 on Apr 14, 2016 12:01:15 GMT
Ok, I'll try a clean install once again; I got connection working yesterday on virtualbox, so it must be something gone wrong. Thanks
|
|
|
Post by alexl83 on Apr 14, 2016 12:03:53 GMT
If DNSmasq is not running then there is a problem there, as DNSmasq is the DHCP server (and the default DNS server). regards, Shouldn't AP module start it automatically, or am I supposed to enable dnsmasq from init ?
|
|
|
Post by xtr4nge on Apr 14, 2016 12:06:55 GMT
No prob, Removing the server= option from /usr/share/fruitywifi/conf/dnsmasq.conf should do the trick. You can also debug the dnsmasq config manually
- start the wireless interface and assign the IP on the default FruityWiFi range (example wlan0)
ifconfig wlan0 10.0.0.1 ifconfig wlan0 up - run dnsmasq manually
dnsmasq -C /usr/share/fruitywifi/conf/dnsmasq.conf -d let me know.
|
|