all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: 白い熊@相撲道 <guix-devel_gnu.org@sumou.com>
Cc: guix-devel@gnu.org
Subject: Re: Problems with wifi connection on one single network, can't ping gateway
Date: Sun, 05 Jul 2015 02:48:59 -0400	[thread overview]
Message-ID: <877fqf5cbo.fsf@netris.org> (raw)
In-Reply-To: <190578f07935c9161304108d297674a8@hcoop.net> ("白い熊@相撲道"'s message of "Sat, 04 Jul 2015 13:47:16 +0200")

白い熊@相撲道 <guix-devel_gnu.org@sumou.com> writes:

> I'm running GuixSD, latest git pull on the Gluglug X200.

Excellent!  I'm also running GuixSD on a Libreboot X200.

> Using wifi
> via commandline, wpa_supplicant, as I will demonstrate below. The
> usage is problemless on all wifi networks, even on the road, however I
> have a problem with my home wifi - which is a pain.
>
> The problem is, it will connect, but then internet is inaccessible, I
> can't ping my gateway address.

If you pass -d to wpa_supplicant, it will output debugging information.
You can also pass -dd for even more detail.  You might also want to
remove the -B option so that it runs in the foreground when debugging.

You might consider using wicd, the wireless connection daemon, which
might include heuristics to deal with common problems, and anyway it is
quite convenient to use.

If you'd like to use wicd, make these changes to your OS config:

* Add (wicd-service) to 'services', and remove (dhcp-client-service).
* Add wicd to the list passed to 'dbus-service'.
* Add wicd to 'packages'.

     Mark

      reply	other threads:[~2015-07-05  6:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-04 11:47 Problems with wifi connection on one single network, can't ping gateway 白い熊@相撲道
2015-07-05  6:48 ` Mark H Weaver [this message]

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=877fqf5cbo.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=guix-devel_gnu.org@sumou.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.