Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On 9/30/21, Stella Ashburne wrote: > Hi > > Thanks for sharing your experience with me. Hi, Stella, you're most welcome. :) >> Sent: Thursday, September 30, 2021 at 2:38 PM >> From: "riveravaldez" >> To: debian-user@lists.debian.org >> Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - >> Connection status show OK but unable to surf the net) >> >> >> Hi, my case was similar, while in Debian I use just >> /etc/network/interfaces >> file or NM, in a Dell laptop with Arch I was using Wicd until it got more >> or less abandoned and out of official repositories (like in Debian, >> IIRC), > > You're right. Before writing this reply, I checked for the latest version of > wicd on packages.debian.org and the latter returned zero results. I used Wicd for a long time, always flawlessly, simple and lightweight. But sadly it seems like last version is from 2016[1] and «wicd depends on python2 and is unmaintained.»[2] I don't know of any port to python3. >> so, following Arch wiki instructions, I changed Wicd for the >> systemd-networkd+iwd combo, and the Wi-Fi connections are working >> fine (previously, wpa_supplicant gave me some persistent problems...). >> So, I can say that it's a pretty functional and simple tool for the task. >> Meaning, it works. >> > According to some tutorials that I found on the internet, it's advisable to > remove/uninstall wpa_supplicant before using iwd due to potential > conflicts. Indeed. You must first remove wpa_supplicant. They perform, more or less, the same function, I guess. > As for your statement "..I changed Wicd for the systemd-networkd+iwd > combo...", how did you do it? Could you share how you used systemd-networkd > with iwd please? I'm still learning Linux, you know and I appreciate all the > help that everyone here is willing to give. Sure, but I did this in an Arch system, so, I'm not sure the steps would be the same -probably not. I followed the detailed instructions you can read (more or less, in that order) at: https://wiki.archlinux.org/title/Network_configuration https://wiki.archlinux.org/title/Network_configuration/Wireless https://wiki.archlinux.org/title/Systemd-networkd https://wiki.archlinux.org/title/Iwd «The systemd package is part of the default Arch installation and contains all needed files to operate a wired network. Wireless adapters, covered later in this article, can be set up by services, such as wpa_supplicant or iwd.» So, IIRC, just be sure to don't have N-M, Wicd, etc., installed. In Debian I just use the /etc/network/interfaces file or N-M, but probably it would be best for you to check these: https://www.debian.org/doc/manuals/debian-reference/ch05.en.html https://wiki.debian.org/NetworkConfiguration https://wiki.debian.org/WiFi https://wiki.debian.org/SystemdNetworkd https://wiki.debian.org/NetworkManager/iwd Sorry I can't provide nothing succinct and useful/straightforward. Best regards! [1] https://launchpad.net/wicd [2] https://wiki.archlinux.org/title/Wicd
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thu 30 Sep 2021 at 14:11:51 (-0400), Lee wrote: > On 9/30/21, Stella Ashburne wrote: > >> Sent: Thursday, September 30, 2021 at 11:48 PM > >> From: to...@de > >> On Thu, Sep 30, 2021 at 10:14:05AM -0400, Henning Follmann wrote: > >> > >> [...] > >> > >> > What baffels me is though, at what length someone would go to not use > >> > the default > >> > methods to connect via wifi. Especially when they showed limited > >> > experience > >> > in networking in the first place. > >> > >> This remark was, IMO, unnecessary: after all, that's how we learn around > >> here, > >> don't we? > >> > >> At least that's how I learn. > >> > > Bingo. I couldn't agree with you more. > > Seriously!!? My wireless is slow, so I've been sort of following this > thread in case something useful (to me :-) gets mentioned, but all the > learning being done seems to be of the negative "this doesn't work" > flavour,, > > Why not stick with standard procedure and follow > https://wiki.debian.org/WiFi/HowToUse > > That at least seems to be a better bet for getting a working wireless > connection that you can then improve upon later. "it's also possible to nearly base your entire networking stack on one codebase with IWD alone. It's an all-in-one wireless client, wireless daemon, and even a DHCP client optionally! At its best, your entire networking stack can be as minimal as IWD + systemd-resolved, and this works wonderfully for many scenarios. It has virtually zero dependencies and uses modern kernel features as often as possible. Anecdotal reports suggest that it's much faster to connect to networks than wpa_supplicant, and has better roaming support, among other perceived improvements." I like the idea of better roaming support. But even at home, I want a connection method that occasionally "goes to sleep" and means crossing the house to sort it out. 'If "EnableNetworkConfiguration=true" is set, you'll also need to configure IWD's name resolving service. It supports systemd-resolved and resolvconf.' Currently I run resolvconf. As I wrote elsewhere, I've not delved into how systemd has disturbed things. Anyway, AIUI this wiki page seems to assume that you're converting a running WiFi from wpa_supplicant to iwd, rather than setting up iwd from scratch. So it (again, seems to) lack too many troubleshooting methods for those doing the latter on a new installation. Cheers, David.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thu 30 Sep 2021 at 19:33:45 +0200, to...@tuxteam.de wrote: > On Thu, Sep 30, 2021 at 12:23:45PM -0400, Henning Follmann wrote: > > On Thu, Sep 30, 2021 at 05:48:19PM +0200, to...@tuxteam.de wrote: > > [...] > > > > At least that's how I learn. > > > > > > > That is not me. > > People tend to be different. That makes things... interesting. That's the bit where advising a user is folloed by How do I copy and paste? or What's a terminal? Interesting? Ever done user-support? > > I will not encourage anyone to set themselves up for failure. > > I might be unpolished, and you expressed before that I am rude. > > Wait a sec. If I did that (if you say so I take it at face value) > please, accept my apologies. > > > However I think most people benefit from a realistic point > > of their own capabilities. > > I just do not think throwing somebody from a ship in the middle > > of the ocean and thinking he/she will learn to swim. I rather send > > them to the kiddie pool, no matter how offended they are. > > > > And it is not the case that I do not want them to learn. Quite the > > opposite is true. > > I I wouldn't propose "throwing somebody from a ship". But if > someone wants to jump, I'd tell them what they can expect > instead of just telling them "don't do it". And have a lifebuoy > at hand. Passenger: I've had enough. I am going to jump. tomas: Can you swim? Passenger: No. tomas: You will drown, but I will throw you a lifebuoy. Passenger: Will that help? tomas: Not really. We are in Artic waters. You will succumb to hypothermia within minites. Passenger: Can you help to alleviate that? tomas: Hold on 10 minutes; I'll get you a duvet. Passenger: That is very civil of you. Will it keep me alive? tomas: For a time. But I'll be cold tonight! Don't forget; it's my duvet. Passenge: Does the duvet have the Debian logo on it? tomas: No, just roses. Passenge: Do you think you could get one with a petunia pattern? tomas: This boat does not support such patterns. Passenge: When I sailed with the Gentoo line they ofered all flower patterns. tomas: The packages they offer to users are different. Passenger: I wish I had used the default method to connect via WiFi to my Debian machine. I am doomed! [Splash.] [ tomas wonders whether a more proactive stance could have put the situation on a more even keel.] [Exit stage left and right.] -- Brian.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thu, Sep 30, 2021 at 02:05:50PM -0400, Henning Follmann wrote: [...] > No apology necessary. OK, thanks. > I know I am opinionated and right in your > face (and a reverse snob as my wife regularly points out). > But I am also a big boy, I can take it if you yell back at me. Still I try hard to not call people "rude". I may characterise a message as rude, yes, but not the person behind it. It doesn't work out always, alas :-) Cheers - t signature.asc Description: Digital signature
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thu 30 Sep 2021 at 15:55:54 (+0200), Stella Ashburne wrote: > > Sent: Thursday, September 30, 2021 at 1:22 PM > > From: "David Wright" > > > [Security] > > > PreSharedKey=a long string of alphanumeric characters > > > Passphrase=aquickbrownfoxjumpsoverthelazydog > > > > I take it that you edited in the passphrase, and iwd wrote > > the PreSharedKey into the file itself? > > > Yes, before I submitted my post to lists.debian.org, I changed my passphrase > to aquickbrownfoxjumpsoverthelazydog I expected that. I was only confirming that you didn't write the PSK, but only the passphrase. iwd then fills it in. Speaking of which, I'm not sure what is meant (in the wiki) by "connect" in "The pre-shared key will be appended to the file at the first connect". Does this mean when one commands iwctl, or when the SSID is seen. > > > [IPv4] > > > Address=192.168.30.115 > > > Netmask=255.255.255.0 > > > Gateway=192.168.30.1 > > > Broadcast=192.168.30.255 > > > DNS=8.8.8.8 > > > > Where did you get the number 115 from? > > > My dear David, I plucked it out of thin air. Mea culpa, mea maxima culpa?? I > could have just typed 130 instead of 115. In which case, is the 30 made up. We just don't know whether the PC is on the same network as the router yet. And I don't have experience of setting up a static network without the router's cooperation on choosing addresses. > > It's claimed that iwd can do DHCP itself. For this, you'd drop > > the [IPv4] paragraph above, and instead put > > > > [General] > > EnableNetworkConfiguration=true > > into /etc/iwd/main.conf (create if necessary). > > > Yes, I think ArchLinux's wiki mentions that starting with iwd's version 0.9, > the latter can do DHCP... > > > > Please note that I have disabled IPv6 by adding the line > > > > > > GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet" > > > > > > to /etc/default/grub > > > > It's claimed that iwd only configures IPv6 if you have > > > > [Network] > > EnableIPv6=true > > > > in /etc/iwd/main.conf. > > > That's absolutely correct. In fact according to the same ArchLinux's wiki, > with iwd, support for IPv6 is disabled by default. > Cheers, David.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thu 30 Sep 2021 at 16:09:44 (+0200), Stella Ashburne wrote: > > Sent: Thursday, September 30, 2021 at 6:06 AM > > From: "Dan Ritter" > > > > Might I suggest wicd, which people here do have experience with > > and have used successfully? > > > Before writing this reply, I checked with packages.debian.org and I couldn't > find the package wicd in Debian's official list of packages for Debian 11. It > seems that it's been removed for some reasons. It requires python2→3 conversion. Python2 is officially expired. PS I wouldn't email Intel iwd developers. It would be a bit like calling the Federal Reserve for help filling in a mortgage form. Cheers, David.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On 9/30/21, Stella Ashburne wrote: > Hi Tomas > >> Sent: Thursday, September 30, 2021 at 11:48 PM >> From: to...@de >> To: debian-user@lists.debian.org >> Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - >> Connection status show OK but unable to surf the net) >> >> On Thu, Sep 30, 2021 at 10:14:05AM -0400, Henning Follmann wrote: >> >> [...] >> >> > What baffels me is though, at what length someone would go to not use >> > the default >> > methods to connect via wifi. Especially when they showed limited >> > experience >> > in networking in the first place. >> >> This remark was, IMO, unnecessary: after all, that's how we learn around >> here, >> don't we? >> >> At least that's how I learn. >> > Bingo. I couldn't agree with you more. Seriously!!? My wireless is slow, so I've been sort of following this thread in case something useful (to me :-) gets mentioned, but all the learning being done seems to be of the negative "this doesn't work" flavour,, Why not stick with standard procedure and follow https://wiki.debian.org/WiFi/HowToUse That at least seems to be a better bet for getting a working wireless connection that you can then improve upon later. Best Regards, Lee
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thu 30 Sep 2021 at 12:23:45 -0400, Henning Follmann wrote: > On Thu, Sep 30, 2021 at 05:48:19PM +0200, to...@tuxteam.de wrote: > > On Thu, Sep 30, 2021 at 10:14:05AM -0400, Henning Follmann wrote: > > > > [...] > > > > > What baffels me is though, at what length someone would go to not use the > > > default > > > methods to connect via wifi. Especially when they showed limited > > > experience > > > in networking in the first place. > > > > This remark was, IMO, unnecessary: after all, that's how we learn around > > here, > > don't we? > > > > At least that's how I learn. > > > > That is not me. > I will not encourage anyone to set themselves up for failure. > I might be unpolished, and you expressed before that I am rude. > However I think most people benefit from a realistic point > of their own capabilities. > I just do not think throwing somebody from a ship in the middle > of the ocean and thinking he/she will learn to swim. I rather send > them to the kiddie pool, no matter how offended they are. Someone jumping in at the deep end is eventually going to learn, but it frequently would involve someone elses considerable time and effort. Something to factor in when co-operation is on the table. Sharing knowledge and experience with a user who hasn't any clear concept of what the shallow end is like very often doesn't lead to a satisfactory outcome. Advising going back to basics is likely to be of the greatest benefit to both parties. > And it is not the case that I do not want them to learn. Quite the > opposite is true. This is very believable. I wouldn't doubt it. -- Brian.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thu, Sep 30, 2021 at 07:33:45PM +0200, to...@tuxteam.de wrote: > On Thu, Sep 30, 2021 at 12:23:45PM -0400, Henning Follmann wrote: > > On Thu, Sep 30, 2021 at 05:48:19PM +0200, to...@tuxteam.de wrote: > > [...] > > > > At least that's how I learn. > > > > > > > That is not me. > > People tend to be different. That makes things... interesting. > > > I will not encourage anyone to set themselves up for failure. > > I might be unpolished, and you expressed before that I am rude. > > Wait a sec. If I did that (if you say so I take it at face value) > please, accept my apologies. > No apology necessary. I know I am opinionated and right in your face (and a reverse snob as my wife regularly points out). But I am also a big boy, I can take it if you yell back at me. -H -- Henning Follmann | hfollm...@itcfollmann.com
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thu, Sep 30, 2021 at 12:23:45PM -0400, Henning Follmann wrote: > On Thu, Sep 30, 2021 at 05:48:19PM +0200, to...@tuxteam.de wrote: [...] > > At least that's how I learn. > > > > That is not me. People tend to be different. That makes things... interesting. > I will not encourage anyone to set themselves up for failure. > I might be unpolished, and you expressed before that I am rude. Wait a sec. If I did that (if you say so I take it at face value) please, accept my apologies. > However I think most people benefit from a realistic point > of their own capabilities. > I just do not think throwing somebody from a ship in the middle > of the ocean and thinking he/she will learn to swim. I rather send > them to the kiddie pool, no matter how offended they are. > > And it is not the case that I do not want them to learn. Quite the > opposite is true. I I wouldn't propose "throwing somebody from a ship". But if someone wants to jump, I'd tell them what they can expect instead of just telling them "don't do it". And have a lifebuoy at hand. But we are different and that's OK. I don't suggest you do like me. I think this is the biggest asset in this list, at least if we understand how to use it :) Cheers - t signature.asc Description: Digital signature
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thursday, September 30, 2021 12:28:54 PM Stella Ashburne wrote: > Your statement: "Be bold, go where no man has gone before" > > I suppose that "man" refers to both men and women, right? (Just kidding. In > this time and age, one has to be seen to be politically correct, yes?) Yes, or at least to Captain Kirk and Uhura (I don't know how to spell that)! ;-)
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Stella Ashburne wrote: > Hi > > Thanks for your words of encouragement. > > > Sent: Thursday, September 30, 2021 at 11:39 PM > > From: rhkra...@gmail.com > > To: debian-user@lists.debian.org > > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > > Connection status show OK but unable to surf the net) > > > > On Thursday, September 30, 2021 10:54:17 AM Stella Ashburne wrote: > > Yes, their email address are displayed on the project's website. > > No, they didn't mention that any Tom, Dick and Harry are welcome to write > > to them. Well, thank goodness your name is Stella ;-) (Sorry!) I think the > > implication of them having their email address on the project's website is > > that Tom, Dick and Harry (and even Stella) are welcome to write to > > them, and they have the implied option of not replying for whatever reason. > > Be bold, go where no man has gone before ;-) > > Your statement: "Be bold, go where no man has gone before" > > I suppose that "man" refers to both men and women, right? (Just kidding. In > this time and age, one has to be seen to be politically correct, yes?) Updated in 1987 by Star Trek: The Next Generation "Space: the final frontier. These are the voyages of the starship Enterprise. Its continuing mission: to explore strange new worlds, to seek out new life and new civilizations, to boldly go where no one has gone before." -dsr-
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Stella Ashburne wrote: > Hi Dan > > > Sent: Thursday, September 30, 2021 at 11:15 PM > > From: "Dan Ritter" > > To: "Stella Ashburne" > > Cc: debian-user@lists.debian.org > > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > > Connection status show OK but unable to surf the net) > > > > > > Try > > > > ip link show > > > > and look for the name of a device which could be your wifi NIC. > > > Nope, ip link show does not show up any device which is my wifi NIC Then the kernel is not recognizing it. Can you spot it in either lspci or lsusb and tell us the hardware? -dsr-
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi Thanks for your words of encouragement. > Sent: Thursday, September 30, 2021 at 11:39 PM > From: rhkra...@gmail.com > To: debian-user@lists.debian.org > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > On Thursday, September 30, 2021 10:54:17 AM Stella Ashburne wrote: > Yes, their email address are displayed on the project's website. > No, they didn't mention that any Tom, Dick and Harry are welcome to write > to them. Well, thank goodness your name is Stella ;-) (Sorry!) I think the > implication of them having their email address on the project's website is > that Tom, Dick and Harry (and even Stella) are welcome to write to > them, and they have the implied option of not replying for whatever reason. > Be bold, go where no man has gone before ;-) Your statement: "Be bold, go where no man has gone before" I suppose that "man" refers to both men and women, right? (Just kidding. In this time and age, one has to be seen to be politically correct, yes?)
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thu, Sep 30, 2021 at 05:48:19PM +0200, to...@tuxteam.de wrote: > On Thu, Sep 30, 2021 at 10:14:05AM -0400, Henning Follmann wrote: > > [...] > > > What baffels me is though, at what length someone would go to not use the > > default > > methods to connect via wifi. Especially when they showed limited experience > > in networking in the first place. > > This remark was, IMO, unnecessary: after all, that's how we learn around here, > don't we? > > At least that's how I learn. > That is not me. I will not encourage anyone to set themselves up for failure. I might be unpolished, and you expressed before that I am rude. However I think most people benefit from a realistic point of their own capabilities. I just do not think throwing somebody from a ship in the middle of the ocean and thinking he/she will learn to swim. I rather send them to the kiddie pool, no matter how offended they are. And it is not the case that I do not want them to learn. Quite the opposite is true. -H -- Henning Follmann | hfollm...@itcfollmann.com
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi Tomas > Sent: Thursday, September 30, 2021 at 11:48 PM > From: to...@tuxteam.de > To: debian-user@lists.debian.org > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > On Thu, Sep 30, 2021 at 10:14:05AM -0400, Henning Follmann wrote: > > [...] > > > What baffels me is though, at what length someone would go to not use the > > default > > methods to connect via wifi. Especially when they showed limited experience > > in networking in the first place. > > This remark was, IMO, unnecessary: after all, that's how we learn around here, > don't we? > > At least that's how I learn. > Bingo. I couldn't agree with you more. The main objective of having a mailing list for Debian users is so that we, as a community of like-minded individuals, are able to share our knowledge and experience.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi Dan > Sent: Thursday, September 30, 2021 at 11:15 PM > From: "Dan Ritter" > To: "Stella Ashburne" > Cc: debian-user@lists.debian.org > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > > Try > > ip link show > > and look for the name of a device which could be your wifi NIC. > Nope, ip link show does not show up any device which is my wifi NIC
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thu, Sep 30, 2021 at 04:54:17PM +0200, Stella Ashburne wrote: > Hi Henning > > > Sent: Thursday, September 30, 2021 at 10:14 PM > > From: "Henning Follmann" > > To: debian-user@lists.debian.org > > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > > Connection status show OK but unable to surf the net) > > > > > > That depends. How did you get their e-mail address? > > Was it from the project webpage? Do they encourage anybody to > > send them direct mail? > > Them yes. > > > Yes, their email address are displayed on the project's website. Wow, we do live in a different reality. I checked the page https://git.kernel.org/pub/scm/network/wireless/iwd.git/ I do not see any of their e-mail address displayed there. So you followed the link to the mailing list and scraped the e-mails from there? > > No, they didn't mention that any Tom, Dick and Harry are welcome to write to > them. I didn't think so. > > > What baffels me is though, at what length someone would go to not use the > > default > > methods to connect via wifi. Especially when they showed limited experience > > in networking in the first place. > > > Pray thee, what are the default methods that you speak of? Well, again the first thing I would check is the debian documentation. Lets look at the "The Debian Administrator's Handbook" section 8.2 https://www.debian.org/doc/manuals/debian-handbook/sect.network-config.en.html And here we find - quote: "NOTE NetworkManager If Network Manager is particularly recommended in roaming setups (see Section 8.2.5, “Automatic Network Configuration for Roaming Users”), it is also perfectly usable as the default network management tool. You can create “System connections” that are used as soon as the computer boots either manually with a .ini-like file in /etc/NetworkManager/system-connections/ or through a graphical tool (nm-connection-editor). If you were using ifupdown, just remember to deactivate the entries in /etc/network/interfaces that you want Network Manager to handle." > > My OS is plain Debian 11 with just lxqt-core and lightdm installed. I'm tired > of using Gnome. again network-manager does not need GNOME. It works perfectly fine whithout any DE and comes with a cli frontend (nmcli). next choice through /e/n/i > > Indeed, I've very limited networking and that's why I'm motivated to learn > how to use iwd to surf the net. > right, sigh, you are willing to learn what you already decided on. Please consider smaller steps. Install your debian initially just by following the predesigned way. Learn how to use it, gain knowledge and confidence from there, then venture to more challenging topics. I think you will be much happier this way. -H -- Henning Follmann | hfollm...@itcfollmann.com
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thu, Sep 30, 2021 at 10:14:05AM -0400, Henning Follmann wrote: [...] > What baffels me is though, at what length someone would go to not use the > default > methods to connect via wifi. Especially when they showed limited experience > in networking in the first place. This remark was, IMO, unnecessary: after all, that's how we learn around here, don't we? At least that's how I learn. Cheers - t signature.asc Description: Digital signature
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thursday, September 30, 2021 10:54:17 AM Stella Ashburne wrote: > Yes, their email address are displayed on the project's website. > > No, they didn't mention that any Tom, Dick and Harry are welcome to write > to them. Well, thank goodness your name is Stella ;-) (Sorry!) I think the implication of them having their email address on the project's website is that Tom, Dick and Harry (and even Stella) are welcome to write to them, and they have the implied option of not replying for whatever reason. Be bold, go where no man has gone before ;-)
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Stella Ashburne wrote: > Oh dear! Oh dear! > > After a reboot, I typed the following word at the command prompt: > > iwctl > > Next, I typed > > station wlan0 show > > The output was: No device found Try ip link show and look for the name of a device which could be your wifi NIC. -dsr-
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi Henning > Sent: Thursday, September 30, 2021 at 10:14 PM > From: "Henning Follmann" > To: debian-user@lists.debian.org > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > > That depends. How did you get their e-mail address? > Was it from the project webpage? Do they encourage anybody to > send them direct mail? > Them yes. > Yes, their email address are displayed on the project's website. No, they didn't mention that any Tom, Dick and Harry are welcome to write to them. > What baffels me is though, at what length someone would go to not use the > default > methods to connect via wifi. Especially when they showed limited experience > in networking in the first place. > Pray thee, what are the default methods that you speak of? My OS is plain Debian 11 with just lxqt-core and lightdm installed. I'm tired of using Gnome. Indeed, I've very limited networking and that's why I'm motivated to learn how to use iwd to surf the net.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Oh dear! Oh dear! > Sent: Thursday, September 30, 2021 at 1:22 PM > From: "David Wright" > To: debian-user@lists.debian.org > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > > [IPv4] > > Address=192.168.30.115 > > Netmask=255.255.255.0 > > Gateway=192.168.30.1 > > Broadcast=192.168.30.255 > > DNS=8.8.8.8 > > > It's claimed that iwd can do DHCP itself. For this, you'd drop > the [IPv4] paragraph above, and instead put > > [General] > EnableNetworkConfiguration=true > > into /etc/iwd/main.conf (create if necessary). > Per your suggestion, I created a file main.conf in /etc/iwd/ and typed in the words: [General] EnableNetworkConfiguration=true and saved it. Next I removed the following lines from /var/lib/iwd/whitecollar.psk as you have suggested: [IPv4] Address=192.168.30.115 Netmask=255.255.255.0 Gateway=192.168.30.1 Broadcast=192.168.30.255 DNS=8.8.8.8 and saved the changes. After a reboot, I typed the following word at the command prompt: iwctl Next, I typed station wlan0 show The output was: No device found
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thursday, September 30, 2021 09:19:45 AM Stella Ashburne wrote: > Do you think any one of them will reply to my email? It's a long shot, I > know. You don't have much to lose by sending an email. If it would require a long email that would take you a fair amount of time to write, you might write a short one just asking if they'd be willing to read your longer one if you composed / sent it. Back in my working (for pay) days, I was quite often gratified by the responses I got from some companies to my letters or emails requesting assistance without a contractual relationship. Notably (I won't remember them all), but DEC (Digital Equipment) and Rockwell Automation.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Thu, Sep 30, 2021 at 03:19:45PM +0200, Stella Ashburne wrote: > Hi > > > Sent: Thursday, September 30, 2021 at 2:29 PM > > From: to...@tuxteam.de > > To: debian-user@lists.debian.org > > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > > Connection status show OK but unable to surf the net) > > > > I don't know about iwd specifically, but given address and > > netmask it should be able to reasonably infer a default > > broadcast. So I'd say "yes, but ask iwd" ;-) > > > Somehow I managed to find out the email addresses of the developers of iwd > (who are all from Intel). > > Do you think any one of them will reply to my email? It's a long shot, I know. > That depends. How did you get their e-mail address? Was it from the project webpage? Do they encourage anybody to send them direct mail? Them yes. What baffels me is though, at what length someone would go to not use the default methods to connect via wifi. Especially when they showed limited experience in networking in the first place. -H -- Henning Follmann | hfollm...@itcfollmann.com
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi Dan, Thanks for your reply. > Sent: Thursday, September 30, 2021 at 6:06 AM > From: "Dan Ritter" > To: "Stella Ashburne" > Cc: "debian-user mailing list" > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > > Might I suggest wicd, which people here do have experience with > and have used successfully? > Before writing this reply, I checked with packages.debian.org and I couldn't find the package wicd in Debian's official list of packages for Debian 11. It seems that it's been removed for some reasons.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hola David > Sent: Thursday, September 30, 2021 at 1:22 PM > From: "David Wright" > To: debian-user@lists.debian.org > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > > So the WiFi's SSID is whitecollar (all lower case)? > Si Señor > > [Security] > > PreSharedKey=a long string of alphanumeric characters > > Passphrase=aquickbrownfoxjumpsoverthelazydog > > I take it that you edited in the passphrase, and iwd wrote > the PreSharedKey into the file itself? > Yes, before I submitted my post to lists.debian.org, I changed my passphrase to aquickbrownfoxjumpsoverthelazydog > > [IPv4] > > Address=192.168.30.115 > > Netmask=255.255.255.0 > > Gateway=192.168.30.1 > > Broadcast=192.168.30.255 > > DNS=8.8.8.8 > > Where did you get the number 115 from? > My dear David, I plucked it out of thin air. Mea culpa, mea maxima culpa?? I could have just typed 130 instead of 115. > It's claimed that iwd can do DHCP itself. For this, you'd drop > the [IPv4] paragraph above, and instead put > > [General] > EnableNetworkConfiguration=true > into /etc/iwd/main.conf (create if necessary). > Yes, I think ArchLinux's wiki mentions that starting with iwd's version 0.9, the latter can do DHCP... > > Please note that I have disabled IPv6 by adding the line > > > > GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet" > > > > to /etc/default/grub > > It's claimed that iwd only configures IPv6 if you have > > [Network] > EnableIPv6=true > > in /etc/iwd/main.conf. > That's absolutely correct. In fact according to the same ArchLinux's wiki, with iwd, support for IPv6 is disabled by default.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi David > Sent: Thursday, September 30, 2021 at 1:25 PM > From: "David Wright" > To: debian-user@lists.debian.org > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > > Err, not with bullseye. That's why I'm interested to see how Stella > gets on with iwd — > Me too. I'm keen to know why I'm unable to surf the net even after iwd has connected my machine to my wireless network.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi Thanks for sharing your experience with me. > Sent: Thursday, September 30, 2021 at 2:38 PM > From: "riveravaldez" > To: debian-user@lists.debian.org > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > > Hi, my case was similar, while in Debian I use just /etc/network/interfaces > file or NM, in a Dell laptop with Arch I was using Wicd until it got more > or less abandoned and out of official repositories (like in Debian, IIRC), You're right. Before writing this reply, I checked for the latest version of wicd on packages.debian.org and the latter returned zero results. > so, following Arch wiki instructions, I changed Wicd for the > systemd-networkd+iwd combo, and the Wi-Fi connections are working > fine (previously, wpa_supplicant gave me some persistent problems...). > So, I can say that it's a pretty functional and simple tool for the task. > Meaning, it works. > According to some tutorials that I found on the internet, it's advisable to remove/uninstall wpa_supplicant before using iwd due to potential conflicts. As for your statement "..I changed Wicd for the systemd-networkd+iwd combo...", how did you do it? Could you share how you used systemd-networkd with iwd please? I'm still learning Linux, you know and I appreciate all the help that everyone here is willing to give.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi > Sent: Thursday, September 30, 2021 at 2:29 PM > From: to...@tuxteam.de > To: debian-user@lists.debian.org > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > I don't know about iwd specifically, but given address and > netmask it should be able to reasonably infer a default > broadcast. So I'd say "yes, but ask iwd" ;-) > Somehow I managed to find out the email addresses of the developers of iwd (who are all from Intel). Do you think any one of them will reply to my email? It's a long shot, I know.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On 9/30/21, David Wright wrote: > On Wed 29 Sep 2021 at 18:06:12 (-0400), Dan Ritter wrote: > >> [ … ] However, while I know a fair amount about >> networking, I don't know anything about iwd. >> >> Very few people here have experience with iwd. It does not yet >> seem to be working for you. >> >> Might I suggest wicd, which people here do have experience with >> and have used successfully? > > Err, not with bullseye. That's why I'm interested to see how Stella > gets on with iwd — I have to switch WiFi client from wicd, and have > no particular reason to favour wpa_supplicant. Hi, my case was similar, while in Debian I use just /etc/network/interfaces file or NM, in a Dell laptop with Arch I was using Wicd until it got more or less abandoned and out of official repositories (like in Debian, IIRC), so, following Arch wiki instructions, I changed Wicd for the systemd-networkd+iwd combo, and the Wi-Fi connections are working fine (previously, wpa_supplicant gave me some persistent problems...). So, I can say that it's a pretty functional and simple tool for the task. Meaning, it works. Just my cents of noise ;) Kind regards and thanks to everybody!
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Wed, Sep 29, 2021 at 11:18:16PM +0200, Stella Ashburne wrote: > Hi Dan > > > Sent: Thursday, September 30, 2021 at 3:09 AM > > From: "Dan Ritter" > > To: "Stella Ashburne" > > Cc: "debian-user mailing list" > > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > > Connection status show OK but unable to surf the net) > > > > Stella Ashburne wrote: > > > Hi Dan > > > > > > Setting static IP address in network configuration > > > Add the following section to /var/lib/iwd/network.type file. For example: > > > > > > /var/lib/iwd/spaceship.psk > > > [IPv4] > > > Address=192.168.1.10 > > > Netmask=255.255.255.0 > > > Gateway=192.168.1.1 > > > Broadcast=192.168.1.255 > > > DNS=192.168.1.1 > > > > > > In the above example the broadcast IP is 192.168.1.255. > > > > > > Question: Does the fourth octet have to be 255? > > > > Technically, no. In practice, you are unlikely to see anything > > else unless you are configuring point-to-point router links. > > > Just to confirm that I understood your statement correctly: can I omit the > line Broadcast=192.168.1.255 in the file spaceship.psk? I don't know about iwd specifically, but given address and netmask it should be able to reasonably infer a default broadcast. So I'd say "yes, but ask iwd" ;-) Cheers - t signature.asc Description: Digital signature
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Wed 29 Sep 2021 at 18:06:12 (-0400), Dan Ritter wrote: > [ … ] However, while I know a fair amount about > networking, I don't know anything about iwd. > > Very few people here have experience with iwd. It does not yet > seem to be working for you. > > Might I suggest wicd, which people here do have experience with > and have used successfully? Err, not with bullseye. That's why I'm interested to see how Stella gets on with iwd — I have to switch WiFi client from wicd, and have no particular reason to favour wpa_supplicant. Cheers, David.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Wed 29 Sep 2021 at 15:18:44 (+0200), Stella Ashburne wrote: > > Sent: Wednesday, September 29, 2021 at 4:45 AM > > From: "Dan Ritter" > > > > Try > > > > sudo dhclient wlan0 > > > > and see if that gives you an IP and a default route, at which > > point apt update should work. > > > > I tried the command: > > sudo dhclient wlan0 > > and no result (nothing) appeared. I'm not sure exactly what *should* appear. Normally, I read about DHCP's actions in the logs. Anyway … > May I refer you to the sub-section titled "Setting static IP address in > network configuration" of ArchLinux' wiki on iwd > (https://wiki.archlinux.org/title/Iwd). > > My file whitecollar.psk located in /var/lib/iwd/ has the following contents: So the WiFi's SSID is whitecollar (all lower case)? > [Security] > PreSharedKey=a long string of alphanumeric characters > Passphrase=aquickbrownfoxjumpsoverthelazydog I take it that you edited in the passphrase, and iwd wrote the PreSharedKey into the file itself? > [IPv4] > Address=192.168.30.115 > Netmask=255.255.255.0 > Gateway=192.168.30.1 > Broadcast=192.168.30.255 > DNS=8.8.8.8 Where did you get the number 115 from? It's claimed that iwd can do DHCP itself. For this, you'd drop the [IPv4] paragraph above, and instead put [General] EnableNetworkConfiguration=true into /etc/iwd/main.conf (create if necessary). > Please note that I have disabled IPv6 by adding the line > > GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet" > > to /etc/default/grub It's claimed that iwd only configures IPv6 if you have [Network] EnableIPv6=true in /etc/iwd/main.conf. Cheers, David.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Wed, 29 Sep 2021 15:04:21 +0200 Stella Ashburne wrote: > What is the exact location of .emacs file? ~/.emacs In case you don't speak fluent Unix, the tilde (~) expands to the user's home directory. So that is a shorthand way of saying, $HOME/.emacs "Dot files", files with a leading dot, are normally hidden by ls and other directory tools. To see then, "ls -a". "man ls" for more information. -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Stella Ashburne wrote: > Hi Dan > > > Sent: Thursday, September 30, 2021 at 3:09 AM > > From: "Dan Ritter" > > To: "Stella Ashburne" > > Cc: "debian-user mailing list" > > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > > Connection status show OK but unable to surf the net) > > > > Stella Ashburne wrote: > > > Hi Dan > > > > > > Setting static IP address in network configuration > > > Add the following section to /var/lib/iwd/network.type file. For example: > > > > > > /var/lib/iwd/spaceship.psk > > > [IPv4] > > > Address=192.168.1.10 > > > Netmask=255.255.255.0 > > > Gateway=192.168.1.1 > > > Broadcast=192.168.1.255 > > > DNS=192.168.1.1 > > > > > > In the above example the broadcast IP is 192.168.1.255. > > > > > > Question: Does the fourth octet have to be 255? > > > > Technically, no. In practice, you are unlikely to see anything > > else unless you are configuring point-to-point router links. > > > Just to confirm that I understood your statement correctly: can I omit the > line Broadcast=192.168.1.255 in the file spaceship.psk? I doubt it. However, while I know a fair amount about networking, I don't know anything about iwd. Very few people here have experience with iwd. It does not yet seem to be working for you. Might I suggest wicd, which people here do have experience with and have used successfully? -dsr-
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
> Sent: Thursday, September 30, 2021 at 3:36 AM > From: "Greg Wooledge" > To: debian-user@lists.debian.org > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > [.} > > It's also worth pointing out that these bitwise operations are *lightning* > fast for computers to do. They're extremely efficient. CPUs have > dedicated circuitry to do them. > Thanks Greg for the detailed tutorial on what netmask is and does. > Let's get back to Debian for a moment. > > Debian doesn't use "iwd" (whatever that is) to configure network > interfaces. Whatever created this file, it's not being used. > Oh. > Debian uses /etc/network/intefaces, which is a file documented by > the man page interfaces(5). Any interface that's correctly defined in > this file will be configured by it. > I confirm that /etc/network/interfaces has been correctly configured because I am able to use a wired LAN connection to sudo apt upgrade and what not. > If network-manager (NM) is installed, it will try to configure any > interfaces that are *not* defined in /etc/network/interfaces. On some > systems, this means NM is the primary means of configuring interfaces. > On others, it may only do the wireless interfaces, while /e/n/i does > the ethernet ones. On still other systems, NM might do nothing, or it > might not even be installed at all. > Thanks again for the detailed explanation about what NM does. However according to the tutorials that I read on the internet, NM and wpasupplicant must be uninstalled prior to installing the package iwd. > Debian also allows you to configure interfaces using some crazy systemd > thing. This isn't done by any of the supported installation task sets. > What did you mean by "installation task sets"? Did you mean the tasksel stage of the installation process where we get to choose to install a Gnome DE, KDE DE, LXQT DE etc?
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi Dan > Sent: Thursday, September 30, 2021 at 3:09 AM > From: "Dan Ritter" > To: "Stella Ashburne" > Cc: "debian-user mailing list" > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > Stella Ashburne wrote: > > Hi Dan > > > > Setting static IP address in network configuration > > Add the following section to /var/lib/iwd/network.type file. For example: > > > > /var/lib/iwd/spaceship.psk > > [IPv4] > > Address=192.168.1.10 > > Netmask=255.255.255.0 > > Gateway=192.168.1.1 > > Broadcast=192.168.1.255 > > DNS=192.168.1.1 > > > > In the above example the broadcast IP is 192.168.1.255. > > > > Question: Does the fourth octet have to be 255? > > Technically, no. In practice, you are unlikely to see anything > else unless you are configuring point-to-point router links. > Just to confirm that I understood your statement correctly: can I omit the line Broadcast=192.168.1.255 in the file spaceship.psk?
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi. On Wed, Sep 29, 2021 at 03:36:29PM -0400, Greg Wooledge wrote: > Debian doesn't use "iwd" (whatever that is) to configure network > interfaces. Whatever created this file, it's not being used. That statement is incorrect. Even then "Debian" actually means "an OS installation", iwd is a part of the main archive, iwd can be installed by user, and iwd can be used to configure IEEE 802.11-compliant network interface. Whenever the file mentioned should be used by iwd in any way is a different question, of course. > Debian uses /etc/network/intefaces, which is a file documented by the > man page interfaces(5). Any interface that's correctly defined in this > file will be configured by it. Not entirely correct. interfaces(5) is only used by either ifupdown or ifupdown2. While the former has "important" priority (the latter is "optional") in bullseye, it's still possible to run Debian, but have no ifupdown or ifupdown2 installed. And even the "correct configuration" of IEEE 802.11-compliant interface at interfaces(5) will do no good unless wpasupplicant (which has "optional" priority) is installed. > If network-manager (NM) is installed, it will try to configure any > interfaces that are *not* defined in /etc/network/interfaces. Pretty accurate description, barring the fact that NetworkManager by itself cannot actually configure 802.11-compliant device. It uses wpasupplicant (which iwd is an alternative for) to do that. > Debian also allows you to configure interfaces using some crazy systemd > thing. Such a harsh description of a poor systemd-networkd. And calling a simple set of plain-text configuration files "crazy" is way too close to exaggeration. "No popular Linux distribution is using systemd-networkd by default" is much closer to the truth. Reco
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
On Wed, Sep 29, 2021 at 03:09:55PM -0400, Dan Ritter wrote:
> Stella Ashburne wrote:
> > [IPv4]
> > Address=192.168.1.10
> > Netmask=255.255.255.0
> > Gateway=192.168.1.1
> > Broadcast=192.168.1.255
> > DNS=192.168.1.1
> >
> > In the above example the broadcast IP is 192.168.1.255.
> >
> > Question: Does the fourth octet have to be 255?
>
> Technically, no. In practice, you are unlikely to see anything
> else unless you are configuring point-to-point router links.
A 32-bit IPv4 address actually consists of two pieces: a network
address, and a host address. The netmask determines where the separation
is between these two pieces.
A netmask address is always a contiguous set of "1" bits followed by a
contiguous set of "0" bits. There are 32 bits altogether. The only
thing that matters is how many "1" bits there are, which determines the
length of the network address piece.
Thus, in more modern notations, the netmask is often written as a simple
number with a slash before it. Your 255.255.255.0 netmask can also be
written as "/24", because it has 24 "1" bits and 8 "0" bits.
Here's how that works. "255" is a number written in base 10. But if
we write it in binary (base 2), it looks like this:
So, the binary representation of your netmask 255.255.255.0 is:
That's 24 "1" bits, and 8 "0" bits, written out in long form.
Now, why on earth do we care what it looks like in base 2? Because of
how it's used. The netmask is called a "mask" because it can be overlaid
on top of another number. It blocks out certain pieces, and lets other
pieces show through. This is done with bitwise arithmetic operations
("AND", "OR" and "NOT").
To see it in action, let's apply this netmask to your IPv4 address, which
in the example above is 192.168.1.10.
We write this address out in base 2:
1100 10101000 0001 1010
Now write it out with the netmask right underneath it:
1100 10101000 0001 1010 (192.168.1.10)
(255.255.255.0)
Now we use bitwise AND to get the network address piece. We look at each
column individually. If both values are "1", the result is "1". Otherwise,
the result is "0". This gives us:
1100 10101000 0001 1010 (192.168.1.10)
(255.255.255.0)
1100 10101000 0001 (192.168.1.0)
And voila: the network address is 192.168.1.0.
The "mask" part works like this: all of the "1"s are like open space
in a physical mask. They let the underlying image come through. All of
the "0"s are opaque material. They hide whatever's underneath.
So, you're only seeing the piece of the underlying address that lines
up with the "1"s in the mask.
Now, you might be thinking: "Hey, I could have just chopped off the
last digit of the IPv4 address and replaced it with a 0! What's with
all this binary nonsense?!"
That assertion is correct for a /24 netmask only. It's a special case.
The bitwise arithmetic tells us how it works in general, with other
netmasks that aren't multiples of 8.
Finally, let's demonstrate how we get the host address piece. For this,
we invert ("NOT") the bits of the netmask, and then "AND" it with the
IPv4 address:
Inverting the netmask gives us:
Applying the inverted mask gives:
1100 10101000 0001 1010 (192.168.1.10)
(0.0.0.255)
1010 (0.0.0.10)
So, the host address part is 0.0.0.10. This identifies the unique
device on the network.
Once again, this looks overly complicated because we're dealing with a
special case, where the number of bits in the netmask is a multiple of 8.
In the general case, where the netmask could be something like /29, the
host address could be a part of a byte, and not easily spotted in the
base 10 "dotted quad" notation that we normally use.
It's also worth pointing out that these bitwise operations are *lightning*
fast for computers to do. They're extremely efficient. CPUs have
dedicated circuitry to do them.
Let's get back to Debian for a moment.
Debian doesn't use "iwd" (whatever that is) to configure network
interfaces. Whatever created this file, it's not being used.
Debian uses /etc/network/intefaces, which is a file documented by
the man page interfaces(5). Any interface that's correctly defined in
this file will be configured by it.
If network-manager (NM) is installed, it will try to configure any
interfaces that are *not* defined in /etc/network/interfaces. On some
systems, this means NM is the primary means of configuring interfaces.
On others, it may only do the wireless interfaces, while /e/n/i does
the ethernet ones. On still other systems, NM might do nothing, or it
might not even be installed at all.
Debian also allows you to configure interfaces using some crazy systemd
thing. This isn't done by any of the supported installation task sets.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Stella Ashburne wrote: > Hi Dan > > Setting static IP address in network configuration > Add the following section to /var/lib/iwd/network.type file. For example: > > /var/lib/iwd/spaceship.psk > [IPv4] > Address=192.168.1.10 > Netmask=255.255.255.0 > Gateway=192.168.1.1 > Broadcast=192.168.1.255 > DNS=192.168.1.1 > > In the above example the broadcast IP is 192.168.1.255. > > Question: Does the fourth octet have to be 255? Technically, no. In practice, you are unlikely to see anything else unless you are configuring point-to-point router links. -dsr-
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi Dan > Sent: Wednesday, September 29, 2021 at 10:08 PM > From: "Dan Ritter" > To: "Stella Ashburne" > Cc: "debian-user mailing list" > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > > You are using Debian, right? > > Yes I do. In fact Debian 11/Bullseye is my distro. > > Different distros do things differently. > Based on my experience with using ArchLinux's tutorials, I have been able to get all of my stuff done on Debian without problems. After all both are Linux distros. It's not like one of them belongs to *BSD family while the other belongs to Linux family. > > > I have no experience using 'iwd', so what I mean is that I > cannot spot a problem in your config. > Let's have a look at ArchLinux's wiki's example (https://wiki.archlinux.org/title/Iwd) which I reproduce here: Setting static IP address in network configuration Add the following section to /var/lib/iwd/network.type file. For example: /var/lib/iwd/spaceship.psk [IPv4] Address=192.168.1.10 Netmask=255.255.255.0 Gateway=192.168.1.1 Broadcast=192.168.1.255 DNS=192.168.1.1 In the above example the broadcast IP is 192.168.1.255. Question: Does the fourth octet have to be 255? > > > then it should assign > > > 192.168.0.30.115 to wlan0 and > > > > > > ip addr show > > > > > > should show that assignation. Does it? > > > > > No, it doesn't. > > Then iwd is not setting up your interface, or your config is > wrong. > Oh dear! This is bad news :(
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Stella Ashburne wrote: > Hi Dan > > > Sent: Wednesday, September 29, 2021 at 9:30 PM > > From: "Dan Ritter" > > To: "Stella Ashburne" > > Cc: "debian-user mailing list" > > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > > Connection status show OK but unable to surf the net) > > > > > > If that's correct configuration for iwd, > > What did you mean by "correct configuration"? I based my .psk file on the > sample provided by ArchLinux's wiki on iwd You are using Debian, right? Different distros do things differently. I have no experience using 'iwd', so what I mean is that I cannot spot a problem in your config. > > then it should assign > > 192.168.0.30.115 to wlan0 and > > > > ip addr show > > > > should show that assignation. Does it? > > > No, it doesn't. Then iwd is not setting up your interface, or your config is wrong. -dsr-
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi Dan > Sent: Wednesday, September 29, 2021 at 9:30 PM > From: "Dan Ritter" > To: "Stella Ashburne" > Cc: "debian-user mailing list" > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > > If that's correct configuration for iwd, What did you mean by "correct configuration"? I based my .psk file on the sample provided by ArchLinux's wiki on iwd > then it should assign > 192.168.0.30.115 to wlan0 and > > ip addr show > > should show that assignation. Does it? > No, it doesn't.
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Stella Ashburne wrote: > Hi Dan > > Thanks for your reply. > > May I refer you to the sub-section titled "Setting static IP address in > network configuration" of ArchLinux' wiki on iwd > (https://wiki.archlinux.org/title/Iwd). > > My file whitecollar.psk located in /var/lib/iwd/ has the following contents: > > [Security] > PreSharedKey=a long string of alphanumeric characters > Passphrase=aquickbrownfoxjumpsoverthelazydog > > [IPv4] > Address=192.168.30.115 > Netmask=255.255.255.0 > Gateway=192.168.30.1 > Broadcast=192.168.30.255 > DNS=8.8.8.8 If that's correct configuration for iwd, then it should assign 192.168.0.30.115 to wlan0 and ip addr show should show that assignation. Does it? -dsr-
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi Dan Thanks for your reply. > Sent: Wednesday, September 29, 2021 at 4:45 AM > From: "Dan Ritter" > To: "Stella Ashburne" > Cc: "debian-user mailing list" > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > > Try > > sudo dhclient wlan0 > > and see if that gives you an IP and a default route, at which > point apt update should work. > I tried the command: sudo dhclient wlan0 and no result (nothing) appeared. May I refer you to the sub-section titled "Setting static IP address in network configuration" of ArchLinux' wiki on iwd (https://wiki.archlinux.org/title/Iwd). My file whitecollar.psk located in /var/lib/iwd/ has the following contents: [Security] PreSharedKey=a long string of alphanumeric characters Passphrase=aquickbrownfoxjumpsoverthelazydog [IPv4] Address=192.168.30.115 Netmask=255.255.255.0 Gateway=192.168.30.1 Broadcast=192.168.30.255 DNS=8.8.8.8 Please note that I have disabled IPv6 by adding the line GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1 quiet" to /etc/default/grub
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Hi guys Thanks for your replies. > Sent: Wednesday, September 29, 2021 at 6:20 AM > From: "Jude DaShiell" > To: "Dan Ritter" , "Stella Ashburne" > , "debian-user mailing list" > Subject: Re: iwd: Using iwd to connect to a wireless network (Part 1 - > Connection status show OK but unable to surf the net) > > Have you got: > (setq gnutls-algorithm-priority "NORMAL:-VERS-TLS1.3") > in your .emacs file? The internet broke for emacs a while ago and this > line fixed that problem. It may also have done some other things as well. > > What is the exact location of .emacs file?
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Have you got: (setq gnutls-algorithm-priority "NORMAL:-VERS-TLS1.3") in your .emacs file? The internet broke for emacs a while ago and this line fixed that problem. It may also have done some other things as well. On Tue, 28 Sep 2021, Dan Ritter wrote: > Stella Ashburne wrote: > > Based on ArchLinux's tutorial on using iwd to connect to a wireless network > > (https://wiki.archlinux.org/title/Iwd), I managed to connect to my wireless > > routeror so I thought :( > > > > Below are the relevant outputs: > > > > Station: wlan0 > >* > > > > Settable PropertyValue > > > > Scanningno > > State connected > > Connected network Stella-Network > > ConnectedBss2b:ef:6a:20:ac:18 > > > username@hostname:~$ sudo apt update > > > > Result: sudo apt update is unable to update the repositories specified in > > /etc/apt/sources.list. I tried to use Firefox to browse the internet to no > > avail. > > You appear to have established a wifi connection, but not > assigned an IP address. > > Try > > sudo dhclient wlan0 > > and see if that gives you an IP and a default route, at which > point apt update should work. > > -dsr- > >
Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)
Stella Ashburne wrote: > Based on ArchLinux's tutorial on using iwd to connect to a wireless network > (https://wiki.archlinux.org/title/Iwd), I managed to connect to my wireless > routeror so I thought :( > > Below are the relevant outputs: > > Station: wlan0 > * > > Settable PropertyValue > > Scanningno > State connected > Connected network Stella-Network > ConnectedBss2b:ef:6a:20:ac:18 > username@hostname:~$ sudo apt update > > Result: sudo apt update is unable to update the repositories specified in > /etc/apt/sources.list. I tried to use Firefox to browse the internet to no > avail. You appear to have established a wifi connection, but not assigned an IP address. Try sudo dhclient wlan0 and see if that gives you an IP and a default route, at which point apt update should work. -dsr-
