all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: On network management and documenting nmcli
Date: Sat, 12 May 2018 19:31:16 -0700	[thread overview]
Message-ID: <87y3goe16z.fsf@gmail.com> (raw)
In-Reply-To: <87in7u33xy.fsf@gmail.com> (Pierre Neidhardt's message of "Fri, 11 May 2018 12:02:49 +0200")

[-- Attachment #1: Type: text/plain, Size: 2890 bytes --]

Pierre Neidhardt <ambrevar@gmail.com> writes:

> During my first encounter with GuixSD, I could not connect to the
> Internet for reasons that puzzled me, and I could not find any mention
> of it in the manual either.
>
> At first I assumed I had done something wrong with the setup.
>
> I had tried to run wpa_supplicant manually, like I often do on other
> distributions.  It's only later that I understood why wpa_supplicant
> failed: it was because it was already running! (It's stupid but
> wpa_supplicant's error messages are extremely misleading.)
>
> The manual is extremely scarse about network configuration.  Sure
> enough, if nm-applet is running it's rather straightforward.  But for a
> desktop-environment-less setup and during the install, the default tool
> is nmcli only (unless another manager is used, but then the user
> probably knows what they are doing).
>
> I don't think any of this is mentioned at all in the manual: I believe
> something so essential should be very explicitly documented.

Did you know we have an example in the manual a (guix) Preparing for
Installation?  Here it is:

--8<---------------cut here---------------start------------->8---
Wireless connection
     To configure wireless networking, you can create a configuration
     file for the ‘wpa_supplicant’ configuration tool (its location is
     not important) using one of the available text editors such as
     ‘nano’:

          nano wpa_supplicant.conf

     As an example, the following stanza can go to this file and will
     work for many wireless networks, provided you give the actual SSID
     and passphrase for the network you are connecting to:

          network={
            ssid="MY-SSID"
            key_mgmt=WPA-PSK
            psk="the network's secret passphrase"
          }

     Start the wireless service and run it in the background with the
     following command (substitute INTERFACE with the name of the
     network interface you want to use):

          wpa_supplicant -c wpa_supplicant.conf -i INTERFACE -B

     Run ‘man wpa_supplicant’ for more information.
--8<---------------cut here---------------end--------------->8---

What do you think of this example?

I think it's good to add an example or two for common use cases and
provide a reference for further reading, but I don't think we should try
to provide an example in the manual for every possible situation.  For
example, if you need to connect over a WEP-"secured" network (which is
not secure at all) using wpa-supplicant, you will need to adjust the
config file, but I don't think even the official wpa-supplicant official
documentation gives you an example of how to do it.  As far as I know,
WPA (WPA2, I guess?) is the preferred and common choice nowadays, so I
think the example is appropriate.

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2018-05-13  2:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 10:02 On network management and documenting nmcli Pierre Neidhardt
2018-05-11 12:21 ` Oleg Pykhalov
2018-05-11 12:57   ` Devan Carpenter
2018-05-11 13:00     ` Pierre Neidhardt
2018-05-11 13:10       ` Devan Carpenter
2018-05-11 13:15         ` Pierre Neidhardt
2018-05-13  7:26         ` Nils Gillmann
2018-05-13 11:08           ` swedebugia
2018-05-13 12:22             ` Nils Gillmann
2018-05-13 12:33               ` Nils Gillmann
2018-05-13  2:31 ` Chris Marusich [this message]
2018-05-13  7:13   ` Pierre Neidhardt
2018-05-13 17:44     ` Chris Marusich
2018-05-13 19:21       ` Pierre Neidhardt
2018-05-22 12:42         ` swedebugia
2018-05-22 15:26           ` Pierre Neidhardt
2018-05-23 15:39           ` Ludovic Courtès
2018-05-23 15:45             ` Pierre Neidhardt
2018-05-23 18:18               ` swedebugia
2018-05-24 12:33               ` Ludovic Courtès
2018-05-24 12:40                 ` Pierre Neidhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y3goe16z.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=ambrevar@gmail.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.