Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #240513 > unrolled thread

iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)

Back to article view | Back to linux.debian.user

Contents

  iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-28 22:30 +0200
    Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Dan Ritter <dsr@randomstring.org> - 2021-09-28 22:50 +0200
      Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Jude DaShiell <jdashiel@panix.com> - 2021-09-29 00:30 +0200
        Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-29 15:10 +0200
          Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Charles Curley <charlescurley@charlescurley.com> - 2021-09-30 04:00 +0200
      Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-29 15:20 +0200
        Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Dan Ritter <dsr@randomstring.org> - 2021-09-29 15:40 +0200
          Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-29 15:50 +0200
            Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Dan Ritter <dsr@randomstring.org> - 2021-09-29 16:20 +0200
              Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-29 20:50 +0200
                Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Dan Ritter <dsr@randomstring.org> - 2021-09-29 21:20 +0200
                  Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Greg Wooledge <greg@wooledge.org> - 2021-09-29 21:40 +0200
                    Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Reco <recoverym4n@enotuniq.net> - 2021-09-29 22:40 +0200
                    Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-29 23:40 +0200
                  Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-29 23:20 +0200
                    Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Dan Ritter <dsr@randomstring.org> - 2021-09-30 00:10 +0200
                      Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) David Wright <deblis@lionunicorn.co.uk> - 2021-09-30 07:30 +0200
                        Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) riveravaldez <riveravaldezmail@gmail.com> - 2021-09-30 08:40 +0200
                          Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-30 15:30 +0200
                            Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) riveravaldez <riveravaldezmail@gmail.com> - 2021-10-01 01:20 +0200
                        Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-30 15:50 +0200
                      Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-30 16:20 +0200
                        Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) David Wright <deblis@lionunicorn.co.uk> - 2021-09-30 20:30 +0200
                    Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) <tomas@tuxteam.de> - 2021-09-30 08:30 +0200
                      Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-30 15:30 +0200
                        Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Henning Follmann <hfollmann@itcfollmann.com> - 2021-09-30 16:20 +0200
                          Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-30 17:00 +0200
                            Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net) rhkramer@gmail.com - 2021-09-30 17:50 +0200
                              Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-30 18:30 +0200
                                Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Dan Ritter <dsr@randomstring.org> - 2021-09-30 18:40 +0200
                                Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net) rhkramer@gmail.com - 2021-09-30 19:40 +0200
                            Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Henning Follmann <hfollmann@itcfollmann.com> - 2021-09-30 18:10 +0200
                          Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) <tomas@tuxteam.de> - 2021-09-30 17:50 +0200
                            Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Henning Follmann <hfollmann@itcfollmann.com> - 2021-09-30 18:30 +0200
                              Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) <tomas@tuxteam.de> - 2021-09-30 19:40 +0200
                                Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Henning Follmann <hfollmann@itcfollmann.com> - 2021-09-30 20:10 +0200
                                  Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) <tomas@tuxteam.de> - 2021-09-30 21:40 +0200
                                Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Brian <ad44@cityscape.co.uk> - 2021-09-30 22:00 +0200
                              Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Brian <ad44@cityscape.co.uk> - 2021-09-30 20:20 +0200
                            Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-30 18:30 +0200
                              Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Lee <ler762@gmail.com> - 2021-09-30 20:20 +0200
                                Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) David Wright <deblis@lionunicorn.co.uk> - 2021-09-30 22:00 +0200
                        Re: iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net) rhkramer@gmail.com - 2021-09-30 16:30 +0200
        Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) David Wright <deblis@lionunicorn.co.uk> - 2021-09-30 07:30 +0200
          Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-30 16:00 +0200
            Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) David Wright <deblis@lionunicorn.co.uk> - 2021-09-30 20:40 +0200
          Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-30 16:40 +0200
            Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Dan Ritter <dsr@randomstring.org> - 2021-09-30 17:20 +0200
              Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Stella Ashburne <rewefie@gmx.com> - 2021-09-30 18:20 +0200
                Re: iwd: Using iwd to connect to a wireless network (Part 1 -  Connection status show OK but unable to surf the net) Dan Ritter <dsr@randomstring.org> - 2021-09-30 18:40 +0200

Page 1 of 3  [1] 2 3  Next page →

