How to get AP working under SPOS v3

[jogglerhase]

Note - Background:
This is a continuation of a topic within the SPOSv3 thread - on how to enable the joggler beeing an Access Point for other devices, bridging jogglers LAN & WLAN.
I got this working w/ Palindroms prior instructions, however, only in wireless g mode, not n mode....

Can you see the WLAN-AP (with a phone and/or tablet)?
What exactly is not working?
check the devices

Code: Select all

iwconfig

are they wlan0 and eth0?

You could try to debug hostapd by issuing:

Code: Select all

sudo /usr/bin/killall hostapd

sudo hostapd -d /etc/hostapd/hostapd.conf

...

... so, here it continues.
I am back on the joggler, where g mode works, but n mode doesn't.

What does not work: If I seach w/ a Laptop for the AP, it is not existent (i.e. via Program inSSIDer).

If I do

Code: Select all

iwconfig

I get:

Code: Select all

br0       no wireless extensions.
wlan0     IEEE 802.11bgn  Mode:Master  Tx-Power=20 dBm
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
lo        no wireless extensions.
eth0      no wireless extensions.

Is that what you expect?

Maybe this is a better hint at what does not work:
If I do

Code: Select all

sudo /usr/bin/killall hostapd 

I get

Code: Select all

hostapd: no process found

Also, when I try to reatart it via

Code: Select all

sudo hostapd -d /etc/hostapd/hostapd.conf

the process is not started and I get this feedback:

Code: Select all

random: Trying to read entropy from /dev/random
Configuration file: /etc/hostapd/hostapd.conf
rfkill: initial event: idx=0 type=1 op=0 soft=0 hard=0
nl80211: Supported cipher 00-0f-ac:1
nl80211: Supported cipher 00-0f-ac:5
nl80211: Supported cipher 00-0f-ac:2
nl80211: Supported cipher 00-0f-ac:4
nl80211: Using driver-based off-channel TX
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 3 iftype 3 (AP)
nl80211: Setup AP(wlan0) - device_ap_sme=0 use_monitor=0
nl80211: Subscribe to mgmt frames with AP handle 0x8c06d68
nl80211: Register frame type=0xb0 nl_handle=0x8c06d68 match=
nl80211: Register frame type=0x0 nl_handle=0x8c06d68 match=
nl80211: Register frame type=0x20 nl_handle=0x8c06d68 match=
nl80211: Register frame type=0xa0 nl_handle=0x8c06d68 match=
nl80211: Register frame type=0xc0 nl_handle=0x8c06d68 match=
nl80211: Register frame type=0xd0 nl_handle=0x8c06d68 match=
nl80211: Register frame type=0x40 nl_handle=0x8c06d68 match=
nl80211: Interface wlan0 is in bridge br0
nl80211: Add own interface ifindex 4
nl80211: Add own interface ifindex 3
phy: phy0
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
Using existing control interface directory.
ctrl_iface bind(PF_UNIX) failed: Address already in use
ctrl_iface exists, but does not allow connections - assuming it was leftover from forced program termination
Successfully replaced leftover ctrl_iface socket '/var/run/hostapd/wlan0'
wlan0: interface state UNINITIALIZED->COUNTRY_UPDATE
Previous country code 00, new country code DE
Continue interface setup after channel list update
ctrl_iface not configured!
random: Got 20/20 bytes from /dev/random

Any ideas / leads / hints?
Heiner

[Man in a van]

I don't understand any of this stuff, but are you certain that the Joggler hardware actually supports n mode?

[jogglerhase]

...., but are you certain that the Joggler hardware actually supports n mode?

Yes, the jogglers std internal Wlan Stick is able to do n-mode - when I used it to connect the Joggler to my network, it was using n mode with speeds >54M

Heiner