nnection via the
nm-tray symbol to a PEAP (WPA-Enterprise?). The problem is that "PEAP"
is not offered to my. It is missing in the "security" drop down menu.
Also WPA-Enterprise is missing.
I assume that some components are missing. But searching the Debian
repository I g
yes`.
>
>
>
> I think `nmcli device set wlan0 managed yes` may not sufficiently
> instruct wpa_supplicant to let go of the device. That means, you still
> might need `systemctl stop wpa_supplicant.service`. Patch welcome to
> properly handle the release of a device by setting it unmana
te:
> >
> > Good day -
> >
> > Whenever I try to run hostapd, NM still runs wpa-supplicant,
> > which periodically tries to put the WiFi interface into scanning
> > mode, which messes up the hostapd session .
> >
> > Please is there a con
od day -
>
> Whenever I try to run hostapd, NM still runs wpa-supplicant,
> which periodically tries to put the WiFi interface into scanning
> mode, which messes up the hostapd session .
>
> Please is there a config file setting or applet interaction
> to disable wpa-supplicant
Good day -
Whenever I try to run hostapd, NM still runs wpa-supplicant,
which periodically tries to put the WiFi interface into scanning
mode, which messes up the hostapd session .
Please is there a config file setting or applet interaction
to disable wpa-supplicant (and maybe configure
On Wed, Mar 07, 2018 at 10:28:18AM +0100, Iris Fiedler wrote:
> Hi,
>
> I found my errror. My radius server had a wrong configuration and didn't send
> the accepted response. So the network manager didn't received it and printed
> an error.
Hi,
good to know!
> Thank you for your help.
Hi,
I found my errror. My radius server had a wrong configuration and didn't send
the accepted response. So the network manager didn't received it and printed an
error.
Thank you for your help.
Iris
___
networkmanager-list mailing list
from nmcli.Is there something else that I'm missing?IrisAm 21.02.2018 09:24 schrieb Beniamino Galvani <bgalv...@redhat.com>:On Mon, Feb 19, 2018 at 12:59:04PM +0100, Iris Fiedler wrote:
Hi,
> freeRADIUS: 3.0.15 (on a different PC with OpenSuse 42.3)
> Konfigured as wpa-eap tls w
On Mon, Feb 19, 2018 at 12:59:04PM +0100, Iris Fiedler wrote:
Hi,
> freeRADIUS: 3.0.15 (on a different PC with OpenSuse 42.3)
> Konfigured as wpa-eap tls with identity and password.
EAP-TLS doesn't support passwords AFAIK. Perhaps you mean EAP-TTLS?
> radius-tls.log
> (35)
[wifi-security]
auth-alg=open
key-mgmt=wpa-eap
[802-1x]
ca-cert=/var/opt/telemotive/etc/cert/ca.pem
client-cert=/var/opt/telemotive/etc/cert/client.p12
eap=tls;
identity=testUser1
password=testUser11
private-key=/var/opt/telemotive/etc/cert/client.p12
private-key-password=testCert1
[ipv4]
dns
On Wed, 2018-01-17 at 18:06 +0100, Beniamino Galvani wrote:
> Commit 87ec5e90fe79 ("supplicant: set key_mgmt independent of pmf
> value") enabled WPA-PSK-SHA256 or WPA-EAP-SHA256 even when the
> supplicant didn't support them, potentially causing connection
> failures.
On 2018/01/18 05:52, Masashi Honma wrote:
> On 2018/01/18 02:06, Beniamino Galvani wrote:
>> Commit 87ec5e90fe79 ("supplicant: set key_mgmt independent of pmf
>> value") enabled WPA-PSK-SHA256 or WPA-EAP-SHA256 even when the
>> supplicant didn't support them,
On 2018/01/18 02:06, Beniamino Galvani wrote:
> Commit 87ec5e90fe79 ("supplicant: set key_mgmt independent of pmf
> value") enabled WPA-PSK-SHA256 or WPA-EAP-SHA256 even when the
> supplicant didn't support them, potentially causing connection
> failures. Instead, us
On Wed, 2018-01-17 at 18:06 +0100, Beniamino Galvani wrote:
> Commit 87ec5e90fe79 ("supplicant: set key_mgmt independent of pmf
> value") enabled WPA-PSK-SHA256 or WPA-EAP-SHA256 even when the
> supplicant didn't support them, potentially causing connection
> failures.
Commit 87ec5e90fe79 ("supplicant: set key_mgmt independent of pmf
value") enabled WPA-PSK-SHA256 or WPA-EAP-SHA256 even when the
supplicant didn't support them, potentially causing connection
failures. Instead, use the 'pmf' capability to detect when they can
be enabl
On Tue, 2017-02-07 at 11:29 +0100, Beniamino Galvani wrote:
> On Sun, Feb 05, 2017 at 11:18:08PM +0100, Thomas Haller wrote:
> > We no longer use wpa_supplicant for MAC address randomization.
> > Instead, NetworkManager
> > handle it on it's own. It is actually important that supplicant
> > does
On Sun, Feb 05, 2017 at 11:18:08PM +0100, Thomas Haller wrote:
> We no longer use wpa_supplicant for MAC address randomization. Instead,
> NetworkManager
> handle it on it's own. It is actually important that supplicant does not
> interfere
> when setting the MAC address of the device.
>
> The
We no longer use wpa_supplicant for MAC address randomization. Instead,
NetworkManager
handle it on it's own. It is actually important that supplicant does not
interfere
when setting the MAC address of the device.
The code was only in effect when a PreassocMacAddr property exists,
which is a
t; > code.
> >
> > 1. Connect to a known wireless network with WPA/WPA2 Personal
> > authentication
> > 2. Once connected, edit the connection
> > 3. In "Wi-Fi Security" select "Dynamic WEP", then "Tunneled TLS" as
> > the
>
t; > code.
> >
> > 1. Connect to a known wireless network with WPA/WPA2 Personal
> > authentication
> > 2. Once connected, edit the connection
> > 3. In "Wi-Fi Security" select "Dynamic WEP", then "Tunneled TLS" as
> > the
>
On Tue, 2016-06-07 at 19:10 +0200, Bastien Nocera wrote:
> Hey,
>
> I get problems when trying this with both nm-connection-editor and
> gnome-control-center, so it's probably a problem in the common code.
>
> 1. Connect to a known wireless network with WPA/WPA2 Personal
&g
Hey,
I get problems when trying this with both nm-connection-editor and
gnome-control-center, so it's probably a problem in the common code.
1. Connect to a known wireless network with WPA/WPA2 Personal
authentication
2. Once connected, edit the connection
3. In "Wi-Fi Security" selec
Hi,
The following is a brain-dump of what I've been using to test all the
WPA Enterprise stuff using freeradius.
1) install freeradius 3.0 or higher
2) in /etc/raddb/certs there is a 'bootstrap' script. You can use this
to generate testing certificates for the CA and the RADIUS server
On Monday 14 of September 2015 12:51:01 Jirka Klimes wrote:
> On Mon, 14 Sep 2015 10:36:59 +0200
>
> Jan Grulich <jgrul...@redhat.com> wrote:
> > Hi,
> >
> > I'm trying to improve our WPA/WPA2 Enterprise support in KDE and I
> > have few questions regardi
On Mon, 14 Sep 2015 10:36:59 +0200
Jan Grulich <jgrul...@redhat.com> wrote:
> Hi,
>
> I'm trying to improve our WPA/WPA2 Enterprise support in KDE and I
> have few questions regarding 802-11x security setting.
>
> 1) When phase2-foo properties should be used instead
On Mon, 14 Sep 2015 13:23:14 +0200
Jan Grulich <jgrul...@redhat.com> wrote:
> On Monday 14 of September 2015 12:51:01 Jirka Klimes wrote:
> > On Mon, 14 Sep 2015 10:36:59 +0200
> >
> > Jan Grulich <jgrul...@redhat.com> wrote:
> > > Hi,
> > >
gt; > Jan Grulich <jgrul...@redhat.com> wrote:
> > > > Hi,
> > > >
> > > > I'm trying to improve our WPA/WPA2 Enterprise support in KDE and I
> > > > have few questions regarding 802-11x security setting.
> > > >
> > >
Hi,
I'm trying to improve our WPA/WPA2 Enterprise support in KDE and I have few
questions regarding 802-11x security setting.
1) When phase2-foo properties should be used instead of just foo properties
(e.g
phase2-private-key/private-key) ? In implementation of gnome-applet I see
On Tue, 2015-06-02 at 21:04 +0200, Pieter Cardoen wrote:
Dear
I want to use the option scan_ssid=0 for the wpa_supplicant configuration.
However when I add this line to the Wifi configuration keyfile of
NetworkManager, it is ignored by the NM daemon. How could I configure the
scan_ssid
Dear
I want to use the option scan_ssid=0 for the wpa_supplicant configuration.
However when I add this line to the Wifi configuration keyfile of
NetworkManager, it is ignored by the NM daemon. How could I configure the
scan_ssid option using NetworkManager?
Thanks in advance!
I've had this problem for awhile now (maybe the last year or 2,
certainly Fedora 20 and Fedora 19, and probably Fedora 18 as well).
When creating a new Wi-Fi connection:
Security: WPA WPA2 Enterprise
Authentication: TLS
User certificate: file in .der format
CA certifcate: file in .der format
On Fri, 2014-05-02 at 14:49 -0400, Chuck Anderson wrote:
I've had this problem for awhile now (maybe the last year or 2,
certainly Fedora 20 and Fedora 19, and probably Fedora 18 as well).
When creating a new Wi-Fi connection:
Security: WPA WPA2 Enterprise
Authentication: TLS
User
:
Security: WPA WPA2 Enterprise
Authentication: TLS
User certificate: file in .der format
CA certifcate: file in .der format
Private key: file in .pem format
Private key password: provided
Could you run nm-connection-editor from a terminal and see what output
it dumps when you
Fedora 18 as well).
When creating a new Wi-Fi connection:
Security: WPA WPA2 Enterprise
Authentication: TLS
User certificate: file in .der format
CA certifcate: file in .der format
Private key: file in .pem format
Private key password: provided
Could you run nm
tried reinstalling the network-manager-gnome package that
provides the applet
further note: im using e17 wm (0.17.3) on debian jessie, but using the
network manager from wheezy becuase of some issues with wpa supplicant
That schema should be defined in org.gnome.nm-applet.gschema.xml, which
to match network manager and that solved the
issue. I guess can only hope that wpa 1.1 will get to testing soon so i
can finally update network manager to 9.8
-Kevin
On 06/26/2013 04:32 PM, Dan Williams wrote:
On Sun, 2013-06-23 at 15:40 +0200, Kevin Brandstatter wrote:
Settings schema 'org.gnome.nm
the applet
further note: im using e17 wm (0.17.3) on debian jessie, but using the
network manager from wheezy becuase of some issues with wpa supplicant
-Kevin
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org
Dear NetworkManager folks,
following a discussion on the linux-wireless list [1], I want to find
out if my WLAN uses WPA(1) or WPA2 security. In his reply Larry Finger
suggests to use `iwlist scan` but I do want to avoid installing the
package containing this and wonder if NetworkManager exposes
On Wed, 2013-06-19 at 09:37 +0200, Paul Menzel wrote:
Dear NetworkManager folks,
following a discussion on the linux-wireless list [1], I want to find
out if my WLAN uses WPA(1) or WPA2 security. In his reply Larry Finger
suggests to use `iwlist scan` but I do want to avoid installing
From: Nicolas Cavallari caval...@lri.fr
From: Nicolas Cavallari caval...@lri.fr
This reverts commit 69247a00eacd00617acbf1dfcee8497437b8ad39,
which disabled all security in Ad-Hoc networks, due to a bug
of wpa_supplicant that only affected WPA-None.
---
libnm-util/nm-utils.c | 4
src
From: Nicolas Cavallari caval...@lri.fr
From: Nicolas Cavallari caval...@lri.fr
This completely removes Ad-Hoc WPA-None support, as it is
not supported by the linux kernel since a long time,
have never been standardized and other vendors already
removed support for it since a long time
The is on Fedora 17, x86_64 (NM 0.9.6.4-3.fc17?), Gnome 3.
First I was a major contributor to 802.11i and wrote the first paper on
the attack on WPA-PSK (and the myth on hiding SSIDs); I am not your
typical end user having a complaint on client behaviour.
Yesterday, I was at a major
On Tue, 2012-12-11 at 06:24 -0500, Robert Moskowitz wrote:
The is on Fedora 17, x86_64 (NM 0.9.6.4-3.fc17?), Gnome 3.
First I was a major contributor to 802.11i and wrote the first paper on
the attack on WPA-PSK (and the myth on hiding SSIDs); I am not your
typical end user having
On 12/11/2012 10:02 AM, Dan Williams wrote:
On Tue, 2012-12-11 at 06:24 -0500, Robert Moskowitz wrote:
The is on Fedora 17, x86_64 (NM 0.9.6.4-3.fc17?), Gnome 3.
First I was a major contributor to 802.11i and wrote the first paper on
the attack on WPA-PSK (and the myth on hiding SSIDs); I am
on
the attack on WPA-PSK (and the myth on hiding SSIDs); I am not your
typical end user having a complaint on client behaviour.
Yesterday, I was at a major corporation for a meeting and the quest SSID
had a 6 digit all numeric passcode. NM would not let me connect; it
seem to insist
contributor to 802.11i and wrote the first paper on
the attack on WPA-PSK (and the myth on hiding SSIDs); I am not your
typical end user having a complaint on client behaviour.
Yesterday, I was at a major corporation for a meeting and the quest SSID
had a 6 digit all numeric passcode. NM would not let
On Tue, 11 Dec 2012 12:53:58 -0600
Dan Williams wrote:
And these devices pass WiFi Alliance certification?
Since this is against golden devices instead of against a rigorous
spec it doesn't actually guarantee that compliance means does what the
spec says it should.
--
Brian Morrison
, x86_64 (NM 0.9.6.4-3.fc17?), Gnome 3.
First I was a major contributor to 802.11i and wrote the first paper on
the attack on WPA-PSK (and the myth on hiding SSIDs); I am not your
typical end user having a complaint on client behaviour.
Yesterday, I was at a major corporation for a meeting
Moskowitz wrote:
The is on Fedora 17, x86_64 (NM 0.9.6.4-3.fc17?), Gnome 3.
First I was a major contributor to 802.11i and wrote the first paper on
the attack on WPA-PSK (and the myth on hiding SSIDs); I am not your
typical end user having a complaint on client behaviour.
Yesterday, I
On Mon, Dec 3, 2012 at 3:32 AM, brom...@lavabit.com wrote:
Hello!
I'd like to try cnetworkmanager. The only thing that stops me is the
following options:
--wep-hex=KEY use this WEP key of 26 hex digits
--wep-pass=KEYuse this WEP passphrase
--wpa-psk-hex=KEY use
Hello!
I'd like to try cnetworkmanager. The only thing that stops me is the
following options:
--wep-hex=KEY use this WEP key of 26 hex digits
--wep-pass=KEYuse this WEP passphrase
--wpa-psk-hex=KEY use this WPA key of 64 hex digits
--wpa-pass=KEYuse this WPA
From: Nicolas Cavallari caval...@lri.fr
This completely removes Ad-Hoc WPA-None support, as it is
not supported by the linux kernel since a long time,
have never been standardized and other vendors already
removed support for it since a long time. The security
of the protocol is also comparable
From: Nicolas Cavallari caval...@lri.fr
This reverts commit 69247a00eacd00617acbf1dfcee8497437b8ad39,
which disabled all security in Ad-Hoc networks, due to a bug
of wpa_supplicant that only affected WPA-None.
---
libnm-util/nm-utils.c |4 ---
src/nm-device-wifi.c | 60
From: Nicolas Cavallari caval...@lri.fr
This completely removes Ad-Hoc WPA-None support, as it is
not supported by the linux kernel since a long time,
have never been standardized and other vendors already
removed support for it since a long time. The security
of the protocol is also comparable
On Sunday 19 of February 2012 17:58:09 Almo Nito wrote:
Hey Guys, im Trying to get Networkmanager to work together with wpa
supplicant.
They are both started fine with the dbus option but networkmanager doesn't
seem to interact with wpa supplicant (it neither tells that is running
On Fri, 2012-02-24 at 12:34 +0100, Jirka Klimes wrote:
On Sunday 19 of February 2012 17:58:09 Almo Nito wrote:
Hey Guys, im Trying to get Networkmanager to work together with wpa
supplicant.
They are both started fine with the dbus option but networkmanager doesn't
seem
On Mon, Feb 20, 2012 at 1:09 AM, Almo Nito almon...@gmx.de wrote:
Im actually getting this error:
NetworkManager[1295]: error [1329674643.782386]
[nm-supplicant-interface.c:570] interface_add_cb(): (wlan0): error adding
interface: Did not receive a reply. Possible causes include: the remote
Hey Guys, im Trying to get Networkmanager to work together with wpa
supplicant.
They are both started fine with the dbus option but networkmanager doesn't
seem to interact with wpa supplicant (it neither tells that is running in
the logs nor sees access points)
What exactly do I want
Im actually getting this error:
NetworkManager[1295]: error [1329674643.782386]
[nm-supplicant-interface.c:570] interface_add_cb(): (wlan0): error adding
interface: Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy
, however setting custom MAC on
WPA2 enabled network connection fails.
Reason is same as what I have seen many years ago, when I played a lot
with wifi.
Reason is that supplicant is not informed of new MAC and thus rejects
WPA handshake, or even worse its told old MAC by NM (I suspect later as
I
.
Reason is same as what I have seen many years ago, when I played a lot
with wifi.
Reason is that supplicant is not informed of new MAC and thus rejects
WPA handshake, or even worse its told old MAC by NM (I suspect later as
I tried restarting the supplicant and that didn't help).
When I set MAC
On 09/12/2011 10:19 PM, Dan Williams wrote:
On Mon, 2011-09-12 at 19:18 +0100, iain wrote:
Hi again,
In case anyone else is wondering about this, I've found a patch from
Android for an older version of wpa-supplicant, that with a bit of
tweaking for 0.7.3 appears to fix the problem
This would
Some further information, when wpa-supplicant carries out a scan there
are a lot of IWEVGENIE overflow errors. What might this indicate (if
anything)?
thanks,
iain
On 09/09/2011 04:42 PM, Lamarque Vieira Souza wrote:
Em Friday 09 September 2011, iain escreveu:
Hi,
I'm running
On Mon, 2011-09-12 at 19:18 +0100, iain wrote:
Hi again,
In case anyone else is wondering about this, I've found a patch from
Android for an older version of wpa-supplicant, that with a bit of
tweaking for 0.7.3 appears to fix the problem
This would appear to indicate a buggy kernel driver
: 2A0100
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 32043048606C
IE: Unknown
On 09/09/2011 04:42 PM, Lamarque Vieira Souza wrote:
Em Friday 09 September 2011, iain escreveu:
Hi,
I'm running NetworkManager 0.9.1 from git and wpa_supplicant 0.7.3 on a
custom distro (based from poky). When I run nmcli dev wifi, the access
points appear but everything seems to be
in
many cases we simply don't know if the failure was password-related or
not.
And the kernel logs say:
May 6 14:03:52 sm1 wpa_supplicant[530]: WPA: 4-Way Handshake failed -
pre-shared key may be incorrect
which indicate that is the case. How many characters long is the PSK,
and what
:52 sm1 wpa_supplicant[530]: WPA: 4-Way Handshake failed -
pre-shared key may be incorrect
May 6 14:03:52 sm1 wpa_supplicant[530]: CTRL-EVENT-DISCONNECTED
bssid=94:fe:f4:f9:63:18 reason=0
May 6 14:03:52 sm1 kernel: [ 1587.798570] cfg80211: All devices are
disconnected, going to restore
We've received many reports that NetworkManager in Ubuntu 10.04 and
Fedora 13 (0.8.1) doesn't like PEM-formatted cert files when
configuring new wireless networks for WPA Enterprise, whereas earlier
versions work fine. Also, 0.8.1 works for existing wireless network
configurations that were
On Fri, 2010-07-30 at 10:00 -0400, RumseyCW wrote:
Mr. Williams et al,
NetworkManager on Fedora 13 (IBM T30) installation can not connect to
a 3CRWE554G72TU wireless router using WPA-PSK -TKIP. The laptop has
the latest updates and all the NetworkManager packages installed
including GNOME
Mr. Williams et al,
NetworkManager on Fedora 13 (IBM T30) installation can not connect to a
3CRWE554G72TU wireless router using WPA-PSK -TKIP. The laptop has the latest
updates and all the NetworkManager packages installed including GNOME GUI.
When I use NetworkManager it will accept the WPA
Washington).
When I try to log on it will only give me the option to enter a WEP
code, not a WPA. With some jiggling--turning radio off and on,
disabling wireless and reenabling it, deleting the connection and
trying to recreate it, even rebooting, I sometimes will get a dialog
box that calls
. In the past
it has worked fine but yesterday afternoon for some reason is cut me off
and
I haven't been able to get back on. All the other boxes work (using that
other OS from Washington).
When I try to log on it will only give me the option to enter a WEP code,
not a WPA. With some
work (using that
other OS from Washington).
When I try to log on it will only give me the option to enter a WEP code,
not a WPA. With some jiggling--turning radio off and on, disabling wireless
and reenabling it, deleting the connection and trying to recreate it, even
rebooting, I sometimes
the option to enter a WEP code, not a
WPA. With some jiggling--turning radio off and on, disabling wireless and
reenabling it, deleting the connection and trying to recreate it, even
rebooting, I sometimes will get a dialog box that calls for the WPA password.
But then the Apply button is greyed
wireless router (again, a DD-WRT
equipped Linksys WRT54GS v5.2 router).
When I use NetworkManager and specify WPA/WPA2 and supply the
passphrase, I simply cannot get a successful connection at all.
Here's the versions I'm using on the iMac G3:
NetworkManager 0.8
nm-applet 0.8
wpa_supplicant 0.6.9
point using the following wpa.conf
network={
ssid=doubidou-net
proto=WPA WPA2
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk= my_secret
On 02/11/2010 04:02 PM, vincent guffens wrote:
Dear list,
I have recently bought a thinkpad edge 64 bits with a realtek 8192.
lspci reports
Network controller: Realtek Semiconductor Co., Ltd. Device 8172 (rev 10)
I have installed ubuntu 9.10 amd64 but Linux does not come with the
On Fri, 2010-02-12 at 14:47 -0600, Larry Finger wrote:
On 02/11/2010 04:02 PM, vincent guffens wrote:
Dear list,
I have recently bought a thinkpad edge 64 bits with a realtek 8192.
lspci reports
Network controller: Realtek Semiconductor Co., Ltd. Device 8172 (rev 10)
I have
What type of wifi card? It may be that driver issues prevent the wifi
card from completing the WPA Ad-Hoc network. WPA Ad-Hoc is more complex
than WEP ad-hoc and there have been kernel driver issues with that
configuration in the past. What kernel version are you using, what wifi
hardware
wrote:
Hi!
I wanted to inform you that I was able to share my connection with WEP64 but
not WPA/WPA2.
I am connecting my Ipod Touch 2nd generation to my notebook (ath5k based
WLAN card, Ubuntu Karmic) which is connected to the internet via UMTS
(Huawei E220, option kernel module
On Sun, 2010-01-17 at 18:04 +0100, Gonsolo wrote:
I wanted to inform you that I was able to share my connection with
WEP64 but
not WPA/WPA2.
I am connecting my Ipod Touch 2nd generation to my notebook (ath5k based
WLAN card, Ubuntu Karmic) which is connected to the internet via
It should not have to be ad-hoc. The wifi card is acting in ap(Access
Point) mode.
How does this work?
Q
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Gonsolo a écrit :
I think my WG511 card would allow WPA
Note that it is not because a card works as a WPA station that it works
as an WPA Access Point.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman
2010/1/18 Marc Herbert marc.herb...@gmail.com:
Gonsolo a écrit :
I think my WG511 card would allow WPA
Note that it is not because a card works as a WPA station that it works
as an WPA Access Point.
I agree.
I remember that when I was testing a rt61-based card, I had problems
when tried
On Mon, Jan 18, 2010 at 6:02 AM, Quintin Beukes quin...@last.za.net wrote:
It should not have to be ad-hoc. The wifi card is acting in ap(Access
Point) mode.
How does this work?
Internally or how to configure?
To configure:
1. Create a new wireless connection with the add button
2.
Hi!
I wanted to inform you that I was able to share my connection with WEP64
but not WPA/WPA2.
I am connecting my Ipod Touch 2nd generation to my notebook (ath5k based
WLAN card, Ubuntu Karmic) which is connected to the internet via UMTS
(Huawei E220, option kernel module).
It works
:37 PM, Gonsolo gons...@gmail.com wrote:
Hi!
I wanted to inform you that I was able to share my connection with WEP64 but
not WPA/WPA2.
I am connecting my Ipod Touch 2nd generation to my notebook (ath5k based
WLAN card, Ubuntu Karmic) which is connected to the internet via UMTS
(Huawei E220
I wanted to inform you that I was able to share my connection with
WEP64 but
not WPA/WPA2.
I am connecting my Ipod Touch 2nd generation to my notebook (ath5k based
WLAN card, Ubuntu Karmic) which is connected to the internet via UMTS
(Huawei E220, option kernel module).
It works
Am 17.01.2010 18:04, schrieb Marc Luethi:
On Sun, 2010-01-17 at 17:37 +0100, Gonsolo wrote:
It works with WEP64 encryption but not with WPA/WPA2 encryption.
If your notebook sets up an ad hoc WiFi network, you can't use WPA or
WPA2.
AFAIK, the ad hoc WiFi mode is still limited to WEP
Are you sure the network is even established? Can you ping the other host?
You mentioned ad-hoc. I've noticed NetworkManager has problems
establishing AdHoc networks using WPA. For the network doesn't
establish in the first place, so sharing won't work.
Maybe this is your problem as well?
try
On Sun, Jan 17, 2010 at 1:28 PM, Quintin Beukes quin...@last.za.net wrote:
Are you sure the network is even established? Can you ping the other host?
You mentioned ad-hoc. I've noticed NetworkManager has problems
establishing AdHoc networks using WPA. For the network doesn't
establish
Am 17.01.2010 22:09, schrieb John Mahoney:
On Sun, Jan 17, 2010 at 1:28 PM, Quintin Beukesquin...@last.za.net wrote:
Are you sure the network is even established? Can you ping the other host?
You mentioned ad-hoc. I've noticed NetworkManager has problems
establishing AdHoc networks using WPA
On Fri, 04 Dec 2009 12:25:26 -0800
Dan Williams d...@redhat.com wrote:
On Thu, 2009-12-03 at 15:03 +, Brian Morrison wrote:
Brian Morrison wrote:
The fix was to paste my WPA key into the entry field after using
the edit menu for my home SSID and then going to the advanced tab
On Thu, 2009-12-03 at 15:03 +, Brian Morrison wrote:
Brian Morrison wrote:
The fix was to paste my WPA key into the entry field after using the
edit menu for my home SSID and then going to the advanced tab (at least
I think that's it, don't have it in front of me just now
Has anyone else suffered from a problem where on occasion F12 will boot
and then be unable to connect to a previously usable AP because the WPA
key is no longer stored? My home network has two APs with the same SSID
but different BSSIDs on each channel.
I have now had this happen twice, the first
Brian Morrison wrote:
The fix was to paste my WPA key into the entry field after using the
edit menu for my home SSID and then going to the advanced tab (at least
I think that's it, don't have it in front of me just now). There is only
an SSID stored, no BSSID.
I should have added
I have not forgotten about this and will gather the needed data. Just
happen to be life-busy for the current time.
On Tue, Nov 17, 2009 at 5:15 PM, Dan Williams wrote:
Can you grab /var/log/messages from a successful run (cert+peap0) and a
failed run so I can look at what NM is sending to the
1 - 100 of 444 matches
Mail list logo