#240513 — iwd: Using iwd to connect to a wireless network (Part 1 - Connection status show OK but unable to surf the net)

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 router....or so I thought :(

Below are the relevant outputs:

In Terminal #1

username@hostname:~$ iwctl
[iwd]# device   wlan0   show

                      Device: wlan0                                *
--------------------------------------------------------------------------------
  Settable     Property          Value
--------------------------------------------------------------------------------
               Name              wlan0
      *        Mode              station
      *        Powered           on
               Address           2b:ef:4d:33:c2:e5
               Adapter           phy0




[iwd]# station wlan0 show
                                 Station: wlan0                                *
--------------------------------------------------------------------------------
  Settable  Property            Value
--------------------------------------------------------------------------------
            Scanning            no
            State               connected
            Connected network   Stella-Network
            ConnectedBss        2b:ef:6a:20:ac:18
            Frequency           2412
            Security            WPA2-Personal
            RSSI                -47                  dBm
            AverageRSSI         -47                  dBm
            TxMode              802.11n
            TxMCS               7
            TxBitrate           150000               Kbit/s
            RxBitrate           1000                 Kbit/s


The asterisk to the right of the word wlan0 is always blinking.

In Terminal #2

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.

I appreciate your help in this matter. Thanks.

[toc] | [next] | [standalone]

#240514

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 router....or so I thought :(
> 
> Below are the relevant outputs:
> 
>                                  Station: wlan0                                *
> --------------------------------------------------------------------------------
>   Settable  Property            Value
> --------------------------------------------------------------------------------
>             Scanning            no
>             State               connected
>             Connected network   Stella-Network
>             ConnectedBss        2b: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-

[toc] | [prev] | [next] | [standalone]

#240521

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 router....or so I thought :(
> >
> > Below are the relevant outputs:
> >
> >                                  Station: wlan0                                *
> > --------------------------------------------------------------------------------
> >   Settable  Property            Value
> > --------------------------------------------------------------------------------
> >             Scanning            no
> >             State               connected
> >             Connected network   Stella-Network
> >             ConnectedBss        2b: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-
>
>

[toc] | [prev] | [next] | [standalone]

#240554

Hi guys

Thanks for your replies.

> Sent: Wednesday, September 29, 2021 at 6:20 AM
> From: "Jude DaShiell" <jdashiel@panix.com>
> To: "Dan Ritter" <dsr@randomstring.org>, "Stella Ashburne" <rewefie@gmx.com>, "debian-user mailing list" <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)
>
> 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?

[toc] | [prev] | [next] | [standalone]

#240609

On Wed, 29 Sep 2021 15:04:21 +0200
Stella Ashburne <rewefie@gmx.com> 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/

[toc] | [prev] | [next] | [standalone]

#240555

Hi Dan

Thanks for your reply.

> Sent: Wednesday, September 29, 2021 at 4:45 AM
> From: "Dan Ritter" <dsr@randomstring.org>
> To: "Stella Ashburne" <rewefie@gmx.com>
> Cc: "debian-user mailing list" <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
>
> 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

[toc] | [prev] | [next] | [standalone]

#240557

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-

[toc] | [prev] | [next] | [standalone]

#240559

Hi Dan

> Sent: Wednesday, September 29, 2021 at 9:30 PM
> From: "Dan Ritter" <dsr@randomstring.org>
> To: "Stella Ashburne" <rewefie@gmx.com>
> Cc: "debian-user mailing list" <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)
>
>
> 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.

[toc] | [prev] | [next] | [standalone]

#240561

Stella Ashburne wrote: 
> Hi Dan
> 
> > Sent: Wednesday, September 29, 2021 at 9:30 PM
> > From: "Dan Ritter" <dsr@randomstring.org>
> > To: "Stella Ashburne" <rewefie@gmx.com>
> > Cc: "debian-user mailing list" <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)
> >
> >
> > 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-

[toc] | [prev] | [next] | [standalone]

#240579

Hi Dan

> Sent: Wednesday, September 29, 2021 at 10:08 PM
> From: "Dan Ritter" <dsr@randomstring.org>
> To: "Stella Ashburne" <rewefie@gmx.com>
> Cc: "debian-user mailing list" <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)
>
>
> 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 :(

[toc] | [prev] | [next] | [standalone]

#240581

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-

[toc] | [prev] | [next] | [standalone]

#240584

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: 11111111

So, the binary representation of your netmask 255.255.255.0 is:

11111111 11111111 11111111 00000000

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:

11000000 10101000 00000001 00001010

Now write it out with the netmask right underneath it:

11000000 10101000 00000001 00001010  (192.168.1.10)
11111111 11111111 11111111 00000000  (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:

11000000 10101000 00000001 00001010  (192.168.1.10)
11111111 11111111 11111111 00000000  (255.255.255.0)
11000000 10101000 00000001 00000000  (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:

00000000 00000000 00000000 11111111

Applying the inverted mask gives:

11000000 10101000 00000001 00001010  (192.168.1.10)
00000000 00000000 00000000 11111111  (0.0.0.255)
00000000 00000000 00000000 00001010  (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.
But if you choose, you could read the systemd man pages and figure out
how to do it this way, and then do it.

[toc] | [prev] | [next] | [standalone]

#240594

	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

[toc] | [prev] | [next] | [standalone]

#240598

> Sent: Thursday, September 30, 2021 at 3:36 AM
> From: "Greg Wooledge" <greg@wooledge.org>
> 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?

[toc] | [prev] | [next] | [standalone]

#240596

Hi Dan

> Sent: Thursday, September 30, 2021 at 3:09 AM
> From: "Dan Ritter" <dsr@randomstring.org>
> To: "Stella Ashburne" <rewefie@gmx.com>
> Cc: "debian-user mailing list" <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)
>
> 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?

[toc] | [prev] | [next] | [standalone]

#240601

Stella Ashburne wrote: 
> Hi Dan
> 
> > Sent: Thursday, September 30, 2021 at 3:09 AM
> > From: "Dan Ritter" <dsr@randomstring.org>
> > To: "Stella Ashburne" <rewefie@gmx.com>
> > Cc: "debian-user mailing list" <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)
> >
> > 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-

[toc] | [prev] | [next] | [standalone]

#240620

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.

[toc] | [prev] | [next] | [standalone]

#240624

On 9/30/21, David Wright <deblis@lionunicorn.co.uk> 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!

[toc] | [prev] | [next] | [standalone]

#240638

Hi

Thanks for sharing your experience with me.

> Sent: Thursday, September 30, 2021 at 2:38 PM
> From: "riveravaldez" <riveravaldezmail@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)
>
>
> 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.

[toc] | [prev] | [next] | [standalone]

#240696

On 9/30/21, Stella Ashburne <rewefie@gmx.com> 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" <riveravaldezmail@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)
>>
>>
>> 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

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | linux.debian.user

csiph-web