Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #193302 > unrolled thread

wireless fail after stretch installation

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  wireless fail after stretch installation Long Wind <longwind2@yahoo.com> - 2018-03-04 00:20 +0100
    Re: wireless fail after stretch installation Brian <ad44@cityscape.co.uk> - 2018-03-04 01:00 +0100
      Re: wireless fail after stretch installation Cindy-Sue Causey <butterflybytes@gmail.com> - 2018-03-04 01:20 +0100
      Re: wireless fail after stretch installation Long Wind <longwind2@yahoo.com> - 2018-03-04 02:40 +0100
      Re: (solved) Re: wireless fail after stretch installation Brian <ad44@cityscape.co.uk> - 2018-03-04 11:40 +0100
        Re: (solved) Re: wireless fail after stretch installation Jude DaShiell <jdashiel@panix.com> - 2018-03-04 17:00 +0100
          Re: (solved) Re: wireless fail after stretch installation Philip Hands <phil@hands.com> - 2018-03-04 19:20 +0100
            Re: (solved) Re: wireless fail after stretch installation Jude DaShiell <jdashiel@panix.com> - 2018-03-04 19:40 +0100
              Re: (solved) Re: wireless fail after stretch installation Philip Hands <phil@hands.com> - 2018-03-04 22:40 +0100
                Re: (solved) Re: wireless fail after stretch installation Brian <ad44@cityscape.co.uk> - 2018-03-05 01:10 +0100
            Re: (solved) Re: wireless fail after stretch installation Brian <ad44@cityscape.co.uk> - 2018-03-05 00:10 +0100
            Re: (solved) Re: wireless fail after stretch installation Ian Jackson <ijackson@chiark.greenend.org.uk> - 2018-03-06 16:10 +0100
              Re: (solved) Re: wireless fail after stretch installation Brian <ad44@cityscape.co.uk> - 2018-03-06 18:10 +0100
                Re: (solved) Re: wireless fail after stretch installation bw <bwtnguy@yahoo.com> - 2018-03-06 18:30 +0100
                Re: (solved) Re: wireless fail after stretch installation Ian Jackson <ijackson@chiark.greenend.org.uk> - 2018-03-06 19:40 +0100
                  Re: (solved) Re: wireless fail after stretch installation bw <bwtnguy@yahoo.com> - 2018-03-06 20:00 +0100
                  Re: (solved) Re: wireless fail after stretch installation Brian <ad44@cityscape.co.uk> - 2018-03-06 21:10 +0100
                    Re: (solved) Re: wireless fail after stretch installation bw <bwtnguy@yahoo.com> - 2018-03-06 21:30 +0100
                    Re: (solved) Re: wireless fail after stretch installation Ian Jackson <ijackson@chiark.greenend.org.uk> - 2018-03-07 14:30 +0100
                      Re: (solved) Re: wireless fail after stretch installation Jude DaShiell <jdashiel@panix.com> - 2018-03-09 04:00 +0100
                      Re: (solved) Re: wireless fail after stretch installation David Wright <deblis@lionunicorn.co.uk> - 2018-03-10 17:00 +0100
                        Re: (solved) Re: wireless fail after stretch installation Brian <ad44@cityscape.co.uk> - 2018-03-10 19:20 +0100
              Re: (solved) Re: wireless fail after stretch installation Ian Jackson <ijackson@chiark.greenend.org.uk> - 2018-03-06 19:30 +0100
                Re: (solved) Re: wireless fail after stretch installation bw <bwtnguy@yahoo.com> - 2018-03-06 19:50 +0100
                  Re: (solved) Re: wireless fail after stretch installation Charlie S <taoquester@gmail.com> - 2018-03-06 23:20 +0100
                Re: (solved) Re: wireless fail after stretch installation Brian Potkin <brian@copernicus.org.uk> - 2018-03-06 20:30 +0100
                Re: (solved) Re: wireless fail after stretch installation Ian Jackson <ijackson@chiark.greenend.org.uk> - 2018-03-07 14:30 +0100
    Re: wireless fail after stretch installation Charlie S <taoquester@gmail.com> - 2018-03-04 02:50 +0100
      Re: wireless fail after stretch installation Long Wind <longwind2@yahoo.com> - 2018-03-04 10:00 +0100

