Wlan unter OpenSuse! Est ging´s, dann nicht

ifcfg-eth-id-00:03:0d:18:0f:84
Code:
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IFPLUGD_PRIORITY='20'
IPADDR=''
MTU=''
NAME='Fujitsu Siemens SiS900 PCI Fast Ethernet'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='ifplugd'
UNIQUE='rBUF.3576OkQaYr3'
USERCONTROL='no'
_nm_name='bus-pci-0000:00:04.0'
 
Zuletzt bearbeitet:
*Ehm*

Die Ethernetkarte ist relativ uninteressant.

Also bitte die ifcfg-wlan*irgendwas* oder die ifcfg-ra*irgendwas* und zusätzlich die Ausgabe von iwconfig.

Dazu noch

Code:
grep -r rt2500 /etc/sysconfig/hardware

grep -r rt2500 /etc/modprobe*

Greetz,

RM
 
sorry, mein fehler

hier die ifcfg-wlan0

Code:
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME='Wireless LAN-Karten, die die direkte PCI-Schnittstelle verwenden'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='manual'
USERCONTROL='yes'
WIRELESS_AP=''
WIRELESS_AUTH_MODE='open'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY=''
WIRELESS_CLIENT_KEY_PASSWORD=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH=''
WIRELESS_EAP_MODE=''
WIRELESS_ESSID='mowgli'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='yes'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK='MeinNetzwerkschlüssel'
_nm_name='wlan1'

und die ifcfg-wlan-id-00:11:09:0b:0a:bf

Code:
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IFPLUGD_PRIORITY='10'
IPADDR=''
MTU=''
NAME='Micro-Star International RT2500 802.11g Cardbus/mini-PCI'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='manual'
UNIQUE='2nea.N0s2Kv5lXr4'
USERCONTROL='yes'
WIRELESS_AP=''
WIRELESS_AUTH_MODE='open'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY=''
WIRELESS_CLIENT_KEY_PASSWORD=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH=''
WIRELESS_EAP_MODE=''
WIRELESS_ESSID='mowgli'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='yes'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK='MeinNetzwerkschlüssel'
_nm_name='bus-pci-0000:00:0b.0'

so, weiter im text

Code:
Mowgli-Linux:/home/christopher # grep -r rt2500 /etc/sysconfig/hardware
/etc/sysconfig/hardware/hwcfg-wlan1:MODULE='rt2500'
/etc/sysconfig/hardware/hwcfg-bus-pci-0000:00:0b.0:MODULE='rt2500'

Mowgli-Linux:/home/christopher # grep -r rt2500 /etc/modprobe*
/etc/modprobe.conf:alias ra0 rt2500
/etc/modprobe.d/blacklist:blacklist rt2500pci
/etc/modprobe.d/blacklist~:blacklist rt2500pci
 
Etwas mehr Konzentration, wenn ich bitten darf.

Code:
WIRELESS_WPA_PSK='MeinNetzwerkschlüssel'

mir selbst schrieb:
- Modus verwaltet, ESSID eintragen, aber KEINEN Schlüssel eintragen und Authentifizierungsmethode offen, das müssen wir später über die Konfigurationsdatei einfügen.

Also Yast öffnen und die Netzwerkeinrichtung wie folgt ändern:

1. Es gibt 2 ifcfg-Files für 1 Karte, das ist unnötig.

- Die selbst eingerichtete Karte löschen, wir verwenden das schon vorhandene File ifcfg-wlan-id-00:11:09:0b:0a:bf.

- Den WPA-PSK herausnehmen, das kann nicht funktionieren, da diese Einstellung für den WPA_supplicant gedacht ist, welchen man aber für diese Karte nicht verwenden kann (zumindest mit diesem Treiber).

2. Anschliessend die Datei als root mit einem Texteditor (z.B. Kate) öffnen und bearbeiten.

Vorher:

Code:
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IFPLUGD_PRIORITY='10'
IPADDR=''
MTU=''
NAME='Micro-Star International RT2500 802.11g Cardbus/mini-PCI'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='manual'
UNIQUE='2nea.N0s2Kv5lXr4'
USERCONTROL='yes'
WIRELESS_AP=''
WIRELESS_AUTH_MODE='open'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY=''
WIRELESS_CLIENT_KEY_PASSWORD=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH=''
WIRELESS_EAP_MODE=''
WIRELESS_ESSID='mowgli'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='yes'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK=''
_nm_name='bus-pci-0000:00:0b.0'

Nachher:

Code:
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IFPLUGD_PRIORITY='10'
IPADDR=''
MTU=''
NAME='Micro-Star International RT2500 802.11g Cardbus/mini-PCI'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='manual'
UNIQUE='2nea.N0s2Kv5lXr4'
USERCONTROL='yes'
[COLOR="Red"][B]WIRELESS_IWPRIV_OPTIONS=''
PREFER_WPA_SUPPLICANT=''[/B][/COLOR]
WIRELESS_AP=''
WIRELESS_AUTH_MODE='open'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY=''
WIRELESS_CLIENT_KEY_PASSWORD=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH=''
WIRELESS_EAP_MODE=''
WIRELESS_ESSID='mowgli'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='yes'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK=''
_nm_name='bus-pci-0000:00:0b.0'

NUR diese beiden Zeilen einfügen, das Bearbeiten erledigen wir mit einem Yast-Tool.

Wenn man ein Problem lösen will, dann hat man einen Plan im Kopf, bisher läuft es im Großen und Ganzen "nach Plan", aber nun kommt der Teil, bei dem ich selbst nicht sicher weiß, wie die Einträge nachher genau aussehen müssen, mir machen besonders die "" in der funktionierenden iwpriv-Befehlsfolge Sorgen, deshalb solltest Du Deine Befehlsfolge von oben mal ohne die "" testen, also:

Code:
iwconfig wlan0 essid "mowgli" #hier ist es noch egal
iwpriv wlan0 set AuthMode=WPAPSK
iwpriv wlan0 set EncrypType=TKIP
iwpriv wlan0 set WPAPSK=DEINSCHLÜSSEL
dhclient wlan0

Wenn das klappt, dann sollte der Rest ohne Probleme möglich sein, ansonsten muss man eben probieren.

