LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Wireless Networking (https://www.linuxquestions.org/questions/linux-wireless-networking-41/)
-   -   receive packet failed on wlan0: Network is down (https://www.linuxquestions.org/questions/linux-wireless-networking-41/receive-packet-failed-on-wlan0-network-is-down-500452/)

juanjavier_xxx 11-10-2006 05:55 PM

receive packet failed on wlan0: Network is down
 
I'm unable to get ip address in my acer aspire 3610
although wlan0 interface rises ok.

[HTML]debian:/home/juanja# iwlist wlan0 scanning

wlan0 Scan completed:
Cell 01 - Address: 00:03:c9:e6:e0:f4
ESSID:"<hidden>"
PROTOCOL: ieee 802.11bg
Mode: Master
Channel: 11
Encryption Key: off
Bit Rates: 54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 6 9 11 18 24 36 48 54
Quality=100/100 Signal level=-230 dBm
Extra: Last beacon: 440ms ago[/HTML]

As you see, the wlan0 interface gets up. However the network doesn't.

[HTML]debian:/home/juanja# dhclient wlan0

DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
receive_packet failed on wlan0: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
No DHCPOFFERS received.

No working leases in persistent database.

Sleeping.[/HTML]

Router has got DHCP on since an athlon via eth0

rises the network and gets ip address fine.

This seems a little tricky!!!

Could someone help me?

What I have found by just googling "receive_packet failed on wlan0: Network is down"

only explains how to configure the network in "Managed" mode asigning step by step ip address, subnet mask and gateway.

And it does not work, because when you ping to the router the message

"destination host unavailable" shows. :-(

Any help would be truly appreciated.

Juan Javier.

dxqcanada 11-10-2006 07:34 PM

I sounds as if you are not really attached yet.

What does "iwconfig" display ??

juanjavier_xxx 11-11-2006 02:30 AM

Quote:

Originally Posted by dxqcanada
I sounds as if you are not really attached yet.

What does "iwconfig" display ??

Here it is:

[HTML]debian:~# iwconfig
lo no wireless extensions.

wlan0 IEEE 802.11b/g ESSID:off/any Nickname:"Broadcom 4310"
Mode:Managed Frequency=2.484 Ghz Access Point: Invalid
Bit Rate=11 Mb/s Tx-Power=19dBm
RTS thr:of Fragment thr:off
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

sit0 no wireless extensions.[/HTML]

dxqcanada 11-11-2006 08:13 AM

iwconfig is showing that you have not connected yet ... otherwise you would see the ESSID and Access Point (MAC address) being displayed.

Is your wireless config setup correctly ??

juanjavier_xxx 11-11-2006 10:25 AM

Quote:

Originally Posted by dxqcanada
Is your wireless config setup correctly ??

How would I check that?

Up until I apt-get updated, apt-get upgraded and apt-get dist-upgraded Debian Testing everything worked fine...I did not even change anything in the router....

Wireless with ndiswrapper worked fine before updating testing...

Greetings,

Juanjavier

juanjavier_xxx 11-11-2006 02:02 PM

apt-get install dhcp3-client solved the problem.

These things may happen because of the ever-changing nature of Debian Testing.

Sometimes, upon updataing things in Testing, things may break, but it is likely to be fixed soon. This seems to be the case.

Thanks for helping...

Juanjavier.

UhhMaybe 05-25-2007 11:40 PM

Redo the "ndiswrapper" work-around after YOU have finished the updating of YOUR system. My way of looking at is..."What have YOU done for me lately"...Operating System. The recent changes are given priority to the original values and settings. Good luck.


All times are GMT -5. The time now is 08:58 PM.