Hi, I'm currently building a project with my Beaglebone Black (rev B) to use it like a battery powered PC running Kali which I can control over SSH by my phone.
I thought that the easiest way to get the whole thing working was to use a WIFI dongle on the Beaglebone to create an AP ad connect through it.
So my setup is something like this
I would use wlan1 to generate the AP and wlan0 as a wifi scanner/attackerCode:_______ |- wlan1: Tplink dongle | | | eth0 --- | BBB | --- POWERED USB HUB ---- * |_______| | |- wlan0: Alfa AWS051NH
I followed some guides, but I can't get it to work.
I got Hostapd set up and working with this:
I've changed /etc/network/interfaces in:Code:interface=wlan1 driver=nl80211 ssid=Grendel-1 hw_mode=g channel=6 macaddr_acl=0 auth_algs=1 ignore_broadcast_ssid=0 wpa=2 wpa_passphrase=TempPassPhrase wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP rsn_pairwise=CCMP
I used this dhcp.conf:Code:auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp iface usb0 inet static address 192.168.7.2 netmask 255.255.255.0 network 192.168.7.0 gateway 192.168.7.1 iface wlan1 inet static address 192.168.42.1 netmask 255.255.255.0 up iptables-restore < /etc/iptables.ipv4.nat
and updated /etc/default/isc-dhcp-server with wlan1 at ' INTERFACES="" '.Code:# # Sample configuration file for ISC dhcpd for Debian # # # The ddns-updates-style parameter controls whether or not the server will # attempt to do a DNS update when a lease is confirmed. We default to the # behavior of the version 2 packages ('none', since DHCP v2 didn't # have support for DDNS.) ddns-update-style none; # option definitions common to all supported networks... #option domain-name "example.org"; #option domain-name-servers ns1.example.org, ns2.example.org; default-lease-time 600; max-lease-time 7200; # If this DHCP server is the official DHCP server for the local # network, the authoritative directive should be uncommented. #authoritative; # Use this to send dhcp log messages to a different log file (you also # have to hack syslog.conf to complete the redirection). log-facility local7; # No service will be given on this subnet, but declaring it helps the # DHCP server to understand the network topology. #subnet 10.152.187.0 netmask 255.255.255.0 { #} # This is a very basic subnet declaration. #subnet 10.254.239.0 netmask 255.255.255.224 { # range 10.254.239.10 10.254.239.20; # option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org; #} # This declaration allows BOOTP clients to get dynamic addresses, # which we don't really recommend. #subnet 10.254.239.32 netmask 255.255.255.224 { # range dynamic-bootp 10.254.239.40 10.254.239.60; # option broadcast-address 10.254.239.31; # option routers rtr-239-32-1.example.org; #} # A slightly different configuration for an internal subnet. #subnet 10.5.5.0 netmask 255.255.255.224 { # range 10.5.5.26 10.5.5.30; # option domain-name-servers ns1.internal.example.org; # option domain-name "internal.example.org"; # option routers 10.5.5.1; # option broadcast-address 10.5.5.31; # default-lease-time 600; # max-lease-time 7200; #} # Hosts which require special configuration options can be listed in # host statements. If no address is specified, the address will be # allocated dynamically (if possible), but the host-specific information # will still come from the host declaration. #host passacaglia { # hardware ethernet 0:0:c0:5d:bd:95; # filename "vmunix.passacaglia"; # server-name "toccata.fugue.com"; #} # Fixed IP addresses can also be specified for hosts. These addresses # should not also be listed as being available for dynamic assignment. # Hosts for which fixed IP addresses have been specified can boot using # BOOTP or DHCP. Hosts for which no fixed address is specified can only # be booted with DHCP, unless there is an address range on the subnet # to which a BOOTP client is connected which has the dynamic-bootp flag # set. #host fantasia { # hardware ethernet 08:00:07:26:c0:a5; # fixed-address fantasia.fugue.com; #} # You can declare a class of clients and then do address allocation # based on that. The example below shows a case where all clients # in a certain class get addresses on the 10.17.224/24 subnet, and all # other clients get addresses on the 10.0.29/24 subnet. #class "foo" { # match if substring (option vendor-class-identifier, 0, 4) = "SUNW"; #} #shared-network 224-29 { # subnet 10.17.224.0 netmask 255.255.255.0 { # option routers rtr-224.example.org; # } # subnet 10.0.29.0 netmask 255.255.255.0 { # option routers rtr-29.example.org; # } # pool { # allow members of "foo"; # range 10.17.224.10 10.17.224.250; # } # pool { # deny members of "foo"; # range 10.0.29.10 10.0.29.230; # } #} subnet 192.168.42.0 netmask 255.255.255.0 { host testpc { hardware ethernet 00:c0:ca:32:cf:f3; fixed-address 192.168.42.1; } range 192.168.42.10 192.168.42.50; option broadcast-address 192.168.42.255; option routers 192.168.42.1; default-lease-time 600; max-lease-time 7200; option domain-name "local"; option domain-name-servers 8.8.8.8, 8.8.4.4; }
I've enabled IP forward on /etc/sysctl.conf (also on the go using sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward")
I've updated the IPTABLES using:
Started dhcp service and launched hostapd.Code:iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE iptables -A FORWARD -i eth0 -o wlan0 -m state --state RELATED,ESTABLISHED -j ACCEPT iptables -A FORWARD -i wlan0 -o eth0 -j ACCEPT sh -c "iptables-save > /etc/iptables.ipv4.nat"
Hostapd seems ok, but I can't get an IP for my tablet when I try to connect to the AP.
dhcp gives this error:
Can someone give me a hint on what to change?Code:Sep 10 18:26:15 grendel-1 dhcpd: Wrote 1 leases to leases file. Sep 10 18:26:15 grendel-1 dhcpd: Sep 10 18:26:15 grendel-1 dhcpd: No subnet declaration for wlan1 (no IPv4 addresses). Sep 10 18:26:15 grendel-1 dhcpd: ** Ignoring requests on wlan1. If this is not what Sep 10 18:26:15 grendel-1 dhcpd: you want, please write a subnet declaration Sep 10 18:26:15 grendel-1 dhcpd: in your dhcpd.conf file for the network segment Sep 10 18:26:15 grendel-1 dhcpd: to which interface wlan1 is attached. ** Sep 10 18:26:15 grendel-1 dhcpd: Sep 10 18:26:15 grendel-1 dhcpd: Sep 10 18:26:15 grendel-1 dhcpd: Not configured to listen on any interfaces!
I'm currently reading the documentation (PDF)