Ach ja und nimm noch aus Posting 56 Deinen WPA-Key raus. *g*

Greetz,

RM
 
Zuletzt bearbeitet von einem Moderator:
WPA-Schlüssel komplizierter machen

Nur ein Kommentar zur allgemeinen Sicherheit Deines WLAN-Netzwerkes.

Wenn es wirklich dein WPA-Schlüssel war, sollte dieser viel länger ausfallen und nicht so sprechend sein. Lexika Angriffe sind nicht so unüblich.

Sonderzeichen und Groß-Klein Schreibung, Zahlen etc einbauen, umso schwerer wird es, den Schlüssel zu knacken. Das ist bei WPA nämlich immer noch möglich. Ich kann ja immer eine neue Maschine ins Netzwerk aufnehmen, wenn ich den Schlüssel kenne. Ist er leicht zu raten, ist man schnell drin, je komplizierter der Schlüssel ist, desto länger dauert es.

Gruß
Yogibaer
 
Nur ein Kommentar zur allgemeinen Sicherheit Deines WLAN-Netzwerkes.

Wenn es wirklich dein WPA-Schlüssel war, sollte dieser viel länger ausfallen und nicht so sprechend sein. Lexika Angriffe sind nicht so unüblich.

Full ACK.

Darum werden wir uns auch noch kümmern, wenn das alles so klappt wie gewünscht.

Zur Zeit ist dieser einfache Schlüssel sogar fast besser, denn es geht ja nur um die prinzipielle Funktionsweise, wenn es mit einem einfachen Schlüssel geht, dann geht es auch mit einem sicheren Schlüssel.

Kleiner Tipp, wo man passende, zufällige Schlüssel bekommen kann:

https://www.grc.com/passwords.htm

Die Dinger werden nirgends gespeichert und sind sehr sicher, sie bleiben nicht mal im Browsercache.

Und wer der Sache trotzdem nicht traut, der kann ja den generierten Schlüssel noch abändern.

Ich empfehle die Verwendung der obersten oder untersten Spalte, die mittlere kann unter Umständen wegen Sonderzeichen Probleme machen.

Greetz,

RM
 
Also das hat ohne probleme geklappt :-)

Code:
Mowgli-Linux:/home/christopher # iwconfig wlan0 essid "mowgli"
Mowgli-Linux:/home/christopher # iwpriv wlan0 set AuthMode=WPAPSK
Mowgli-Linux:/home/christopher # iwpriv wlan0 set EncrypType=TKIP
Mowgli-Linux:/home/christopher # iwpriv wlan0 set WPAPSK=***
Mowgli-Linux:/home/christopher # dhclient wlan0
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/

Listening on LPF/wlan0/00:11:09:0b:0a:bf
Sending on   LPF/wlan0/00:11:09:0b:0a:bf
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPOFFER from 192.168.1.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.3 -- renewal in 1538 seconds.
Mowgli-Linux:/home/christopher # ping -c1 google.de
PING google.de (66.249.93.104) 56(84) bytes of data.
64 bytes from google.de (66.249.93.104): icmp_seq=1 ttl=245 time=47.1 ms

--- google.de ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 47.175/47.175/47.175/0.000 ms

noch ne frage wegen des Schlüssels! ich meine der kann doch nur geknackt werden, wenn man direkten zugang zu meinem drahtlosnetzwerk hat! Also entweder einer meiner nachbarn oder jemand mit einem laptop unten auf der strasse! da über mein netzwerk auch mal rechner von besuchern reingehen habe ich den schlüssel ienfach gehalten, das erspart lästiges ablesen bzw. diktieren

ach ja, und wegen des schlüssels in der ifcfg-wlan-id-00:11:09:0b:0a:bf

ich habe bei yast den schlüssel rausgenommen und trotzdem bleib der ausdruck in der datei erhalten! ich habe ihn jetzt manuell rausgelöscht
 
Jetzt stell dir aber mal vor, dass Dir einer etwas Böses will. Dann setzt der sich draußen hin mit seinem Laptop, weiß natürlich, dass Dein WLAN im Unixboard ans laufen gebracht worden ist, und bucht über deine Verbindung irgendetwas, was Du bezahlen musst. Als kleine Sache. Da könnte noch viel mehr gehen. Man schaut auch nicht in die Köpfe der Nachbarn. Ich hatte mal einen, der hat dann seine Frau umgebracht im Affekt. Eigentlich ein sehr netter Mann. Das sind nur Beispiele, aber wenn du Dein Netz dicht haben willst, dann nimm einen sicheren Schlüssel. Übrigens, eine sehr einfache Methode, den Schlüssel zu speichern ist: kopier eine Textdatei, die deinen Schlüssel im Klartext enthält, auf eine CD. Die legst Du dann jeweils ein, wenn Du Besuch hast, dem Du Netzzugang verschaffen willst (ginge vielleicht auch per Kabel, ich weiß es nicht), machst einen Editor auf und kopierst den Schlüssel per copy und paste in die entspechenden Eingabefenster. Dass tut es auch hervorragend unter Windows. Dann kann der Schlüssel so komplex sein wie er möchte. Du gibst ihn immer gleich ein.
Wenn Dein Netz unsicher sein soll, mach es mit deinem alten Schlüssel.
Gruß
Yogibaer
Für Rückfragen, Du weißt wo ich zu finden bin, nämlich ab und an hier.
 
Ok, dann der nächste Schritt:

Ich gehe davon aus, daß die beiden Zeilen auch schon in die ifcfg-Datei eingefügt wurden.

In der Datei /etc/sysconfig/network/ifcfg.template steht unter anderem Folgendes:

Code:
## Type:        string
## Default:     ''
#
[B]# If you need to set options for iwpriv then write the complete option string as
# you would append it to iwpriv but without the interface name to the variables
# below. For multiple options you may (but need not) add linebreaks in the
# string.[/B]
[COLOR="Red"]WIRELESS_IWPRIV_OPTIONS=''[/COLOR]

## Type:        yesno
## Default:     yes
#
# If you configured only one wireless network and are not using WPA, the
# device can be set up without using wpa_supplicant, although it would be
# possible to use it. This variable defines whether wpa_supplicant should be
# used in that case.
[COLOR="red"]PREFER_WPA_SUPPLICANT=''[/COLOR]

