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

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

Re: WiFi interface unexpected response

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

  Re: WiFi interface unexpected response "zetam.imap" <zetam@insiberia.net> - 2019-08-06 23:20 +0200
    Re: WiFi interface unexpected response Andrei POPESCU <andreimpopescu@gmail.com> - 2019-08-07 08:50 +0200
      Re: WiFi interface unexpected response Patrick Bartek <nemommxiv@gmail.com> - 2019-08-07 19:40 +0200
      Re: WiFi interface unexpected response "zetam.imap" <zetam@insiberia.net> - 2019-08-08 04:00 +0200

#212339 — Re: WiFi interface unexpected response

[ The prior reply was only sent tu user account. Sorry ]

El 6/8/19 a las 03:16, Andrei POPESCU escribió:
> On Ma, 06 aug 19, 01:34:43, zetam.imap wrote:
> network and broadcast are not necessary. 

done

> Why do you need this if you configure wpa in /etc/network/interfaces?

Normally the wireless interface is activated when a user accesses their
account on the graphical interface.
This host has to perform unattended tasks on that network even if no
user is logged in.

> Try switching wlp3s0 from auto to allow-hotplug.

I've switched to allow-hotplug, however this modification didn't work,
things remains the same.

Thank you for your reply
Greetings

[toc] | [next] | [standalone]

#212348

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

On Ma, 06 aug 19, 18:13:02, zetam.imap wrote:
> 
> > Why do you need this if you configure wpa in /etc/network/interfaces?
> 
> Normally the wireless interface is activated when a user accesses their
> account on the graphical interface.
> This host has to perform unattended tasks on that network even if no
> user is logged in.

Let me rephrase that: why do you need *both* /etc/network/interfaces and 
wpa_supplicant.conf?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#212380

On Wed, 7 Aug 2019 09:48:03 +0300
Andrei POPESCU <andreimpopescu@gmail.com> wrote:

> On Ma, 06 aug 19, 18:13:02, zetam.imap wrote:
> >   
> > > Why do you need this if you configure wpa in /etc/network/interfaces?  
> > 
> > Normally the wireless interface is activated when a user accesses their
> > account on the graphical interface.
> > This host has to perform unattended tasks on that network even if no
> > user is logged in.  
> 
> Let me rephrase that: why do you need *both* /etc/network/interfaces and 
> wpa_supplicant.conf?

I wondered this, too.  But every doc, wiki or article I read about
manually setting up wireless with encryption said that's the way you
do it.  However, just to find out, I commented out the network stanza
for my USB wireless dongle in wpa_supplicant.conf, and rebooted.
Wireless works fine just with the basic info
from /etc/network/interfaces. Only thing left not commented out in
wpa_supplicant.conf is the config to enable wpa_cli, which doesn't run
by default.

FWIW: My system, a box under the desk, not a laptop, is very basic with
an atypical install of Stretch -- window manager only, sysvinit, no
wired Ethernet -- built part by part from a terminal-only install. Boots
to terminal, login there, then startx to bring up GUI.

B

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

#212395

El 7/8/19 a las 03:48, Andrei POPESCU escribió:
> Let me rephrase that: why do you need *both* /etc/network/interfaces and
> wpa_supplicant.conf?
>
> Kind regards,
> Andrei

Thank you Andrei. Your insights driven me to solve the blob. By reading
no haste and at the right place, I can understand it. Everything was
there https://wiki.debian.org/WiFi/HowToUse

However, Patrick's quote make sense too. If you ggle out you will find a
lot of tuts teaching the configuration of both tools at the same time.
Of course keyword was wpa_ssid ;)

Finally I left empty wpa_supplicant.conf file, reboot et... voilà thinks
work fine now!

The curious detail was to verify wpa_supplicant was not running I got a
funny surprise.

  root@:~ # ps ax | grep supp
     696 ?        Ss     0:00 /sbin/wpa_supplicant -s -B -P
/run/wpa_supplicant.wlp3s0.pid -i wlp3s0 -D nl80211,wext -C
/run/wpa_supplicant

Thank you guys

[toc] | [prev] | [standalone]

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

csiph-web