Integrate wifi access point

[cyberorg]

Keeping MSS simple is one of the most important feature, hence we will not be integrating anything that can be done more efficiently by external devices/services. No modifications are needed on MSS to make use of external wifi router's capabilities to serve content>

Any wifi routers https://www.google.com/search?q=buy+wifi+router+india has web based GUI for configuration, are cheap, easy to extend as per number of connections required and easy to maintain.

[cyberorg]

A very basic wifi access point on hardwares that support AP mode will be set up, this feature is also too complicated to implement on MSS, just not worth all the effort when the same and more is easily achieved using cheap external AP. For more complicated AP with authentication etc. use add-on AP hardware.

[cyberorg]

mssupdate install.server.ip mssap

Will set up very basic wifi accesspoint with no password. For more complex setup see "create_ap --help" and modify /usr/bin/mssap script accordingly.

mssap script provides basic management: stop, enable, disable, unmanage

Network is not manageable by NetworkManager while AP mode is on, so to switch static/dynamic or modify it run "mssap stop"

enable and disable options for service start during boot.

Sometimes "mssap stop" does not release the devices it is managing, to let NetworkManager manage it again run "mssap unmanage"

[cyberorg]

Needs hostapd and haveged installed, which is not available on older MSS.

apt update && apt install hostapd haveged

We also need one updated script

cd /usr/bin/ rm networkvariables.sh wget installserverip/mss/networkvariables.sh && chmod +x networkvariables.sh

[intelliant01]

Needs hostapd and haveged installed

apt update && apt install hostapd haveged

@cyberorg Guess this is only needed on older nuc mss installs.

And thereafter when I domssupdate <install_server_ip> mssap I am getting this error -

$ sudo mssupdate 192.168.2.30 mssap
[sudo] password for mssadmin: 
--2017-06-27 18:45:59--  http://192.168.2.30/mss/mssap
Connecting to 192.168.2.30:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 91
Saving to: ‘mssap’

mssap               100%[===================>]      91  --.-KB/s    in 0s      

2017-06-27 18:45:59 (6.81 MB/s) - ‘mssap’ saved [91/91]

--2017-06-27 18:45:59--  http://192.168.2.30/mss/mssap.tar.xz
Connecting to 192.168.2.30:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14656 (14K) [application/x-xz]
Saving to: ‘mssap.tar.xz’

mssap.tar.xz        100%[===================>]  14.31K  --.-KB/s    in 0s      

2017-06-27 18:45:59 (130 MB/s) - ‘mssap.tar.xz’ saved [14656/14656]

etc/
etc/create_ap.conf
usr/
usr/bin/
usr/bin/create_ap
usr/bin/mssap
usr/lib/
usr/lib/systemd/
usr/lib/systemd/system/
usr/lib/systemd/system/mssap.service
usr/share/
usr/share/bash-completion/
usr/share/bash-completion/completions/
usr/share/bash-completion/completions/create_ap
grep: wlp2s0: No such file or directory
something went wrong

[intelliant01]

@cyberorg Found the reason of the above error. The wifi adapter should not be connected in client mode when attempting the install.

[intelliant01]

This issue was moved to RechercheTech/mss#18