Du hast eine Karte, die mit "iwpriv" eingerichtet wird und deshalb _nicht_ den wpa_supplicant verwendet.

Sollten die Einträge vorhanden sein, dann kann man über

Yast => System => Editor für /etc/sysconfig-Dateien => Hardware => Network => Karte aussuchen (ID steht ja da)

editieren.

In das Feld für WIRELESS_IWPRIV_OPTIONS kommt folgendes rein.

Code:
set AuthMode=WPAPSK set EncrypType=TKIP set WPAPSK=[B]DEINSCHLÜSSEL[/B]
Genau so wie es da steht, keine "" und keine Trennzeichen, nur Leerzeichen zwischen den einzelnen Optionen (so verstehe ich zumindest die Angabe aus obiger ifcfg.template).

Bei der Option PREFER_WPA_SUPPLICANT (na was wohl?)

Code:
no

Danach abspeichern lassen und testen:

Code:
su

Passwort

ifdown wlan0

ifup wlan0
Meldungen posten und wenn alles gut geht, dann ist nach dem ifup-Befehl eine Verbindung da (Wieder pingen wie oben auch).

Poste auch die ifcfg-Datei im veränderten Zustand.

Greetz,

RM
 
Code:
Mowgli-Linux:/home/christopher # ifdown wlan0
    wlan0     device: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
    wlan0     configuration: wlan-id-00:11:09:0b:0a:bf
Mowgli-Linux:/home/christopher # ifup wlan0
    wlan0     device: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
    wlan0     configuration: wlan-id-00:11:09:0b:0a:bf
    wlan0     warning: using NO encryption
Starting DHCP Client Daemon on wlan0... . . . . . no IP address yet... backgrounding.

Mowgli-Linux:/home/christopher # ping -c1 google.de
ping: unknown host google.de

das hat schonmal nicht geklappt

Code:
## This is a template for a network interface configuration file used with ifup.
## See 'man 8 ifup' for details.
## Additionally to the following variables you can set every variable from the
## interface independent configurations files (config, dhcp, wireless) also in
## the interface configuration file to overwrite the global settings.

## Type: list(auto,hotplug,ifplugd,nfsroot,manual,off,onboot)
## Default: auto
#
# STARTMODE tells ifup when a interface should be set up. Possible values are:
# - auto:    start it as soon as the interface is available. Either when booting
#            or when a device is plugged or initialized at runtime
# - hotplug: alias for auto, only difference is that configurations with that
#            startmode are not considered to be mandatory if list of mandatory
#            devices is derived automatically.
# - ifplugd: interface will be controlled by ifplugd daemon. (If you like to use
#            multiple interfaces mutually exclusive you have to set also
#            IFPLUGD_PRIORITY.)
# - nfsroot: Nearly like 'auto'. But interfaces with this startmode will never
#            be shut down via 'rcnetwork stop'. 'ifdown <iface>' still works.
#            Use this when you have a nfs root filesystem.
# - manual:  start it only when ifup is called manually
# - off:     will not be started at all
# - onboot:  alias for auto, deprecated, only for backward compliance
STARTMODE=

## Type:    integer(0:100)
## Default: 0
#
# All interfaces with STARTMODE=ifplugd and with IFPLUGD_PRIORITY != 0 will be
# used mutually exclusive. If more then one of these interfaces is 'plugged'
# then we need a way to decide which interface to take up. Therefore we have to
# set the priority of each interface.
# Note: Connection detection of wireless devices is not very reliable.
# Therefore we currently simple consider a wlan interface as always connected.
# With a lower priority as all other interfaces it will then be set up if no
# other connection is established.
# A value of 0 means no priority set.
#
IFPLUGD_PRIORITY=

## Type:    list(static,dhcp,autoip,dhcp+autoip,6to4)
## Default: static
#
# With BOOTPROTO you can choose in which mode the interface will be set up:
# - static:      Set up static address(es)
# - dhcp:        Start a dhcp client on that interface.
# - autoip:      Automatic search for a free address and assign it statically.
# - dhcp+autoip: Try dhcp and use autoip if dhcp fails.
# - 6to4:        Set up ipv6 over ipv4 tunnel (see man ifcfg-tunnel)
# If you use dhcp or autoip you may additionally specify static address(es).
#
BOOTPROTO=

## Type:    string
## Default: ""
#
# If using a static configuration you have to set an IP address and a netmask
# or prefix length. The following examples are equivalent:
# 1) IPADDR=192.168.1.1
#    NETMASK=255.255.255.0
# 2) IPADDR=192.168.1.1
#    PREFIXLEN=24              # NETMASK will be ignored
# 3) IPADDR=192.168.1.1/24     # NETMASK and PREFIXLEN will be ignored
#
# For multiple addresses use this variable multiple times and extend them with
# different suffixes. For example IPADDR_1=, IPADDR_2=. See section 'Multiple
# addresses' in manpage ifcfg).
#
IPADDR=


## Type:    string
## Default: ""
#
# Set the network mask for the ip address. This variable will be ignored if a
# prefixlength is set in variable PREFIXLEN in IPADDR.
# For multiple addresses use the same suffixes as with IPADDR.
#
NETMASK=

## Type:    integer(0,64)
## Default: ""
#
# Set the prefixlength of the ip address. This variable will be ignored if a
# prefixlength is set in variable IPADDR.
# For multiple addresses use the same suffixes as with IPADDR.
#
PREFIXLEN=

## Type:    string
## Default: ""
#
# Set the broadcast address of the interface. If you leave it empty a default
# will be used. See DEFAULT_BROADCAST in /etc/sysconfig/network/config.
# For multiple addresses use the same suffixes as with IPADDR.
#
BROADCAST=

## Type:    string
## Default: ""
#
# If you'd like to set up a point to point connection you may specify the
# remote IP here.
# For multiple addresses use the same suffixes as with IPADDR.
#
REMOTE_IPADDR=

## Type:    string
## Default: ""
#
# Set a label for the interface. This may be neccessary if you still use
# ifconfig and configured multiple addresses. (See manpage ifcfg).
# For multiple addresses use the same suffixes as with IPADDR.
#
LABEL=

