[Wifi] je vais devenir fou :) [ABANDONNE]

Poischack · Last edited by Poischack on Sat May 28, 2005 12:11 pm; edited 1 time in total

Bonjour,
y a des jours où je me dit "et merdeeeee pourquoi j'ai fait ça ?" c'est exactement ce que je me suis dit aujorud'hui midi:
sur mon portable depuis un moment je ne pouvais plus me servir de ma connexion wifi, je ne pouvais plus spécifier le essid et donc plus me connecter à réseau lan, donc je me suis dit ça marchais avant alros pourquoi je réinstallerais pas ?
Hier soir j'ai pris mes deux cou***es en main j'ai fais qques backups, formatter/réinstaller gentoo (2005.0), à midi après avoir récupérer un système utilisable (emerge unmerge nano, emerge vim

), je vais pour configurer ma IPN2220 Wireless LanExpress (qui marche bien sous WinXP). Et là au boot je me rends compte d'un truc: le dmesg ne m'indique pas que mon kernel est trouvé ma carte

Je re-regarde mon kernel l'option wireless lan cad support est activé. Je boot sur le live-cd en me disant que j'ai peut etre mal configuré une option dans le kernel même soucis....
Je redemarre sous windows, la carte est là. Ma question est donc: selon vous pourquoi ma carte n'est plus détécté au boot ? (j'ai compris ça en essayant de config ma carte avec ndiswrapper ensuite quand je ne pouvais rien faire (pas de config du essid et tout ce qui suit)

