From: znavko@disroot.org
To: Ricardo Wurmus <rekado@elephly.net>, znavko@tutanota.com
Cc: Help Guix <help-guix@gnu.org>
Subject: Re: wpa-supplicant service configuration. Guile is hard
Date: Sat, 06 Apr 2019 17:55:29 +0000 [thread overview]
Message-ID: <84bec7c771a305a520d0a174753fa320@disroot.org> (raw)
In-Reply-To: <871s2gxv9d.fsf@elephly.net>
Situation is this now:
1. I have wonderful configured services: wpa-supplicant and dhcp-client
2. I see the messages during boot process:
wpa-supplicant successfully initialized
rfkill: WLAN soft blocked
service networking could not be started
3. I open terminal after boot and do this:
su -
rfkill unblock wifi
herd restart networking
4. And I have Internet.
Bios has no wifi blocking. Do not know why wifi comes blocked. Need to know how to unblock. Do I need own service with `rfkill unblock wifi`, and if so, how to run networking service after my own service?
April 6, 2019 4:36 AM, "Ricardo Wurmus" <rekado@elephly.net> wrote:
> znavko@tutanota.com writes:
>
>> Hello! I have several questions about wpa-supplicant + dhcpcd services.
>>
>> First of all I do not want to use networkmanager and I usually get Internet working manually with
>> this:
>> # cat startnet
>> #!/bin/sh
>> #connect to wi-fi through wpa_supplicant
>> herd stop wpa-supplicant
>> rfkill unblock wifi
>> wpa_supplicant -B -i wlp2s0 -c /etc/wpa_supplicant/wpa_supplicant.conf
>> sleep 2
>> dhclient -v wlp2s0
>
> Why do you do this all manually instead of using
> wpa-supplicant-service-type and dhcp-client-service-type?
>
> Your configuration looks … adventurous. Here are some recommendations:
>
> * don’t nest modify-services. Nothing good will come of this. It only
> serves to confuse you. “modify-services” can modify more than one
> service at once.
>
> * don’t leave parentheses on lines all by themselves. They get lonely.
>
> * don’t use dhcpd-service-type unless you want to run a DHCP server.
> Use dhcp-client-service-type for the DHCP *client*.
>
> * you don’t need to add wpa-supplicant to the list of globally installed
> packages. The service is enough.
>
> * maybe try fixing the indentation (Emacs can do this with M-q) — it’s
> very hard to understand the configuration when the indentation tries
> hard to mislead you.
>
> --
> Ricardo
next prev parent reply other threads:[~2019-04-06 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <LbdoDpd--3-1@tutanota.com-LbdrIe9----1>
2019-04-04 20:36 ` wpa-supplicant service configuration. Guile is hard znavko
[not found] ` <Lbe0PNU--3-1@tutanota.com-Lbe3LhE----1>
2019-04-05 9:41 ` znavko
2019-04-05 16:38 ` Ricardo Wurmus
2019-04-06 8:54 ` znavko
2019-04-06 8:57 ` znavko
2019-04-06 17:55 ` znavko [this message]
2019-04-05 13:49 ` jbranso
2019-04-05 14:34 ` znavko
2019-04-04 19:26 znavko
2019-04-04 20:01 ` Quiliro Ordonez
2019-04-05 16:47 ` Ricardo Wurmus
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=84bec7c771a305a520d0a174753fa320@disroot.org \
--to=znavko@disroot.org \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
--cc=znavko@tutanota.com \
/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.