I'm not sure it's really solved.
If I try to connect with a fresh setup from the network manager gui, it
works but /var/log/wpa_supplicant.log contains:
CTRL-EVENT-SCAN-RESULTS
Associated with 00:1e:be:a7:f6:90
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0
I tried several experiments, and I think the following comments would be
useful:
First, I think several different bugs are present in this bug report.
Some people can resolve their problem with the laster network manager
(from PPA), but it's not working with me.
Second, I am trying to connect to
An idea: if wpa_supplicant is ok and parameter of network manager is
correct, I think the bug(s) could be how parameters are transmit by
network manager. How network manager communicate the connection
parameters to wpa_supplicant ? I think it used DBUS (as wpa_supplicant
uses the "-u" parameter) bu
I'm not sure it's the good place to ask but: is it a way to increase
verbose from wpa_supplicant when used by network manager ? I have the
same problem and I will be happy to help with log and some experiments
;-)
Julien.
On Thu, Dec 4, 2008 at 4:37 PM, Niall Murphy <[EMAIL PROTECTED]> wrote:
> B
Public bug reported:
Hello,
I have a problem with my WPA connection since a fresh 8.10 installation.
The network manager refuses to connect with WPA2 mode using TTLS and
PAP. When I don't use certificate, I have errors logged in
/var/log/wpa_supplicant.log (see attached file) and I can't connect.
** Attachment added: "Log errors from wpa_supplicant when using without
certificate"
http://launchpadlibrarian.net/19944642/without-certificate.txt
--
invalid characters in links from /etc/ssl/certs
https://bugs.launchpad.net/bugs/302182
You received this bug notification because you are a m
*** This bug is a duplicate of bug 272185 ***
https://bugs.launchpad.net/bugs/272185
** This bug has been marked a duplicate of bug 272185
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
--
inv
I've something also interesting: on a full patched fresh intrepid
install, I can connect on WPA2 using TTLS and PAP the first time. But
when I disconnect and reconnect using the network applet, it doesn't
work anymore.
--
"Trouble-a-cat limited"
--
[Intrepid] iwl3945 + iwlagn -- network-manager
I'm not sure it's the good place to ask but: is it a way to increase
verbose from wpa_supplicant when used by network manager ? I have the
same problem and I will be happy to help with log and some experiments
;-)
Julien.
On Thu, Dec 4, 2008 at 4:37 PM, Niall Murphy <[EMAIL PROTECTED]> wrote:
> B
Public bug reported:
Hello,
I have a problem with my WPA connection since a fresh 8.10 installation.
The network manager refuses to connect with WPA2 mode using TTLS and
PAP. When I don't use certificate, I have errors logged in
/var/log/wpa_supplicant.log (see attached file) and I can't connect.
** Attachment added: "Log errors from wpa_supplicant when using without
certificate"
http://launchpadlibrarian.net/19944642/without-certificate.txt
--
invalid characters in links from /etc/ssl/certs
https://bugs.launchpad.net/bugs/302182
You received this bug notification because you are a m
*** This bug is a duplicate of bug 272185 ***
https://bugs.launchpad.net/bugs/272185
** This bug has been marked a duplicate of bug 272185
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
--
inv
I've something also interesting: on a full patched fresh intrepid
install, I can connect on WPA2 using TTLS and PAP the first time. But
when I disconnect and reconnect using the network applet, it doesn't
work anymore.
--
"Trouble-a-cat limited"
--
[Intrepid] iwl3945 + iwlagn -- network-manager
I tried several experiments, and I think the following comments would be
useful:
First, I think several different bugs are present in this bug report.
Some people can resolve their problem with the laster network manager
(from PPA), but it's not working with me.
Second, I am trying to connect to
An idea: if wpa_supplicant is ok and parameter of network manager is
correct, I think the bug(s) could be how parameters are transmit by
network manager. How network manager communicate the connection
parameters to wpa_supplicant ? I think it used DBUS (as wpa_supplicant
uses the "-u" parameter) bu
I tried several experiments, and I think the following comments would be
useful:
First, I think several different bugs are present in this bug report.
Some people can resolve their problem with the laster network manager
(from PPA), but it's not working with me.
Second, I am trying to connect to
An idea: if wpa_supplicant is ok and parameter of network manager is
correct, I think the bug(s) could be how parameters are transmit by
network manager. How network manager communicate the connection
parameters to wpa_supplicant ? I think it used DBUS (as wpa_supplicant
uses the "-u" parameter) bu
I'm not sure it's the good place to ask but: is it a way to increase
verbose from wpa_supplicant when used by network manager ? I have the
same problem and I will be happy to help with log and some experiments
;-)
Julien.
On Thu, Dec 4, 2008 at 4:37 PM, Niall Murphy <[EMAIL PROTECTED]> wrote:
> B
I'm not sure it's really solved.
If I try to connect with a fresh setup from the network manager gui, it
works but /var/log/wpa_supplicant.log contains:
CTRL-EVENT-SCAN-RESULTS
Associated with 00:1e:be:a7:f6:90
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0
Public bug reported:
Hello,
I have a problem with my WPA connection since a fresh 8.10 installation.
The network manager refuses to connect with WPA2 mode using TTLS and
PAP. When I don't use certificate, I have errors logged in
/var/log/wpa_supplicant.log (see attached file) and I can't connect.
** Attachment added: "Log errors from wpa_supplicant when using without
certificate"
http://launchpadlibrarian.net/19944642/without-certificate.txt
--
invalid characters in links from /etc/ssl/certs
https://bugs.launchpad.net/bugs/302182
You received this bug notification because you are a m
*** This bug is a duplicate of bug 272185 ***
https://bugs.launchpad.net/bugs/272185
** This bug has been marked a duplicate of bug 272185
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
--
inv
I've something also interesting: on a full patched fresh intrepid
install, I can connect on WPA2 using TTLS and PAP the first time. But
when I disconnect and reconnect using the network applet, it doesn't
work anymore.
--
"Trouble-a-cat limited"
--
[Intrepid] iwl3945 + iwlagn -- network-manager
I tried several experiments, and I think the following comments would be
useful:
First, I think several different bugs are present in this bug report.
Some people can resolve their problem with the laster network manager
(from PPA), but it's not working with me.
Second, I am trying to connect to
An idea: if wpa_supplicant is ok and parameter of network manager is
correct, I think the bug(s) could be how parameters are transmit by
network manager. How network manager communicate the connection
parameters to wpa_supplicant ? I think it used DBUS (as wpa_supplicant
uses the "-u" parameter) bu
I'm not sure it's the good place to ask but: is it a way to increase
verbose from wpa_supplicant when used by network manager ? I have the
same problem and I will be happy to help with log and some experiments
;-)
Julien.
On Thu, Dec 4, 2008 at 4:37 PM, Niall Murphy <[EMAIL PROTECTED]> wrote:
> B
Public bug reported:
Hello,
I have a problem with my WPA connection since a fresh 8.10 installation.
The network manager refuses to connect with WPA2 mode using TTLS and
PAP. When I don't use certificate, I have errors logged in
/var/log/wpa_supplicant.log (see attached file) and I can't connect.
** Attachment added: "Log errors from wpa_supplicant when using without
certificate"
http://launchpadlibrarian.net/19944642/without-certificate.txt
--
invalid characters in links from /etc/ssl/certs
https://bugs.launchpad.net/bugs/302182
You received this bug notification because you are a m
*** This bug is a duplicate of bug 272185 ***
https://bugs.launchpad.net/bugs/272185
** This bug has been marked a duplicate of bug 272185
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
--
inv
I've something also interesting: on a full patched fresh intrepid
install, I can connect on WPA2 using TTLS and PAP the first time. But
when I disconnect and reconnect using the network applet, it doesn't
work anymore.
--
"Trouble-a-cat limited"
--
[Intrepid] iwl3945 + iwlagn -- network-manager
I'm not sure it's really solved.
If I try to connect with a fresh setup from the network manager gui, it
works but /var/log/wpa_supplicant.log contains:
CTRL-EVENT-SCAN-RESULTS
Associated with 00:1e:be:a7:f6:90
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0
I'm not sure it's really solved.
If I try to connect with a fresh setup from the network manager gui, it
works but /var/log/wpa_supplicant.log contains:
CTRL-EVENT-SCAN-RESULTS
Associated with 00:1e:be:a7:f6:90
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0
I'm not sure it's really solved.
If I try to connect with a fresh setup from the network manager gui, it
works but /var/log/wpa_supplicant.log contains:
CTRL-EVENT-SCAN-RESULTS
Associated with 00:1e:be:a7:f6:90
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0
I tried several experiments, and I think the following comments would be
useful:
First, I think several different bugs are present in this bug report.
Some people can resolve their problem with the laster network manager
(from PPA), but it's not working with me.
Second, I am trying to connect to
An idea: if wpa_supplicant is ok and parameter of network manager is
correct, I think the bug(s) could be how parameters are transmit by
network manager. How network manager communicate the connection
parameters to wpa_supplicant ? I think it used DBUS (as wpa_supplicant
uses the "-u" parameter) bu
I'm not sure it's the good place to ask but: is it a way to increase
verbose from wpa_supplicant when used by network manager ? I have the
same problem and I will be happy to help with log and some experiments
;-)
Julien.
On Thu, Dec 4, 2008 at 4:37 PM, Niall Murphy <[EMAIL PROTECTED]> wrote:
> B
Public bug reported:
Hello,
I have a problem with my WPA connection since a fresh 8.10 installation.
The network manager refuses to connect with WPA2 mode using TTLS and
PAP. When I don't use certificate, I have errors logged in
/var/log/wpa_supplicant.log (see attached file) and I can't connect.
** Attachment added: "Log errors from wpa_supplicant when using without
certificate"
http://launchpadlibrarian.net/19944642/without-certificate.txt
--
invalid characters in links from /etc/ssl/certs
https://bugs.launchpad.net/bugs/302182
You received this bug notification because you are a m
*** This bug is a duplicate of bug 272185 ***
https://bugs.launchpad.net/bugs/272185
** This bug has been marked a duplicate of bug 272185
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
--
inv
I've something also interesting: on a full patched fresh intrepid
install, I can connect on WPA2 using TTLS and PAP the first time. But
when I disconnect and reconnect using the network applet, it doesn't
work anymore.
--
"Trouble-a-cat limited"
--
[Intrepid] iwl3945 + iwlagn -- network-manager
I tried several experiments, and I think the following comments would be
useful:
First, I think several different bugs are present in this bug report.
Some people can resolve their problem with the laster network manager
(from PPA), but it's not working with me.
Second, I am trying to connect to
An idea: if wpa_supplicant is ok and parameter of network manager is
correct, I think the bug(s) could be how parameters are transmit by
network manager. How network manager communicate the connection
parameters to wpa_supplicant ? I think it used DBUS (as wpa_supplicant
uses the "-u" parameter) bu
I'm not sure it's the good place to ask but: is it a way to increase
verbose from wpa_supplicant when used by network manager ? I have the
same problem and I will be happy to help with log and some experiments
;-)
Julien.
On Thu, Dec 4, 2008 at 4:37 PM, Niall Murphy <[EMAIL PROTECTED]> wrote:
> B
Public bug reported:
Hello,
I have a problem with my WPA connection since a fresh 8.10 installation.
The network manager refuses to connect with WPA2 mode using TTLS and
PAP. When I don't use certificate, I have errors logged in
/var/log/wpa_supplicant.log (see attached file) and I can't connect.
** Attachment added: "Log errors from wpa_supplicant when using without
certificate"
http://launchpadlibrarian.net/19944642/without-certificate.txt
--
invalid characters in links from /etc/ssl/certs
https://bugs.launchpad.net/bugs/302182
You received this bug notification because you are a m
*** This bug is a duplicate of bug 272185 ***
https://bugs.launchpad.net/bugs/272185
** This bug has been marked a duplicate of bug 272185
[Intrepid] iwl3945 + iwlagn -- network-manager will not connect to a WPA EAP
(Enterprise) network (disassociating by local choice (reason=3) )
--
inv
I've something also interesting: on a full patched fresh intrepid
install, I can connect on WPA2 using TTLS and PAP the first time. But
when I disconnect and reconnect using the network applet, it doesn't
work anymore.
--
"Trouble-a-cat limited"
--
[Intrepid] iwl3945 + iwlagn -- network-manager
I'm not sure it's really solved.
If I try to connect with a fresh setup from the network manager gui, it
works but /var/log/wpa_supplicant.log contains:
CTRL-EVENT-SCAN-RESULTS
Associated with 00:1e:be:a7:f6:90
CTRL-EVENT-EAP-STARTED EAP authentication started
CTRL-EVENT-EAP-METHOD EAP vendor 0
48 matches
Mail list logo
