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

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

problem with wifi

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

  problem with wifi Long Wind <longwind2@yahoo.com> - 2021-01-17 21:20 +0100
    Re: problem with wifi David Christensen <dpchrist@holgerdanske.com> - 2021-01-18 09:00 +0100
      Re: problem with wifi Long Wind <longwind2@yahoo.com> - 2021-01-18 10:00 +0100
        Re: problem with wifi David Christensen <dpchrist@holgerdanske.com> - 2021-01-18 10:20 +0100
        Re: problem with wifi Long Wind <longwind2@yahoo.com> - 2021-01-18 10:20 +0100
          Re: problem with wifi "Andrew M.A. Cater" <amacater@einval.com> - 2021-01-18 11:30 +0100
          Re: problem with wifi David Christensen <dpchrist@holgerdanske.com> - 2021-01-18 21:40 +0100
            Re: problem with wifi "Gareth Evans" <donotspam@fastmail.fm> - 2021-01-19 04:00 +0100
              Re: problem with wifi Andrei POPESCU <andreimpopescu@gmail.com> - 2021-01-19 09:00 +0100
                Re: problem with wifi "Gareth Evans" <donotspam@fastmail.fm> - 2021-01-19 11:40 +0100
                  Re: problem with wifi Andrei POPESCU <andreimpopescu@gmail.com> - 2021-01-19 21:00 +0100
                    Re: problem with wifi "Gareth Evans" <donotspam@fastmail.fm> - 2021-01-19 22:30 +0100
    Re: problem with wifi didier gaumet <didier.gaumet@gmail.com> - 2021-01-18 11:30 +0100

#230760 — problem with wifi

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

wifi is ok with cell phone, it isn't with buster
allow-hotplug  wlx0022c0001a59
iface wlx0022c0001a59 inet dhcp
wireless-essid JHotel

buster can connect to wifi with above
but after some time, connection is lost
i have to run ifdown/ifup again

any idea? Thanks!

[toc] | [next] | [standalone]

#230777

On 2021-01-17 12:15, Long Wind wrote:
> wifi is ok with cell phone, it isn't with buster
> allow-hotplug  wlx0022c0001a59
> iface wlx0022c0001a59 inet dhcp
> wireless-essid JHotel
> 
> buster can connect to wifi with above
> but after some time, connection is lost
> i have to run ifdown/ifup again
> 
> any idea? Thanks!


What is the make and model of the device that serves as your Wi-Fi 
access point (AP)?


Does the AP have the ability to do a radio channel congestion survey?


Is the AP configured to automatically select a low-congestion channel?


Is the AP stationary?


What is the make and model of the computer "buster"?


What is the make and model of the Wi-Fi interface in "buster"?


Is "buster" stationary?


Please run the following commands as root and post:

     # cat /etc/debian_version

     # uname -a


On "buster", I would look for clues in /var/log .  Post any interesting 
snippets.


David

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

#230780

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

 
    On Monday, January 18, 2021, 3:53:23 PM GMT+8, David Christensen <dpchrist@holgerdanske.com> wrote: 

 


What is the make and model of the device that serves as your Wi-Fi 
access point (AP)?


Does the AP have the ability to do a radio channel congestion survey?


Is the AP configured to automatically select a low-congestion channel?


Is the AP stationary?


What is the make and model of the computer "buster"?


What is the make and model of the Wi-Fi interface in "buster"?


Is "buster" stationary?


Please run the following commands as root and post:

    # cat /etc/debian_version

    # uname -a


On "buster", I would look for clues in /var/log .  Post any interesting 
snippets.




Thank David, but my problem disappear, i don't why


  

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

#230783

On 2021-01-18 00:52, Long Wind wrote:

> Thank David, but my problem disappear, i don't why

Maybe your neighbor(s) stopped using Wi-Fi.


Do the radio survey and see what choices you have for the active 
channel(s) (2.4 and/or 5 Hhz bands).


David

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

#230784

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

 buster's wifi connection is ok for several hours, so i think problem disappearbut after rebooting pc, problem appears again
wifi is provided by hotel, they hide AP somewhere, i don't know where, i think it's reliable
buster can connect to hot spot of cell phone, no problem

