From owner-freebsd-wireless@FreeBSD.ORG  Mon Sep  8 11:30:25 2014
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C6E188C2
 for <freebsd-wireless@freebsd.org>; Mon,  8 Sep 2014 11:30:25 +0000 (UTC)
Received: from land.berklix.org (land.berklix.org [144.76.10.75])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 4E8E71E9E
 for <freebsd-wireless@freebsd.org>; Mon,  8 Sep 2014 11:30:24 +0000 (UTC)
Received: from mart.js.berklix.net (p5DCBEEB8.dip0.t-ipconnect.de
 [93.203.238.184]) (authenticated bits=128)
 by land.berklix.org (8.14.5/8.14.5) with ESMTP id s88ATu6E022256;
 Mon, 8 Sep 2014 10:29:56 GMT (envelope-from jhs@berklix.com)
Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41])
 by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id s88AWEsa083622;
 Mon, 8 Sep 2014 12:32:14 +0200 (CEST) (envelope-from jhs@berklix.com)
Received: from fire.js.berklix.net (localhost [127.0.0.1])
 by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id s88AVpDs089788;
 Mon, 8 Sep 2014 12:32:03 +0200 (CEST) (envelope-from jhs@berklix.com)
Message-Id: <201409081032.s88AVpDs089788@fire.js.berklix.net>
To: Vladimir Botka <vlado@netng.org>
Subject: Re: Issues with urtwn
From: "Julian H. Stacey" <jhs@berklix.com>
Organization: http://berklix.com BSD Unix Linux Consultants, Munich Germany
User-agent: EXMH on FreeBSD http://berklix.com/free/
X-URL: http://www.berklix.com
In-reply-to: Your message "Mon, 08 Sep 2014 09:59:09 +0200."
 <20140908095909.12c56bde@planb.g3.netng.org>
Date: Mon, 08 Sep 2014 12:31:51 +0200
Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless/>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 08 Sep 2014 11:30:25 -0000

> wpa_gui as a next step. In the upstream, wpa_gui is maintained together
> with wpa_supplicant by the same maintainer. Therefor wpa_gui has always
> been working fine with wpa_supplicant and might help you to create a
> consistent configuration.

I too have found wpa_gui useful to detect syntax errs from my 
wpa_supplicant.conf  (& useful to know same maintainer).

Matthias, a word of warning:
copy wpa_supplicant.conf before you enable 
	update_config=1
because wpa_gui will discard all lines with comments.

Cheers,
Julian
-- 
Julian Stacey, BSD Linux Unix C Sys Eng Consultant Munich http://berklix.com
		Interleave replies Below, like a play script.