Ich drehe hier gleich durch :-(

Message
Author
Blinky
Posts: 10
Joined: 09. Jan 2007 16:34
Location: Lübeck

Ich drehe hier gleich durch :-(

#1 Post by Blinky »

seit geschlagenen drei tagen doktore ich jetzt hier rum meine config sieht ca so aus
Suse Linux 10.0 auf nem x86 er system
einen Thomson SpeedTouch 546 Router
Einen (leider) windoof laptop mit automatischer DHCP IP:
Zugewiesen ist
IP:10.0.0.1
Netmask 255.255.255.0
standard gateway 10.0.0.138

der linux rechner hat nun folgendes prob.wenn ich die ip vom DHCP zuweisen lassen will dann zeigt Knetworkmanager an das die verbindung getrennt ist und stellt sie auch nicht her.Wenn ich vom windows rechner das netzwerk mit etheral "abhöre" kommt kein traffic zustande und wenn ich die IP,Subnetmask,DNS majnuell eingebe komme ich zu keinem traffic :?:
Was mache ich blos falsch????

danke im schon mal im vorraus.

pingu_
Posts: 58
Joined: 13. Mar 2004 22:02

#2 Post by pingu_ »

Hallo,
ich nehme mal an, dass Suse die netzwerkkarte mit eth0 bezeichnet...
Was zeigt

Code: Select all

ifconfig
und

Code: Select all

 dmesg | pgrep eth0 
und

Code: Select all

 route 

versuch mal folgendes:

Code: Select all

 ifconfig eth0 ifconfig 10.0.0.1 netmask 255.255.255.0 
und

Code: Select all

 route add default gw 10.0.0.138  netmask 255.255.255.0 dev eth0 
dann versuch mal den Gateway (router) zu pingen

gruss pingu_

Blinky
Posts: 10
Joined: 09. Jan 2007 16:34
Location: Lübeck

#3 Post by Blinky »

huiiiii danke für die promte antwort schon stehen wir vor dem nächsten prob die konsole zeigt da richtige an aber der Knetworkmanager zeigt was völlig anderes an siehe
http://img440.imageshack.us/img440/3753/linuxlz2.jpg

und zugriff aufs internet hab ich auch nich

axo und in die routing table hab ich den router eingefügt
und bei dmesg kommt garnichts

THX 2all

Blinky

pingu_
Posts: 58
Joined: 13. Mar 2004 22:02

#4 Post by pingu_ »

Hallo,
leider ist das Bild nicht von sonderlich guter qualität. :(
Du kannst doch den output von ifconfig mit der Maus selektieren und dann im Menu Bearbeiten das selektiere kopieren und hier eintragen.

welchen eintrag hast du im file: /etc/network/interface

Code: Select all

less /etc/network/interface
sollte in etwa so aussehen:

Code: Select all

#The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
        address 192.168.1.10
        netmask 255.255.255.0
        network 192.168.1.0
        broadcast 192.168.1.255
        gateway 192.168.1.1
        dns-nameservers xx.yy.xx.yy
Greets pingu_

pingu_
Posts: 58
Joined: 13. Mar 2004 22:02

#5 Post by pingu_ »

Hallo,
leider ist das Bild nicht von sonderlich guter qualität. :(
Du kannst doch den output von ifconfig mit der Maus selektieren und dann im Menu Bearbeiten das selektiere kopieren und hier eintragen.

welchen eintrag hast du im file: /etc/network/interface

Code: Select all

less /etc/network/interface
sollte in etwa so aussehen:

Code: Select all

#The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
        address 192.168.1.10
        netmask 255.255.255.0
        network 192.168.1.0
        broadcast 192.168.1.255
        gateway 192.168.1.1
        dns-nameservers xx.yy.xx.yy
Wenn in diesem File die Angaben die KNetwork-manager anzeigt drine sind, ändere sie mal mit den Daten, die du benötigst.

Zuerst noch ein backup des files machen... im falle des falles....

Code: Select all

cp /etc/network/interface /root/interface.bck 
Restore:

Code: Select all

cp /root/interface.bck /etc/network/interface
Greets pingu_

Blinky
Posts: 10
Joined: 09. Jan 2007 16:34
Location: Lübeck

#6 Post by Blinky »

1. ich kann auf dem bild alle erkennen evtl die bildgrößenanpassung ausschalten...

2.

Code: Select all

less /etc/network/interface
bringt nur

Code: Select all

 /etc/network/interface: no such file or directory


:-(((

pingu_
Posts: 58
Joined: 13. Mar 2004 22:02

#7 Post by pingu_ »

Hallo
Welche Subdirectories und Files hast du im Directory: /etc/network/ ?

Greets pingu_

Blinky
Posts: 10
Joined: 09. Jan 2007 16:34
Location: Lübeck

#8 Post by Blinky »

es gibt kein verzeichniss /network

pingu_
Posts: 58
Joined: 13. Mar 2004 22:02

#9 Post by pingu_ »

Hm,
ok, hast du irgendwelche files oder subdirecotries im directory /etc/sysconfig/network ?

Blinky
Posts: 10
Joined: 09. Jan 2007 16:34
Location: Lübeck

#10 Post by Blinky »

oh ja jede menge

im verzeichnis /etc/sysconfig/network/
gibt es die dateien:

config
dhcp
ifcfg-eth-id "mac adresse"
ifcfg-lo
ifroute-lo
routes
routes.Yast2save

und dann noch die verzeichnisse:p

/if-down.d
/ifservicestemplate
/if-up.d
/providers mit nem schloss davor
/scripts

das wars

mfg Blinky

pingu_
Posts: 58
Joined: 13. Mar 2004 22:02

#11 Post by pingu_ »

Das ist gut :-)
Zeige nun mal den inhalt vom file config

Blinky
Posts: 10
Joined: 09. Jan 2007 16:34
Location: Lübeck

#12 Post by Blinky »

hehe

Code: Select all

## Path:	Network/Hardware/Config
## Description:	Set some general network configuration
## Type:	string("","-","+")
## Default:	"+"
## ServiceRestart: network
#
# DEFAULT_BROADCAST is used when no individual BROADCAST is set. It can get one
# of the following values:
# ""  : don't set a broadcast address
# "-" : use IPADDR with all host bits deleted
# "+" : use IPADDR with all host bits set
DEFAULT_BROADCAST="+"

## Type:	yesno
## Default:	yes
# sometimes we want some script to be executed after an interface has been
# brought up, or before an interface is taken down. 
# default dir is /etc/sysconfig/network/if-up.d for POST_UP and
# /etc/sysconfig/network/if-down.d for PRE_DOWN
# Note: if you use NetworkManager then down scripts will be called after the
# interface is down and not before.
GLOBAL_POST_UP_EXEC="yes"
GLOBAL_PRE_DOWN_EXEC="yes"

## Type:        yesno
## Default:     no
# If ifup should check if an ip address is already in use, set this to yes.
# Make sure that packet sockets (CONFIG_PACKET) are supported in the kernel,
# since this feature uses arping, which depends on that.
# Also be aware that this takes one second per interface; consider that when
# setting up a lot of interfaces. 
CHECK_DUPLICATE_IP="no"

## Type:        yesno
## Default:     no
# Switch on/off debug messages for all network configuration stuff. If set to no
# most scripts can enable it locally with "-o debug".
DEBUG="no"

## Type:        yesno
## Default:     yes
# All error and info messages from network and hardware configuration scripts go
# to stderr. Most tools that call sysconfig scripts (udev, rcnetwork, scpm,
# YaST) catch these messages and can log them. So some messages appear twice in
# syslog. If you don't like that, then set USE_SYSLOG=no.
USE_SYSLOG="yes"

## Type:        yesno
## Default:     yes
# There are some services (ppp, ippp, dhcp-client, pcmcia, hotplug) that have to
# change the /etc/resolv.conf dynamically at certain times.  E.g. if ppp/ippp
# establishes a connection and is supplied by the peer with a list of
# nameservers. Or pcmcia needs to set the correct nameserver for the choosen
# configuration scheme. If you don't like these services to change
# /etc/resolv.conf at all, then set this variable to "no".
# If unsure, leave it at the default (which is "yes").
#
MODIFY_RESOLV_CONF_DYNAMICALLY="yes"

## Type:        yesno
## Default:     no
# Like MODIFY_RESOLV_CONF_DYNAMICALLY, except it modifies /etc/named.conf.
# If unsure, leave it at the default (which is "no").
#
MODIFY_NAMED_CONF_DYNAMICALLY="no"

## Type:        string
## Default:     ""
# If you need a special nameserver that should always be prepended to the list
# of dynamically changed nameservers, you may add it here.
#
MODIFY_RESOLV_CONF_STATIC_DNS=""

# Handling of network connections
# ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# These features are designed for the convenience of the experienced
# user. If you encounter problems you don't understand then switch
# them off. That is the default.
# Please do not complain if you get troubles. But if you want help to
# make them smarter write to <http&#58;//www.suse.de/feedback>.

## Type&#58;	yesno
## Default&#58;	no
#
# If you are interested in the connections and nfs mounts that use a
# network interface, you can set CONNECTION_SHOW_WHEN_IFSTATUS="yes".
# Then you will see them with 'ifstatus <interface>' &#40;or 'ifstatus
# <config>'&#41;
# This one _should_ never harm ;&#41;
#
CONNECTION_SHOW_WHEN_IFSTATUS="no"

## Type&#58;	yesno
## Default&#58;	no
#
# If an interface should be set down only if there are no active
# connections, then use CONNECTION_CHECK_BEFORE_IFDOWN="yes"
#
CONNECTION_CHECK_BEFORE_IFDOWN="no"

## Type&#58;	yesno
## Default&#58;	no
#
# If these connetions &#40;without the nfs mounts&#41; should be closed when
# shutting down an interface, set CONNECTION_CLOSE_BEFORE_IFDOWN="yes".
# WARNING&#58; Be aware that this may terminate applications which need
# one of these connections!
#
CONNECTION_CLOSE_BEFORE_IFDOWN="no"

## Type&#58;	yesno
## Default&#58;	no
#
# If you are a mobile laptop user and like even nfs mounts to be
# closed when you leave your current workplace, then set
# CONNECTION_UMOUNT_NFS_BEFORE_IFDOWN="yes". This does only work
# if CONNECTION_CLOSE_BEFORE_IFDOWN="yes", too.
# WARNING&#58; Be aware that this may terminate applications which use
# these nfs mounts as working directory. Be very carefull if your home
# is mounted via nfs!!!
# WARNING&#58; This may even lead to hanging ifdown processes if there are
# processes that could not be terminated. If you are using
# hotpluggable devices &#40;pcmcia, usb, firewire&#41;, first shut them down
# before unplugging!
#
CONNECTION_UMOUNT_NFS_BEFORE_IFDOWN="no"

## Type&#58;	yesno
## Default&#58;	no
#
# If terminating processes that use a connection or nfs mount is not
# enough, then they can be killed after an unsuccesfull termination.
# If you want that set CONNECTION_SEND_KILL_SIGNAL="yes"
#
CONNECTION_SEND_KILL_SIGNAL="no"

## Type&#58;        string
## Default&#58;     ""
#
# Here you may specify which interfaces have to be up and configured properly
# after 'rcnetwork start'. rcconfig will return 'failed' if any of these
# interfaces is not up. You may use interface names as well but better use
# hardware descriptions of the devices &#40;eth-id-<macaddress> or eth-bus-...  See
# man ifup for 'hardware description'&#41;. The network start script will wait for
# these interfaces, but not longer as set in WAIT_FOR_INTERFACES.
# You need not to add dialup or tunnel interfaces here, only physical devices.
# The interface 'lo' is always considered to be mandatory and can be omitted.
#
# If this variable is empty, rcnetwork tries to derive the list of mandatory
# devices automatically from the list of existing configurations. Configurations
# with names bus-pcmcia or bus-usb or with STARTMODE=hotplug are skipped. &#40;try
# '/etc/init.d/rc5.d/S*network start -o debug fake | grep MANDAT'&#41;
MANDATORY_DEVICES=""

## Type&#58;	integer
## Default&#58;	20
#
# Some interfaces need some time to come up or come asynchronously via hotplug.
# WAIT_FOR_INTERFACES is a global wait for all mandatory interfaces in
# seconds. If empty no wait occurs.
#
WAIT_FOR_INTERFACES="20"

## Type&#58;	yesno
## Default&#58;	yes
#
# With this variable you can determine if the SuSEfirewall when enabled
# should get started when network interfaces are started.
FIREWALL="yes"

## Type&#58;        string
## Default&#58;     "eth*&#91;0-9&#93;|tr*&#91;0-9&#93;|wlan&#91;0-9&#93;|ath&#91;0-9&#93;"
#
# Automatically add a linklocal route to the matching interfaces.
# This string is used in a bash "case" statement, so it may contain
# '*', '&#91;', '&#93;'  and '|' meta-characters.
#
LINKLOCAL_INTERFACES="eth*&#91;0-9&#93;|tr*&#91;0-9&#93;|wlan&#91;0-9&#93;|ath&#91;0-9&#93;"

## Type&#58;        string
## Default&#58;     "-f -I"
#
# Set default options for ifplugd. You may also set them in an ifcfg-* file
# individually. Have a look at 'man ifplug' for details. We let ifplugd set the
# interface UP when starting, because there are many interfaces where link beat
# cannot be detected otherwise. If you want the interface to stay down then add
# the option '-a'. If you like ifplugd to beep on cable &#40;un&#41;plug, remove '-b'.
#
IFPLUGD_OPTIONS="-f -I -b"

## Type&#58;        yesno
## Default&#58;     yes
#
# Forces all interfaces eth* ath* wlan* and ra* to be persistent via udev.
# See /usr/share/doc/package/sysconfig/README.Persistent_Interface_Names for
# details. 
#
FORCE_PERSISTENT_NAMES="yes"

## Type&#58;        yesno
## Default&#58;     no
#
# Instead of the usual network setup &#40;now called 'NetControl'&#41; you may also use
# 'NetworkManager' to control your interfaces.
#
# NetControl is what you were used to in SUSE Linux up to now. It has a wide
# range of configurations means for setting up any number of different virtual
# and real interfaces. It should be used if you&#58;
# - want a static network setup
# - have many interfaces
# - need VLAN, bonding, bridging, multiple IP addresses
# - must restrict network control to root
# It may also switch interfaces automatically, but lacks a usable GUI for normal
# users.
#
# NetworkManager lets the user control interfaces and switches automatically if
# network interfaces lose/gain physical connection. It should be used if you&#58;
# - move between networks frequently
# - want a GUI for network control
# Especially on mobile computers that use mainly one wired and one wireless
# interface NetworkManager will please you.
#
# If you are used to SCPM then you might probably stay with NetControl. But at
# least try NetworkManager, because it can replace SCPM in some usage scenarios.
# 
NETWORKMANAGER="no"

## Type&#58;        yesno
## Default&#58;     yes
#
# When using NetworkManager you may want to trigger special actions when an
# interface comes up. NetworkManagerDispatcher is a daemon that listens to
# dbus-messages that tell that an interface is up/down and triggers whatever
# you like. Read more about it in the manpage to NetworkManagerDispatcher.
#
# This variable has no effect if NETWORKMANAGER=no
#
NM_DISPATCHER="yes"

pingu_
Posts: 58
Joined: 13. Mar 2004 22:02

#13 Post by pingu_ »

Die config schaut soweit ok aus..
hast du files in den directories /etc/sysconfig/network/if-up.d und /etc/sysconfig/network/scrits ?

Blinky
Posts: 10
Joined: 09. Jan 2007 16:34
Location: Lübeck

#14 Post by Blinky »

if-up.d ist ein file mit name

dhcpcd-hook-samba

im scripts ordner is ne menge drin

soll ich den inhalt posten ??

mfg blinky

pingu_
Posts: 58
Joined: 13. Mar 2004 22:02

#15 Post by pingu_ »

ups sorry, war ein wenig zu schnell mit meinem schreiben... sorry...

Zeig mir bitte mal den inhalt vom file: /etc/sysconfig/network/ifcfg-eth-id "mac adresse". Dies sollte nun die config der netzwerkkarte sein...

Post Reply