Ni[o · Posted: Mon May 23, 2005 5:39 pm Post subject:

peut être te faut-il un module non présent dans le noyaux ?

Cas des modules rt2500 (Ralink) par ex.

Si toi tu passes par le module ip2200 je pense tu dois installer le module, le firmware pour que cela marche...

http://ipw2200.sourceforge.net/
http://gentoo-wiki.com/HOWTO_Wireless_Configuration_and_Startup
http://gentoo-wiki.com/HARDWARE_ipw2200
_________________
http://www.destination-linux.org/
http://www.entre-aide.org/
http://www.lessteinmetz.net/

naerex · Posted: Mon May 23, 2005 5:40 pm Post subject:

ta carte n'est pas supportée d'origine.

essaye avec ça:

sinarf · n00b Joined: 08 Mar 2003 Posts: 40

NiLuJe · Posted: Mon May 23, 2005 8:47 pm Post subject:

Heu, question idiote : Tu la vois dans un lspci au moins?

Poischack · Posted: Mon May 23, 2005 9:00 pm Post subject:

NiLuJe> Il faudrais que j'arrete de boire de la biere en plus de rendre obèse ça rends idiot: c'est pas dmesg que je vois la carte d'habitude mais dans lspci et oui elle apparait bien dedans.

Ni[o> oui j'avais deja cru comprendre qu'elle ne marchais pas "directement" et qu'il fallais passer par ndiswrapper

Sinon pour le IPW2200 c'est pas le bon c'est une IPN2200. Je vais ré-emerger wireless-tool et ndiswrapper ce soir, mais je sais ce qu'il m'attends: l'impossibilité de spécifier le essid ainsi que le channel ....

Poischack · Posted: Tue May 24, 2005 11:17 am Post subject:

Donc voila je viens de ré-emerge wireless-tool et ndiswrapper dans leurs dernieres versions stables.
je fais donc mon petit:

laptop Winxp # ndiswrapper -i neti2220.inf
Installing neti2220

laptop Winxp # modprobe ndiswrapper

laptop Winxp # dmesg
[...]
ndiswrapper version 1.1 loaded (preempt=yes,smp=no)
ndiswrapper: driver neti2220 (LanExpress,03/29/2004,2.10.03.2004) loaded
ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 11 (level, low) -> IRQ 11
ndiswrapper: using irq 11
wlan0: ndiswrapper ethernet device 00:0e:9b:55:44:18 using driver neti2220, configuration file 17FE:2220:1468:0305.5.conf
wlan0: encryption modes supported: WEP, WPA with TKIP, WPA with AES/CCMP

laptop Winxp # iwconfig wlan0
wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
Bit Rate:1 Mb/s
RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Power Management:off
Link Quality:100/100 Signal level:56/154 Noise level:0/154
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

laptop Winxp # iwconfig wlan0 essid FBpowa mode Managed key restricted 044AADE3FB

laptop Winxp # iwconfig wlan0 wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
Bit Rate:1 Mb/s
RTS thr:2347 B Fragment thr:2346 B
Encryption key:044A-ADE3-FB Security mode:restricted
Power Management:off
Link Quality:100/100 Signal level:56/154 Noise level:0/154
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

le essid refuse de changer.
Mon reseau wifi est sur le channel 11, je vais donc essayer de mettre la cartesur le bon channel:

laptop Winxp # iwconfig wlan0 channel 11
Error for wireless request "Set Frequency" (8B04) :
SET failed on device wlan0 ; Invalid argument.

laptop Winxp # dmesg
ndiswrapper (iw_set_freq:289): setting configuration failed (C0010015)

Vous n'auriez pas une idée d'où pourrez provenir le problème ?

NiLuJe · Posted: Tue May 24, 2005 1:51 pm Post subject:

vim /etc/conf.d/wireless && ln -sf /etc/init.d/net.l0 /etc/init.d/net.wlan0 && /etc/init.d/net.wlan0 start

;? Non? (Jms essayé de le faire à la mano perso, donc j'dis ça, j'dis rien hein ^^)

Poischack · Posted: Tue May 24, 2005 2:12 pm Post subject:

/etc/conf.d/wireless n'est apparu qu'avec les dernieres versions de baselayout je crois, j'ai préféré continuer sans mettre à jour pour le moment au cas où le problème vienne de là (mais il semble que non).
et puis ce que tu me dis de faire fais pareil que moi mais de maniere automatique (et vu que pour le moment ça marche pas) ....

NiLuJe · Posted: Tue May 24, 2005 2:42 pm Post subject:

Ouep, chui en ~x86 pour le baselayout, aucune idée si c'est passé en stable ...

Justement, le fait est que je suis directement passé par les outils
`automatisés` mis à ma disposition, et que ça marche, donc j'me suis pas cassé la tête à essayer de le faire à la main ... ^^ Ça te coûte rien d'essayer, y'a 3 lignes à renseigner et un symlink à faire

Ey · l33t Joined: 07 Apr 2005 Posts: 863 Location: Paris

Le fait qu'il ne t'indique le essid off/any ça peut signifier qu'il n'a pas réussi à se connecter au réseau. Essaie de vérifier si tu as bien mis la bonne clef par exemple.

Poischack · Posted: Tue May 24, 2005 3:11 pm Post subject:

NiLuJe> ouai bha j'essayerais plus tard dans la soirée (compil de gnome en cours)
Ey> Je suis certains de ma clé.

ablyes · Guru Joined: 06 Nov 2004 Posts: 429

essaie avec ça :

kernelsensei · Posted: Wed May 25, 2005 11:52 am Post subject:

Poischack · Posted: Wed May 25, 2005 3:59 pm Post subject:

Alors: j'ai emerger la deniere version ~x86 de baselayout -> aucun changement en mode manuelle(je vais essayer le mode automatique tout de suite), sinon:
laptop ~ # iwconfig wlan0
wlan0 IEEE 802.11g ESSID:off/any
Mode:Managed Frequency:2.437 GHz Access Point: 00:00:00:00:00:00
Bit Rate:1 Mb/s
RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Power Management:off
Link Quality:100/100 Signal level:56/154 Noise level:0/154
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
laptop ~ # iwconfig wlan0 mode ad-hoc
laptop ~ # iwconfig wlan0
wlan0 IEEE 802.11g ESSID:off/any
Mode:Ad-Hoc Frequency:2.437 GHz Cell: 00:00:00:00:00:00 [...]
laptop ~ # iwconfig wlan0 essid FBpowa
laptop ~ # iwconfig wlan0
wlan0 IEEE 802.11g ESSID:off/any [...]
laptop ~ # iwlist wlan0 scanning
wlan0 No scan results

Poischack · Posted: Wed May 25, 2005 4:21 pm Post subject:

laptop ~ # /etc/init.d/net.wlan0 start
* Starting wlan0
* Configuring wireless network for wlan0
* wlan0 does not support setting keys
* or the parameter "mac_key_FBpowa" or "key_FBpowa" is incorrect
* Failed to configure wireless for wlan0

dmesg -> [...]
ndiswrapper (iw_set_tx_power:354): setting tx_power failed (C0010017)
ndiswrapper (add_wep_key:644): adding encryption key 1 failed (C0010015)
ndiswrapper (iw_set_tx_power:354): setting tx_power failed (C0010017)
ndiswrapper (iw_set_tx_power:354): setting tx_power failed (C0010017)
ndiswrapper (add_wep_key:644): adding encryption key 1 failed (C0010015)
ndiswrapper (iw_set_tx_power:354): setting tx_power failed (C0010017)

mon fichier wireless:
##############################################################################
# HINTS
##############################################################################
# Remember to change eth0 to your wireless interface which may be
# eth0, eth1, wlan0, ath0 - you get the idea. If you're not sure
# you can type "iwconfig" at the command prompt and it will tell you which
# interfaces are wireless.
# Say that your wireless interface is ath0 - the line
essid_wlan0="FBpowa"
# becomes
# #essid_ath0="any"
#
# Remember to change ESSID to your ESSID.
# Say that your ESSID is My NET - the line
key_FBpowa="s:044AADE3FB"
# becomes
# #key_My_NET="s:passkey"
# Notice that the space has changed to an underscore - do the same with all
# characters not in a-z A-Z (english alphabet) 0-9.
#
# Any ESSID's in quotes like essid_eth0="My NET" may need to be escaped
# This means placing the character \ before the character
# \" need to be escaped for example
# So if your ESSID is
# My "\ NET
# it becomes
# My \"\\ NET
# for example
#essid_eth0="My\"\\NET"
#
# As a final note, most users will just need to set the following options
# key_ESSID1="s:yourkeyhere enc open" # s: means a text key
# key_ESSID2="aaaa-bbbb-cccc-dd" # no s: means a hex key
# preferred_aps=( "ESSID1" "ESSID2" )
#
# Clear? Good. Now configure your wireless network below
#########################################################

##############################################################################
# SETTINGS
##############################################################################
# Hard code an ESSID to an interface - leave this unset if you wish the driver
# to scan for available Access Points
# Set to "any" to connect to any ESSID - the driver picks an Access Point
# This needs to be done when the driver doesn't support scanning
# This may work for drivers that don't support scanning but you need automatic
# AP association
# I would only set this as a last resort really - use the preferred_aps
# setting at the bottom of this file

# However, using ad-hoc (without scanning for APs) and master mode
# do require the ESSID to be set - do this here
#essid_eth0="any"

# Set the mode of the interface (managed, ad-hoc, master or auto)
# The default is auto
# If it's ad-hoc or master you also may need to specify the channel below
mode_wlan0="managed"

# If managed mode fails, drop to ad-hoc mode with the below ESSID?
#adhoc_essid_eth0="WLAN"

#Channel can be set (1-14), but defaults to 3 if not set.
#
# The below is taken verbatim from the BSD wavelan documentation found at
# http://www.netbsd.org/Documentation/network/wavelan.html
# There are 14 channels possible; We are told that channels 1-11 are legal for
# North America, channels 1-13 for most of Europe, channels 10-13 for France,
# and only channel 14 for Japan. If in doubt, please refer to the documentation
# that came with your card or access point. Make sure that the channel you
# select is the same channel your access point (or the other card in an ad-hoc
# network) is on. The default for cards sold in North America and most of Europe# is 3; the default for cards sold in France is 11, and the default for cards
# sold in Japan is 14.
channel_wlan0="11"

# Setup any other config commands. This is basically the iwconfig argument
# without the iwconfig $iface
#iwconfig_eth0=""

# Set private driver ioctls. This is basically the iwpriv argument without
# the iwpriv $iface
#iwpriv_eth0=""

# Seconds to wait before scanning
# Some drivers need to wait until they have finished "loading"
# before they can scan - otherwise they error and claim that they cannot scan
# or resource is unavailable. The default is to wait zero seconds
sleep_scan_wlan0="1"

# Seconds to wait until associated. The default is to wait 10 seconds
#sleep_associate_eth0="5"

# By default a successful association in Managed mode sets the MAC
# address of the AP connected to. However, some drivers (namely
# the ipw2100) don't set an invalid MAC address when association
# fails - so we need to check on link quality which some drivers
# don't report properly either.
# So if you have connection problems try flipping this setting
# Valid options are MAC, quality and all - defaults to MAC
#associate_test_eth0="MAC"

# Some driver/card combinations need to scan in Ad-Hoc mode
# After scanning, the mode is reset to the one defined above
#scan_mode_eth0="Ad-Hoc"

# Below you can define private ioctls to run before and after scanning
# Format is the same as the iwpriv_eth0 above
# This is needed for the HostAP drivers
#iwpriv_scan_pre_eth0="host_roaming 2"
#iwpriv_scan_post_eth0="host_roaming 0"

# Define a WEP key per ESSID or MAC address (of the AP, not your card)
# The encryption type (open or restricted) must match the
# encryption type on the Access Point
# You can't use "any" for an ESSID here
#key_ESSID="1234-1234-1234-1234-1234-1234-56"
# or you can use strings. Passphrase IS NOT supported
# To use a string, prefix it with s:
# Note - this example also sets the encryption method to open
# which is regarded as more secure than restricted
#key_ESSID="s:foobar enc open"
#key_ESSID="s:foobar enc restricted"

# If you have whitespace in your key, here's how to set it and use other
# commands like using open encryption.
#key_ESSID="s:'foo bar' enc open"

# WEP key for the AP with MAC address 001122334455
#mac_key_001122334455="s:foobar"

# Here are some more examples of keys as some users find others work
# and some don't where they should all do the same thing
#key_ESSID="open s:foobar"
#key_ESSID="open 1234-5678-9012"
#key_ESSID="s:foobar enc open"
#key_ESSID="1234-5678-9012 enc open"

# You may want to set muliple keys - here's an example
# It sets 4 keys on the card and instructs to use key 2 by default
#key_ESSID="[1] s:passkey1 key [2] s:passkey2 key [3] s:passkey3 key [4] s:passkey4 key [2]"

# You can also override the interface settings found in /etc/conf.d/net
# per ESSID - which is very handy if you use different networks a lot
config_FBpowa=( "dhcp" )
dhcpcd_FBpowa="-t 5"
#routes_ESSID=()
#fallback_ESSID=()

# Setting name/domain server causes /etc/resolv.conf to be overwritten
# Note that if DHCP is used, and you want this to take precedence then
# please put -R in your dhcpcd options
#dns_servers_ESSID=( "192.168.0.1" "192.168.0.2" )
#dns_domain_ESSID="some.domain"
#dns_search_domains_ESSID="search.this.domain search.that.domain"
# Please check the man page for resolv.conf for more information
# as domain and search (searchdomains) are mutually exclusive and
# searchdomains takes precedence

# You can also set any of the /etc/conf.d/net variables per MAC address
# incase you use Access Points with the same ESSID but need different
# networking configs. Below is an example - of course you use the same
# method with other variables
#mac_config_001122334455=( "dhcp" )
#mac_dhcpcd_001122334455="-t 10"
#mac_dns_servers_001122334455=( "192.168.0.1" "192.168.0.2" )

# Map a MAC address to an ESSID
# This is used when the Access Point is not broadcasting it's ESSID
# WARNING: This will override the ESSID being broadcast due to some
# Access Points sending an ESSID even when they have been configured
# not too!
# Change 001122334455 to the MAC address and ESSID to the ESSID
# it should map to
#mac_essid_001122334455="ESSID"

# This lists the preferred ESSIDs to connect to in order
# ESSID's can contain any characters here as they must match the broadcast
# ESSID exactly.
# Surround each ESSID with the " character and seperate them with a space
# If the first ESSID isn't found then it moves onto the next
# If this isn't defined then it connects to the first one found
#preferred_aps=( "ESSID 1" "ESSID 2" )

# You can also define a preferred_aps list per interface
#preferred_aps_eth0=( "ESSID 3" "ESSID 4" )

# You can also say whether we only connect to preferred APs or not
# Values are "any", "preferredonly", "forcepreferred", "forcepreferredonly" and "forceany"
# "any" means it will connect to visible APs in the preferred list and then any
# other available AP
# "preferredonly" means it will only connect to visible APs in the preferred list
# "forcepreferred" means it will forceably connect to APs in order if it does not find
# them in a scan
# "forcepreferredonly" means it forceably connects to the APs in order and does not bother
# to scan
# "forceany" does the same as forcepreferred + connects to any other available AP
# Default is "any"
#associate_order="any"
#associate_order_eth0="any"

# You can define blacklisted Access Points in the same way
#blacklist_aps=( "ESSID 1" "ESSID 2" )
#blacklist_aps_eth0=( "ESSID 3" ESSID 4" )

# If you have more than one wireless card, you can say if you want
# to allow each card to associate with the same Access Point or not
# Values are "yes" and "no"
# Default is "yes"
#unique_ap="yes"
#unique_ap_eth0="yes"

# IMPORTANT: preferred_only, blacklisted_aps and unique_ap only work when
# essid_eth0 is not set and your card is capable of scanning

# NOTE: preferred_aps list ignores blacklisted_aps - so if you have
# the same ESSID in both, well, you're a bit silly :p

##############################################################################
# ADVANCED CONFIGURATION
#
# Two functions can be defined which will be called surrounding the
# associate function. The functions are called with the interface
# name first so that one function can control multiple adapters.
#
# The return values for the preassociate function should be 0
# (success) to indicate that configuration or deconfiguration of the
# interface can continue. If preassociate returns a non-zero value, then
# interface configuration will be aborted.
#
# The return value for the postassociate function is ignored
# since there's nothing to do if it indicates failure.

#preassociate() {
# # The below adds two configuration variables leap_user_ESSID
# # and leap_pass_ESSID. When they are both confiugred for the ESSID
# # being connected to then we run the CISCO LEAP script
#
# local user pass
# eval user=\"\$\{leap_user_${ESSIDVAR}\}\"
# eval pass=\"\$\{leap_pass_${ESSIDVAR}\}\"
#
# if [[ -n ${user} && -n ${pass} ]]; then
# if [[ ! -x /opt/cisco/bin/leapscript ]]; then
# eend "For LEAP support, please emerge net-misc/cisco-aironet-client-utils"
# return 1
# fi
# einfo "Waiting for LEAP Authentication on \"${ESSID//\\\\//}\""
# if /opt/cisco/bin/leapscript ${user} ${pass} | grep -q 'Login incorrect'; then
# ewarn "Login Failed for ${user}"
# return 1
# fi
# fi
#
# return 0
#}

#postassociate() {
# # This function is mostly here for completeness... I haven't
# # thought of anything nifty to do with it yet ;-)

# # Return 0 always
# return 0
#}

tomlohave · n00b Joined: 11 May 2005 Posts: 17

Bonjour,

Vérifie que l'acpi est activé dans ton noyau ...

j'ai eu exactement les mêmes problèmes et tout venait de l'acpi

cordialement

tomlohave · n00b Joined: 11 May 2005 Posts: 17

Adrien · Posted: Thu May 26, 2005 8:23 am Post subject:

Poischack · Posted: Thu May 26, 2005 10:39 am Post subject:

J'ai retiré la clé du fichier de conf, le lancement du service rate (il me dit que la config a raté).
Mais si je fais un iwconfig il me dit que le nickname est FBpowa hors ça devrais etre essid le FBpowa
j'e suis passé en mode adhoc pour scanner, aucun changement.

(merci lesgars de m'aider jecommence vraiment à croire que j'y arriverais jamais)

Adrien · Posted: Thu May 26, 2005 11:27 am Post subject:

tomlohave · n00b Joined: 11 May 2005 Posts: 17

tomlohave · n00b Joined: 11 May 2005 Posts: 17

Voila un petit script pour tester :

Poischack · Posted: Sat May 28, 2005 12:10 pm Post subject:

Finalement j'ai abandonné j'ai installé une ubuntu pour mon portable (mon fixe reste fidèle à gentoo), mais avec une présentation de dossier universitaire qui se rapproche, je n'ai plus le temps de passer du temps à configurer ma gentoo pour le portable.
Merci quand même à toutes vos réponses