Re: WiFi without Network Manager

2019-02-15 Thread didier gaumet
Hello,

- As a GUI alternative to NetworkManager; Wicd has been mentionned, but
there is also Connman
- the GUI part of NetworkManager (the gnome applet:
network-manager-gnome) is not mandatory: there are TUI (nmtui) and CLI
(nmcli) interfaces included in the NetworkManager base package
(network-manager)
- In my opinion, it would probably be simpler to use only NetworkManager
than NetworkManager and /etc/interfaces in your use case



Re: WiFi without Network Manager

2019-02-14 Thread Kenneth Parker
On Thu, Feb 14, 2019 at 10:54 PM mett  wrote:

> On 2019年2月15日 8:23:04 JST, Kenneth Parker  wrote:
>>
>> On Tue, Feb 12, 2019 at 9:30 AM  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 
>>>
>>> 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
>>
>
> sudo iwlist wlan0 scan
>

Many Thanks.  Just what I needed!

 >
>

And thanks for the link.  If they're still in business, they are worth my
Subscription!

Kenneth Parker


Re: WiFi without Network Manager

2019-02-14 Thread mett
On 2019年2月15日 8:23:04 JST, Kenneth Parker  wrote:
>On Tue, Feb 12, 2019 at 9:30 AM  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 
>>
>> 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

sudo iwlist wlan0 scan



Re: WiFi without Network Manager

2019-02-14 Thread Kenneth Parker
On Tue, Feb 12, 2019 at 9:30 AM  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 
>
> 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


Re: WiFi without Network Manager

2019-02-13 Thread Ric Moore

On 2/13/19 9:14 AM, John Hasler wrote:
s better not to post "Thanks" to a busy mailing list.  If you must do

so please put "Thanks" in the subject line.


OR "solved", which is much more useful for the next guy. No need for 
"thanks" as "solved" is the ultimate goal for posterity. It's what I 
look for in a google search to click on. Ric




Re: WiFi without Network Manager

2019-02-13 Thread John Hasler
 deb wrote:
> note: this is why I think top-posting is best.  People don't have to
> scroll through tons of crap to get to "Thanks" :-)

When I open a message on a mailing list or newsgroup and see nothing but
quoted text I usually just move on to the next message.  On the other
hand I find top-posted responses that remain cryptic until I've scrolled
through a hundred lines of mostly-irrelevant quoted text a bit
irritating too.

It's better not to post "Thanks" to a busy mailing list.  If you must do
so please put "Thanks" in the subject line.

rhkramer writes:
> I vary the use of top-posting and "bottom"-posting depending on
> circumstances.
> ...
> On lists that prefer "bottom"-posting, I try to ususally comply, with
> exceptions.

> In either case, I advocate quite extensive eliding of irrelevant parts
> of a post.

I elide as required and interleave my response.  I recall only one
instance of someone objecting (on Usenet many years ago.)
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA



Re: WiFi without Network Manager

2019-02-13 Thread mick crane

On 2019-02-13 13:32, deb wrote:

note: this is why I think top-posting is best.

People don't have to scroll through tons of crap to get to "Thanks" :-)



A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

--
Key ID4BFEBB31



Re: WiFi without Network Manager

2019-02-13 Thread rhkramer
On Wednesday, February 13, 2019 08:32:22 AM deb wrote:
> note: this is why I think top-posting is best.
> 
> People don't have to scroll through tons of crap to get to "Thanks" :-)

I vary the use of top-posting and "bottom"-posting depending on circumstances.

For thanks and similar, top posting works very well.  In dealing with some 
other groups or "types" of people, top-posting works well (because, in many 
cases, it is what they expect or are used to).

On lists that prefer "bottom"-posting, I try to ususally comply, with 
exceptions.

In either case, I advocate quite extensive eliding of irrelevant parts of a 
post.



Re: WiFi without Network Manager

2019-02-13 Thread deb

note: this is why I think top-posting is best.

