jenux for me for the future
Reason I haven't got the real archlinux on this computer is because I'm in a low grade wi-fi network and iwctl does a couple things that make it impossible to install archlinux. The first is minor but the second is a show stopper. The device list command constantly scrolls the screen with the same information coming up on it. Same thing happens with the station wlan0 connect command scrolling available networks constantly. The second thing iwctl does which is a show stopper is to get the correct network name entered which has a couple spaces in it and get the correct password and then fail to connect throwing an error. I'm using Jenux since somehow Jenux gets around both of these problems. I think iwctl either needs to be cleaned up and improved or I think iwctl needs to be replaced with something that works for wi-fi networks better than iwctl can do it. I don't know how to set up debugging for iwctl and capture useful error information otherwise you'd have that useful error information in this message. We're on penteledata.net so internet quality is also low and was no better on verizon-fios when I used that. These problems are not unique to me either. I was helping a friend for a couple weeks until he finally managed to connect to wi-fi in a remote location with iwctl on archlinux. He is sighted and also had a problem with the scrolling. We were finally able to get his connection up and running and it is just as well it happened this way since I had just learned to use iwctl before Lawrence needed to learn to use it. -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940.
On Tue, 2024-08-06 at 08:40 -0400, Jude DaShiell wrote:
If SSID (or password) have spaces (or other interesting characters) in them iwctl command should work fine with single quotes around them. e.g. iwctl station wlan0 connect 'ssid with spaces' -p 'pw( )rd' gene
iwctl failed with single quotes and also with double quotes. -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Tue, 6 Aug 2024, Genes Lists wrote:
Hi Jude, On 06.08.24 14:40, Jude DaShiell wrote:
There are alternatives to the iwd package (which contains the iwctl command). Maybe you can just switch to wpa_supplicant instead? The good thing about Arch is, you have the freedom of choice yourself. I would even consider combining it with NetworkManager, which might offer you a more convenient way of changing the network configuration using the nmtui command, if you like terminal user interfaces. Kind regards, Moabeat
I do like terminal interfaces, can iwctl be run on an install disk in such a way that lots more informative output can be saved to a log? I know how to use tee and like it better than script. If I get instructions on how to do that, I got no problem making debug logs for this command available to any legitimately interested parties. If I find a bug and can help toward fixing the bug I'm willing to do so. -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Tue, 6 Aug 2024, Moabeat wrote:
Hello ! The issue is finding the right app on the archiso. What I do, and is totally scriptable is to use wpa_supplicant plus dhcpd. Both available through the archiso according to head of master [1]. If you know how the configurations information required for your AP, you can follow instruction on the archwiki [2], and I usually go for the manual configuration rather than the interactive process, and usually such configuration ends up being actually pretty basic, like for pure WPA3 [3]. Once the connection has been established, which turns the corresponding interface up for it, you can start the dhcpcd [4] service without initial configuration if having a dhcp server somewhere in your network, otherwise you have to configure the static routes. For later automation, you can enable the wpa_supplicant hook for dhcpcd [5]. Is sounds more complicated than it actually is... And it's been working through ages... That might be an options to consider. A non standard way would be, given you already have an Arch (or your derivative of choice) working on your network you could "cp -a" the ful disk of the working system into the disk of the new box, and modify the usernames and such (you really need to know everything about it), and make the box boot, once booting into the box, then you can modify passwords and such... This might be an option I'd guess, a slow one given the disk copy, though it might reduce time on installing and configuring packages, and so on... Greetings ! -- Javier [1] https://gitlab.archlinux.org/archlinux/archiso/-/blob/master/configs/releng/... [2] https://wiki.archlinux.org/title/Wpa_supplicant [3] https://wiki.archlinux.org/title/Wpa_supplicant#Connections_to_pure_WPA3-SAE... [4] https://wiki.archlinux.org/title/Dhcpcd [5] https://wiki.archlinux.org/title/Dhcpcd#10-wpa_supplicant
Hello Jude, On Tuesday, 6 August 2024 at 11:06 (-0400), Jude DaShiell wrote:
I do like terminal interfaces, can iwctl be run on an install disk in such a way that lots more informative output can be saved to a log?
In fact iwctl has a command line mode as well as its interactive mode. Here is a small excerpt of its man page:
I tested this series of commands, and they all result in a static output to the console. I hope this is helpful, Jaron
Ey, Could you link me to Jenux? I can't find anything online. -- Cheers, Aᴀʀᴏɴ
https://nashcentral.duckdns.org/projects/ Jenux is only part of what's in that directory. If you have any trouble developer's address is dnl.nash@gmail.com. -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Tue, 6 Aug 2024, Aaron Liu wrote:
Ey,
Could you link me to Jenux? I can't find anything online.
On 8/6/24 7:40 AM, Jude DaShiell wrote:
Is there any possibility the whitespace you are talking about is something other than good old ASCII 0x20? I don't have a box with wifi to test on, but the only thing I can think of from a technical point of view that would let jenux work an Arch fail with iwctl would be some kind of character-set or encoding difference that isn't handles whatever whitespace is in the network name and password differently. This is just a guess, but since it came to mind I thought I would pass it along. Can you hexdump the name and password in some way and test? -- David C. Rankin, J.D.,P.E.
participants (7)
-
Aaron Liu
-
David C. Rankin
-
Genes Lists
-
Jaron Kent-Dobias
-
Javier
-
Jude DaShiell
-
Moabeat