Page 2 of 2 — ← Prev page 1 [2]

#193583 — Re: (solved) Re: wireless fail after stretch installation

On Wed 07 Mar 2018 at 13:25:16 (+0000), Ian Jackson wrote:
> bw writes ("Re: (solved) Re: wireless fail after stretch installation"):
> > On Tue, 6 Mar 2018, Brian wrote:
> > > One user calls it a "sick joke". After five years and with no attempt
> > > to rectify the situation, I'm beginning to have sympathy with that view.
> 
> Debian, like all ordinary software, is full of bugs.  Many bugs
> languish unfixed for years.  This is not malice, or a "sick joke".
> It's just that there is too much to do and too few people to do it.

I'm afraid I've been misquoted. The exchange was (my lines are marked ★):

--✄--------

> How connectivity is re-established on a machine with only a wireless
> interface is left as an exercise for the user.

This is some sort of sick joke. ★

--✄--------

https://lists.debian.org/debian-user/2018/02/msg00015.html

> There are rare cases where horrible people deliberately sabotage
> things.  They are very high profile because they are so outrageous,
> but they are not the norm.  I see no evidence in relation to this bug
> that anyone is sabotaging anything.

I made no accusations of sabotage. Again:

--✄--------

> > > So this must be intentioal, wouldn't you say?
> > 
> > No. ★

[…]

> > > And this is also clearly intentional.
> > 
> > Intended to do what? ★
> 
> To leave the user without network connectivity after first boot? There
> are at least three bug reports against netcfg on the matter. My
> recollection is that no deeper intention is revealed there.

[…]

Yes, I don't think the intentions are deeper, but just that simple ★
cases have been overlooked, and overlooked for several years. ★

--✄--------

The thing that seemed odd to me when I examined the log was that the
installer removed the wireless configuration right at the last moment,
with no method of circumventing it.

On discovering the udeb package called netcfg and looking through its
bugs, it seemed that the network connection was torn down (with good
reason, to do with DHCP leases perhaps) but then the configuration
itself was also torn down, and this was considered a good thing for
reasons I couldn't fathom, and which seemed to forget the case of a
wireless interface and its intended future use of ifupdown with /e/n/i
after rebooting.

> The correct approach to this bug is to figure out how to fix it, and
> send a patch.
> 
> > Brute forcing this thing with wifi to /e/n/i might not be the best 
> > approach?  What about people who want a different config than the 
> > installer?  What about people who don;t want to be UP (auto) on bootup?  
> > What about static configs?  Wifi is by nature a mobile environment, what 
> > about security or several devices?  Let's help the devs by hashing out the 
> > pros and cons and making a coherent proposal?
> 
> We are considering the situation where the user has installed a
> barebones system, with no GUI network management tools.
> 
> Such a user will probably *expect* to edit a configuration file when
> they want to change their network configuration, whether because their
> needs change, or because their needs are different to those of the
> majority of people.
> 
> Consequently, there is no problem in principle with setting up /e/n/i
> to have the wifi configuration from the install.  That is what most
> people who do this will want; and if it doesn't suit them, they can
> change it.  (It is easier to change it or delete it, than it is to set
> it up from scratch.)

Yes, that's just what I had originally expected, and would be great.

> AFAICT from reading #694068, the reason d-i currently strips this
> information out of the installed system is because it contains the
> wifi password in /e/n/i, a world-readable file.  That would obviously
> be wrong.

The odd thing about this reasoning was that I seem to recall several
generations ago (more than ten years?) finding that /e/n/i was not
world-readable upon installation. (If this was when I was using ppp/
mgetty/CHAPS etc, it would be pre-2004. I could be misremembering here.)

