Public bug reported:
With Feisty beta, when my Dell LS400 boots the Lucent Orinoco Gold Wi-Fi
NIC does not associate with the configured SSID, instead it connects to
a neighbor's SSID - it never obtains an IP address. If the interface is
ifdown'ed then ifup'ed it correctly associates with my AP a
Apologies for missing some key info.
uname -a
Linux ethel 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686
GNU/Linux
It's a PIII 450 MHz Dell LS400 laptop.
Since filling the bug report I've tidied up my interfaces file and
iftab, so what was eth1 is now wlan0, and eth0 has been cleane
output of lspci --vvnn
Thanks for the rapid response, and apologies for my slow turnaround.
Thanks
Alan
** Attachment added: "lspci-vvnn.log"
http://librarian.launchpad.net/7216068/lspci-vvnn.log
--
Wireless LAN associates with wrong AP on wrong SSID
https://bugs.launchpad.net/bugs/99838
Y
Based on other bugs listed here I enabled nm-applet, removed all entries
for interfaces from /etc/network/interfaces and a few UI familiarity
issues aside it all appears to work correctly now - i.e. if I start the
PC from cold or bring it back from hibernation it connects to the
correct AP etc. I
Public bug reported:
With Feisty beta, when my Dell LS400 boots the Lucent Orinoco Gold Wi-Fi
NIC does not associate with the configured SSID, instead it connects to
a neighbor's SSID - it never obtains an IP address. If the interface is
ifdown'ed then ifup'ed it correctly associates with my AP a
Based on other bugs listed here I enabled nm-applet, removed all entries
for interfaces from /etc/network/interfaces and a few UI familiarity
issues aside it all appears to work correctly now - i.e. if I start the
PC from cold or bring it back from hibernation it connects to the
correct AP etc. I
Apologies for missing some key info.
uname -a
Linux ethel 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686
GNU/Linux
It's a PIII 450 MHz Dell LS400 laptop.
Since filling the bug report I've tidied up my interfaces file and
iftab, so what was eth1 is now wlan0, and eth0 has been cleane
output of lspci --vvnn
Thanks for the rapid response, and apologies for my slow turnaround.
Thanks
Alan
** Attachment added: "lspci-vvnn.log"
http://librarian.launchpad.net/7216068/lspci-vvnn.log
--
Wireless LAN associates with wrong AP on wrong SSID
https://bugs.launchpad.net/bugs/99838
Y
Apologies for missing some key info.
uname -a
Linux ethel 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686
GNU/Linux
It's a PIII 450 MHz Dell LS400 laptop.
Since filling the bug report I've tidied up my interfaces file and
iftab, so what was eth1 is now wlan0, and eth0 has been cleane
output of lspci --vvnn
Thanks for the rapid response, and apologies for my slow turnaround.
Thanks
Alan
** Attachment added: "lspci-vvnn.log"
http://librarian.launchpad.net/7216068/lspci-vvnn.log
--
Wireless LAN associates with wrong AP on wrong SSID
https://bugs.launchpad.net/bugs/99838
Y
Based on other bugs listed here I enabled nm-applet, removed all entries
for interfaces from /etc/network/interfaces and a few UI familiarity
issues aside it all appears to work correctly now - i.e. if I start the
PC from cold or bring it back from hibernation it connects to the
correct AP etc. I
Public bug reported:
With Feisty beta, when my Dell LS400 boots the Lucent Orinoco Gold Wi-Fi
NIC does not associate with the configured SSID, instead it connects to
a neighbor's SSID - it never obtains an IP address. If the interface is
ifdown'ed then ifup'ed it correctly associates with my AP a
Public bug reported:
With Feisty beta, when my Dell LS400 boots the Lucent Orinoco Gold Wi-Fi
NIC does not associate with the configured SSID, instead it connects to
a neighbor's SSID - it never obtains an IP address. If the interface is
ifdown'ed then ifup'ed it correctly associates with my AP a
Public bug reported:
With Feisty beta, when my Dell LS400 boots the Lucent Orinoco Gold Wi-Fi
NIC does not associate with the configured SSID, instead it connects to
a neighbor's SSID - it never obtains an IP address. If the interface is
ifdown'ed then ifup'ed it correctly associates with my AP a
Apologies for missing some key info.
uname -a
Linux ethel 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686
GNU/Linux
It's a PIII 450 MHz Dell LS400 laptop.
Since filling the bug report I've tidied up my interfaces file and
iftab, so what was eth1 is now wlan0, and eth0 has been cleane
output of lspci --vvnn
Thanks for the rapid response, and apologies for my slow turnaround.
Thanks
Alan
** Attachment added: "lspci-vvnn.log"
http://librarian.launchpad.net/7216068/lspci-vvnn.log
--
Wireless LAN associates with wrong AP on wrong SSID
https://bugs.launchpad.net/bugs/99838
Y
Based on other bugs listed here I enabled nm-applet, removed all entries
for interfaces from /etc/network/interfaces and a few UI familiarity
issues aside it all appears to work correctly now - i.e. if I start the
PC from cold or bring it back from hibernation it connects to the
correct AP etc. I
Apologies for missing some key info.
uname -a
Linux ethel 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686
GNU/Linux
It's a PIII 450 MHz Dell LS400 laptop.
Since filling the bug report I've tidied up my interfaces file and
iftab, so what was eth1 is now wlan0, and eth0 has been cleane
output of lspci --vvnn
Thanks for the rapid response, and apologies for my slow turnaround.
Thanks
Alan
** Attachment added: "lspci-vvnn.log"
http://librarian.launchpad.net/7216068/lspci-vvnn.log
--
Wireless LAN associates with wrong AP on wrong SSID
https://bugs.launchpad.net/bugs/99838
Y
Based on other bugs listed here I enabled nm-applet, removed all entries
for interfaces from /etc/network/interfaces and a few UI familiarity
issues aside it all appears to work correctly now - i.e. if I start the
PC from cold or bring it back from hibernation it connects to the
correct AP etc. I
Public bug reported:
With Feisty beta, when my Dell LS400 boots the Lucent Orinoco Gold Wi-Fi
NIC does not associate with the configured SSID, instead it connects to
a neighbor's SSID - it never obtains an IP address. If the interface is
ifdown'ed then ifup'ed it correctly associates with my AP a
Apologies for missing some key info.
uname -a
Linux ethel 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686
GNU/Linux
It's a PIII 450 MHz Dell LS400 laptop.
Since filling the bug report I've tidied up my interfaces file and
iftab, so what was eth1 is now wlan0, and eth0 has been cleane
output of lspci --vvnn
Thanks for the rapid response, and apologies for my slow turnaround.
Thanks
Alan
** Attachment added: "lspci-vvnn.log"
http://librarian.launchpad.net/7216068/lspci-vvnn.log
--
Wireless LAN associates with wrong AP on wrong SSID
https://bugs.launchpad.net/bugs/99838
Y
Based on other bugs listed here I enabled nm-applet, removed all entries
for interfaces from /etc/network/interfaces and a few UI familiarity
issues aside it all appears to work correctly now - i.e. if I start the
PC from cold or bring it back from hibernation it connects to the
correct AP etc. I
24 matches
Mail list logo