People don't have to scroll through tons of crap to get to "Thanks" :-)


On 2/12/2019 3:07 PM, ghe wrote:

On 2/12/19 9:15 AM, deb wrote:


Glenn, thanks for this!

More than welcome.

For your amazement, here's the comcastRoutes.sh from my laptop, running
Buster. This is run just after the WiFi interface has been brought up
and Comcast has scribbled all over my IP files. It looks like maybe I'm
removing the default the twice on the WiFi...

#! /bin/bash

echo 'Adding Comcast routes'
route del default
route add default gw 

# Debian mirrors:
# picosecond
route add -host 184.105.204.138 gw 10.0.0.1 wlan0
# U-CHICAGO
route add -host 128.135.10.29 gw 10.0.0.1 wlan0
# MIT
route add -host 128.30.2.26 gw 10.0.0.1 wlan0
# Georgia Tech
route add -host 128.61.240.89 gw 10.0.0.1 wlan0
# Wikimedia
route add -host 208.80.154.15 gw 10.0.0.1 wlan0

route del default wlan0
route del -net 10.0.0.0 netmask 255.255.255.0

cp -a /etc/resolv.conf.sls /etc/resolv.conf



Thank you!

I'll give that a crack!





Re: WiFi without Network Manager

2019-02-12 Thread ghe
On 2/12/19 9:15 AM, deb wrote:

> Glenn, thanks for this!

More than welcome.

For your amazement, here's the comcastRoutes.sh from my laptop, running
Buster. This is run just after the WiFi interface has been brought up
and Comcast has scribbled all over my IP files. It looks like maybe I'm
removing the default the twice on the WiFi...

#! /bin/bash

echo 'Adding Comcast routes'
route del default
route add default gw 

# Debian mirrors:
# picosecond
route add -host 184.105.204.138 gw 10.0.0.1 wlan0
# U-CHICAGO
route add -host 128.135.10.29 gw 10.0.0.1 wlan0
# MIT
route add -host 128.30.2.26 gw 10.0.0.1 wlan0
# Georgia Tech
route add -host 128.61.240.89 gw 10.0.0.1 wlan0
# Wikimedia
route add -host 208.80.154.15 gw 10.0.0.1 wlan0

route del default wlan0
route del -net 10.0.0.0 netmask 255.255.255.0

cp -a /etc/resolv.conf.sls /etc/resolv.conf

-- 
Glenn English



Re: WiFi without Network Manager

2019-02-12 Thread Kenneth Parker
On Tue, Feb 12, 2019, 1:42 PM Eduardo M KALINOWSKI <
edua...@kalinowski.com.br wrote:

> On ter, 12 fev 2019, Kenneth Parker wrote:
> > What gives you the list of potential WiFi hosts, to choose from?  (These
> > LAN Parties may be at a Coffee House I haven't been to before).
> >
> > That's what I meant by "Interactive".
>
> So you want something that does exactly what NetworkManager does, but
> is not NetworkManager?
>
> There's wicd, which is similar. I don't know of any others.
>

NetworkManager does what I want, but is too much of a Control Freak (even
approaching Autocratic).  I don't have much experience with wicd, but have
heard good things about it.

>
Perhaps I should check out the Source for nm and wicd:  That should give me
the "how", and Code Samples.

-- 
> Eduardo M KALINOWSKI
> edua...@kalinowski.com.br


Thanks!

Kenneth Parker


Re: WiFi without Network Manager

2019-02-12 Thread Eduardo M KALINOWSKI

On ter, 12 fev 2019, Kenneth Parker wrote:

What gives you the list of potential WiFi hosts, to choose from?  (These
LAN Parties may be at a Coffee House I haven't been to before).

That's what I meant by "Interactive".


So you want something that does exactly what NetworkManager does, but  
is not NetworkManager?


There's wicd, which is similar. I don't know of any others.
--
Eduardo M KALINOWSKI
edua...@kalinowski.com.br




Re: WiFi without Network Manager

2019-02-12 Thread Kenneth Parker
On Tue, Feb 12, 2019, 9:59 AM  On Tue, Feb 12, 2019 at 09:44:47AM -0500, Kenneth Parker wrote:
> > On Tue, Feb 12, 2019, 9:30 AM  >
> > > 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".
>
> [...]
>
> > > Of course it relies on wpasupplicant and dhclient to do the actual
> > > magic behind the scenes.
> > >
> >
> > Which part is "interactive", asking me for WiFi and Password?
> > Wpasupplicant?  Thanks!
>
> There's no interactive part. I just invoke "sudo ifup wlan0" on console
> (this is because I have neither "auto wlan0" nor "allow-hotplug wlan0"
> on my /etc/network/interfaces: I actually want to decide whether to
> wlan or not) -- and seconds later I have a connection. That's all.
>

What gives you the list of potential WiFi hosts, to choose from?  (These
LAN Parties may be at a Coffee House I haven't been to before).

That's what I meant by "Interactive".

>
> Cheers
> -- t
>

Thanks!Kenneth Parker

>


Glenn -> Re: WiFi without Network Manager

2019-02-12 Thread deb



On 2/12/2019 9:46 AM, ghe wrote:

comcastRoutes.sh is a shell script that fixes the routing table and
resolv.conf to



Glenn, thanks for this!

Is there much to comcastRoutes.sh and resolv.conf that would require 
scrubbing so that you might be able to share these?


(I'm on comcast as well; and I want to set this up too.)

Thanks

(still installing 9.7 ...)





Re: WiFi without Network Manager

2019-02-12 Thread tomas
On Tue, Feb 12, 2019 at 09:44:47AM -0500, Kenneth Parker wrote:
> On Tue, Feb 12, 2019, 9:30 AM  
> > 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".

[...]

> > Of course it relies on wpasupplicant and dhclient to do the actual
> > magic behind the scenes.
> >
> 
> Which part is "interactive", asking me for WiFi and Password?
> Wpasupplicant?  Thanks!

There's no interactive part. I just invoke "sudo ifup wlan0" on console
(this is because I have neither "auto wlan0" nor "allow-hotplug wlan0"
on my /etc/network/interfaces: I actually want to decide whether to
wlan or not) -- and seconds later I have a connection. That's all.

Cheers
-- t


signature.asc
Description: Digital signature


Re: WiFi without Network Manager

2019-02-12 Thread ghe
On 2/12/19 7:10 AM, Kenneth Parker wrote:

> 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).

How about (a non-auto entry from my interfaces file):

# wlan0 -- Get DHCP from Comcast and tidy up a bit
iface wlan0 inet dhcp
wpa-ssid 
wpa-psk 
post-up /etc/sls/comcastRoutes.sh

comcastRoutes.sh is a shell script that fixes the routing table and
resolv.conf to set the default and DNS back to non-comcast IPs and to
enter some routes -- I use this for big downloads from the mirrors, etc.

"ifup wlan0" or "ifconfig wlan0 up" bring it up. And they don't turn off
my T1 Ethernet connection.

-- 
Glenn English



Re: WiFi without Network Manager

2019-02-12 Thread Kenneth Parker
On Tue, Feb 12, 2019, 9:30 AM  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 
>
> 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.
>

Which part is "interactive", asking me for WiFi and Password?
Wpasupplicant?  Thanks!

>
> Enjoy simple life :-)
>
> Cheers
> -- t
>

Indeed.  Debian Always!

Kenneth Parker   (eyeblinkuniverse.com)


Re: WiFi without Network Manager

2019-02-12 Thread tomas
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 

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.

Enjoy simple life :-)

Cheers
-- t


signature.asc
Description: Digital signature


WiFi without Network Manager

2019-02-12 Thread Kenneth Parker
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).

Thank you!

Kenneth Parker (eyeblinkuniverse.com)