zhou@debian:~$ cat /etc/debian_version
10.5
zhou@debian:~$ uname -a
Linux debian 4.19.0-10-686 #1 SMP Debian 4.19.132-1 (2020-07-24) i686 GNU/Linux
zhou@debian:~$ 


   
   

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

#230789

On Mon, Jan 18, 2021 at 09:14:06AM +0000, Long Wind wrote:
>  buster's wifi connection is ok for several hours, so i think problem disappearbut after rebooting pc, problem appears again
> wifi is provided by hotel, they hide AP somewhere, i don't know where, i think it's reliable
> buster can connect to hot spot of cell phone, no problem
> 
> zhou@debian:~$ cat /etc/debian_version
> 10.5
> zhou@debian:~$ uname -a
> Linux debian 4.19.0-10-686 #1 SMP Debian 4.19.132-1 (2020-07-24) i686 GNU/Linux
> zhou@debian:~$ 
> 
> 
>    
>    
Long Wind

Two quick points:

If you're still using 10.5 - it might be a good and useful thing to 
dist-upgrade to 10.7. [10.8 happens at the end of the month.]

If you're still using 32 bit - you are probably OK for the lifetime of Debian 
11 but may then need to change - see discussions on 32 bit support.

All the very best, as ever,

Andy C

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

#230809

On 2021-01-18 01:14, Long Wind wrote:
>   buster's wifi connection is ok for several hours, so i think problem disappearbut after rebooting pc, problem appears again
> wifi is provided by hotel, they hide AP somewhere, i don't know where, i think it's reliable
> buster can connect to hot spot of cell phone, no problem
> 
> zhou@debian:~$ cat /etc/debian_version
> 10.5
> zhou@debian:~$ uname -a
> Linux debian 4.19.0-10-686 #1 SMP Debian 4.19.132-1 (2020-07-24) i686 GNU/Linux
> zhou@debian:~$

Then it sounds like your Debian is okay and there is a bug or feature 
with the hotel Wi-Fi.

David

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

#230821

On Mon, 18 Jan 2021, at 20:33, David Christensen wrote:
> On 2021-01-18 01:14, Long Wind wrote:
> >   buster's wifi connection is ok for several hours, so i think problem disappearbut after rebooting pc, problem appears again
> > wifi is provided by hotel, they hide AP somewhere, i don't know where, i think it's reliable
> > buster can connect to hot spot of cell phone, no problem
> > 
> > zhou@debian:~$ cat /etc/debian_version
> > 10.5
> > zhou@debian:~$ uname -a
> > Linux debian 4.19.0-10-686 #1 SMP Debian 4.19.132-1 (2020-07-24) i686 GNU/Linux
> > zhou@debian:~$
> 
> Then it sounds like your Debian is okay and there is a bug or feature 
> with the hotel Wi-Fi.
> 
> David

If the machine in question has a desktop environment and NetworkManager (or equivalent), doesn't /etc/network/interfaces (or interfaces.d) config override nm (etc)?

I thought without eg. connman, a dropped connection on a wifi NIC configured in /etc/network/interfaces would not automatically be re-established, and that this config had to be removed (or commented-out) for something like NetworkManager or wicd to manage the connection, in the case of a DE.  Is that wrong?

Thanks,
Gareth

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

#230825

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

On Ma, 19 ian 21, 02:51:21, Gareth Evans wrote:
> 
> If the machine in question has a desktop environment and 
> NetworkManager (or equivalent), doesn't /etc/network/interfaces (or 
> interfaces.d) config override nm (etc)?

It should (barring misconfiguration).

> I thought without eg. connman, a dropped connection on a wifi NIC 
> configured in /etc/network/interfaces would not automatically be 
> re-established, 

The physical WiFi connection is established and maintained by 
wpasupplicant, which runs as a daemon and should reconnect as needed.

The major difference is the (lack of) convenience in switching between 
and/or adding new networks.

> and that this config had to be removed (or commented-out) for 
> something like NetworkManager or wicd to manage the connection, in the 
> case of a DE.  Is that wrong?

There are different ways to prevent conflicts, the method you mentioned 
being one of them.

As a general recommendation, pick one software to manage your network 
interfaces and stick with it for everything. This tends to reduce 
complexity and conflicts.

Technically it should be possible to have different softwares managing 
different interfaces, though great care is needed so they don't trample 
on each other's toes.

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

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

#230831

