David Wright wrote:
I was casting round for a simple way to run iwd + resolvconf +
systemd-networkd as replacement.
I run a similar setup, with iwd, systemd-networkd and systemd-resolved.
This has been working without problems on my host for for quite a while
now.
Make a copy of your /etc/reso
On Mon 14 Mar 2022 at 07:15:12 (+), Thomas Pircher wrote:
> David Wright wrote:
> > I was casting round for a simple way to run iwd + resolvconf +
> > systemd-networkd as replacement.
>
> I run a similar setup, with iwd, systemd-networkd and systemd-resolved.
> This has been working without pr
> iwd Highly functional & low resource & DHCP client.
Thank you for your informative and useful account of iwd. Apologies
if my snipping is too brutal :).
It is almost a no-brainer to eastablish a wireless link with iwd. I
think the single command
iwctl station wlan0 connect Yo
David Wright wrote:
As I said, I tried that.
Ack. I must have glossed over that. Sorry. The rest of my mail stands,
though.
You can configure various settings for the DNS resolver in your
systemd-networkd setting and in /etc/systemd/resolved.conf.
Like what?
Full description here:
https:/
On Thu 17 Mar 2022 at 09:33:30 -0400, Stefan Monnier wrote:
> > However, your post inspired me. The installed size of iwd is a fifth
> > that of wpasuppicant.
>
> I'm curious what is the explanation for that size difference, since from
> a casual look it appears that iwd provides pretty much a su
On Sun 13 Mar 2022 at 20:04:06 -0500, David Wright wrote:
[...]
> By the end of all this, the link should be working, and a file
> like this will have been written (that only root can see):
>
> # cat /var/lib/iwd/YourSSID.psk
> [Security]
> PreSharedKey=abdcef0123456789…abdcef0123456789…abdcef0
I just wanted to say thanks for the post and instructions. I've been
using IWD on a different distro and wish that Debian will someday adopt
it as its default.
On Thu 17 Mar 2022 at 12:12:28 (+), Thomas Pircher wrote:
> David Wright wrote:
> > As I said, I tried that.
>
> Ack. I must have glossed over that. Sorry. The rest of my mail stands,
> though.
>
> > > You can configure various settings for the DNS resolver in your
> > > systemd-networkd sett
On Thu 17 Mar 2022 at 09:33:30 (-0400), Stefan Monnier wrote:
> > However, your post inspired me. The installed size of iwd is a fifth
> > that of wpasuppicant.
>
> I'm curious what is the explanation for that size difference, since from
> a casual look it appears that iwd provides pretty much a s
On Thu 17 Mar 2022 at 14:50:06 (+), Brian wrote:
> On Sun 13 Mar 2022 at 20:04:06 -0500, David Wright wrote:
>
> [...]
>
> > By the end of all this, the link should be working, and a file
> > like this will have been written (that only root can see):
> >
> > # cat /var/lib/iwd/YourSSID.psk
On Wed 16 Mar 2022 at 22:40:07 (+), Brian wrote:
> > iwd Highly functional & low resource & DHCP client.
>
> Thank you for your informative and useful account of iwd. Apologies
> if my snipping is too brutal :).
>
> It is almost a no-brainer to eastablish a wireless link with
On Thu 17 Mar 2022 at 23:39:39 -0500, David Wright wrote:
> On Thu 17 Mar 2022 at 14:50:06 (+), Brian wrote:
> > On Sun 13 Mar 2022 at 20:04:06 -0500, David Wright wrote:
> >
> > [...]
> >
> > > By the end of all this, the link should be working, and a file
> > > like this will have been wri
On Thu 17 Mar 2022 at 23:40:28 -0500, David Wright wrote:
> On Wed 16 Mar 2022 at 22:40:07 (+), Brian wrote:
[...]
> > OTOH, the Debian iwd package
> > does not provide any integration with ifupdown
>
> Does iwd need ifupdown at all? It seems to be able to configure the
> interface itself.
On Thu, Mar 17, 2022, 11:57 PM David Wright
wrote:
> On Thu 17 Mar 2022 at 12:12:28 (+), Thomas Pircher wrote
> >
> > Cool. If you just type resolvectl, it will show you which information it
> > got on each interface.
>
> This is machine F, where /etc/resolv.conf is a file, containing
> 192.1
On Sun 13 Mar 2022 at 20:04:06 -0500, David Wright wrote:
[...]
> Install iwd, and resolvconf if necessary. You may then need to reboot
> if the wifi interface has already been renamed by the kernel, ie if
> it's not wlan0. (With buster, there's a missing file that needs adding
> first; see below
On Fri, 18 Mar 2022 14:32:40 +
Brian wrote:
> Regarding the installer: at present it provides an /e/n/i with wpa-*
> lines. Changing wpasupplicant to iwd in d-i would requir some work.
> No matter what the benefits of iwd are, I do not see that happening
> in the near future. wpasupplicant re
On Fri 18 Mar 2022 at 20:57:38 +, Brian wrote:
> On Sun 13 Mar 2022 at 20:04:06 -0500, David Wright wrote:
>
> [...]
>
> > Install iwd, and resolvconf if necessary. You may then need to reboot
> > if the wifi interface has already been renamed by the kernel, ie if
> > it's not wlan0. (With b
On Sat, Mar 19, 2022 at 7:33 AM Brian wrote:
> On Fri 18 Mar 2022 at 20:57:38 +, Brian wrote:
>
> > On Sun 13 Mar 2022 at 20:04:06 -0500, David Wright wrote:
> >
> > [...]
> >
> > > Install iwd, and resolvconf if necessary. You may then need to reboot
> > > if the wifi interface has already b
On Fri 18 Mar 2022 at 14:08:36 (-0500), Nicholas Geovanis wrote:
> On Thu, Mar 17, 2022, 11:57 PM David Wright wrote:
> > On Thu 17 Mar 2022 at 12:12:28 (+), Thomas Pircher wrote
> > >
> > > Cool. If you just type resolvectl, it will show you which information it
> > > got on each interface.
>
On Fri 18 Mar 2022 at 20:57:38 (+), Brian wrote:
> On Sun 13 Mar 2022 at 20:04:06 -0500, David Wright wrote:
>
> [...]
>
> > Install iwd, and resolvconf if necessary. You may then need to reboot
> > if the wifi interface has already been renamed by the kernel, ie if
> > it's not wlan0. (With
On Sat 19 Mar 2022 at 10:15:45 -0500, David Wright wrote:
> On Fri 18 Mar 2022 at 20:57:38 (+), Brian wrote:
> > On Sun 13 Mar 2022 at 20:04:06 -0500, David Wright wrote:
> >
> > [...]
> >
> > > Install iwd, and resolvconf if necessary. You may then need to reboot
> > > if the wifi interface
On Sat 19 Mar 2022 at 10:12:54 -0500, Nicholas Geovanis wrote:
> On Sat, Mar 19, 2022 at 7:33 AM Brian wrote:
>
> > On Fri 18 Mar 2022 at 20:57:38 +, Brian wrote:
> >
> > > On Sun 13 Mar 2022 at 20:04:06 -0500, David Wright wrote:
> > >
> > > [...]
> > >
> > > > Install iwd, and resolvconf i
Mon cheri
> Sent: Sunday, March 20, 2022 at 2:40 AM
> From: "Brian"
> To: debian-user@lists.debian.org
> Subject: Re: iwd + systemd-networkd + resolvconf wrinkles
>
> In truth, it is not a biggie for my intended use of iwd on some
> non-roaming machines, although i
On Wed 23 Mar 2022 at 13:06:12 (+0100), Stella Ashburne wrote:
> From: "Brian"
> >
> > In truth, it is not a biggie for my intended use of iwd on some
> > non-roaming machines, although it did break my /e/n/i. A couple of
> > edits fixed that.
>
> Would you like to elaborate what stuff was broken
On Sat 19 Mar 2022 at 10:18:49 (+1100), Charlie wrote:
> On Fri, 18 Mar 2022 14:32:40 + Brian wrote:
>
> > Regarding the installer: at present it provides an /e/n/i with wpa-*
> > lines. Changing wpasupplicant to iwd in d-i would requir some work.
> > No matter what the benefits of iwd are, I
On Tue 22 Mar 2022 at 23:06:08 -0500, David Wright wrote:
> On Sat 19 Mar 2022 at 10:18:49 (+1100), Charlie wrote:
> > On Fri, 18 Mar 2022 14:32:40 + Brian wrote:
> >
> > > Regarding the installer: at present it provides an /e/n/i with wpa-*
> > > lines. Changing wpasupplicant to iwd in d-i w
On Tue 22 Mar 2022 at 23:06:08 -0500, David Wright wrote:
> (OTOH wicd appears to be able to detect that the interface has come
> up, and to configure it, DHCP and all. In fact, I've found it more
> reliable for wired interfaces as well, where I suspect glitches have
> been caused by Powerline dev
27 matches
Mail list logo