## Type:    string
## Default: ""
#
# Set the  scope  of the area where this address is valid. 
# See manpage ip for details.
# For multiple addresses use the same suffixes as with IPADDR.
#
SCOPE=

## Type:    string
## Default: ""
#
# Every other option from "ip address add" can be added here.
# See manpage ip for details.
# For multiple addresses use the same suffixes as with IPADDR.
#
IP_OPTIONS=

## Type:    string
## Default: ""
#
# Set the interface type if ifup cannot determine it properly. This may be
# needed if you use unusual interface names for special interfaces like
# modems.
#
INTERFACETYPE=

## Type:    integer
## Default: ""
#
# Set a specific Maximum Transmission Unit (MTU) for this interface.
#
MTU=

## Type:    string
## Default: ""
#
# Set a specific link level address (LLADDR), a.k.a. MAC address or hardware
# address, for this interface (if the driver supports it).
#
LLADDR=

## Type:    string
## Default: ""
#
# Every other option from "ip link set" can be added here.
# Example:
#       LINK_OPTIONS="multicast off"
# See manpage ip for details.
#
LINK_OPTIONS=

## Type:    string
## Default: ""
#
# If this variable is not empty ifup will call ethtool with this
# options. See manpage ethtool for available options.
# If option string starts with a '-' (e.g. '-K iface rx on') then the
# second word in the string will be replaced with the current interface
# name. Else (e.g. 'autoneg off speed 10') ifup prepends '-s <interface>'.
#
ETHTOOL_OPTIONS=

## Type:    yesno
## Default: yes
#
# This options defines whether the script /etc/ppp/poll.tcpip is run after
# connecting to the internet via a dialup connection or not. The script
# itself calls various jobs like fetchmail, fetchnews and sendmail.
#
RUN_POLL_TCPIP=

## Type:    yesno
## Default: no
#
# If an interface may be controlled from a user via kinternet or cinternet you
# have to set this variable to yes.
#
USERCONTROL=

## Type:    string
## Default: ""
#
# This string is used as description of the device in YaST.
# This variable is not used in ifup and friends.
#
NAME=

## Type:    string
## Default: ""
#
# Internal variable for YaST. Don't change it.
# This variable is not used in ifup and friends.
#
UNIQUE=

## Type:    string
## Default: ""
#
# Internal variable for YaST. Don't change it.
# This variable is not used in ifup and friends.
#
_nm_name=

## Type:    yesno
## Default: no
#
# If the network is managed with NetworkManager but you want to control an
# interface manually with ifup/down you can set this variable to 'yes'.
#
NM_CONTROLLED=no


##########################################################################
### FIXME:
### From here one up to 'bridge settings' the file is not up to date


## Multiple addresses
##    You can extend the variable name 'IPADDR' by any string you like (IPADDR_1,
##    IPADDR_FOO, IPADDRxxx, ...) and use these variables for your IP addresses.
##    If you need some additional parameters for these addresses, then just add
##    the same extension to these variable names.
##    IPADDR_AAA=1.2.3.4
##    NETMASK_AAA=255.0.0.0
##    BROADCAST_AAA=1.2.3.55
##    IPADDR_BBB=10.10.2.3/16
##    LABEL_BBB=BBB
##    an so on ...
##
## You do not need to set a label for any address. But then you should not use
## ifconfig any longer; go and use ip. If you want to use ifconfig then omit the
## label for your main address and set a label for every additional address.

## Routing:
## If you need special routes for a configuration, then use a file named
## ifroute-<config> where <config> is the same string as in ifcfg-<config>.
## It has the same syntax like routes except one difference:
## If you omit the interface name (4th field) in the ifroute file it will be
## set to the current interface name when setting up the interface. You need to
## do this with hotpluggable devices, where you do not know which interface name
## they will get at the time when you plug them.
## See man 5 routes.


##########################################################################
## DHCP settings

## Type: list("",yes,no)
## Default: ""
#
# Multiple DHCP clients:
#
# With two or more DHCP clients running, they would concurrently try to replace
# the default route or rewrite resolv.conf, rewrite ntp.conf etc. There are two
# ways of dealing with this conflict (and it is a conflict, because you can
# have only one default route even though routes are stackable, and there can
# only be one resolv.conf file):
#
#  1) allow both clients to do that stuff. This would work in many cases if
#     only one of the interfaces is used at a time. However, it would lead to
#     undefined behaviour.
#
#  2) allow only one of the DHCP clients to do that stuff. This implies
#     that there would be a "primary" interface and a "secondary". This is the
#     assumption the default configuration is based on. But since the system
#     can't guess which interface is "more important" and should have the
#     default route and resolver configuration associated with it, it simply
#     chooses the first interface that is started with DHCP to be
#     "authoritative".  Which one that is can be influenced by adding
#     DHCLIENT_PRIMARY_DEVICE=yes to one of the /etc/sysconfig/network/ifcfg-*
#     files. This can even be added to more than one file, to achieve the
#     behaviour described in 1).  Thus, there is the flexibility to do it
#     either way.
#
# Per default, only the DHCP client that is started first will be allowed to
# change the default route / resolver configuration etc.  All other running
# clients will only configure the interface with an address, but not change
# "global" configuration.
#
# Thus, to specifically allow an interface's DHCP client to change "global"
# configuration, set the following variable to "yes". Or you can make an
# interface's DHCP client never change these settings if you set it to "no".
# If you leave it empty then ifup-dhcp will decide.
#
DHCLIENT_PRIMARY_DEVICE=


## Type:
## Default:
#
# Even more finegrained control can be excerted by setting any of the variables
# from /etc/sysconfig/network/dhcp here:
DHCLIENT_DEBUG=
DHCLIENT_SET_HOSTNAME=
DHCLIENT_SET_DOMAINNAME=
DHCLIENT_KEEP_SEARCHLIST=
DHCLIENT_MODIFY_RESOLV_CONF=
DHCLIENT_SET_DEFAULT_ROUTE=
DHCLIENT_MODIFY_NTP_CONF=
DHCLIENT_MODIFY_NIS_CONF=
DHCLIENT_TIMEOUT=
DHCLIENT_REBOOT_TIMEOUT=
DHCLIENT_CLIENT_ID=
DHCLIENT_HOSTNAME_OPTION=
DHCLIENT_VENDOR_CLASS_ID=
DHCLIENT_LEASE_TIME=
DHCLIENT_ADDITIONAL_OPTIONS=