On Tue, 19 Jan 2021, at 07:53, Andrei POPESCU wrote:
> On Ma, 19 ian 21, 02:51:21, Gareth Evans wrote:
> > 
> > If the machine in question has a desktop environment and 
> > NetworkManager (or equivalent), doesn't /etc/network/interfaces (or 
> > interfaces.d) config override nm (etc)?
> 
> It should (barring misconfiguration).
> 
> > I thought without eg. connman, a dropped connection on a wifi NIC 
> > configured in /etc/network/interfaces would not automatically be 
> > re-established, 
> 
> The physical WiFi connection is established and maintained by 
> wpasupplicant, which runs as a daemon and should reconnect as needed.
> 
> The major difference is the (lack of) convenience in switching between 
> and/or adding new networks.
> 
> > and that this config had to be removed (or commented-out) for 
> > something like NetworkManager or wicd to manage the connection, in the 
> > case of a DE.  Is that wrong?
> 
> There are different ways to prevent conflicts, the method you mentioned 
> being one of them.
> 
> As a general recommendation, pick one software to manage your network 
> interfaces and stick with it for everything. This tends to reduce 
> complexity and conflicts.
> 
> Technically it should be possible to have different softwares managing 
> different interfaces, though great care is needed so they don't trample 
> on each other's toes.
> 
> Kind regards,
> Andrei
> -- 
> http://wiki.debian.org/FAQsFromDebianUser
> 
> Attachments:
> * signature.asc


Hi Andrei,

> > I thought without eg. connman, a dropped connection on a wifi NIC 
> > configured in /etc/network/interfaces would not automatically be 
> > re-established, 

Just out of interest, was that ever the case?  Pre-WPA or even pre-WEP perhaps?  

I'm sure I've seen tutorials etc (which now don't seem to exist, and may never have been correct of course) which mentioned the need for NetworkManager to re-establish dropped connections.  I wondered if that might be an issue for Long Wind, but obviously not - thanks for clarifying.

Best wishes,
Gareth

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

#230860

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

On Ma, 19 ian 21, 10:37:57, Gareth Evans wrote:
> On Tue, 19 Jan 2021, at 07:53, Andrei POPESCU wrote:
> > On Ma, 19 ian 21, 02:51:21, Gareth Evans wrote:
> 
> > > I thought without eg. connman, a dropped connection on a wifi NIC 
> > > configured in /etc/network/interfaces would not automatically be 
> > > re-established, 
> 
> Just out of interest, was that ever the case?  Pre-WPA or even pre-WEP perhaps?  

According to Wikipedia development for NetworkManager was initiated in 
2004 whereas WPA became available in 2003 (WPA2 in 2004) and the first 
release of wpa_supplicant was in 2003.

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

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

#230862

On Tue, 19 Jan 2021, at 19:59, Andrei POPESCU wrote:
> On Ma, 19 ian 21, 10:37:57, Gareth Evans wrote:
> > On Tue, 19 Jan 2021, at 07:53, Andrei POPESCU wrote:
> > > On Ma, 19 ian 21, 02:51:21, Gareth Evans wrote:
> > 
> > > > I thought without eg. connman, a dropped connection on a wifi NIC 
> > > > configured in /etc/network/interfaces would not automatically be 
> > > > re-established, 
> > 
> > Just out of interest, was that ever the case?  Pre-WPA or even pre-WEP perhaps?  
> 
> According to Wikipedia development for NetworkManager was initiated in 
> 2004 whereas WPA became available in 2003 (WPA2 in 2004) and the first 
> release of wpa_supplicant was in 2003.
> 
> Kind regards,
> Andrei
> -- 
> http://wiki.debian.org/FAQsFromDebianUser
> 
> Attachments:
> * signature.asc

OK, thanks again.  
Gareth

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

#230788

Le 17/01/2021 à 21:15, Long Wind a écrit :
> wifi is ok with cell phone, it isn't with buster
> 
> allow-hotplug  wlx0022c0001a59
[...]

is it a wireless card managed by the mt76 driver (perhaps am I mistaken 
but the name reminds me of it)?
mt76 support having been introduced in Linux 4.19, it's fairly new and 
most of the time it would not function on my Buster with stock kernel. I 
would recommend in this case to install a backported kernel.

[toc] | [prev] | [standalone]

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

csiph-web