Annoying wireless error - Ubuntu

This is a discussion on Annoying wireless error - Ubuntu ; Hi NG I installed a wireless card in for my friend, Atheros chip (proxim orinoco card). When I start the PC and try to log on, the logon process freeze trying to start firestarter, it fails, and I have to ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Annoying wireless error

  1. Annoying wireless error

    Hi NG

    I installed a wireless card in for my friend, Atheros chip (proxim orinoco
    card).
    When I start the PC and try to log on, the logon process freeze trying to
    start firestarter, it fails, and I have to hit CTRL+BACKSPACE, and then log
    again. At this point I have no network and must restart the network service
    manually, and everything starts working. There is a laptop with with the
    exact same config but different card, no problem what so ever!
    Here is the output for /etc/init.d/networking restart
    >>>

    Reconfiguring network interfaces...
    * Stopping the Firestarter firewall...
    ...done.
    * Starting the Firestarter firewall...
    ...fail!
    run-parts: /etc/network/if-down.d /50firestarter exited with return code 2
    There is already a pid file /var/run/dhclient.ath0.pid with pid 5629
    killed old client process, removed PID file
    Internet Systems Consortium DHCP Client V3.0.5
    Copyright 2004-2006 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/

    wifi0: unknown hardware address type 801
    wifi0: unknown hardware address type 801
    Listening on LPF/ath0/00:20:a6:54:f9:61
    Sending on LPF/ath0/00:20:a6:54:f9:61
    Sending on Socket/fallback
    DHCPRELEASE on ath0 to 192.168.50.1 port 67
    wlan0: ERROR while getting interface flags: No such device
    Error for wireless request "Set Encode" (8B2A) :
    SET failed on device wlan0 ; No such device.
    Error for wireless request "Set ESSID" (8B1A) :
    SET failed on device wlan0 ; No such device.
    There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519120
    Internet Systems Consortium DHCP Client V3.0.5
    Copyright 2004-2006 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/

    wifi0: unknown hardware address type 801
    SIOCSIFADDR: No such device
    wlan0: ERROR while getting interface flags: No such device
    wlan0: ERROR while getting interface flags: No such device
    wifi0: unknown hardware address type 801
    Bind socket to interface: No such device
    Failed to bring up wlan0.
    There is already a pid file /var/run/dhclient.ath0.pid with pid 134519120
    Internet Systems Consortium DHCP Client V3.0.5
    Copyright 2004-2006 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/

    wifi0: unknown hardware address type 801
    wifi0: unknown hardware address type 801
    Listening on LPF/ath0/00:20:a6:54:f9:61
    Sending on LPF/ath0/00:20:a6:54:f9:61
    Sending on Socket/fallback
    DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
    DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
    DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
    DHCPOFFER from 192.168.50.1
    DHCPREQUEST on ath0 to 255.255.255.255 port 67
    DHCPACK from 192.168.50.1
    bound to 192.168.50.4 -- renewal in 35253 seconds.
    * Stopping the Firestarter firewall...
    ...done.
    * Starting the Firestarter firewall...
    ...done.

    How do I resolve this issue?

    TIA
    --
    :-)

  2. Re: Annoying wireless error

    On 2008-01-18, Holz wrote:
    > Hi NG
    >
    > I installed a wireless card in for my friend, Atheros chip (proxim orinoco
    > card).
    > When I start the PC and try to log on, the logon process freeze trying to
    > start firestarter, it fails, and I have to hit CTRL+BACKSPACE, and then log
    > again. At this point I have no network and must restart the network service
    > manually, and everything starts working. There is a laptop with with the
    > exact same config but different card, no problem what so ever!
    > Here is the output for /etc/init.d/networking restart
    >>>>

    > Reconfiguring network interfaces...
    > * Stopping the Firestarter firewall...
    > ...done.
    > * Starting the Firestarter firewall...
    > ...fail!
    > run-parts: /etc/network/if-down.d /50firestarter exited with return code 2
    > There is already a pid file /var/run/dhclient.ath0.pid with pid 5629
    > killed old client process, removed PID file
    > Internet Systems Consortium DHCP Client V3.0.5
    > Copyright 2004-2006 Internet Systems Consortium.
    > All rights reserved.
    > For info, please visit http://www.isc.org/sw/dhcp/
    >
    > wifi0: unknown hardware address type 801
    > wifi0: unknown hardware address type 801
    > Listening on LPF/ath0/00:20:a6:54:f9:61
    > Sending on LPF/ath0/00:20:a6:54:f9:61
    > Sending on Socket/fallback
    > DHCPRELEASE on ath0 to 192.168.50.1 port 67
    > wlan0: ERROR while getting interface flags: No such device
    > Error for wireless request "Set Encode" (8B2A) :
    > SET failed on device wlan0 ; No such device.
    > Error for wireless request "Set ESSID" (8B1A) :
    > SET failed on device wlan0 ; No such device.
    > There is already a pid file /var/run/dhclient.wlan0.pid with pid 134519120
    > Internet Systems Consortium DHCP Client V3.0.5
    > Copyright 2004-2006 Internet Systems Consortium.
    > All rights reserved.
    > For info, please visit http://www.isc.org/sw/dhcp/
    >
    > wifi0: unknown hardware address type 801
    > SIOCSIFADDR: No such device
    > wlan0: ERROR while getting interface flags: No such device
    > wlan0: ERROR while getting interface flags: No such device
    > wifi0: unknown hardware address type 801
    > Bind socket to interface: No such device
    > Failed to bring up wlan0.
    > There is already a pid file /var/run/dhclient.ath0.pid with pid 134519120
    > Internet Systems Consortium DHCP Client V3.0.5
    > Copyright 2004-2006 Internet Systems Consortium.
    > All rights reserved.
    > For info, please visit http://www.isc.org/sw/dhcp/
    >
    > wifi0: unknown hardware address type 801
    > wifi0: unknown hardware address type 801
    > Listening on LPF/ath0/00:20:a6:54:f9:61
    > Sending on LPF/ath0/00:20:a6:54:f9:61
    > Sending on Socket/fallback
    > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
    > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
    > DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
    > DHCPOFFER from 192.168.50.1
    > DHCPREQUEST on ath0 to 255.255.255.255 port 67
    > DHCPACK from 192.168.50.1
    > bound to 192.168.50.4 -- renewal in 35253 seconds.
    > * Stopping the Firestarter firewall...
    > ...done.
    > * Starting the Firestarter firewall...
    > ...done.
    >
    > How do I resolve this issue?
    >
    > TIA


    I would put out the firestarter, turn off the firewall. See if that helps. I
    find getting rid of all the bits not required helps to track down the
    problem. Less parts to go wrong. Then once working put all the bits back.
    Trust that makes sense

  3. Re: Annoying wireless error

    Gordon wrote:

    > I would put out the firestarter

    Firestarter is not the problem, verified that.
    --
    :-)

  4. Re: Annoying wireless error

    Holz wrote:

    > Gordon wrote:
    >
    >> I would put out the firestarter

    > Firestarter is not the problem, verified that.

    Well, I ended up writing a short logon script that will restart networking
    and then the firewall, it is working now, though I am still puzzled.
    --
    :-)

+ Reply to Thread