> Someone should implement and test the suggestion made by Trent Buck,
> here,
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694068#47
> 
> Specifically:
> 
> |  If you don't want to udebify wpa_passphrase, you can do it by hand:
> |
> |      cat >"/etc/wpa_supplicant/wpa_supplicant-$iface.conf" <<EOF
> |      network={
> |	 ssid="$ssid"
> |	 psk="$passphrase"
> |      }
> |      EOF
> 
> This should be arranged in the appropriate bit of d-i, so that the
> installed system works the same way as the installer.

That would be a great improvement, and with least surprise.

BTW if you read right to the end of
https://lists.debian.org/debian-user/2018/02/msg00015.html
the last sentence is meant to be a reference to our
Great Leader's Orwellian press briefings.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#193587 — Re: (solved) Re: wireless fail after stretch installation

At some point Jude DaShiell Cc'ed -devel. This accounts for some of the
traffic in this thread. I am also Cc'ing -devel. You didn't, but I am
not trimming any of your post; nor am I replying to every portion in
it.


On Sat 10 Mar 2018 at 09:53:58 -0600, David Wright wrote:

> On Wed 07 Mar 2018 at 13:25:16 (+0000), Ian Jackson wrote:
> > bw writes ("Re: (solved) Re: wireless fail after stretch installation"):
> > > On Tue, 6 Mar 2018, Brian wrote:
> > > > One user calls it a "sick joke". After five years and with no attempt
> > > > to rectify the situation, I'm beginning to have sympathy with that view.
> > 
> > Debian, like all ordinary software, is full of bugs.  Many bugs
> > languish unfixed for years.  This is not malice, or a "sick joke".
> > It's just that there is too much to do and too few people to do it.
> 
> I'm afraid I've been misquoted. The exchange was (my lines are marked ★):
> 
> --✄--------
> 
> > How connectivity is re-established on a machine with only a wireless
> > interface is left as an exercise for the user.
> 
> This is some sort of sick joke. ★
> 
> --✄--------
> 
> https://lists.debian.org/debian-user/2018/02/msg00015.html

Many apologies for quoting out of context.

> > There are rare cases where horrible people deliberately sabotage
> > things.  They are very high profile because they are so outrageous,
> > but they are not the norm.  I see no evidence in relation to this bug
> > that anyone is sabotaging anything.
> 
> I made no accusations of sabotage. Again:
> 
> --✄--------
> 
> > > > So this must be intentioal, wouldn't you say?
> > > 
> > > No. ★
> 
> […]
> 
> > > > And this is also clearly intentional.
> > > 
> > > Intended to do what? ★
> > 
> > To leave the user without network connectivity after first boot? There
> > are at least three bug reports against netcfg on the matter. My
> > recollection is that no deeper intention is revealed there.
> 
> […]

The word "deliberately" was picked up and labelled as giving the message
an unfortunate tone and then linked with "deliberately breaking stuff".
A deliberate action need not be done with malice and there was nothing
in what I said which put ill-intent forward as a reason.

> Yes, I don't think the intentions are deeper, but just that simple ★
> cases have been overlooked, and overlooked for several years. ★
> 
> --✄--------
> 
> The thing that seemed odd to me when I examined the log was that the
> installer removed the wireless configuration right at the last moment,
> with no method of circumventing it.


