How To: Create an 802.11n AP (Access Point) w/ Debian on a Dockstar/Pogoplug/kirkwood device

@Joey : fair comment! and yes at least we know its possible and feasable.

Just to say, using the instructions on the first page with minimal alterations, I've got my Pogoplug Pro with internal wifi working as a bridge. Using latest version (4.0.0-oxnas-tld-2) of debian and u-boot. It's early days, so I don't know yet about long-term stability.

Peter

I know this is an old thread but i have 3 pogoplug-pro v3 's, one for a daily use unit and one for messing with (which now I want to use as an AP) and the other for parts, (not many parts but its still operational,lol) well I wanted to try this out with a wireless access point and instead of using the instructions listed I used network-manager over my vnc connection, for some reason I have 2 issues:

1. the wireless key will not work to connect to the hotspot created.Any ideas would be helpful!!!!!

2. I had a serial connection (picocom) and wifi (ssh over local network)on two terminals and while trying to figure out the issues I typed in journalctl -f on the wifi connected ssh terminal and for some reason it carried over to the serial terminal as well. I cannot get the journalctl to stop scrolling on the serial terminal, I tried ctl-c, I restarted, I shutdown then unplugged then restarted, nothing is working to stop this from occurring. I am running debian 10 sid on this device, and its been working great other than the 2 issues, any ideas how to stop journalctl from constantly running on the serial terminal??

number 2 is a bit off topic but part of the issue:)

Thanks !!

Echowarrior108

device: pogoplug-pro v3

Currently running:
Debian GNU/Linux Bullseye 12-9-22
Linux 5.4.224-oxnas-tld-1 armv6l GNU/Linux 11-27-22

gave up on #2 and copied my backup rootfs that I saved for things above my intelligence grade:)




EDIT: this did not help. it still does the logging on the serial while trying to type... going to start a new topic on this!

Echowarrior108

device: pogoplug-pro v3

Currently running:
Debian GNU/Linux Bullseye 12-9-22
Linux 5.4.224-oxnas-tld-1 armv6l GNU/Linux 11-27-22



Edited 1 time(s). Last edit at 11/08/2019 11:10PM by echowarrior108.

echowarrior108,

> gave up on #2 and copied my backup rootfs that I
> saved for things above my intelligence grade:)

Sounds just like what I do from time to time :)

A hobby ceases to be fun when we spend way too much time on it! that's the story of my couple false starts on my recent atempts on building certain Marvel SoC u-boots. I have strong affinity for simple and open source solution. Eg. if I need an NDA with the manufacturer to understand something, I'll am just like, screw it :) I think in a way, it is similar in your case, what is journalctl doing there, I have no idea why.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I rebooted 3 more times and it appears to have cleared up, what was strange was it came back after a full format and reinstall. I had to do a lot to install rtl88x2bu module , simply because I have not installed modules before so it was a challenge but its not my main plug so I don't mind starting over. but you are right about a hobby becoming a job:)
I had to walk away for a few , my plan is to have an rtl88xbu usb ac1200 running as the AP, I can list the steps needed after days of doing the same thing with the same results:) lol

When I get it working I will make a list of the right way to do it as i have found a few hundred wrong ways to do it:)

It will be fun when it works:)

update: I had it do it again, kinda at screw it stage with this setup , time for a vacation:)

update 2: after installing the duplicate of my "good" copy on a new drive I was running ok until I installed network-manager and all it would do was log on the root screen non-stop. I am assuming this was the issue and not journalctl as I had thought, I purged out network-manager and rebooted and it stopped the logging problem. Has anyone had an issue with network-manager before?


update 3: figured out the one issue, it was related to the logging for the realtek module, was a simple fix but I am still unsure what caused it to run on the main display. below are the instructions just need to change the module name to your current module. mine is rtl88x2bu and it was a pain to install.

