LRiedel

OK, cool, so does this make sense then? I'd really hate to screwing it up and having to flash the system again # Wired adapter #1 allow-hotplug eth0 no-auto-down eth0 iface eth0 inet dhcp #address 192.168.0.100 #netmask 255.255.255.0 #gateway 192.168.0.1 #dns-nameservers 8.8.8.8 8.8.4.4 # hwaddress ether # if you want to set MAC manually # pre-up /sbin/ifconfig eth0 mtu 3838 # setting MTU for DHCP, static just: mtu 3838 # Wireless adapter #1 # Armbian ships with network-manager installed by default. To save you time # and hassles consider using 'sudo nmtui' instead of configuring Wi-Fi settings # manually. The below lines are only meant as an example how configuration could # be done in an anachronistic way: # allow-hotplug wlan0 iface wlan0 inet dhcp address 192.168.0.100 netmask 255.255.255.0 gateway 192.168.0.1 dns-nameservers 8.8.8.8 8.8.4.4 # wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf #wireless-mode Managed #wireless-power off # Local loopback auto lo iface lo inet loopback I basically uncommented the whole DHCP stuff... There's also interfaces.hostapd, which looks like this: auto lo br0 iface lo inet loopback auto eth0 iface eth0 inet manual auto wlan0 iface wlan0 inet manual iface br0 inet dhcp bridge_ports eth0 wlan0 #hwaddress ether # will be added at first boot It seems to me that this is the file which is used by armbian-config for the HOTSPOT option. So could it be that instead of "iface wlan0 inet manual" I should set this line to "iface wlan0 inet dhcp" and add the parameters like in the "interfaces" file?

Ah, ok, I guess I would have to do the manual setup then, since the bridged option didn't work either (I mostly tried the NAT option before). Also - as far as I understand - it should be used when I'm simultaneously connected to another network over ethernet, which is not the case. There's a bunch of different interfaces.* files. Which one am i supposed to edit? root@nanopiair:/etc/network# ll total 68 drwxr-xr-x 7 root root 4096 Apr 25 12:33 ./ drwxr-xr-x 97 root root 4096 Apr 25 12:33 ../ drwxr-xr-x 2 root root 4096 Apr 20 13:01 if-down.d/ drwxr-xr-x 2 root root 4096 Apr 25 11:17 if-post-down.d/ drwxr-xr-x 2 root root 4096 Apr 25 11:17 if-pre-up.d/ drwxr-xr-x 2 root root 4096 Apr 20 13:04 if-up.d/ -rw-r--r-- 1 root root 992 Apr 25 12:45 interfaces -rw-r--r-- 1 root root 525 Apr 25 02:24 interfaces.bonding drwxr-xr-x 2 root root 4096 Jan 24 2016 interfaces.d/ -rw-r--r-- 1 root root 992 Apr 25 12:28 interfaces.debian-config.backup -rw-r--r-- 1 root root 992 Apr 25 02:24 interfaces.default -rw-r--r-- 1 root root 197 Apr 25 02:24 interfaces.hostapd -rw-r--r-- 1 root root 182 Apr 25 02:24 interfaces.network-manager -rw-r--r-- 1 root root 173 Apr 25 12:33 interfaces.out.tmp -rw-r--r-- 1 root root 495 Apr 25 02:24 interfaces.r1 -rw-r--r-- 1 root root 610 Apr 25 02:24 interfaces.r1router -rw-r--r-- 1 root root 359 Apr 25 02:24 interfaces.r1switch

No no, i want to use either the wireless connection or the access point, i.e. be able to switch between them. As I said, the AP configuration from armbian-config didn't work, I can see the network, the password is accepted too, but it just keeps connecting forever. Linux nanopiair 3.4.113-sun8i #4 SMP PREEMPT Tue Apr 25 02:57:36 CEST 2017 armv7l armv7l armv7l GNU/Linux

Just FYI, I just switched to daily build, et voilá, there now is a new /etc/hostapd.conf file. So I tried the armbian-config HOTSPOT option again, again with the same results, i.e. the whole wifi functional dying on me. Pretty neat that I always can restore the whole system from an SD card. A couple of questions still: 1. Are the Debian-micro-home-server tools also going to fully support the Ubuntu version? 2. I started it ("softie", right?) and there's no ACCESS POINT option to be found there. Am I missing something? PS: Sorry for nagging, I just really want Armbian to work, because the FriedlyArm Linux is totally not an option

That sounds pretty great! Since I'm pretty much a self taught linux newbie (obviously), I was wondering how to "switch to daily builds". Could you elaborate on that? (pretty much off topic, isn't it?) And when do you think you would manage to finish such a script? We kinda have a whole project going that strongly depends on the access point functionality. Again, thank you guys for the already awesome support (especially compared to the FriendlyArm folks). BTW, I tried out the "HOTSPOT" option in the armbian-config, with same results. Well, actually, much worse results, since it kinda breaks the normal WiFi-connection mode, so after using the HOSTSPOT option I can't connect/see any other WiFi networks.

Hello Armbian community! First time poster here As everyone in this thread, I have a Nanopi NEO Air and I recently switched from the (kinda horrible) FriendlyArm Linux to the beautiful Armbian. Yet one thing in the FriendlyArm Linux was kinda great: the ` turn-wifi-into-apmode yes/no` script. Something like this is missing in the Armbian unfortunately. I tried out the scripts FergusL posted here, and I also encountered several problems: 1. /var/run/NetworkManager/dnsmasq.pid and /run/dnsmasq.br0.pid seem to be missing in my version for some reason 2. the hostapd.conf was missing, so I've stolen the file from the FriendlyArm distro, assuming it should be the same 3. Like StuxNet, I can see the access point but cannot connect to it. Your help would be amazingly appreciated PS: Here's my hostapd.conf hw_mode=g channel=1 driver=nl80211 ssid=nanopi-wifiap interface=wlan0 # possible MAC address restriction #macaddr_acl=0 #accept_mac_file=/etc/hostapd.accept #deny_mac_file=/etc/hostapd.deny #ieee8021x=1 # Use 802.1X authentication # encryption wpa=2 wpa_passphrase=123456789 wpa_key_mgmt=WPA-PSK wpa_pairwise=TKIP CCMP rsn_pairwise=CCMP ctrl_interface=/var/run/hostapd # Only root can configure hostapd ctrl_interface_group=0