> 
> On discovering the udeb package called netcfg and looking through its
> bugs, it seemed that the network connection was torn down (with good
> reason, to do with DHCP leases perhaps) but then the configuration
> itself was also torn down, and this was considered a good thing for
> reasons I couldn't fathom, and which seemed to forget the case of a
> wireless interface and its intended future use of ifupdown with /e/n/i
> after rebooting.
> 
> > The correct approach to this bug is to figure out how to fix it, and
> > send a patch.
> > 
> > > Brute forcing this thing with wifi to /e/n/i might not be the best 
> > > approach?  What about people who want a different config than the 
> > > installer?  What about people who don;t want to be UP (auto) on bootup?  
> > > What about static configs?  Wifi is by nature a mobile environment, what 
> > > about security or several devices?  Let's help the devs by hashing out the 
> > > pros and cons and making a coherent proposal?
> > 
> > We are considering the situation where the user has installed a
> > barebones system, with no GUI network management tools.
> > 
> > Such a user will probably *expect* to edit a configuration file when
> > they want to change their network configuration, whether because their
> > needs change, or because their needs are different to those of the
> > majority of people.
> > 
> > Consequently, there is no problem in principle with setting up /e/n/i
> > to have the wifi configuration from the install.  That is what most
> > people who do this will want; and if it doesn't suit them, they can
> > change it.  (It is easier to change it or delete it, than it is to set
> > it up from scratch.)
> 
> Yes, that's just what I had originally expected, and would be great.
> 
> > AFAICT from reading #694068, the reason d-i currently strips this
> > information out of the installed system is because it contains the
> > wifi password in /e/n/i, a world-readable file.  That would obviously
> > be wrong.
> 
> The odd thing about this reasoning was that I seem to recall several
> generations ago (more than ten years?) finding that /e/n/i was not
> world-readable upon installation. (If this was when I was using ppp/
> mgetty/CHAPS etc, it would be pre-2004. I could be misremembering here.)
> 
> > Someone should implement and test the suggestion made by Trent Buck,
> > here,
> >   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694068#47
> > 
> > Specifically:
> > 
> > |  If you don't want to udebify wpa_passphrase, you can do it by hand:
> > |
> > |      cat >"/etc/wpa_supplicant/wpa_supplicant-$iface.conf" <<EOF
> > |      network={
> > |	 ssid="$ssid"
> > |	 psk="$passphrase"
> > |      }
> > |      EOF
> > 
> > This should be arranged in the appropriate bit of d-i, so that the
> > installed system works the same way as the installer.
> 
> That would be a great improvement, and with least surprise.
> 
> BTW if you read right to the end of
> https://lists.debian.org/debian-user/2018/02/msg00015.html
> the last sentence is meant to be a reference to our
> Great Leader's Orwellian press briefings.

Trent W. Buck said in #694068:

  > This issue's history seems to be bogged down on whether
  > interfaces(5) can be mode 0600 (to hide the cleartext
  > passphrase).

As can be seen from
 
 https://lists.debian.org/debian-boot/2012/09/msg00282.html

having mode 0600 for /e/n/i was not given as a reason.

Futher on in the thread is:

 https://lists.debian.org/debian-boot/2012/09/msg00313.html

  > IIRC we decided on this default before we added the code to
  > change the access mode of /e/n/i if it contains a password.
  > The main reason for defaulting to no configuration in
  > this case was to avoid having passwords in there. If people
  > think it should default to ifupdown in this case this can be
  > changed.

Nothing about mode 0600 as a reason for the design and there was a
willingness to change the default.

You said earlier:

 > The thing that seemed odd to me when I examined the log was that the
 > installer removed the wireless configuration right at the last moment,
 > with no method of circumventing it.

That is touched on in the same -boot thread.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#193414 — Re: (solved) Re: wireless fail after stretch installation

Brian writes ("Re: (solved) Re: wireless fail after stretch installation"):
> #694068, #696755, #727740 and #777439.

Thanks.

I have read the bug logs and Trent Buck's message here
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694068#47
seems to suggest a way forward.

Perhaps someone would care to write and test a patch to d-i's network
configuration arrangements, to implement Trent's suggestion ?  I think
that the people who don't have network-manager would probably prefer
this to use ifupdown, and making a whole new udeb will be work, so
Trent's second suggestion seems sensible.

> > > The plain and simple fact is that a user who installs over a wireless
> > > link and does not have network-manager does not have any connectivity
> > > to the internet after first boot. Long Wind solved the issue by taking
> > > the advice given and Charlie S used his initiative and knowledge to
> > > devise an /e/n/i file which replaced the one the installer had wiped
> > > out.
> > > 
> > > This has been going on since Debian 7.0.0 and is not the first time the
> > > issue has arisen here. Debian must be the only OS which deliberately
> > > removes connectivity present during installation.