How to set driver debug log level
2016/02/22
1 Introduction.
1.1 The driver’s debug log level is as follows,
enum {
_DRV_NONE_ = 0,
_DRV_ALWAYS_ = 1,
_DRV_ERR_ = 2,
_DRV_WARNING_ = 3,
_DRV_INFO_ = 4,
_DRV_DEBUG_ = 5,
_DRV_MAX_ = 6
};
1.2 The default log level is “_DRV_INFO_”.
1.3 The default compiling flag is “CONFIG_RTW_DEBUG”, which is defined in
“Makefile”.
2 How to change debug log level during runtime.
2.1 Use the following command to set different log level.
# echo x > /proc/net/rtl8723bs/log_level
x : is a number mapping to log level in driver.
For example, if you want to change to log level to “_DRV_ERR_”, please
execute the command below,
# echo 2 > /proc/net/rtk8723bs/log_level
3 How to change debug log level during inserting driver module.
For example for change log level to _DRV_WARNING_,
# insmod 8723bs.ko rtw_drv_log_level=3
4 How to disable all debug log level during runtime and inserting driver module.
4.1 during runtime, please execute the command below,
# echo 0 > /proc/net/rtk8723bs/log_level
4.2 during inserting driver module , please execute the command below,
# insmod 8723bs.ko rtw_drv_log_level=0

btw sorry if I used the code thing wrong:)

Echowarrior108

device: pogoplug-pro v3

Currently running:
Debian GNU/Linux Bullseye 12-9-22
Linux 5.4.224-oxnas-tld-1 armv6l GNU/Linux 11-27-22



Edited 5 time(s). Last edit at 11/12/2019 11:07PM by echowarrior108.

After properly installing the usb wifi ( https://forum.doozan.com/read.php?2,92749 ) I found out that I could use the create_ap program which works really well! I am running it from my internal pci below and broadcasting from my usb below also:

create_ap wlxb wlp0s0  wifiname wifipassword
or
create_ap -g 192.168.5.1 wlxb wlp0s0  wifiname wifipassword
( if you want to assign your own ip)

in this code the (wlxb or whatever your device name is ) will be the broadcasting wifi and the wlp0s0 would be the receiving wifi. if they are both the same card ( i believe some are capable ) then they would be the same.

lspci -v
00:00.0 Network controller: Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak] (rev 34)
	Subsystem: Intel Corporation Centrino Advanced-N 6230 AGN
	Flags: bus master, fast devsel, latency 0, IRQ 11
	Memory at 48000000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [e0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number XX.XX>X>>>>>>.xx
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

T:  Bus=01 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#=  5 Spd=480 MxCh= 0
D:  Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0bda ProdID=b812 Rev=02.10
S:  Manufacturer=Realtek
S:  Product=USB3.0 802.11ac 1200M Adapter
S:  SerialNumber=123456
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#=0x0 Alt= 0 #EPs= 5 Cls=ff(vend.) Sub=ff Prot=ff Driver=rtl88x2bu

and the iwconfig: (54 ft from main router and 3 walls between)

ap0       IEEE 802.11abgn  Mode:Master  Tx-Power=15 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          
wlxbcec23c36d26  unassociated  Nickname:"<haha>"
          Mode:Managed  Frequency=2.412 GHz  Access Point: Not-Associated   
          Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

sit0      no wireless extensions.

lo        no wireless extensions.

eth0      no wireless extensions.

wlp0s0    IEEE 802.11abgn  ESSID:"formetoknow"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: 00:00:00:00:00:00   
          Bit Rate=216 Mb/s   Tx-Power=15 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=65/70  Signal level=-45 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:46   Missed beacon:0

I haven't had the need to try the ethernet port but I believe there is a setting for that as well.

Echowarrior108

device: pogoplug-pro v3

Currently running:
Debian GNU/Linux Bullseye 12-9-22
Linux 5.4.224-oxnas-tld-1 armv6l GNU/Linux 11-27-22



Edited 1 time(s). Last edit at 11/18/2019 11:36PM by echowarrior108.

Echowarrior108,

Well done :)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Echowarrior108,

Please add details about create_ap. I.e. How do users install it?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi bodhi, I used the instructions from github,https://github.com/oblique/create_ap

