I can't confirm this symptom in 9.04. Please set the status to:
1) New if reproducible in a supported or development Ubuntu version, or
2) Fix Released if you cannot reproduce it in a supported or development Ubuntu
version.
Feel free to try a daily-live or desktop image of 9.04 alpha 2.
** Chan
I've got a customised version of Ubuntu on a memory stick so I tried
setting that up to start my wifi in /etc/network/interfaces.
iface wlan0 inet dhcp
wpa-ssid "MySSID"
wpa-psk "secret"
With Hardy wpa_supplicant did start, but I had the original symptoms of
no network traffic working, ev
Has the new wireless stack and network-manager application fixed this
issue? If so this bug can be closed.
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Unfortunately I don't have Ubuntu installed at the moment. I might be
installing it on a wireless system in a few weeks, but that will be
further complicated because it needs ndiswrapper. Did anyone open a bug
for ifupdown? That's where the problem seemed to be to me in the end.
--
wpa_supplicant
[Expired for wpasupplicant (Ubuntu) because there has been no activity
for 60 days.]
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
after ifup'ing, can you connect to the supplicant with wpa_cli, issue a
'level 0' and paste the output here?
** Changed in: wpasupplicant (Ubuntu)
Status: Unconfirmed => Needs Info
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91477
--
ubuntu-bugs
All it prints is "OK". Nothing appears to happen after that. I'm not
sure what you were expecting.
After a bit of playing around I think network-manager might have been
interfering with the results. Since uninstalling that I'm now getting
the same results as I had with Edgy: it won't connect at bo
H. is network-manager perhaps starting a private wpa_supplicant
instance?
While at the wpa_cli shell, you can use the command 'status' for
connection status. use 'help' for a list of available commands.
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91
I think you might be right about network-manager, but that isn't the
real problem.
I've done some poking around with wrapper scripts and extra logging etc
and it appears that when the network is brought up at boot by "auto" it
skips the pre-up phase which is where wpa_supplicant gets started. It
d
hmm. this sounds interesting. Let's create a bugtask against ifupdown
then
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91477
--
ubuntu-bugs mailing list
ubuntu-bugs@
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Medium
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Medium
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Has the new wireless stack and network-manager application fixed this
issue? If so this bug can be closed.
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Unfortunately I don't have Ubuntu installed at the moment. I might be
installing it on a wireless system in a few weeks, but that will be
further complicated because it needs ndiswrapper. Did anyone open a bug
for ifupdown? That's where the problem seemed to be to me in the end.
--
wpa_supplicant
[Expired for wpasupplicant (Ubuntu) because there has been no activity
for 60 days.]
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
after ifup'ing, can you connect to the supplicant with wpa_cli, issue a
'level 0' and paste the output here?
** Changed in: wpasupplicant (Ubuntu)
Status: Unconfirmed => Needs Info
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91477
--
ubuntu-bugs
All it prints is "OK". Nothing appears to happen after that. I'm not
sure what you were expecting.
After a bit of playing around I think network-manager might have been
interfering with the results. Since uninstalling that I'm now getting
the same results as I had with Edgy: it won't connect at bo
H. is network-manager perhaps starting a private wpa_supplicant
instance?
While at the wpa_cli shell, you can use the command 'status' for
connection status. use 'help' for a list of available commands.
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91
I think you might be right about network-manager, but that isn't the
real problem.
I've done some poking around with wrapper scripts and extra logging etc
and it appears that when the network is brought up at boot by "auto" it
skips the pre-up phase which is where wpa_supplicant gets started. It
d
hmm. this sounds interesting. Let's create a bugtask against ifupdown
then
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91477
--
ubuntu-bugs mailing list
ubuntu-bugs@
I can't confirm this symptom in 9.04. Please set the status to:
1) New if reproducible in a supported or development Ubuntu version, or
2) Fix Released if you cannot reproduce it in a supported or development Ubuntu
version.
Feel free to try a daily-live or desktop image of 9.04 alpha 2.
** Chan
I've got a customised version of Ubuntu on a memory stick so I tried
setting that up to start my wifi in /etc/network/interfaces.
iface wlan0 inet dhcp
wpa-ssid "MySSID"
wpa-psk "secret"
With Hardy wpa_supplicant did start, but I had the original symptoms of
no network traffic working, ev
Has the new wireless stack and network-manager application fixed this
issue? If so this bug can be closed.
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Unfortunately I don't have Ubuntu installed at the moment. I might be
installing it on a wireless system in a few weeks, but that will be
further complicated because it needs ndiswrapper. Did anyone open a bug
for ifupdown? That's where the problem seemed to be to me in the end.
--
wpa_supplicant
I can't confirm this symptom in 9.04. Please set the status to:
1) New if reproducible in a supported or development Ubuntu version, or
2) Fix Released if you cannot reproduce it in a supported or development Ubuntu
version.
Feel free to try a daily-live or desktop image of 9.04 alpha 2.
** Chan
I've got a customised version of Ubuntu on a memory stick so I tried
setting that up to start my wifi in /etc/network/interfaces.
iface wlan0 inet dhcp
wpa-ssid "MySSID"
wpa-psk "secret"
With Hardy wpa_supplicant did start, but I had the original symptoms of
no network traffic working, ev
[Expired for wpasupplicant (Ubuntu) because there has been no activity
for 60 days.]
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Medium
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
after ifup'ing, can you connect to the supplicant with wpa_cli, issue a
'level 0' and paste the output here?
** Changed in: wpasupplicant (Ubuntu)
Status: Unconfirmed => Needs Info
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91477
--
ubuntu-bugs
All it prints is "OK". Nothing appears to happen after that. I'm not
sure what you were expecting.
After a bit of playing around I think network-manager might have been
interfering with the results. Since uninstalling that I'm now getting
the same results as I had with Edgy: it won't connect at bo
H. is network-manager perhaps starting a private wpa_supplicant
instance?
While at the wpa_cli shell, you can use the command 'status' for
connection status. use 'help' for a list of available commands.
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91
I think you might be right about network-manager, but that isn't the
real problem.
I've done some poking around with wrapper scripts and extra logging etc
and it appears that when the network is brought up at boot by "auto" it
skips the pre-up phase which is where wpa_supplicant gets started. It
d
hmm. this sounds interesting. Let's create a bugtask against ifupdown
then
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91477
--
ubuntu-bugs mailing list
ubuntu-bugs@
after ifup'ing, can you connect to the supplicant with wpa_cli, issue a
'level 0' and paste the output here?
** Changed in: wpasupplicant (Ubuntu)
Status: Unconfirmed => Needs Info
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91477
--
ubuntu-bugs
All it prints is "OK". Nothing appears to happen after that. I'm not
sure what you were expecting.
After a bit of playing around I think network-manager might have been
interfering with the results. Since uninstalling that I'm now getting
the same results as I had with Edgy: it won't connect at bo
H. is network-manager perhaps starting a private wpa_supplicant
instance?
While at the wpa_cli shell, you can use the command 'status' for
connection status. use 'help' for a list of available commands.
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91
I think you might be right about network-manager, but that isn't the
real problem.
I've done some poking around with wrapper scripts and extra logging etc
and it appears that when the network is brought up at boot by "auto" it
skips the pre-up phase which is where wpa_supplicant gets started. It
d
hmm. this sounds interesting. Let's create a bugtask against ifupdown
then
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91477
--
ubuntu-bugs mailing list
ubuntu-bugs@
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Medium
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
[Expired for wpasupplicant (Ubuntu) because there has been no activity
for 60 days.]
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
after ifup'ing, can you connect to the supplicant with wpa_cli, issue a
'level 0' and paste the output here?
** Changed in: wpasupplicant (Ubuntu)
Status: Unconfirmed => Needs Info
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91477
--
ubuntu-bugs
All it prints is "OK". Nothing appears to happen after that. I'm not
sure what you were expecting.
After a bit of playing around I think network-manager might have been
interfering with the results. Since uninstalling that I'm now getting
the same results as I had with Edgy: it won't connect at bo
H. is network-manager perhaps starting a private wpa_supplicant
instance?
While at the wpa_cli shell, you can use the command 'status' for
connection status. use 'help' for a list of available commands.
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91
I think you might be right about network-manager, but that isn't the
real problem.
I've done some poking around with wrapper scripts and extra logging etc
and it appears that when the network is brought up at boot by "auto" it
skips the pre-up phase which is where wpa_supplicant gets started. It
d
hmm. this sounds interesting. Let's create a bugtask against ifupdown
then
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91477
--
ubuntu-bugs mailing list
ubuntu-bugs@
Has the new wireless stack and network-manager application fixed this
issue? If so this bug can be closed.
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Unfortunately I don't have Ubuntu installed at the moment. I might be
installing it on a wireless system in a few weeks, but that will be
further complicated because it needs ndiswrapper. Did anyone open a bug
for ifupdown? That's where the problem seemed to be to me in the end.
--
wpa_supplicant
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Medium
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
[Expired for wpasupplicant (Ubuntu) because there has been no activity
for 60 days.]
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
I can't confirm this symptom in 9.04. Please set the status to:
1) New if reproducible in a supported or development Ubuntu version, or
2) Fix Released if you cannot reproduce it in a supported or development Ubuntu
version.
Feel free to try a daily-live or desktop image of 9.04 alpha 2.
** Chan
I've got a customised version of Ubuntu on a memory stick so I tried
setting that up to start my wifi in /etc/network/interfaces.
iface wlan0 inet dhcp
wpa-ssid "MySSID"
wpa-psk "secret"
With Hardy wpa_supplicant did start, but I had the original symptoms of
no network traffic working, ev
after ifup'ing, can you connect to the supplicant with wpa_cli, issue a
'level 0' and paste the output here?
** Changed in: wpasupplicant (Ubuntu)
Status: Unconfirmed => Needs Info
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91477
--
ubuntu-bugs
All it prints is "OK". Nothing appears to happen after that. I'm not
sure what you were expecting.
After a bit of playing around I think network-manager might have been
interfering with the results. Since uninstalling that I'm now getting
the same results as I had with Edgy: it won't connect at bo
H. is network-manager perhaps starting a private wpa_supplicant
instance?
While at the wpa_cli shell, you can use the command 'status' for
connection status. use 'help' for a list of available commands.
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91
I think you might be right about network-manager, but that isn't the
real problem.
I've done some poking around with wrapper scripts and extra logging etc
and it appears that when the network is brought up at boot by "auto" it
skips the pre-up phase which is where wpa_supplicant gets started. It
d
hmm. this sounds interesting. Let's create a bugtask against ifupdown
then
** Also affects: ifupdown (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://launchpad.net/bugs/91477
--
ubuntu-bugs mailing list
ubuntu-bugs@
** Changed in: ifupdown (Ubuntu)
Importance: Undecided => Medium
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Has the new wireless stack and network-manager application fixed this
issue? If so this bug can be closed.
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Unfortunately I don't have Ubuntu installed at the moment. I might be
installing it on a wireless system in a few weeks, but that will be
further complicated because it needs ndiswrapper. Did anyone open a bug
for ifupdown? That's where the problem seemed to be to me in the end.
--
wpa_supplicant
I can't confirm this symptom in 9.04. Please set the status to:
1) New if reproducible in a supported or development Ubuntu version, or
2) Fix Released if you cannot reproduce it in a supported or development Ubuntu
version.
Feel free to try a daily-live or desktop image of 9.04 alpha 2.
** Chan
I've got a customised version of Ubuntu on a memory stick so I tried
setting that up to start my wifi in /etc/network/interfaces.
iface wlan0 inet dhcp
wpa-ssid "MySSID"
wpa-psk "secret"
With Hardy wpa_supplicant did start, but I had the original symptoms of
no network traffic working, ev
[Expired for wpasupplicant (Ubuntu) because there has been no activity
for 60 days.]
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
Has the new wireless stack and network-manager application fixed this
issue? If so this bug can be closed.
--
wpa_supplicant doesn't work in "managed mode" in Feisty
https://bugs.launchpad.net/bugs/91477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Unfortunately I don't have Ubuntu installed at the moment. I might be
installing it on a wireless system in a few weeks, but that will be
further complicated because it needs ndiswrapper. Did anyone open a bug
for ifupdown? That's where the problem seemed to be to me in the end.
--
wpa_supplicant
I can't confirm this symptom in 9.04. Please set the status to:
1) New if reproducible in a supported or development Ubuntu version, or
2) Fix Released if you cannot reproduce it in a supported or development Ubuntu
version.
Feel free to try a daily-live or desktop image of 9.04 alpha 2.
** Chan
I've got a customised version of Ubuntu on a memory stick so I tried
setting that up to start my wifi in /etc/network/interfaces.
iface wlan0 inet dhcp
wpa-ssid "MySSID"
wpa-psk "secret"
With Hardy wpa_supplicant did start, but I had the original symptoms of
no network traffic working, ev
66 matches
Mail list logo
