[Bug 240520] Re: [hardy] ifup fails to trigger association with WEP access points

Andrew Shadura bugzilla at tut.by
Wed Dec 21 09:22:08 UTC 2011


** Package changed: ifupdown (Ubuntu) => wireless-tools (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/240520

Title:
  [hardy] ifup fails to trigger association with WEP access points

Status in The acton project:
  New
Status in “wireless-tools” package in Ubuntu:
  New

Bug description:
  Binary package hint: ifupdown

  I've been debugging a customer problem with a MID device in which they
  report that Manual Configuration of WEP access points doesn't work (
  ie. my device doesn't associate with the AP, and thus never comes
  online ).

  I have no problems connecting to the same access point using
  NetworkManager / nm-applet.

  It's taken me awhile, but I've finally traced Manual Configuration of
  Wireless from the gnome-system-tools application network-admin to
  liboob, to system-tools-backends, to ifupdown.

  I've also had most of the people in my office ( Canonical Lexington )
  try the same scenario, and so far, nobody else has been able to get
  Manual Configuration / WEP to work either, so this is not a problem
  specific to the device ( or driver ) we're working with.  FYI, the
  driver in question has it's own problems...  it's the Marvell sd8686
  driver ported by Intel.

  I've also tried manually running ifup with the same interfaces stanzas
  that network-admin produces, which is why I'm adding this as an
  ifupdown bug.

  The version of ifupdown on the system's I've tested is 0.6.8ubuntu8.

  Here's what my /etc/network/interfaces file contains:

  --------------------------------------------------------------------
  auto lo
  iface l0 inet loopback


  iface wlan0 inet dhcp
  wireless-key s:FAKEKEYFORWEP
  wireless-essid UbuntuTest

  auto wlan0
  -----------------------------------------------------------------------

  Note -- I've tried this with a Macbook Pro ( Santa Rosa ) running
  madwifi, a Sony Vaio using an ipw2x00 card, a ThinkPad running madwifi
  0.9.4, and none of them work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/acton/+bug/240520/+subscriptions




More information about the foundations-bugs mailing list