I have to say that the tone of this message is rather unfortunate.
You make it sound like someone is deliberately breaking stuff.  That
doesn't seem to be the case.

Comparing to other distros can be very helpful but generalised
statements that they don't have this bug is less useful than looking
into how they solve the problem.

Ian.

-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

[toc] | [prev] | [next] | [standalone]

#193418 — Re: (solved) Re: wireless fail after stretch installation

On Tue, 6 Mar 2018, Ian Jackson wrote:

> Brian writes ("Re: (solved) Re: wireless fail after stretch installation"):
> > #694068, #696755, #727740 and #777439.
> 
> Thanks.
> 
> I have read the bug logs and Trent Buck's message here
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694068#47
> seems to suggest a way forward.
> 
> Perhaps someone would care to write and test a patch to d-i's network
> configuration arrangements, to implement Trent's suggestion ?  I think
> that the people who don't have network-manager would probably prefer
> this to use ifupdown, and making a whole new udeb will be work, so
> Trent's second suggestion seems sensible.
> 

Second suggestion being networkd preferred over ifupdown?  yeah, I had 
thought this was going to come up eventually.  State it in plain english, 
if ifupdown is to be replaced, then let's get on with it.

> > > > The plain and simple fact is that a user who installs over a wireless
> > > > link and does not have network-manager does not have any connectivity
> > > > to the internet after first boot. Long Wind solved the issue by taking
> > > > the advice given and Charlie S used his initiative and knowledge to
> > > > devise an /e/n/i file which replaced the one the installer had wiped
> > > > out.
> > > > 
> > > > This has been going on since Debian 7.0.0 and is not the first time the
> > > > issue has arisen here. Debian must be the only OS which deliberately
> > > > removes connectivity present during installation.
> 
> I have to say that the tone of this message is rather unfortunate.
> You make it sound like someone is deliberately breaking stuff.  That
> doesn't seem to be the case.
> 
> Comparing to other distros can be very helpful but generalised
> statements that they don't have this bug is less useful than looking
> into how they solve the problem.
> 
> Ian.
> 
> -- 
> Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.
> 
> If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
> a private address which bypasses my fierce spamfilter.
> 
> 

I think the whole thread is unfortunate, because it was started by a 
person (Long Wind) who earlier posted a request for help about how to hack 
into their neighbor's wireless network to steal internet service.

I'm really shocked that anybody would try and make wireless easier to use 
for thieves.  They should be shunned, not used as example clueless users 
to implement fixes or new features.

Sorry to get personal, and apologies for being blunt if I offended.

bw

[toc] | [prev] | [next] | [standalone]

#193433 — Re: (solved) Re: wireless fail after stretch installation

On Tue, 6 Mar 2018 13:46:24 -0500 (EST) bw sent:

