Hi!

 

I am having a really weird issue today with my armbian system.

 

Its default configuration is as an AP with a NGINX server running at boot so that I can connect to my board and access to a website stored locally.

 

I wanted to do some updates to the systems, so I have switched off the board, and opened the SDcard to my debian desktop system.

 

I have modified the autoconnect value of my AP nmconnection file to false and switched the one of my infrastructure mode nmconnection file to true, so that at next boot, my board connects to my local network and I can run my updates.

 

my board has never shown up in my router list.

Not a big deal, I modify back the files to get the autoconnect back on my AP file.

 

and the problem now is that the AP doesn't get created anymore.

 

does anyone have a clue of what is no longer working? Considering that those are the only modifications I have done and it was working flawlessly before.

 

you'll find below my nmconenction file

 

[connection]
id=AP
uuid=1cfa65ae-cd8b-4d19-8d18-5ca935fc9d27
type=wifi
autoconnect=true
interface-name=wlan0
permissions=

[wifi]
band=bg
mac-address-blacklist=
mode=ap
ssid=PROJECTprototype

[wifi-security]
key-mgmt=wpa-psk
psk=password

[ipv4]
dns-search=
method=shared

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto

[proxy]

 

 

thank you for your help and feedback,

 

Tibibs

2 hours ago, tibibs said:

weird issue today with my armbian system

Your issues are referring to the application called Network manager. https://www.google.com/search?q=network+manger+manual For specific version related problems look around Debian / Ubuntu manuals.

Moved to Common issues / peer to peer technical support