##########################################################################
## bridge settings. See ifcfg-bridge(5) and brctl(8) for mor information
## 

## Type:    yesno
## Default: yes
#
# This option must be set to 'yes' to identify this interface as a bridge
# interface.
#
BRIDGE='yes'

## Type:    string
## Default: 
#
# This variable contains a space-separated list of N interfaces which take part 
# in the bridging. You may use also hardware descriptions if your interface
# names are not persistent.
#
BRIDGE_PORTS=''

## Type:    integer(0:)
## Default: 
#
# This option sets the ethernet address ageing time, in seconds. After <time> 
# seconds of not having seen a frame coming from a certain address, the bridge 
# will delete that address from the forwarding database. Setting ageing time 
# to zero makes all entries permanent.
#
BRIDGE_AGEINGTIME=''

## Type:    integer(0:)
## Default:
#
# Forwarding delay time is the time in seconds spent in each of the listening
# and learning states before the forwarding state is entered. This delay is  
# so that when a new bridge comes onto a busy network it looks at some traffic 
# before participating.
#
BRIDGE_FORWARDDELAY=''

## Type:    integer(0:)
## Default:
#
# Periodically, a hello packet is sent out by the root bridge and the designated 
# bridges. Hello packets are used to communicate information about the topology 
# throughout the entire bridged local area network.
#
BRIDGE_HELLOTIME=''

## Type:    integer(0:)
## Default:
#
# If a another bridge in the spanning tree does not send out a hello packet for
# a long period of time, it is assumed to be dead. This timeout can be set with 
# this variable.
#
BRIDGE_MAXAGE=''

## Type:    string
## Default:
#
# This is a space-separated list of costs corresponding to the interfaces in 
# BRIDGE_PORTS. Each interface in BRIDGE_PORTS could have a different speed 
# and this value is used when deciding which link to use. Faster interfaces
# should have lower costs. 
#
BRIDGE_PATHCOSTS=''

## Type:    string
## Default:
#
# This is a space-separated list of priorities corresponding to the interfaces 
# in BRIDGE_PORTS. The priority value is an unsigned 8-bit quantity (a number 
# between 0 and 255), and has no dimension. This metric is used in the
# designated port and root port selection algorithms.
#
BRIDGE_PORTPRIORITIES=''

## Type:    integer(0:65535)
## Default: 
#
# This option sets the bridge's priority. The priority value is an unsigned 
# 16-bit quantity (a number between 0 and 65535), and has no dimension. Lower 
# priority values are 'better'. The bridge with the lowest priority will be
# elected 'root bridge'.
#
BRIDGE_PRIORITY=''

## Type:    list(on,off)
## Default: off
#
# Multiple ethernet bridges can work together to create even larger networks 
# of ethernets using the IEEE 802.1d spanning tree protocol. This protocol  
# is used for finding the shortest path between  two  ethernets, and for 
# eliminating loops from the topology.
# 
# The spanning tree protocol can also be turned off (for those situations
# where it just doesn't make sense, for example when this linux box is
# the only bridge on the LAN, or when you know that there are no loops in
# the topology.)
#
BRIDGE_STP=''

## Type:	yesno
## Default:	""
#
# Defines whether this interface is wireless or not.  This variable is usually
# not set, WLAN capabilities get auto-detected in this case.  As the WIRELESS
# variable is device speficic and not network specific, it can have no suffix.
WIRELESS=''


## Type:	string
## Default:	"managed"
#
# Set the operating mode of the device, which depends on the network topology.
# Set to ad-hoc for network composed of only one cell and without Access
# Point, managed for network composed of many cells, with roaming or with an
# Access Point, master if you want your system act as an Access Point or
# synchronisation master. If unset, managed will be used.
WIRELESS_MODE=''

## Type:	string
## Default:	""
#
# Set the SSID/ESSID (or Network Name - in some products it may also called
# Domain ID). The ESSID is used to identify cells which are part of the same
# virtual network. If emtpy or set to any the node will connect to the
# Access Point with the best signal strength around (in managed operating
# mode). For WLANs that make use of WPA (see WIRELESS_AUTH_MODE below)
# you need to set your ESSID.
WIRELESS_ESSID=''

## Type:	list(open,sharedkey,psk,eap)
## Default:	open
#
# Sets authentication mode. The mode depends on the protection technology
# beeing used, WEP or WPA. WEP (Wired Equivalent Privacy) is a system to
# encrypt wireless network traffic, with an optional authentication on the
# basis of the used encryption key. In most cases where WEP is used, open
# mode (no authentication at all) is fine. This does not mean that you can
# not use WEP encryption. Some networks may require sharedkey authentication.
# NOTE: Shared key authentication makes it easier for a potential attacker to
# break into your network. Unless you have specific needs for shared key
# authentication, use the open mode. As WEP has been proved insecure, WPA
# (Wi-Fi Protected Access) was defined to close its security wholes, but not
# every hardware supports WPA. In case you want to use WPA-PSK (WPA preshared
# key authentication, aka WPA "Home"), set this to psk. In case you want
# to use WPA-EAP (WPA with Extensible Authentication Protocol, aka WPA
# "Enterprise"), set this to eap. WPA authentication modes are only
# possible when WIRELESS_MODE is set to managed.
WIRELESS_AUTH_MODE=''

## Type:	string
## Default:	""
#
# When using WPA-PSK authentication, you need to specify your preshared key
# here. The key is used for authentication and encryption purposes. You can
# enter it in hex digits (needs to be exactly 64 digits long) or as passphrase
# getting hashed (8 to 63 ASCII characters long).
WIRELESS_WPA_PSK=''

## Type:	string
## Default:	""
#
# WPA-EAP can use different authentication modes. Supported
# values are TLS, PEAP, and TTLS. Default is to allow any.
# When using WIRELESS_AP_SCANMODE 2, this variable needs to be set.
WIRELESS_EAP_AUTH=''