> On Tue, 6 Mar 2018, Ian Jackson wrote:
> 
> > Brian writes ("Re: (solved) Re: wireless fail after stretch
> > installation"):  
> > > #694068, #696755, #727740 and #777439.  
> > 
> > Thanks.
> > 
> > I have read the bug logs and Trent Buck's message here
> >   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694068#47
> > seems to suggest a way forward.
> > 
> > Perhaps someone would care to write and test a patch to d-i's
> > network configuration arrangements, to implement Trent's
> > suggestion ?  I think that the people who don't have
> > network-manager would probably prefer this to use ifupdown, and
> > making a whole new udeb will be work, so Trent's second suggestion
> > seems sensible. 
> 
> Second suggestion being networkd preferred over ifupdown?  yeah, I
> had thought this was going to come up eventually.  State it in plain
> english, if ifupdown is to be replaced, then let's get on with it.
> 
<snip>

Let's not get rid of ifupdown or that way to bring the connection, wifi
or otherwise, up or down.

[disclaimer] Ifup/down is a personal preference [end disclaimer]

I do not do a "guided" or automagic install. Though I dislike the term,
because I am not, I used the expert install. So the following may be a
stupid suggestion.

The root of the problem appears to be: for someone who has installed
Debian on more machines, through a wifi connection and wants to
continue using that connection type, will know that the actual
connection requirement used by the installer is removed. No surprise.

Then write the /etc/network/interfaces file as required if that's the
way they wish to connect [ifup/down].

Maybe that should just be documented [exampled choices] in the
installer for anyone who doesn't install a Debian O/S all that often or
only once?

Never having used network manager or similar am not certain how they
work. However, the documentation during install at the appropriate time
could read something like: if you wish to continue using a wifi
connection after reboot, please edit /etc/network/interfaces [give an
example] or install network manager or whatever helper to do this?

Just a thought
Charlie

[toc] | [prev] | [next] | [standalone]

#193422 — Re: (solved) Re: wireless fail after stretch installation

On Tue 06 Mar 2018 at 18:27:29 +0000, Ian Jackson wrote:

> Brian writes ("Re: (solved) Re: wireless fail after stretch installation"):
> > #694068, #696755, #727740 and #777439.
> 
> Thanks.
> 
> I have read the bug logs and Trent Buck's message here
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694068#47
> seems to suggest a way forward.
> 
> Perhaps someone would care to write and test a patch to d-i's network
> configuration arrangements, to implement Trent's suggestion ?  I think
> that the people who don't have network-manager would probably prefer
> this to use ifupdown, and making a whole new udeb will be work, so
> Trent's second suggestion seems sensible.

I would hazard a guess and say that 100% of users would expect to be
able to use the network they have set up during installation, afterwards.
Without an ethernet interface on the machine it becomes resorting to
setting it up again (5%), resorting to -user or the internet from
another machine (20%) or some head-scratching followed by walking away.
(The percentages are rough estimates).
 
> > > > The plain and simple fact is that a user who installs over a wireless
> > > > link and does not have network-manager does not have any connectivity
> > > > to the internet after first boot. Long Wind solved the issue by taking
> > > > the advice given and Charlie S used his initiative and knowledge to
> > > > devise an /e/n/i file which replaced the one the installer had wiped
> > > > out.
> > > > 
> > > > This has been going on since Debian 7.0.0 and is not the first time the
> > > > issue has arisen here. Debian must be the only OS which deliberately
> > > > removes connectivity present during installation.
> 
> I have to say that the tone of this message is rather unfortunate.
> You make it sound like someone is deliberately breaking stuff.  That
> doesn't seem to be the case.

The message was written to -user. Besides having a really helpful bunch
of users, there can sometimes be a robustness and directness to the
exchanges. Don't let it put you off if you are used to a more gentile
environment.

I hadn't realised the breakage was accidental and unplanned. OTOH, I am
not in possession of the reasons behind it; apart from some conjecture,
they still remain unknown. As you will see from the bug record, even
Debian developers are mystified.

> Comparing to other distros can be very helpful but generalised
> statements that they don't have this bug is less useful than looking
> into how they solve the problem.

We don't know what the problem is.

-- 
Brian.

[toc] | [prev] | [next] | [standalone]

#193463 — Re: (solved) Re: wireless fail after stretch installation

bw writes ("Re: (solved) Re: wireless fail after stretch installation"):
> On Tue, 6 Mar 2018, Ian Jackson wrote:
> > I have read the bug logs and Trent Buck's message here
> >   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694068#47
> > seems to suggest a way forward.
> > 
> > Perhaps someone would care to write and test a patch to d-i's network
> > configuration arrangements, to implement Trent's suggestion ?  I think
> > that the people who don't have network-manager would probably prefer
> > this to use ifupdown, and making a whole new udeb will be work, so
> > Trent's second suggestion seems sensible.
> 
> Second suggestion being networkd preferred over ifupdown?  yeah, I had 
> thought this was going to come up eventually.  State it in plain english, 
> if ifupdown is to be replaced, then let's get on with it.

I appreciate that you have reason for your paranoia, but in this case
it is entirely misplaced.  You have misunderstood me.  I meant this
part of Trent's suggestion:

|  If you don't want to udebify wpa_passphrase, you can do it by hand:
|
|      cat >"/etc/wpa_supplicant/wpa_supplicant-$iface.conf" <<EOF
|      network={
|	 ssid="$ssid"
|	 psk="$passphrase"
|      }
|      EOF

which is part of a suggestion of how to configure ifupdown in the
installed system.

> I think the whole thread is unfortunate, because it was started by a 
> person (Long Wind) who earlier posted a request for help about how to hack 
> into their neighbor's wireless network to steal internet service.

"Whatever".  Now, this thread is about Bug#694068.  Which is annoying
a number of people and should be fixed.

> I'm really shocked that anybody would try and make wireless easier to use 
> for thieves.  They should be shunned, not used as example clueless users 
> to implement fixes or new features.

I struggle to see how fixing #694068 is about helping "thieves".

Ian.

-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

[toc] | [prev] | [next] | [standalone]

#193306

On Sat, 3 Mar 2018 23:17:07 +0000 (UTC) Long Wind sent:

> i've just installed stretchi've config wireless during
> installationand it work during installation but after i boot into
> stretch, wireless doesn't worki didn't install network manager during
> installation how can i get wireless to work now?Thanks!


	After contemplation, my reply is:

I have just installed Stretch on a laptop, used the net install image
and used the wireless connection instead of the Ethernet.

It left me with a very bare bones /etc/network/interfaces which was to
be expected, having run into this before:

# This file describes the network interfaces available on your system #
and how to activate them. For more information, see interfaces(5).

Source /etc/network/interfaces.d/*

# The loopback network interface auto lo iface lo inet loopback 


That was all, I had to enter:

# The primary network interface
# allow-hotplug eth0
iface enp5s0 inet dhcp

# The primary network interface
# allow-hotplug wlan0 
iface wlp6s0 inet dhcp 
wpa-ssid xxxxx 
wpa-psk xxxxxxxx

I don't allow hotplugging of anything, for various reasons, needing no
explanation here.

I used the "eth0" and "wlan0" for old times sake. [laughing]

Then used;

ifup wlp6s0

in a terminal, which is the way I always bring up the internet.

Hope that helps, though it might be a bit primitive.

Charlie

[toc] | [prev] | [next] | [standalone]

#193307

[Multipart message — attachments visible in raw view] — view raw

Thank Charlie!
i plan to change wireless setting.your example can be helpful!
 

    On Saturday, March 3, 2018 8:42 PM, Charlie S <taoquester@gmail.com> wrote:
 

 On Sat, 3 Mar 2018 23:17:07 +0000 (UTC) Long Wind sent:

> i've just installed stretchi've config wireless during
> installationand it work during installation but after i boot into
> stretch, wireless doesn't worki didn't install network manager during
> installation how can i get wireless to work now?Thanks!


    After contemplation, my reply is:

I have just installed Stretch on a laptop, used the net install image
and used the wireless connection instead of the Ethernet.

It left me with a very bare bones /etc/network/interfaces which was to
be expected, having run into this before:

# This file describes the network interfaces available on your system #
and how to activate them. For more information, see interfaces(5).

Source /etc/network/interfaces.d/*

# The loopback network interface auto lo iface lo inet loopback 


That was all, I had to enter:

# The primary network interface
# allow-hotplug eth0
iface enp5s0 inet dhcp

# The primary network interface
# allow-hotplug wlan0 
iface wlp6s0 inet dhcp 
wpa-ssid xxxxx 
wpa-psk xxxxxxxx

I don't allow hotplugging of anything, for various reasons, needing no
explanation here.

I used the "eth0" and "wlan0" for old times sake. [laughing]

Then used;

ifup wlp6s0

in a terminal, which is the way I always bring up the internet.

Hope that helps, though it might be a bit primitive.

Charlie



   

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web