[opensuse] Wicked + iwlist fails on "Failed to read scan data: Argument list too long"
I am running tumbleweed on a Dell XPS 1575 currently kernel 4.17.3-1. Normally when I start the machine I can connect wireless to my phone via tether from Yast using wicked. I now find in a shared work office space that I am unable to connect to my phone via tether, as before. Journal reports wicked[6795]: wlp2s0 setup-in-progress If I bring down the interface # wicked ifdown wlp2s0 Then journal reports wicked[6795]: wlp2s0 device-ready If I turn on WICKED_DEBUG = 'all' in /etc/sysconfig/network/config then when I bring the interface up and down in wicked with # wicked ifdown wlp2s0 # wicked ifup wlp2s0 then journal reports repeatedly 'Scanning signal received (not handled)'. Usually repeats message 5-10 times. I have also observed that iwlist fails to work in shared office space where there are a huge number of SSIDs advertised. # iwlist wlp2s0 scan wlp2s0 Failed to read scan data: Argument list too long # iwlist wlp2s0 scan essid WeWork wlp2s0 Failed to read scan data: Argument list too long Using the is command works fine. # iw wlp2s0 scan [lengthy output] If I leave the shared office e environment and return to the street, both iwlist and yast/wickedd begin to work again. Question: Is it the case that yast/wickedd have a dependency on iwlist (that can cause wickedd to fail when iwlist fails on too many SSID results)? If so, can yast/wickedd be configured to use iw instead of iwlist? -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op maandag 11 februari 2019 21:51:02 CET schreef Michael Hieb:
I am running tumbleweed on a Dell XPS 1575 currently kernel 4.17.3-1.
Normally when I start the machine I can connect wireless to my phone via tether from Yast using wicked. I now find in a shared work office space that I am unable to connect to my phone via tether, as before. Journal reports
wicked[6795]: wlp2s0 setup-in-progress
If I bring down the interface
# wicked ifdown wlp2s0
Then journal reports
wicked[6795]: wlp2s0 device-ready
If I turn on WICKED_DEBUG = 'all' in /etc/sysconfig/network/config then when I bring the interface up and down in wicked with
# wicked ifdown wlp2s0 # wicked ifup wlp2s0
then journal reports repeatedly 'Scanning signal received (not handled)'. Usually repeats message 5-10 times.
I have also observed that iwlist fails to work in shared office space where there are a huge number of SSIDs advertised.
# iwlist wlp2s0 scan wlp2s0 Failed to read scan data: Argument list too long
# iwlist wlp2s0 scan essid WeWork wlp2s0 Failed to read scan data: Argument list too long
Using the is command works fine.
# iw wlp2s0 scan [lengthy output]
If I leave the shared office e environment and return to the street, both iwlist and yast/wickedd begin to work again.
Question: Is it the case that yast/wickedd have a dependency on iwlist (that can cause wickedd to fail when iwlist fails on too many SSID results)?
If so, can yast/wickedd be configured to use iw instead of iwlist? That's an ancient TW version. When did you last zypper dup?
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I have installed a fresh TW and run zypper dup to ensure installation is up to date and I replicate the behavior on up to date installation. To summarize the behavior; 1. iwlist [dev] scan will work fine in home and on the street, but will fail in a shared office environment where there are a large number of advertised SSIDs available. E.g. ## iwlist wlp2s0 scan #wlp2s0 Failed to read scan data: Argument list too long ## iwlist wlp2s0 scan essid WeWork #wlp2s0 Failed to read scan data: Argument list too long 2. iw [dev] scan works fine in both environments. E.g. ## iw wlp2s0 scan #[lengthy output] 3. In shared office environment both yast->network settings and systemctl start wicked.service fail (but they work fine at home and on street). Details of the failure in post below. QUESTION: is there a dependency on the deprecated iwlist (or the underlying code) in yast and wicked.service that needs to be changed to rely on iw (or the underlying code) instead? Best, Michael On 11/02/2019 20:53, Knurpht-openSUSE wrote:
Op maandag 11 februari 2019 21:51:02 CET schreef Michael Hieb:
I am running tumbleweed on a Dell XPS 1575 currently kernel 4.17.3-1.
Normally when I start the machine I can connect wireless to my phone via tether from Yast using wicked. I now find in a shared work office space that I am unable to connect to my phone via tether, as before. Journal reports
wicked[6795]: wlp2s0 setup-in-progress
If I bring down the interface
# wicked ifdown wlp2s0
Then journal reports
wicked[6795]: wlp2s0 device-ready
If I turn on WICKED_DEBUG = 'all' in /etc/sysconfig/network/config then when I bring the interface up and down in wicked with
# wicked ifdown wlp2s0 # wicked ifup wlp2s0
then journal reports repeatedly 'Scanning signal received (not handled)'. Usually repeats message 5-10 times.
I have also observed that iwlist fails to work in shared office space where there are a huge number of SSIDs advertised.
# iwlist wlp2s0 scan wlp2s0 Failed to read scan data: Argument list too long
# iwlist wlp2s0 scan essid WeWork wlp2s0 Failed to read scan data: Argument list too long
Using the is command works fine.
# iw wlp2s0 scan [lengthy output]
If I leave the shared office e environment and return to the street, both iwlist and yast/wickedd begin to work again.
Question: Is it the case that yast/wickedd have a dependency on iwlist (that can cause wickedd to fail when iwlist fails on too many SSID results)?
If so, can yast/wickedd be configured to use iw instead of iwlist? That's an ancient TW version. When did you last zypper dup?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I have installed a fresh TW and run zypper dup to ensure installation is up to date and I replicate the behavior on up to date installation. ## uname -a # Linux [] 4.20.7-1-default #1 SMP PREEMPT Thu Feb 7 07:16:45 UTC 2019 (730812f) x86_64 x86_64 x86_64 GNU/Linux ## zypper dup # Loading repository data... # Reading installed packages... # Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are # compatible before you continue. See 'man zypper' for more information about this command. # Computing distribution upgrade... # # Nothing to do. To summarize the problem behavior; 1. iwlist [dev] scan will work fine in home and on the street, but will fail in a shared office environment where there are a large number of advertised SSIDs available. E.g. ## iwlist wlp2s0 scan #wlp2s0 Failed to read scan data: Argument list too long ## iwlist wlp2s0 scan essid WeWork #wlp2s0 Failed to read scan data: Argument list too long 2. iw [dev] scan works fine in both environments. E.g. ## iw wlp2s0 scan #[lengthy output] 3. In shared office environment both yast->network settings and systemctl start wicked.service fail (but they work fine at home and on street). Details of the failure in post below. QUESTION: is there a dependency on the deprecated iwlist (or the underlying code) in yast and wicked.service that needs to be changed to rely on iw (or the underlying code) instead? Best, Michael On 11/02/2019 20:53, Knurpht-openSUSE wrote:
Op maandag 11 februari 2019 21:51:02 CET schreef Michael Hieb:
I am running tumbleweed on a Dell XPS 1575 currently kernel 4.17.3-1.
Normally when I start the machine I can connect wireless to my phone via tether from Yast using wicked. I now find in a shared work office space that I am unable to connect to my phone via tether, as before. Journal reports
wicked[6795]: wlp2s0 setup-in-progress
If I bring down the interface
# wicked ifdown wlp2s0
Then journal reports
wicked[6795]: wlp2s0 device-ready
If I turn on WICKED_DEBUG = 'all' in /etc/sysconfig/network/config then when I bring the interface up and down in wicked with
# wicked ifdown wlp2s0 # wicked ifup wlp2s0
then journal reports repeatedly 'Scanning signal received (not handled)'. Usually repeats message 5-10 times.
I have also observed that iwlist fails to work in shared office space where there are a huge number of SSIDs advertised.
# iwlist wlp2s0 scan wlp2s0 Failed to read scan data: Argument list too long
# iwlist wlp2s0 scan essid WeWork wlp2s0 Failed to read scan data: Argument list too long
Using the is command works fine.
# iw wlp2s0 scan [lengthy output]
If I leave the shared office e environment and return to the street, both iwlist and yast/wickedd begin to work again.
Question: Is it the case that yast/wickedd have a dependency on iwlist (that can cause wickedd to fail when iwlist fails on too many SSID results)?
If so, can yast/wickedd be configured to use iw instead of iwlist? That's an ancient TW version. When did you last zypper dup?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 17/02/2019 16.56, Michael Hieb wrote:
I have installed a fresh TW and run zypper dup to ensure installation is up to date and I replicate the behavior on up to date installation.
Maybe you can try network manager instead. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Michael Hieb wrote:
To summarize the problem behavior;
1. iwlist [dev] scan will work fine in home and on the street, but will fail in a shared office environment where there are a large number of advertised SSIDs available. E.g. ## iwlist wlp2s0 scan #wlp2s0 Failed to read scan data: Argument list too long
## iwlist wlp2s0 scan essid WeWork #wlp2s0 Failed to read scan data: Argument list too long
2. iw [dev] scan works fine in both environments. E.g. ## iw wlp2s0 scan #[lengthy output]
3. In shared office environment both yast->network settings and systemctl start wicked.service fail (but they work fine at home and on street). Details of the failure in post below.
QUESTION: is there a dependency on the deprecated iwlist (or the underlying code) in yast and wicked.service that needs to be changed to rely on iw (or the underlying code) instead?
I would open a bug report. https://bugzilla.opensuse.org/ -- Per Jessen, Zürich (1.0°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Carlos E. R.
-
Knurpht-openSUSE
-
Michael Hieb
-
Per Jessen