first install the following if not installed:

apt install dnsmasq
apt install hostapd
apt install haveged

Installation
Generic

git clone https://github.com/oblique/create_ap
cd create_ap
make install

there is a readme file there which is helpful.

I did do a quick install on my other plug give the details along with the help file:

git clone https://github.com/oblique/create_ap
Cloning into 'create_ap'...
remote: Enumerating objects: 4, done.
remote: Counting objects: 100% (4/4), done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 1038 (delta 0), reused 0 (delta 0), pack-reused 1034
Receiving objects: 100% (1038/1038), 355.43 KiB | 1.24 MiB/s, done.
Resolving deltas: 100% (571/571), done.
root@debian:~# cd create_ap
root@debian:~/create_ap# make install
install -Dm755 create_ap /usr/bin/create_ap
install -Dm644 create_ap.conf /etc/create_ap.conf
[ ! -d /lib/systemd/system ] || install -Dm644 create_ap.service /usr/lib/systemd/system/create_ap.service
install -Dm644 bash_completion /usr/share/bash-completion/completions/create_ap
install -Dm644 README.md /usr/share/doc/create_ap/README.md
root@debian:~/create_ap# systemctl start create_ap
root@debian:~/create_ap# create_ap --help
Usage: create_ap [options] <wifi-interface> [<interface-with-internet>] [<access-point-name> [<passphrase>]]

Options:
  -h, --help              Show this help
  --version               Print version number
  -c <channel>            Channel number (default: 1)
  -w <WPA version>        Use 1 for WPA, use 2 for WPA2, use 1+2 for both (default: 1+2)
  -n                      Disable Internet sharing (if you use this, don't pass
                          the <interface-with-internet> argument)
  -m <method>             Method for Internet sharing.
                          Use: 'nat' for NAT (default)
                               'bridge' for bridging
                               'none' for no Internet sharing (equivalent to -n)
  --psk                   Use 64 hex digits pre-shared-key instead of passphrase
  --hidden                Make the Access Point hidden (do not broadcast the SSID)
  --mac-filter            Enable MAC address filtering
  --mac-filter-accept     Location of MAC address filter list (defaults to /etc/hostapd/hostapd.accept)
  --redirect-to-localhost If -n is set, redirect every web request to localhost (useful for public information networks)
  --hostapd-debug <level> With level between 1 and 2, passes arguments -d or -dd to hostapd for debugging.
  --isolate-clients       Disable communication between clients
  --ieee80211n            Enable IEEE 802.11n (HT)
  --ieee80211ac           Enable IEEE 802.11ac (VHT)
  --ht_capab <HT>         HT capabilities (default: [HT40+])
  --vht_capab <VHT>       VHT capabilities
  --country <code>        Set two-letter country code for regularity (example: US)
  --freq-band <GHz>       Set frequency band. Valid inputs: 2.4, 5 (default: 2.4)
  --driver                Choose your WiFi adapter driver (default: nl80211)
  --no-virt               Do not create virtual interface
  --no-haveged            Do not run 'haveged' automatically when needed
  --fix-unmanaged         If NetworkManager shows your interface as unmanaged after you
                          close create_ap, then use this option to switch your interface
                          back to managed
  --mac <MAC>             Set MAC address
  --dhcp-dns <IP1[,IP2]>  Set DNS returned by DHCP
  --daemon                Run create_ap in the background
  --stop <id>             Send stop command to an already running create_ap. For an <id>
                          you can put the PID of create_ap or the WiFi interface. You can
                          get them with --list-running
  --list-running          Show the create_ap processes that are already running
  --list-clients <id>     List the clients connected to create_ap instance associated with <id>.
                          For an <id> you can put the PID of create_ap or the WiFi interface.
                          If virtual WiFi interface was created, then use that one.
                          You can get them with --list-running
  --mkconfig <conf_file>  Store configs in conf_file
  --config <conf_file>    Load configs from conf_file

