Salut, depuis peu, je peux pas me connecter en wifi malgré que le réseau ne soit pas crypté... Je n'ai fais aucune manipulation particulière si ce n'ai d'avoir quitté se réseau un moment pour me connecter sur plusieurs réseaux crypté en WEP et WPA à mon retour, impossible de me connecter sur le réseau en clair car je n'obtient aucune adresse IP.
Je possède une car Intel IPW2200BG, je suis sous Debian Sid et voici les infos disponibles.
iwconfig :
Code :
1
2
3
4
5
6
7
8
9
10
|
eth2 IEEE 802.11b ESSID:"ARPEJ5"
Mode:Managed Frequency:2.427 GHz Access Point: 00:13:46:FF:C5:21
Bit Rate:11 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=59/100 Signal level=-65 dBm Noise level=-85 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:6 Missed beacon:0 |
ifconfig :
Code :
1
2
3
4
5
6
7
8
9
|
eth2 Lien encap:Ethernet HWaddr 00:13:CE:80:9C:4D
adr inet6: fe80::213:ceff:fe80:9c4d/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70 errors:0 dropped:6 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:302312 (295.2 KiB) TX bytes:4128 (4.0 KiB)
Interruption:20 Mémoire:ffcfe000-ffcfefff |
modinfo ipw2200 :
Code :
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
|
filename: /lib/modules/2.6.22-1-686/kernel/drivers/net/wireless/ipw2200.ko
license: GPL
author: Copyright(c) 2003-2006 Intel Corporation
version: 1.2.0kmq
description: Intel(R) PRO/Wireless 2200/2915 Network Driver
srcversion: C8FDDECE3284D323185C636
alias: pci:v00008086d00004224sv*sd*bc*sc*i*
alias: pci:v00008086d00004223sv*sd*bc*sc*i*
alias: pci:v00008086d00004221sv*sd*bc*sc*i*
alias: pci:v00008086d00004220sv*sd*bc*sc*i*
alias: pci:v00008086d0000104Fsv*sd*bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002762bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002761bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002754bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002753bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002752bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002751bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002742bc*sc*i*
alias: pci:v00008086d00001043sv0000103Csd00002741bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002741bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002732bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002731bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002722bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002721bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002712bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002711bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002702bc*sc*i*
alias: pci:v00008086d00001043sv00008086sd00002701bc*sc*i*
depends: ieee80211,firmware_class
vermagic: 2.6.22-1-686 SMP mod_unload 686
parm: disable:manually disable the radio (default 0 [radio on]) (int)
parm: associate:auto associate when scanning (default on) (int)
parm: auto_create:auto create adhoc network (default on) (int)
parm: led:enable led control on some systems (default 0 off)
(int)
parm: debug:debug output mask (int)
parm: channel:channel to limit associate to (default 0 [ANY]) (int)
parm: qos_enable:enable all QoS functionalitis (int)
parm: qos_burst_enable:enable QoS burst mode (int)
parm: qos_no_ack_mask:mask Tx_Queue to no ack (int)
parm: burst_duration_CCK:set CCK burst value (int)
parm: burst_duration_OFDM:set OFDM burst value (int)
parm: mode:network mode (0=BSS,1=IBSS,2=Monitor) (int)
parm: bt_coexist:enable bluetooth coexistence (default off) (int)
parm: hwcrypto:enable hardware crypto (default off) (int)
parm: cmdlog:allocate a ring buffer for logging firmware commands (int)
parm: roaming:enable roaming support (default on) (int)
parm: antenna:select antenna 1=Main, 3=Aux, default 0 [both], 2=slow_diversity (choose the one with lower background noise) (int) |
dmseg | grep eth :
Code :
1
2
3
4
5
6
7
8
9
10
11
|
eth0: RealTek RTL8139 at 0x1000, 00:03:0d:3d:db:65, IRQ 18
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
eth0: link down
ADDRCONF(NETDEV_UP): eth0: link is not ready
eth2: no IPv6 routers present
martian source 255.255.255.255 from 192.168.5.254, on dev eth2
martian source 255.255.255.255 from 192.168.5.254, on dev eth2
martian source 255.255.255.255 from 192.168.5.254, on dev eth2
martian source 255.255.255.255 from 192.168.5.254, on dev eth2
martian source 255.255.255.255 from 192.168.5.62, on dev eth2 |
Et lorsque je lance la connexion,
invoke-rc.d networking start :
Code :
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
|
Configuring network interfaces...
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth2/00:13:ce:80:9c:4d
Sending on LPF/eth2/00:13:ce:80:9c:4d
Sending on Socket/fallback
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 16
DHCPOFFER from 192.168.5.254
DHCPREQUEST on eth2 to 255.255.255.255 port 67
DHCPNAK from 192.168.5.254
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 3
DHCPOFFER from 192.168.5.254
DHCPREQUEST on eth2 to 255.255.255.255 port 67
DHCPNAK from 192.168.5.254
DHCPREQUEST on eth2 to 255.255.255.255 port 67
DHCPNAK from 192.168.5.254
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 3
DHCPOFFER from 192.168.5.254
DHCPREQUEST on eth2 to 255.255.255.255 port 67
DHCPNAK from 192.168.5.254
DHCPREQUEST on eth2 to 255.255.255.255 port 67
DHCPNAK from 192.168.5.254 |
Il semble que le client DHCP n'obtient pas d'adresse IP et en même temps s'inscrit dans le log,
tail /var/log/message :
Code :
1
2
3
4
5
6
7
8
9
10
11
|
Aug 27 23:49:36 korola kernel: martian source 255.255.255.255 from 192.168.5.254, on dev eth2
Aug 27 23:49:36 korola kernel: ll header: ff:ff:ff:ff:ff:ff:00:16:ae:36:c8:5a:08:00
Aug 27 23:49:39 korola kernel: martian source 255.255.255.255 from 192.168.5.254, on dev eth2
Aug 27 23:49:39 korola kernel: ll header: ff:ff:ff:ff:ff:ff:00:16:ae:36:c8:5a:08:00
Aug 27 23:49:43 korola kernel: martian source 255.255.255.255 from 192.168.5.254, on dev eth2
Aug 27 23:49:43 korola kernel: ll header: ff:ff:ff:ff:ff:ff:00:16:ae:36:c8:5a:08:00
Aug 27 23:49:53 korola kernel: martian source 255.255.255.255 from 192.168.5.254, on dev eth2
Aug 27 23:49:53 korola kernel: ll header: ff:ff:ff:ff:ff:ff:00:16:ae:36:c8:5a:08:00
Aug 27 23:50:01 korola kernel: martian source 255.255.255.255 from 192.168.5.254, on dev eth2
Aug 27 23:50:01 korola kernel: ll header: ff:ff:ff:ff:ff:ff:00:16:ae:36:c8:5a:08:00 |
Je ne vois pas d'où vient le problème d'autant plus que je n'ai rien touché au niveau de ma configuration. De plus sous Windows XP, le même phénomène semble intervenir car lors de la connexion il reste figé avec le message "Lecture de l'adresse résau", et ne semble pas obtenir d'adresse IP.
Donc je ne comprends vraiment rien d'aut que d'autres PCs arrivent à se connecter au résau.
28/08/2007, 00h18
Connexion WIFI impossible
00
Trouvez facilement les réponses à toutes vos questions
Arnaud Feltz
Installation de Code::Blocks sous Debian à partir de Nightly Builds
