Thread Tools
This thread is privately moderated by Jack Crossfire, who may elect to delete unwanted replies.
Oct 18, 2015, 10:55 PM
Registered User
Jack Crossfire's Avatar
Thread OP
Discussion

Odroid access point


After weeks of baby steps, the Odroid finally connected to the phone as an access point. It was just as unreliable as the Pi. This didn't involve a kernel recompile, since trying to compile the kernel failed.

The old RT8192 wifi dongle once again reappeared for the access point role. This time, one must download the mysterious hostapd_realtek.tar from somewhere. This contains a mysterious version of hostapd which Realtek modified to actually work. Plugging in the dongle got the right kernel module to load, the 8192cu.

The hostapd command was:

/root/hostapd /root/rtl_minimal.conf&

The dhcp command was:
dnsmasq

The hostapd config file was:

# wlan interface. Check ifconfig to find what's your interface
interface=wlan0

# Network SSID (Your network name)
ssid=Truck

# Channel to be used! preferred 6 or 11
channel=2

# Your network Password
wpa_passphrase=xxxxxxxx

# Only change below if you are sure of what you are doing
ctrl_interface=/var/run/hostapd
#wpa=2
driver=rtl871xdrv
beacon_int=20
hw_mode=g
ieee80211n=1
wme_enabled=1
ht_capab=[SHORT-GI-20][SHORT-GI-40][HT40+]
wpa_key_mgmt=WPA-PSK
wpa_pairwise=CCMP
max_num_sta=8
wpa_group_rekey=86400





Key to getting hostapd to work was not using encryption. Commenting wpa=2 disabled it. Enabling encryption caused dhcp to fail. Another requirement was deleting /usr/sbin/NetworkManager. There was no other way to disable NetworkManager than removing the program.


The dnsmasq config file was /etc/dnsmasq.conf

interface=wlan0
no-dhcp-interface=eth0

dhcp-range=interface:wlan0,10.0.1.5,10.0.1.131,12h



Since the access point's sole purpose was aligning the camera, there was no need for encryption.
Sign up now
to remove ads between posts


Quick Reply
Message:
Thread Tools