Reported fixed by the original reporter. However, there is still an
issue; we need to figure out why that specific combination of settings
isn't supported.
** Changed in: network-manager (Ubuntu)
Status: Incomplete = Triaged
--
You received this bug notification because you are a member
Looks like this was actually because a ad-hoc network was setup with key
management (e.g. radius) which is not supported unless in infrastructure
mode, marking Invalid.
For reference, this is rsn_flags 0x188, which is
NM_802_11_AP_SEC_KEY_MGMT_PSK, with CCMP for PAIR and GROUP level
security (see
Thanks for your help problem solved !!
On Fri, Mar 4, 2011 at 10:59 PM, Mathieu Trudel-Lapierre mathieu.tl@
gmail.com wrote:
If you changed the settings you will probably need to recreate the
connection, here all it says is that the applet went back to
disconnected.
Please, attach an
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729123
Title:
I cannot connect to an adhoc network created with windows
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Hi,
Thanks for reporting this bug and helping to make Ubuntu better.
If you have enabled security settings in creating the ad-hoc network on
the Windows machine, could you try to disable them and create a network
as simple as possible in case it allows us to further isolate the issue
to a
I have disabled the security setting on the windows machine (no password
required to connect)
now i get this messages from the terminal:
** (nm-applet:4261): DEBUG: old state indicates that this was not a
disconnect 0
** (nm-applet:4261): DEBUG: old state indicates that this was not a
disconnect
If you changed the settings you will probably need to recreate the
connection, here all it says is that the applet went back to
disconnected.
Please, attach an excerpt from /var/log/syslog rather than the messages
from the console or xsession-errors, as most of the information
regarding how NM
