On Tue, Feb 12, 2019 at 9:30 AM <to...@tuxteam.de> wrote: > On Tue, Feb 12, 2019 at 09:10:08AM -0500, Kenneth Parker wrote: > > I occasionally run, what I will describe as "Coffee House Lan Parties". > > That means I connect to the Internet via WiFi, and then supply a "Local > > Ethernet" network (with ipv4), for others to connect with. > > > > Doing this with Network Manager "worked", but only with "loud > complaining" > > by Network Manager. > > > > What I want now, are the "steps" that Network Manager takes, to bring up > > WiFi, so I can create an "in-demand" Root-level Script that I can run, > for > > the WiFi part. (The rest works fine, using /etc/network/interfaces). > > Actually ifupdown is perfectly capable of doing the work (well, it just > orchestrates it, but it commes with all the necessary scripts for that). > > Here's my stanza in /etc/network/interfaces (passphrase somewhat decorated, > to protect the innocent): > > iface wlan0 inet dhcp > wpa-ssid dubcek > wpa-psk XXXXXXXXXXXXXXXX > > That's all it is needed for ifup to set up wlan0, go out with DHCP and > fetch an IP address from our local DHCP server. > > Of course it relies on wpasupplicant and dhclient to do the actual > magic behind the scenes. >
What did you have to do, the first time? When you were determining the Network Name (wpa-ssid)? (Having to know everything in advance isn't too cool, when you visit multiple Coffee Houses. And connecting to the wrong ssid could get you into some *SERIOUS* trouble!) I am doing my own investigation, by the way, finding general information on a "competing" Distro (Arch): https://wiki.archlinux.org/index.php/WPA_supplicant This site suggests that wpa_cli gives useful information, so I will see what that looks like, and then use your interfaces method. Enjoy simple life :-) > > Cheers > -- t > Thanks! Kenneth Parker
