On Tue, 2006-03-21 at 18:26 -0300, Cesar Cardoso wrote:
Hi Cesar!
It looks that connection was not provided by NM, but by plain
wpa_supplicant :-(
you don't need the driver-workarounds patch anymore (yay for madwifi
developers, finally!), just upgrade to 0.6.1. I use r1474 madwifi-ng
driver
On Wed, 2006-03-22 at 09:50 +0100, Gour wrote:
Any idea?
On #networkmanager I got a help and applied the following patch:
http://cvs.fedora.redhat.com/viewcvs/*checkout*/devel/NetworkManager/special-case-madwifi.patch?rev=1.1
Now it works :-)
but NM quickly drops connection :-(
Sincerely,
Firstly, would just like to say thanks to all the developers,
NetworkManager is turning into a really useful tool.
I've just rebuilt NM from source* on an FC5 machine and run
into a couple of issues:
1) WPA2 Enterprise connection works fine when all the credentials
are entered (using TLS a
Hm, that's a difference here. I went back to wpa_supplicant 0.4.8.
On 3/22/06, Gour [EMAIL PROTECTED] wrote:
On Tue, 2006-03-21 at 18:26 -0300, Cesar Cardoso wrote:
Hi Cesar!
It looks that connection was not provided by NM, but by plain
wpa_supplicant :-(
you don't need the
Hi listSince I am very eager to have the LEAP stuff implemented in NM, I decided to dump a complete session log to the developer list (attached). Maybe it can be of some use to someone...I have tried to get a grip on how NM works (codewise) but there are still a few gray areas. I have got very
On Wed, 2006-03-22 at 11:02 -0300, Cesar Cardoso wrote:
Hm, that's a difference here. I went back to wpa_supplicant 0.4.8.
I'm with wpa_supplicant-0.5.2 and now everything works except that NM
drops connection from time to time although plain wpa was very stable
robust.
Sincerely,
Gour
On Thu, 2006-03-16 at 16:09 +0100, Radek Vokál wrote:
Hi, I've realized that 25sec DHCP timeout limit is not enough on my slow
network, so I've proposed a small patch on RH bugzilla for adding new
option to NetworkManager, allowing to specify the timeout value.
Please see
Has there been any progress in NM toward differentiating between Managed
and AdHoc networks? I'm still ditching NM and manually configuring the
card when I'm onsite (couple days a week) at one customer where all
their users are on Windows laptops and there always seems to be one that
is
I have had other bug reports that users need DHCP timeouts in the 30~40
second range. To be sure, most ifup scripts wait longer than 25s.
I think a timeout in the 30-40 second range would also resolve the
issues with portfast...
___
On Wed, 2006-03-22 at 10:27 -0500, Robert Love wrote:
On Thu, 2006-03-16 at 16:09 +0100, Radek Vokál wrote:
Hi, I've realized that 25sec DHCP timeout limit is not enough on my slow
network, so I've proposed a small patch on RH bugzilla for adding new
option to NetworkManager, allowing to
On Wed, 2006-03-22 at 10:57 -0500, Darren Albers wrote:
I have had other bug reports that users need DHCP timeouts in the 30~40
second range. To be sure, most ifup scripts wait longer than 25s.
I think a timeout in the 30-40 second range would also resolve the
issues with portfast...
On Tue, 2006-03-14 at 10:41 -0500, Dan Williams wrote:
What's the situation here? NM only cares if the machine's ethernet card
has a link or not, which is reported by the driver for the card itself.
Once the driver reports that it has a link, NM will attempt to acquire a
DHCP address on that
The way this is supposed to work is that you configure STP for each of
the ports you're using to communicate with other switches, and thus you
get high availability out of it. What actually happens is that network
admins get lazy, and instead of planning their network, they turn STP on
for
On Wed, 2006-03-22 at 18:38 +, [EMAIL PROTECTED] wrote:
Today I've been trying to connect to a wireless network that uses
802.11x.
I was told by someone who connected using an Apple laptop that I needed
to use TTLS with PAP. In the WPA Enterprise window that appeared when
I tried to
Hi, guys.
I checked a first-pass at Dynamic WEP into CVS, on both HEAD and the 0.6
branch (since it was not overly complex).
Jan and Dennis, I would love to hear if it works for you and, if not,
what goes wrong.
Thanks!
Robert Love
___
On Wed, 2006-03-22 at 14:50 -0500, Robert Love wrote:
I checked a first-pass at Dynamic WEP into CVS, on both HEAD and the 0.6
branch (since it was not overly complex).
Jan and Dennis, I would love to hear if it works for you and, if not,
what goes wrong.
If not obvious: Select Dynamic WEP
On wo, 2006-03-22 at 14:54 -0500, Robert Love wrote:
If not obvious: Select Dynamic WEP as the Key type in the WPA
Enterprise configuration.
Another question is, if NM detects your Dynamic WEP-based AP, does it
think it is doing WPA Enterprise? It should.
Robert, you rock!
I'll test in
On Wed, 2006-03-22 at 20:58 +0100, Dennis Kaarsemaker wrote:
Sorry to hijack this thread but that would also explain (parts of) my
802.1x/WEP problem I posted about 2 days ago - that one uses PAP too.
AFAIK you can simply send wpa_supplicant this parameter via the control
channel at the same
On Wed, 2006-03-22 at 21:14 +0100, Jan Mynarik wrote:
Another question is, if NM detects your Dynamic WEP-based AP, does it
think it is doing WPA Enterprise? It should.
No, when I select this network from nm-applet's list, n-m tries to
connect and then opens dialog asking for WEP
Hello.
On Wed, 2006-03-22 at 15:08, Robert Love wrote:
to wpa_supplicant if the user selects a specific option. But I need to
better understand the problem. What is PAP ? What other second-stage
authentications are there? Are they only valid with certain ciphers?
From the
On 3/22/06, Gour [EMAIL PROTECTED] wrote:
On Wed, 2006-03-22 at 11:02 -0300, Cesar Cardoso wrote: Hm, that's a difference here. I went back to wpa_supplicant 0.4.8.I'm with wpa_supplicant-0.5.2 and now everything works except that NMdrops connection from time to time although plain wpa was very
On wo, 2006-03-22 at 15:14 -0500, Robert Love wrote:
Hrm. That is a problem. Kind of sucks if there is no way for the AP
to advertise that it does half-WPA/half-WEP. I presumed it would
advertise the WPA-EAP stuff, but then non-WPA cards might not grok
that.
There is no such way indeed.
On Tue, 2006-03-21 at 09:29 -0500, Robert Love wrote:
On Tue, 2006-03-21 at 12:24 +, Jan Mynarik wrote:
same here (802.1x EAP/TLS) and no n-m's WPA profile works (via Connect to
Other
Wireless Network).
I am going to look at adding this -- but, what in here actually says
use WEP
On Wed, 2006-03-22 at 11:18 -0700, Mike Bydalek wrote:
The problem has nothing to do with NetworkManager, but with your drivers
(at least that was the case with me). I use the ipw2200 driver, and the
one that came with Breezy didn't work with VMware, so I had to manually
upgrade to the latest
On Tue, 2006-03-21 at 09:48 -0500, Robert Love wrote:
I read the config once again later and said that to myself too :-) Our
admins at work told me it's WEP/TLS. And n-m offers me only WEP when I
connect to our wifi network. I need to use Connect to other wireless
network to be able to set
On Wed, 2006-03-22 at 15:14 -0500, Robert Love wrote:
On Wed, 2006-03-22 at 21:14 +0100, Jan Mynarik wrote:
Another question is, if NM detects your Dynamic WEP-based AP, does it
think it is doing WPA Enterprise? It should.
No, when I select this network from nm-applet's list, n-m
NetworkManager right now sets invisible_char to the default value of *
in all .glade files, that is not needed and poses an even bigger problem
if the system default is changed. attached patch removes all
property name=invisible_char*/property
entries from .glade files in cvs
j
Index:
On Wed, 2006-03-22 at 23:29 +0100, [EMAIL PROTECTED] wrote:
NetworkManager right now sets invisible_char to the default value of *
in all .glade files, that is not needed and poses an even bigger problem
if the system default is changed. attached patch removes all
property
On Wed, 2006-03-22 at 21:57 +0100, Luka Renko wrote:
I think this is know issue with madwifi drivers: NM does scans also
when conected and madwifi driver cannot perform such scan in
background, therefore it disconnects current connection to perform
scan.
Huh...this is certainly explaining
29 matches
Mail list logo