## Type:	string
## Default:	""
#
# Using this variable you can specify the WPA protocol to be used.
# Valid values are WPA and RSN (aka WPA2, can be also used as synonym).
# Default is to allow both. When using WIRELESS_AP_SCANMODE 2, this
# variable needs to be set, otherwise WPA will be used as fallback.
WIRELESS_WPA_PROTO=''

## Type:	string
## Default:	""
#
# Needs to be set in conjunction with WPA-EAP. Set to your identity as
# configured on the RADIUS server.
WIRELESS_WPA_IDENTITY=''

## Type:	string
## Default:	""
#
# Needs to be set in conjunction with WPA-EAP. Set to your password as
# configured on the RADIUS server.
WIRELESS_WPA_PASSWORD=''

## Type:	string
## Default:	"anonymous"
#
# Sets anonymous identity. Default is "anonymous". The anonymous identity is
# used with WPA-EAP protocols that support different tunnelled identities
# (e.g., TTLS).
WIRELESS_WPA_ANONID=''

## Type:	string
## Default:	""

# Used with WPA-EAP. If you want to check the RADIUS server's authenticity,
# which is highly recommended, you need specify the certificate of the
# CA (Certification Authority) which signed the server's certificate.
# Point this variable to the certificate file including full path.
WIRELESS_CA_CERT=''

## Type:	string
## Default:	""
#
# Used with WPA-EAP. If you are using TLS as authentication protocol you need
# to authenticate yourself through a client certificate. Point this variable
# to the certificate file including full path.
WIRELESS_CLIENT_CERT=''

## Type:	string
## Default:	""
#
# Used with WPA-EAP. Authentication mode TLS uses a public/private key method
# to encrypt negotiation data. Point this variable to the file containing your
# client private key including full path.
WIRELESS_CLIENT_KEY=''

## Type:	string
## Default:	""
#
# Used with WPA-EAP. Set to the passphrase of your client private key file.
WIRELESS_CLIENT_KEY_PASSWORD=''

## Type:	yesno
## Default:	yes
#
# Defines whether hidden SSID scan support should be enabled.  Setting this to
# "no" can speed up scanning and makes the usage of WIRELESS_PRIORITY
# possible. This is only used in conjunction with wpa_supplicant.
WIRELESS_HIDDEN_SSID=''

## Type:	integer
## Default:	""
#
# This variable only makes sense used in conjunction with multiple
# networks. If you want to prefer one configured network for over another, set
# the respecitve WIRELESS_PRIORITY variable (means, with the same suffix) to a
# higher value (integer only). NOTE: This does not work for networks that are
# configured with WIRELESS_HIDDEN_SSID="yes" (which is default). For networks
# with hidden SSID scanning support the suffix number is important.  The
# network with the lowest suffix number gets probed first.
WIRELESS_PRIORITY=''

## Type:	list(0,1,2)
## Default:	1
#
# Defines which SSID scan mode should be used. Mode 0 means the driver
# performs the scan. Mode 1 means wpa_supplicant takes care of scanning.  Mode
# 2 is basically the same as mode 0 but the access point gets chosen by
# security policy and SSID. This mode does not support multiple network
# settings. Default is "1" for most drivers. Try "0" or "2" if you have
# problems associating to your access point. This variable can have no
# suffix. This is only used in conjuntion with wpa_supplicant.
WIRELESS_AP_SCANMODE=''

## Type:	string
## Default:	""
#
# If have configured a WPA mode in WIRELESS_AUTH_MODE you can use this
# variable to supply a custom wpa_supplicant.conf that will be used instead of
# the one ifup would generate. The file has to be specified with full path. Of
# course you can setup any configuration suitable for wpa_supplicant with
# this, not only WPA modes. This variable can have no suffix. If you want to
# have multiple network support, you need to create a wpa_supplicant.conf with
# mulitle network sections (see wpa_supplicant documentation).
WIRELESS_WPA_CONF=''

## Type:	yesno
## Default:	yes
#
# If you configured only one wireless network and are not using WPA, the
# device can be set up without using wpa_supplicant, although it would be
# possible to use it. This variable defines whether wpa_supplicant should be
# used in that case.
PREFER_WPA_SUPPLICANT=''

## Type:	string
## Default:	""
#
# In environments with multiple Access points you may want to define the one
# to connect to by entering its MAC address. Format is 6x2 hex digits,
# seperated by colons, eg 01:02:03:04:05:06.
WIRELESS_AP=''

## Type:	yesno
## Default:	no
#
# If set to yes, ifup tries to enable power saving for this device. This is
# not supported by all cards resp. drivers.
WIRELESS_POWER=''

## Type:	string
## Default:	""
# Set the nickname, or the station name. Most 802.11 products do define it,
# but this is not used as far as the protocols (MAC, IP, TCP) are concerned
# and completely accessory as far as configuration goes. If this variable is
# empty the hostname will be used as nick.
WIRELESS_NICK=''

## Type:	string
## Default:	""
#
# Set the Network ID (in some products it is also called Domain ID). As all
# adjacent wireless networks share the same medium, this parameter is used to
# differenciate them (create logical colocated networks) and identify nodes
# belonging to the same cell.
WIRELESS_NWID=''

## Type:	string
## Default:	""
#
# With this variable you can define the channel being used. This is only
# applicable to ad-hoc and master operating modes. Channels are usually
# numbered starting at 1, and you may use iwpriv(8) to get the total number of
# channels and list the available frequencies. Depending on regulations, some
# frequencies/channels may not be available.
WIRELESS_CHANNEL=''

## Type:	integer
## Default:	""
#
# Set the sensitivity threshold. This is the lowest signal level for which we
# attempt a packet reception, signal lower than this are not received. This
# is used to avoid receiving background noise.
WIRELESS_SENS=''

## Type:	string
## Default:	"auto"
#
# Usually the highest bitrate available gets used. If you have specific needs
# to set a bitrate, you can do it here (rates are in Mbit/s). Bitrates above
# 11 are only available for cards compliant to 802.11a or 802.11g standards.
WIRELESS_RATE=''

