On Du, 12 iul 20, 03:56:57, Marco d'Itri wrote:
> On Jul 11, Jonas Smedegaard wrote:
>
> > > (Way more people should switch from wpa_supplicant to iwd.)
> >
> > Difficult when network-manager depends (not recommends) wpa-supplicant:
> > https://bugs.debian.org/919619
> How to switch to iwd:
>
Quoting Marc Haber (2020-07-14 16:05:28)
> On Sun, 12 Jul 2020 03:56:57 +0200, Marco d'Itri wrote:
> >On Jul 11, Jonas Smedegaard wrote:
> >
> >> > (Way more people should switch from wpa_supplicant to iwd.)
> >>
> >> Difficult when network-manager depends (not recommends) wpa-supplicant:
> >>
On Sun, 12 Jul 2020 03:56:57 +0200, Marco d'Itri wrote:
>On Jul 11, Jonas Smedegaard wrote:
>
>> > (Way more people should switch from wpa_supplicant to iwd.)
>>
>> Difficult when network-manager depends (not recommends) wpa-supplicant:
>> https://bugs.debian.org/919619
>How to switch to iwd:
>
Quoting Russell Stuart (2020-07-13 00:16:01)
> On Sat, 2020-07-11 at 22:12 -0400, The Wanderer wrote:
> > I don't run either systemd or NetworkManager, and I'm not currently
> > interested in changing either of those things, but I am interested
> > in trying out an alternative to wpa_supplicant.
Quoting Luca Capello (2020-07-14 13:44:17)
> Hi there,
>
> On Sun, 12 Jul 2020 19:15:47 +, Jeremy Stanley wrote:
> > On 2020-07-12 20:35:56 +0200 (+0200), Jonas Smedegaard wrote:
> > [...]
> > > What is (unusual but) usable, however, is to *not* use Network
> > > Manager for wifi, but use
Hi there,
On Sun, 12 Jul 2020 19:15:47 +, Jeremy Stanley wrote:
> On 2020-07-12 20:35:56 +0200 (+0200), Jonas Smedegaard wrote:
> [...]
> > What is (unusual but) usable, however, is to *not* use Network
> > Manager for wifi, but use IWD+systemd or IWD standalone for wifi,
> > and use Network
On Sat, 2020-07-11 at 22:12 -0400, The Wanderer wrote:
> I don't run either systemd or NetworkManager, and I'm not currently
> interested in changing either of those things, but I am interested in
> trying out an alternative to wpa_supplicant. Is there an appropriate
> similar procedure for such
On 2020-07-12 20:35:56 +0200 (+0200), Jonas Smedegaard wrote:
[...]
> What is (unusual but) usable, however, is to *not* use Network
> Manager for wifi, but use IWD+systemd or IWD standalone for wifi,
> and use Network Manager to manage _other_ network components.
>
> In such unusual-but-real
Quoting Andrey Rahmatullin (2020-07-12 20:00:23)
> On Sun, Jul 12, 2020 at 08:29:08PM +0300, Andrei POPESCU wrote:
> > > Network-Manager needing wpa-supplicant in _most_ situations is a reason
> > > to _recommend_ it not a reason to _depend_ on it, per Debian Policy!
> >
> > If Network Manager
On Sun, Jul 12, 2020 at 08:29:08PM +0300, Andrei POPESCU wrote:
> > Network-Manager needing wpa-supplicant in _most_ situations is a reason
> > to _recommend_ it not a reason to _depend_ on it, per Debian Policy!
>
> If Network Manager needs to depend on the wireless component, that could
>
On Du, 12 iul 20, 13:33:13, Jonas Smedegaard wrote:
>
> Network-Manager needing wpa-supplicant in _most_ situations is a reason
> to _recommend_ it not a reason to _depend_ on it, per Debian Policy!
If Network Manager needs to depend on the wireless component, that could
probably be:
Quoting Andrey Rahmatullin (2020-07-12 16:27:16)
> On Sun, Jul 12, 2020 at 01:07:37PM +0200, Jonas Smedegaard wrote:
> > How to use iwd without NetworkManager or systemd:
> >
> > apt install iwd resolvconf
> > cat << END > /etc/NetworkManager/conf.d/iwd.conf
> "without NetworkManager" yet
On Sun, Jul 12, 2020 at 01:07:37PM +0200, Jonas Smedegaard wrote:
> How to use iwd without NetworkManager or systemd:
>
> apt install iwd resolvconf
> cat << END > /etc/NetworkManager/conf.d/iwd.conf
"without NetworkManager" yet "/etc/NetworkManager/conf.d"? What will read
this config?
--
WBR,
Quoting Andrey Rahmatullin (2020-07-12 09:34:32)
> On Sun, Jul 12, 2020 at 02:02:50AM +0200, Jonas Smedegaard wrote:
> > > > Difficult when network-manager depends (not recommends) wpa-supplicant:
> > > > https://bugs.debian.org/919619
> > > That Depends is not a problem.
> >
> > Yes a problem,
Quoting Marco d'Itri (2020-07-12 03:56:57)
> On Jul 11, Jonas Smedegaard wrote:
>
> > > (Way more people should switch from wpa_supplicant to iwd.)
> >
> > Difficult when network-manager depends (not recommends) wpa-supplicant:
> > https://bugs.debian.org/919619
> How to switch to iwd:
>
> apt
Quoting The Wanderer (2020-07-12 04:12:54)
> On 2020-07-11 at 21:56, Marco d'Itri wrote:
>
> > On Jul 11, Jonas Smedegaard wrote:
> >
> >>> (Way more people should switch from wpa_supplicant to iwd.)
> >>
> >> Difficult when network-manager depends (not recommends) wpa-supplicant:
> >>
On Sun, Jul 12, 2020 at 12:34:32PM +0500, Andrey Rahmatullin wrote:
> On Sun, Jul 12, 2020 at 02:02:50AM +0200, Jonas Smedegaard wrote:
> > > > Difficult when network-manager depends (not recommends) wpa-supplicant:
> > > > https://bugs.debian.org/919619
> > > That Depends is not a problem.
> >
>
On Sun, Jul 12, 2020 at 02:02:50AM +0200, Jonas Smedegaard wrote:
> > > Difficult when network-manager depends (not recommends) wpa-supplicant:
> > > https://bugs.debian.org/919619
> > That Depends is not a problem.
>
> Yes a problem, but not a unsurmountable one: You can...
>
> a) pollute your
On 2020-07-11 at 21:56, Marco d'Itri wrote:
> On Jul 11, Jonas Smedegaard wrote:
>
>>> (Way more people should switch from wpa_supplicant to iwd.)
>>
>> Difficult when network-manager depends (not recommends) wpa-supplicant:
>> https://bugs.debian.org/919619
>
> How to switch to iwd:
>
> apt
On Jul 11, Jonas Smedegaard wrote:
> > (Way more people should switch from wpa_supplicant to iwd.)
>
> Difficult when network-manager depends (not recommends) wpa-supplicant:
> https://bugs.debian.org/919619
How to switch to iwd:
apt install iwd
cat << END > /etc/NetworkManager/conf.d/iwd.conf
Quoting Andrey Rahmatullin (2020-07-11 22:21:22)
> On Sat, Jul 11, 2020 at 10:08:11PM +0200, Jonas Smedegaard wrote:
> > > (Way more people should switch from wpa_supplicant to iwd.)
> >
> > Difficult when network-manager depends (not recommends) wpa-supplicant:
> > https://bugs.debian.org/919619
On Sun, Jul 12, 2020 at 01:21:22AM +0500, Andrey Rahmatullin wrote:
> On Sat, Jul 11, 2020 at 10:08:11PM +0200, Jonas Smedegaard wrote:
> > > (Way more people should switch from wpa_supplicant to iwd.)
> >
> > Difficult when network-manager depends (not recommends) wpa-supplicant:
> >
On Sat, Jul 11, 2020 at 10:08:11PM +0200, Jonas Smedegaard wrote:
> > (Way more people should switch from wpa_supplicant to iwd.)
>
> Difficult when network-manager depends (not recommends) wpa-supplicant:
> https://bugs.debian.org/919619
That Depends is not a problem.
--
WBR, wRAR
Quoting Marco d'Itri (2020-07-11 19:48:03)
> On Jun 28, Jaime wrote:
>
> > Given that this is guaranteed to fail, isn't it worth "not doing"? Is
> > there anyway that I can get dhclient to wait for a successful
> > connection *before* sending out any DHCPDISCOVERs? (In the wired
> > world, it
On Jun 28, Jaime wrote:
> Given that this is guaranteed to fail, isn't it worth "not doing"? Is
> there anyway that I can get dhclient to wait for a successful
> connection *before* sending out any DHCPDISCOVERs? (In the wired
> world, it doesn't make sense to issue a DHCPDISCOVER before
On 29/06/2020, Simon Richter wrote:
> Hi Jaime,
> Yes, that's a long-standing issue.
> A less portable or featureful client has a greater chance of supporting
> this directly.
>Simon
Timo, Simon and Simon,
Thank you all for your replies. Now that I understand the
issues/background, I'm
Hi Jaime,
On Sun, Jun 28, 2020 at 12:06:02PM +0100, Jaime wrote:
> I noticed that my debian wireless clients never get a DHCPOFFER from
> their first DHCPDISCOVER, and looking at the log shows why:
Yes, that's a long-standing issue.
The difficulty is that the ISC client is written to be very
On Sun, 28 Jun 2020 at 12:06:02 +0100, Jaime wrote:
> I noticed that my debian wireless clients never get a DHCPOFFER from
> their first DHCPDISCOVER
...
> So it's clear that dhclient is sending out the first DHCPDISCOVER
> *before* wpa_supplicant has authenticated/associated/connected to the
>
On Sun, 28 Jun 2020, Jaime wrote:
Given that this is guaranteed to fail, isn't it worth "not doing"? Is
there anyway that I can get dhclient to wait for a successful
connection *before* sending out any DHCPDISCOVERs? (In the wired
world, it doesn't make sense to issue a DHCPDISCOVER before
Hi all.
I noticed that my debian wireless clients never get a DHCPOFFER from
their first DHCPDISCOVER, and looking at the log shows why:
journalctl output (very much shortened/redacted):
09:34:30 sudo[4373]: COMMAND=/usr/sbin/ifup wlp4s0
09:34:30 wpa_supplicant[4384]: Successfully initialized
30 matches
Mail list logo
