[Bug 245968] Re: D-Link DWL-G520 (Atheros chipset) hangs system with incorrect /etc/network/interfaces

Launchpad Bug Tracker 245968 at bugs.launchpad.net
Fri Jun 28 04:17:48 UTC 2013


[Expired for wireless-tools (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: wireless-tools (Ubuntu)
       Status: Incomplete => Expired

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

Title:
  D-Link DWL-G520 (Atheros chipset) hangs system with incorrect
  /etc/network/interfaces

Status in “wireless-tools” package in Ubuntu:
  Expired

Bug description:
  Hello,

  I am trying to configure atheros-based wireless adapter D-Link DWL-G520 in Ubuntu 8.04.1 as an access point. 
  It can be brought up using sequence like 
    wlanconfig ath0 destroy
    wlanconfig ath0 create wlandev wifi0 wlanmode master
    ifconfig ath0 192.168.1.2 up
    iwconfig ath0 essid "Desktop_computer" 
  from command line. 
  However, when I try to put this in /etc/network/interfaces, the card behaves strangely. Following instructions from http://madwifi.org/wiki/UserDocs/SimpleAccessPoint I tried to up ath0 at start time:
  My /etc/network/interfaces:
    auto lo
    iface lo inet loopback

    iface eth0 inet static
    address xx.xx.xx.xx
    netmask xx.xx.xx.xx
    gateway xx.xx.xx.xx
    auto eth0

    iface ath0 inet static
    pre-up wlanconfig ath0 destroy || true
    pre-up wlanconfig ath0 create wlandev wifi0 wlanmode ap
    post-down wlanconfig ath0 destroy
    wireless-mode master
    wireless-channel 11
    wireless-essid my_ssid
    address 192.168.0.2
    netmask 255.255.255.0
    auto ath0

  Then after "sudo /etc/init.d/networking restart" or during reboot computer hangs. 
  If I comment two lines 
  #  wireless-mode master
  #  wireless-channel 11
  , it does not hang. However, 
  1) "route" stops working: routing tables clean and   "route add ... " gives an error "SIOCADDRT: no such process" (maybe this is not important and can be fixed independently)
  2) Interface is brought up in managed mode and with void ESSID.

  UPD.  Setting 
    options ath_pci autocreate=ap
  in /etc/modprobe.d/madwifi
  and 
    madwifi-base wifi0
    madwifi-mode master
    wireless-essid my_ssid
  in /etc/network/interfaces works well.
  However, I do confirm hangup with incorrect interfaces file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-tools/+bug/245968/+subscriptions




More information about the foundations-bugs mailing list