Non-Bridging Options:
  --no-dns                Disable dnsmasq DNS server
  --no-dnsmasq            Disable dnsmasq server completely
  -g <gateway>            IPv4 Gateway for the Access Point (default: 192.168.12.1)
  -d                      DNS server will take into account /etc/hosts
  -e <hosts_file>         DNS server will take into account additional hosts file

Useful informations:
  * If you're not using the --no-virt option, then you can create an AP with the same
    interface you are getting your Internet connection.
  * You can pass your SSID and password through pipe or through arguments (see examples).
  * On bridge method if the <interface-with-internet> is not a bridge interface, then
    a bridge interface is created automatically.

Examples:
  create_ap wlan0 eth0 MyAccessPoint MyPassPhrase
  echo -e 'MyAccessPoint\nMyPassPhrase' | create_ap wlan0 eth0
  create_ap wlan0 eth0 MyAccessPoint
  echo 'MyAccessPoint' | create_ap wlan0 eth0
  create_ap wlan0 wlan0 MyAccessPoint MyPassPhrase
  create_ap -n wlan0 MyAccessPoint MyPassPhrase
  create_ap -m bridge wlan0 eth0 MyAccessPoint MyPassPhrase
  create_ap -m bridge wlan0 br0 MyAccessPoint MyPassPhrase
  create_ap --driver rtl871xdrv wlan0 eth0 MyAccessPoint MyPassPhrase
  create_ap --daemon wlan0 eth0 MyAccessPoint MyPassPhrase
  create_ap --stop wlan0

There is a list of examples in the Readme.md

With this plug I am using eth0 to the usb wifi for example purposes.

Here is the current setup prior to running create_ap:
Note: I have no clue how to change the Nickname...

~# iwconfig
wlxbcec23c36d26  unassociated  Nickname:"<WIFI@REALTEK>"
          Mode:Auto  Frequency=2.412 GHz  Access Point: Not-Associated   
          Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

sit0      no wireless extensions.

lo        no wireless extensions.

eth0      no wireless extensions.

this got me to the point where I had a basic install and shared internet, later on I will do the configuration files but create_ap gives you a tmp file that works and you can use that as a guide to a permanent profile.

~# create_ap wlxbcec23c36d26 eth0 MyAccessPoint MyPassPhrase
WARN: Your adapter does not fully support AP virtual interface, enabling --no-virt
Config dir: /tmp/create_ap.wlxbcec23c36d26.conf.YPLXNDlB
PID: 7222
Sharing Internet using method: nat
hostapd command-line interface: hostapd_cli -p /tmp/create_ap.wlxbcec23c36d26.conf.YPLXNDlB/hostapd_ctrl
Configuration file: /tmp/create_ap.wlxbcec23c36d26.conf.YPLXNDlB/hostapd.conf
wlxbcec23c36d26: Could not connect to kernel driver
Using interface wlxbcec23c36d26 with hwaddr xx:xx:xx:xx:xx:xx and ssid "MyAccessPoint"
wlxbcec23c36d26: interface state UNINITIALIZED->ENABLED
wlxbcec23c36d26: AP-ENABLED

I do have one issue I am trying to figure out, at the end of the initialization it hangs and I simply open a new terminal and all is working, not sure why yet but it may be because i have not completed an actual create_ap.conf file as of yet.

I am sure I will work the kinks out in time:)

so there will be edits to this:)

but for now this is after installing:

wlxbcec23c36d26  IEEE 802.11bg  ESSID:"MyAccessPoint"  Nickname:"<WIFI@REALTEK>"
          Mode:Master  Frequency:2.412 GHz  Access Point: xx:xx:xx:xx:xx:xx   
          Bit Rate:54 Mb/s   Sensitivity:0/0  
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=79/100  Signal level=51/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

sit0      no wireless extensions.

lo        no wireless extensions.

eth0      no wireless extensions.

any input or constructive criticism on what to do is appreciated:)

Echowarrior108

device: pogoplug-pro v3

Currently running:
Debian GNU/Linux Bullseye 12-9-22
Linux 5.4.224-oxnas-tld-1 armv6l GNU/Linux 11-27-22