Mainpage
Searchform
History
Versions
Categories
Contents
Deutsch
Kernel: Versions since 2.0.
Check first, if the network device, the network card is recognized by the
kernel. Correct function can be proven by looking into
/var/log/messages
which can be scanned to the keywords
eth0
for Ethernet netzwerk cards,
sdla
for Frame relay devices
atp
for parallel port adapter
arc
für arcnet devices
plip
for parallel port devices
slip_proto
for Slip interfaces to boot
mkiss_proto
for KISS (AX25)
strip_proto
for Starmode Radio IP
ppp_prot
for PPP protocoll
dummy
for das dummy device
eql
for Line Balancing
tr
for Token Ring
fddi
for FDDI
tunl
for Tunnel device
bif
lo
for loopback device
isdn
for ISDN device (Raw IP)
ippp
for ISDN device (IP over PPP on ISDN)
ppp
for PPP
If the support of the device is realized as module, the file
/etc/conf.modules
must be checked, whether the parameters included
herein, especially ports, interrupts, memory, interface conform with the real
world.
A typical entry looks like
# Aliases - specify your hardware alias eth0 tulipund weiter unten
options tulip options=0
Additionally, the loading operations of modules must be checked using command
lsmod
.
If a module or a kernel built in device has been found according to
/var/log/messages
, the configuration can be checked by the command
ifconfig
A typical result screen looks like
eth0 Link encap:10Mbps Ethernet HWaddr 00:40:05:41:4C:51 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:22369990 errors:0 dropped:0 overruns:0 TX packets:13964874 errors:2514 dropped:0 overruns:0 Interrupt:9 Base address:0x6100It is important, that cards with a real hardware address (Ethernet, Arcnet, FDDI) display a real HWaddr, not 00:00:00:00:00:00 or ff:ff:ff:ff:ff:ff. The IP address is assigned by YaST.
If the module cannot be loaded, or the kernel bound in driver cannot access the device, checks should be done:
If necessary the exchange of the card in doubt by a equal one and thereafter by a sample of completely different construction can be of great value to isolate the fault.
If the driver is loaded correctly, the interface eth0 can be configured by
ifconfig eth0 192.168.110.1 broadcast 192.168.110.255 netmask 255.255.255.0 upfor the IP address
192.168.110.1
. Thereafter, for test purposes a
route can be set invoking
route add -net 192.168.110.0 netmask 255.255.255.0 eth0Then the interface must be accessible by the command
ping 192.168.110.1
If the commands ifconfig
or route add
fail, conflicts
in IP addresses, routes and interface names might have been occured. The
described configurations by hand should only be done for testing purposes, if
the canonical configuration with YaST does not succeed. The final
configuration will be done naturally with YaST.
The most recent network card drivers are available from http://cesdis.gsfc.nasa.gov/linux/drivers. Those drivers replace their predecessors in their suitable directory and the kernel must be recompiled and reinstalled, see manual!
See also:
Keywords: NETWORK, NIC, NETWORKCARD, NETWORKINTERFACECARD, SLIP, PPP, ISDN
Categories:
Network
Mainpage
Searchform
History
Versions
Categories
Contents
Deutsch