## Type:	string
## Default:	""
#
# You can define up to 4 WEP encryption keys. You can use WEP with open and
# sharedkey authentication. The key can be entered in different formats:
# Either directly in hex digits, with or without dashes, or in the key's ASCII
# representation (prefix s: ), or as a passphrase which will be hashed (prefix
# h: ). The amount of hex digits resp. length of the ASCII key depends on the
# key size being used: 10 hex digits or 5 ASCII characters for 64 bit keys, 26
# hex digits or 6 to 13 ASCII characters for 128 bit keys (see
# WIRELESS_KEY_LENGTH below). Examples:
#
# WIRELESS_KEY_0="0123-4567-89"
# WIRELESS_KEY_0-"s:hello"
# WIRELESS_KEY_0="h:mysecretphrase"
#
# You  can also use 1, 2, or 3 as suffix for multiple key settings. This
# is usually not necessary. Leave empty if you do not want WEP.
WIRELESS_KEY=''

## Type:	list(40,104)
## Default:	104
#
# Defines the length in bits for all keys used. There are currently 40 and 104
# bit keys supported. Sometimes they are also called 64 resp. 128 bits
# (depends on whether you count the 24 bit initialization vetor or not).
# This variable is only meaningful if you enter the key as passphrase.
WIRELESS_KEY_LENGTH=''

## Type:	list(0,1,2,3)
## Default:	0

# Sets the default WEP key. The default key is used to encrypt outgoing
# packets, incoming ones are decrypted with the key number specified in the
# packet. This defaults to 0.
WIRELESS_DEFAULT_KEY=''



## Type:	string
## Default:	"off"
#
# RTS/CTS adds a handshake before each packet transmission to make sure that
# the channel is clear. This adds overhead, but increase performance in case
# of hidden nodes or large number of active nodes. Possible values: any
# integer (representing the size of the smallest packet for which the node
# sends RTS), auto, fixed, or off.
WIRELESS_RTS=''

## Type:	string
## Default:	"off"
#
# Fragmentation allow to split a IP packet in a burst of smaller fragments
# transmitted on the medium. In most cases this adds overhead, but in very
# noisy environment this reduce the error penalty. Possible values: any
# integer (representing the maximum fragment size), auto, fixed, or off.
WIRELESS_FRAG=''

## Type:	string
## Default:	""
#
# If you need other options for iwconfig, then write the complete option string
# as you would append it to iwconfig but without the interface name to the
# variables below. For multiple options you may (but need not) add linebreaks in
# the string.
WIRELESS_IWCONFIG_OPTIONS=''

## Type:	string
## Default:	""
#
# If you need to set options for iwspy, then write the complete option string as
# you would append it to iwspy but without the interface name to the variables
# below. For multiple options you may (but need not) add linebreaks in the
# string.
WIRELESS_IWSPY_OPTIONS=''

## Type:	string
## Default:	''
#
# If you need to set options for iwpriv then write the complete option string as
# you would append it to iwpriv but without the interface name to the variables
# below. For multiple options you may (but need not) add linebreaks in the
# string.
WIRELESS_IWPRIV_OPTIONS=''

## Type:	string
## Default:	''
#

# For WPA modes you can set the WPA protocol to be used, WPA or RSN
# (aka WPA2).  Default is to allow both protocols. When using
# WIRELESS_AP_SCANMODE 2, this variable needs to be set, or WPA will
# be used as fallback. Note: WPA2 can be used as an alias for RSN.
WIRELESS_WPA_PROTO=''

## Type:	string
## Default:	''
#
# WPA modes support two different encryption systems, TKIP and
# CCMP. This variable defines which to use for unicast communication.
# Default is to allow both. In case you want to restrict it to one
# protocol, set this variable. When using WIRELESS_AP_SCANMODE 2, this
# variable needs to be set, otherwise TKIP will be used as fallback.
WIRELESS_CIPHER_PAIRWISE=''

## Type:	string
## Default:	''
#
# WPA modes support two different encryption systems, TKIP and
# CCMP. This variable defines which to use for broad-/multicast
# communication.  Default is to allow both. In case you want to
# restrict it to one protocol, set this variable. When using
# WIRELESS_AP_SCANMODE 2, this variable needs to be set, otherwise
# TKIP will be used as fallback.
WIRELESS_CIPHER_GROUP=''

## Type:	string
## Default:	''
#
# When using WPA-EAP with PEAP authentication, you can use
# this variable to force which PEAP version (0 or 1) to be used.
# Default is to allow both.
WIRELESS_PEAP_VERSION=''

das ist die ifcfg.template nach dem editieren mit yast! habe mir gedacht, dass es vielleicht daran liegt, das yast die änderungen irgendwie da nicht reingeschrieben hat und habe sie manuell durch
Code:
kdesu kate
reingeschrieben, allerdings mit dem selben ergebnis!
es funktioniert weiterhin nicht
 
*ARGL*

Das war nur die Beispieldatei, wo diese Funktionen _DOKUMENTIERT_ sind!

Du musst es natürlich in DEINE Konfigurationsdatei der WLAN-Karte reinschreiben, siehe auch Posting 64.

Wenn das nicht funktionieren sollte, dann zeige die Ausgaben von ifup wlan0 und auch den Inhalt der ifcfg-wlan*irgendwas*, der Inhalt der ifcfg.template ist uninteressant, die habe ich selbst auf der Kiste.

Greetz,

RM
 
Zuletzt bearbeitet von einem Moderator:
oops, mein fehler, sorry

hier die ifcfg-wlan-00:usw.

Code:
BOOTPROTO='dhcp'
BROADCAST=''
ETHTOOL_OPTIONS=''
IFPLUGD_PRIORITY='10'
IPADDR=''
MTU=''
NAME='Micro-Star International RT2500 802.11g Cardbus/mini-PCI'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='manual'
UNIQUE='2nea.N0s2Kv5lXr4'
USERCONTROL='yes'
WIRELESS_IWPRIV_OPTIONS='set AuthMode=WPAPSK set EncrypType=TKIP set WPAPSK=***'
PREFER_WPA_SUPPLICANT='no'
WIRELESS_AP=''
WIRELESS_AUTH_MODE='open'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY=''
WIRELESS_CLIENT_KEY_PASSWORD=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH=''
WIRELESS_EAP_MODE=''
WIRELESS_ESSID='mowgli'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='yes'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK=''
_nm_name='bus-pci-0000:00:0b.0'

ist also alles korrekt drinne und die ausgabe von ifup wlan0 findest du in posting 70 im ersten code-fenster
 
OK, dann mal folgender Versuch von Hand, die ganzen iwpriv-Optionen in eine Zeile packen.

Code:
iwconfig wlan0 essid [B]DEINEESSID[/B]
iwpriv wlan0 set AuthMode=WPAPSK set EncrypType=TKIP set WPAPSK=[B]DEINSCHLÜSSEL[/B]

dhclient wlan0

Wenn das nicht klappt, dann hier mal ein Script für den halbwegs automatisierten Start.

Code:
#!/bin/sh
# Script für WLAN-Start
/sbin/rcnetwork stop
/sbin/ifconfig wlan0 down
/usr/sbin/iwconfig wlan0 essid [B]DEINEESSID[/B]
/usr/sbin/iwpriv wlan0 set AuthMode=WPAPSK
/usr/sbin/iwpriv wlan0 set EncrypType=TKIP
/usr/sbin/iwpriv wlan0 set WPAPSK=[B]DEINSCHLÜSSEL[/B]
/sbin/dhclient wlan0

Das ganze in eine Textdatei packen mit einem schönen Namen versehen (z.B. WLANstart.sh) und ausführbar machen (geht über Rechtsklick => Eigenschaften) und in /usr/local/sbin kopieren (als root).

Dann als root mit

Code:
WLANstart.sh
ausführen.

Greetz,

RM
 
Nutzt du den Treiber von Suse oder von Serialmonkey, der vorzuziehen wäre?
 
Sorry, hab drauf los geschrieben. Trotzdem ist der von Serialmonkey für diesen Chipsatz vorzuziehen.

Röschtösch, wobei auch die "Treiber von SuSE" eigentlich von Serialmonkey stammen, nur dummerweise sind die im Paket "wlan-kmp-*Kernelflavor*" enthaltenen, neuen rt2x00-Treiber noch ziemlich "unfertig" und werden hoffentlich im neuen Kernel ab 2.6.22, der den ebenfalls neuen ieee80211-Stack "mac80211" enthält, besser funktionieren.

Und so lange muss man sich eben -leider- mit den "Legacy"-Treibern herumschlagen.

Greetz,

RM
 
Code:
Mowgli-Linux:/home/christopher # iwconfig wlan0 essid mowgli
Mowgli-Linux:/home/christopher # iwpriv wlan0 set AuthMode=WPAPSK set EncrypType=TKIP set WPAPSK=***
Mowgli-Linux:/home/christopher # dhclient wlan0
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/

Listening on LPF/wlan0/00:11:09:0b:0a:bf
Sending on   LPF/wlan0/00:11:09:0b:0a:bf
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
das hat nicht funktioniert! schreibe jetzt das skript und poste gleich nochmal

Code:
Shutting down network interfaces:
    eth0      device: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)
    eth0      configuration: eth-id-00:03:0d:18:0f:84                done
    wlan0     device: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01)
    wlan0     configuration: wlan-id-00:11:09:0b:0a:bf               done
Shutting down service network  .  .  .  .  .  .  .  .  .  .  .  .  . done.
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/

Listening on LPF/wlan0/00:11:09:0b:0a:bf
Sending on   LPF/wlan0/00:11:09:0b:0a:bf
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
DHCPOFFER from 192.168.1.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.3 -- renewal in 1753 seconds.

das hat geklappt! muss ich jetzt bei jedem neustart dieses skript ausführen??
 
Zuletzt bearbeitet:
Ich häng mich nochmal kurz rein. Wenn du gewillt bist den Treiber von Serialmonkey komplett auf der Konsole zu installieren, dann hast du den Vorteil, dass du die GUI die dem Treiber beiliegt für die WPA Konfigurierung benutzen kannst, welche den Networkmanager alt aussehen lässt.
Dann hätt ich eine sehr gute Anleitung (ist allerding Debian, aber konsole ist konsole), die ich immer benutze und mich in 3-4 min ins Netz bringt.
 
@Emess
Da du den Thread offenbar weder ganz gelesen noch verstanden hast, worum es hier überhaupt geht ... hier nochmal zum nachlesen:
1. Man findet wahrlich reichlich Probleme mit Ralink-Karten und ich habe schon an so einigen Threads in verschiedensten Foren mitgewirkt, aber bisher hat noch kein TE sich so weit bereit erklärt, daß mal konsequent zu testen, damit auch am Ende eine ausführliche Beschreibung herauskommt.
Das möchte ich hier ändern (für mich der Hauptgrund, warum ich überhaupt helfe, daß XYZ ProblemABC hat, ist mir prinzipiell wurscht, ich will die Lösung für ProblemABC finden.)

2. Die Einrichtung von WPA kann über verschiedenste Weise erfolgen und auch hier würde ich so versuchen vorzugehen, daß es der Einrichtung mit den Bordmitteln (Yast und ifup/ifdown) am nächsten käme. Sollte das nicht funktionieren, dann gibt es noch genügend Möglichkeiten, da Du aber einen Laptop verwendest und vielleicht auch noch ein anderes Netz nutzen möchtest, ist gerade hier wichtig, wie man das Ganze möglichst flexibel einrichtet und da der NetworkManager wegfällt, schränken sich auch die weiteren Möglichkeiten etwas ein.

[...]

OK, langer Rede kurzer Sinn, wenn Du bereit bist, ein wenig Zeit zu investieren, dann wird hier hoffentlich eine Anleitung entstehen, die anderen Usern mit dem selben Problem (und das sind nicht wenige) weiterhilft, dafür kannst Du aber auch von mir dementsprechende Hilfestellungen erwarten.

Der Treiber ist installiert und funktioniert auch.
Hier geht es um die Einrichtung dieser Karte mit YaST ... und die Möglichkeit in Zukunft entsprechende Konfigurationsdateien bereitstellen zu können, um anderen Usern die Einrichtung zu erleichtern.
 

Ähnliche Themen

Problem: Speedport + Windows + Linux

OpenSuse und WLAN

WLAN: Probleme mit Namensauflösung (DNS)

openSUSE 11 KDE 4 und Wlan Verbindung zum Router aber kein WWW

opensuse 11 und Fritz!Wlan Stick

Zurück
Oben