[LUGA] Mit freundlicher Unterstützung von:
WSR

Mail Thread Index


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[luga] Re: fehler beim routen




Herbert Dirnberger schrieb mir am Tue, 17 Mar 1998 15:40:40 +0100:
> To: luga <luga@luga.or.at>, rolf@suse.de, herbert.dirnberger@telecom.at, manfred.wirlach@lsr-noe.gv.at, support@suse.de, suse-linux@suse.de
> From: Herbert Dirnberger <herbert.dirnberger@telecom.at>
> Subject: fehler beim routen
> 
> Dies ist eine mehrteilige Nachricht im MIME-Format.
> --------------6BF7E62982F453A96F04A435
> Content-Type: text/plain; charset=iso-8859-1
> Content-Transfer-Encoding: 8bit
> 
> ich arbeite zur Zeit an einem Projekt an der HTL-VA St.Pölten,
> Automatisierungstechnik,
> nebenbei sollte ich auch eine Firewall installieren, doch ich hänge zur
> Zeit noch an der Netzanbindung, weiters wollte ich den Zugang vom an das
> interne Netz mit IP-Masq. lösen......(übrigens kann der AHA 2940 UW nach
> dem Kernel compilieren Probleme bereiten, auch hier suche ich noch
> Erfahrungen....)
> 
> 
> leider ist es mir nicht möglich, einen linux rechner an ein kabelmodem
> richtig anzubinden
> 
> die provider-daten
> 
> Protokoll:      TCP/IP
> Gateway:       195.202.141.2
> Subnet mask: 255.255.255.0
> DNS:             195.202.138.2
> Mailserver:     mail.kfs.at
> Mailrelay(POP): mail.kfs.at
> Proxy:           proxy.kfs.at
> Port:             1080
> IP:                195.202.141.40
> 
> ich verwende die SUSE 5.1 Distribution Ausgabe November 97,
> die Kernelmodule aha 7... (für AHA-2940UW) und de 4x5 (D-Link DFE-500
> TX)
> 
> ich wählte die minimale Installation des YAST-Menüs
> 
> die Netzwerk-Konfiguration unter YAST:
> 
> Rechnername: fire
> Domain:          htlva
> ---->echtes Netzwerk
> 
> ---->Typ: eth0
> ---->IP:    195.202.141.40 (des eigenen Rechners)
> ---->Netmask: 255.255.255.0
> ---->Gateway: 195.2020.141.2
> ---->inetd: nein
> ---->portmap: nein
> ---->nameserver: 195.202.138.2
> ---->domain: kfs.at
> 
> Die Netzwerkkarte wird beim Booten erkannt, doch es ist mir nicht
> möglich, einen ping nach außen zu senden,
> beim route befehl, kommt immer ein dummy0 vor (:-<)
> 
> wo liegt der fehler, kann mir jemand von euch helfen, dieses problem zu
> lösen, kann der
> fehler bei der physikalischen Netzanbindung liegen. (bin mir fast
> sicher), eigentlich dachte ich mir das anbinden eines linux-rechner
> eigentlich kein problem sein dürfte, hab mich aber gewaltig getäuscht,
> bei der anbindung hab ich schon zig Stunden verbracht, doch leider kann
> mir hier der zeitfaktor auch nicht helfen,
> ..............................
> 
> vielen dank im voraus!
> 
> 
> --------------6BF7E62982F453A96F04A435
> Content-Type: text/plain; charset=us-ascii; name="rc.config"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline; filename="rc.config"
> 
> #
> # /etc/rc.config
> #
> # Copyright (c) 1996 S.u.S.E. GmbH Fuerth, Germany.  All rights reserved.
> #
> # Author: Florian La Roche <florian@suse.de>, 1996
> #	  Werner Fink <werner@suse.de>, 1996
> #	  Burchard Steinbild <bs@suse.de>, 1996
> #
> # Configuration database for shell scripts in /sbin/init.d, /sbin/SuSEconfig 
> # and /root/bin/cron.daily
> #
> # Please edit this file and execute /sbin/SuSEconfig to configure everything.
> # Also don't forget to edit the following files:
> #	- /etc/lilo.conf
> #	- /etc/fstab
> #	- /etc/profile
> #	- /etc/hosts
> #
> 
> #
> # Some people don't want SuSEconfig to modify the system. With this
> # entry you can disable SuSEconfig completely. 
> # Please don't contact our support if you have trouble configuring your 
> # system after having disabled SuSEconfig.  (yes/no)
> #
> ENABLE_SUSECONFIG=yes
> 
> 
> #
> # SuSEconfig can mail reports (created by YaST or included in packages)
> # to you.  Here you can set the address.  If you don't want it, simply
> # set it to "".
> #
> MAIL_REPORTS_TO="root"
> 
> #
> # There are two levels of mailing.  If you set MAIL_LEVEL it to "warn"
> # you only get the important mails.  If you set it to "all", you get
> # logs also.
> #
> MAIL_LEVEL="warn"
> 
> #
> # Which device is the mouse ? (e.g. "/dev/ttyS0")
> #
> MOUSE=""
> 
> #
> # Which device is the modem ? (e.g. "/dev/cua1")
> #
> MODEM=""
> 
> #
> # keytable and console font
> # (e.g. "de-latin1-nodeadkeys" for KEYTABLE, empty for US settings)
> #
> KEYTABLE="de-lat1-nd"
> FONT=""
> 
> #
> # keyboard repeat rate (2.0 - 30.0)
> # keyboard delay time in ms (250, 500, 750, 1000)
> # (you have to set both, if "kbdrate" should be called)
> #
> KBD_RATE=""
> KBD_DELAY=""
> 
> #
> # NumLock on? ("yes" or "no")
> KBD_NUMLOCK="no"
> 
> #
> # CapsLock on? ("yes" or "no")
> KBD_CAPSLOCK="no"
> 
> #
> # tty's for NumLock and CapsLock 
> # example: "tty1 tty2"
> # "" for all tty's
> #
> KBD_TTY="tty1 tty2 tty3 tty4 tty5 tty6"
> 
> 
> #
> # Set to "-u" if your system clock is set to GMT, otherwise "".
> #
> GMT=""
> 
> #
> # Timezone (e.g. MET)
> # (this will set /usr/lib/zoneinfo/localtime)
> #
> TIMEZONE="MET"
> 
> #
> # start loopback networking? ("yes" or "no")
> #
> START_LOOPBACK="yes"
> 
> #
> # networking
> #
> # number of network cards: "_0" for one, "_0 _1 _2 _3" for four cards
> #
> NETCONFIG="_0"
> 
> #
> # IP Adresses
> #
> IPADDR_0="195.202.141.40"
> IPADDR_1=""
> IPADDR_2=""
> IPADDR_3=""
> 
> #
> # network device names (e.g. "eth0")
> #
> NETDEV_0="eth0"
> NETDEV_1=""
> NETDEV_2=""
> NETDEV_3=""
> 
> #
> # parameteres for ifconfig, if you put "bootp" into it, bootp will
> # be used to configure it
> # sample entry for ethernet:
> # IFCONFIG_0="192.168.81.38 broadcast 192.168.81.63 netmask 255.255.255.224"
> #
> IFCONFIG_0="195.202.141.40 broadcast 195.202.141.255 netmask 255.255.255.0 up"
> IFCONFIG_1=""
> IFCONFIG_2=""
> IFCONFIG_3=""
> 
> # 
> # setup dummy network device for IPADDR_0? this is useful for non permanent
> # network connections (e.g. SLIP, PPP). Some software needs a connection
> # to FQHOSTNAME (e.g. plp). (yes, no)
> SETUPDUMMYDEV=yes
> 
> 
> #
> # SuSEconfig can do some checks and modifications for /etc/hosts. 
> # If this is not wanted, set the following variable to 'no' (yes, no).
> #
> CHECK_ETC_HOSTS=yes
> 
> 
> #
> # hostname of the system (full name)
> # if zero, and bootp is used above, bootp will also set the hostname
> # (e.g. "riemann.suse.de" or "hugo.linux.de")
> # don't forget to also edit /etc/hosts for your system
> #
> FQHOSTNAME="fire.htlva"
> 
> #
> # SuSEconfig can create and check the /etc/host.conf for you. Should this
> # be done ("yes" or "no").
> #
> CREATE_HOSTCONF="yes"
> 
> #
> # Shall SuSEconfig maintain /etc/resolv.conf (needed for DNS) ? 
> # If set to yes and one of SEARCHLIST and NAMESERVER is empty,
> # it is assumed, that no DNS is wanted and /etc/resolv.conf will
> # be deleted. If yes and both are filled out, it will be created.
> # "no" simply lets /etc/resolv.conf untouched.
> #
> CREATE_RESOLVCONF=yes
> 
> #
> # Should NIS be used for name resolving (yes/no)
> #
> USE_NIS_FOR_RESOLVING=no
> 
> #
> # domain searchlist that should be used in /etc/resolv.conf
> # (e.g. "suse.de linux.de uni-stuttgart.de")
> # Attention! this has to be filled out, if you want to access a name server
> #
> SEARCHLIST="kfs.at"
> 
> #
> # space separated list of nameservers that should be used for /etc/resolv.conf
> # give a maximum of 3 IP numbers
> # (e.g. "192.168.116.11 192.168.7.7")
> #
> NAMESERVER="195.202.138.2"
> 
> #
> # Used for News-Postings.
> #
> ORGANIZATION=""
> 
> #
> # News server.
> #
> NNTPSERVER=""
> 
> #
> # space separated list of irc servers
> #
> IRCSERVER=""
> 
> #
> # start the inet daemon in multi-user? ("yes" or "no")
> # this is needed, if you have to telnet/rlogin to your own machine.
> # It is also needed for the man page formatter in S.u.S.E. Help system
> # and for starting the plp lp daemon.
> #
> START_INETD="no"
> 
> #
> # have mail daemon on SMTP port? ("yes" or "no")
> # needed, if you receive email from other hosts via tcp/ip
> # not needed, if you have a uucp-only host or only out-going email.
> # If set to "yes", sendmail will be started as daemon.
> # As uucp site, you can get along with "SMTP=no", if you make
> # a "sendmail -q" call after each poll. (As rmail is queuing the mail only
> # and not delivering it...)
> #
> SMTP="yes"
> 
> #
> # From:-Line in email and News postings
> # (otherwise the FQDN is used)
> #
> FROM_HEADER="fire.htlva"
> 
> #
> # start kernel daemon? ("yes" or "no")
> #
> START_KERNELD="yes"
> 
> #
> # start cron daemon? ("yes" or "no")
> # should be left unchanged to the default "yes" entry
> #
> CRON="yes"
> 
> #
> # start portmap? ("yes" or "no")
> # this is needed, if the NFS server is started or if NIS is used
> #
> START_PORTMAP="no"
> 
> #
> # should the NFS server be started on this host? ("yes" or "no")
> # (needs activated portmapper)
> #
> NFS_SERVER="yes"
> 
> #
> # should translate server client for userid and goupid be started 
> # ("yes" or "no") - will only be started, if NFS_SERVER is "yes".
> #
> NFS_SERVER_UGID="yes"
> 
> 
> #
> # should imported NFS be reexported? ("yes" or "no")
> #
> REEXPORT_NFS="no"
> 
> #
> # when shutting down routing, all net connection can be closed (not useful
> # in all cases).  If CLOSE_CONNECTIONS is set to "true" /sbin/init.d/route
> # scans /proc to search for network connections and sends a term signal
> # to the processes.
> #
> CLOSE_CONNECTIONS="false"
> 
> #
> # start pcnfsd (for PCNFS clients; needs activated portmapper - 
> # see man pcnfsd) (yes/no)
> #
> START_PCNFSD=no
> 
> #
> # start bwnfsd (pcnfs related) (yes/no)
> #
> START_BWNFSD=no
> 
> #
> # pcnfsd and bwnfsd need spool directory for lpd. Set it here.
> #
> PCNFSD_LPSPOOL=/var/spool/lpd
> 
> #
> # should gpm be started on this machine? ("yes" or "no")
> #
> START_GPM="no"
> 
> #
> # gpm will be started with these parameters
> # it won't be started in runlevel 3 (xdm)
> # (example: "-t msc -m /dev/mouse")
> #
> GPM_PARAM=""
> 
> #
> # start the the routed (for dynamic routing - see man routed) (yes/no)
> #
> START_ROUTED=no
> 
> #
> # start the named (package bind)? You have to configure the named first,
> # before you can start it (man named).
> #
> START_NAMED=no
> 
> #
> # should updatedb (for locate) be started by cron.daily ("yes" or "no")
> #
> RUN_UPDATEDB=yes
> 
> #
> # should mandb and whatis be recreated by cron.daily ("yes" or "no")
> #
> REINIT_MANDB=yes
> 
> #
> # updatedb has a parameter "--localuser". it runs the find as this user.
> # some people think, its a security hole to run it as root (because you
> # can get information about directories you can not read normally). Some
> # think its useful to hold all files in the database. If you want full
> # information in locate db, set RUN_UPDATEDB_AS=root. If you want security
> # use RUN_UPDATEDB_AS=nobody.
> #
> RUN_UPDATEDB_AS=nobody
> 
> #
> # uptdatedb normally only scans local harddisks, but can include net paths
> # in database as well. If you specify directories here, they will be scanned.
> #
> UPDATEDB_NETPATHS=""
> 
> #
> # uptdatedb can skip directories for its database. The following parameter
> # says which.
> #
> UPDATEDB_PRUNEPATHS="/mnt /cdrom /tmp /usr/tmp /var/tmp /var/spool /proc"
> 
> #
> # search net paths as ? (e.g. nobody)
> #
> UPDATEDB_NETUSER=""
> 
> #
> # old corefiles? should they be deleted ("yes" or "no")
> # if set to no, cron.daily will tell you, if it finds old core files.
> # please note, that this feature needs RUN_UPDATEDB to be set to "yes".
> #
> DELETE_OLD_CORE=no
> 
> #
> # how old are 'old' core files? (in days)
> #
> MAX_DAYS_FOR_CORE=7
> 
> 
> #
> # we have a small script to generate usr/info/dir file. This needs perl..
> # ("yes" or "no")
> #
> CREATE_INFO_DIR="yes"
> 
> # 
> # SuSEconfig can call chkstat to check permissions and ownerships for
> # files and directories (using /etc/permissions). 
> # Setting to "set" will correct it, "warn" produces warnings, if 
> # something strange is found. Disable this feature with "no".
> #
> CHECK_PERMISSIONS=set
> 
> #
> # S.u.S.E. Linux contains two different configurations for
> # chkstat. The differences can be found in /etc/permissions.secure
> # and /etc/permissions.easy. If you create your own configuration
> # (e.g. permissions.foo), you can enter the extension here as well.
> #
> # (easy/secure local foo whateveryouwant).
> #
> PERMISSION_SECURITY="easy local"
> 
> 
> #
> # How long to store old log files. If set to 0, log files will be untouched.
> # The log files below will be checked by cron.daily. The number
> # after the name means the minimum size in k, the file has to have, before
> # it will be backed up (root gets a mail, if it happens).
> #
> # /tmp/log_mg.* (1024), /var/log/wtmp (400), /var/log/isdn (4096),
> # /var/lib/xdm/xdm-errors (200), /var/spool/uucp/Log (2048),
> # /var/spool/uucp/Stats (1024), /var/log/debug (1024), /var/log/warn (1024),
> # /var/log/messages (4096), /var/log/xferlog (4096), 
> # /local/www/logs/access_log (4096), /local/www/logs/error_log (1024)
> # /var/adm/isdn.log (1024), /var/log/isdncalls (1024)
> #
> MAX_DAYS_FOR_LOG_FILES=365
> 
> #
> # cron.daily can make backup the rpm database. Set the path here, and
> # cron.daily will make backup everytime it is called and the db has
> # changed.  This backups are recommended.  If you don not want this
> # feature, set it to "".
> #
> RPMDB_BACKUP_DIR=/var/adm/backup/rpmdb
> 
> #
> # here you can set the maximum number of backup files for the rpm
> # database.
> #
> MAX_RPMDB_BACKUPS=5
> 
> #
> # cron.daily can check for old files in tmp-dirs. It will delete all files
> # not accessed for more than MAX_DAYS_IN_TMP. If MAX_DAYS_IN_TMP is not set
> # or set to 0, this feature will be disabled. 
> #
> MAX_DAYS_IN_TMP=0
> 
> #
> # You can specify in TMP_DIRS_TO_CLEAR, which directories have to be 
> # searched for old files, to be deleted.
> #
> TMP_DIRS_TO_CLEAR="/tmp /var/tmp"
> 
> #
> # In OWNER_TO_KEEP_IN_TMP, you can specify, whoms file shall not be deleted.
> #
> OWNER_TO_KEEP_IN_TMP="root"
> 
> #
> # Do you want to have "." in root path?  This is not recommended, but
> # many people do prefer it (yes/no).
> #
> CWD_IN_ROOT_PATH="no"
> 
> 
> #
> # If you want to allow root logins from other machines, set ROOT_LOGIN_REMOTE
> # to "yes". 
> #
> ROOT_LOGIN_REMOTE="no"
> 
> 
> 
> 
> #
> # possibly a script in /sbin/init.d or cron.daily sends mails. 
> # So please let MM_RUNASROOT be set to "true".
> #
> MM_RUNASROOT=true
> export MM_RUNASROOT
> 
> umask 022
> 
> #
> # Attention! This variable PATH is NOT setting the PATH for user or root
> # shells. It is only used internally for /sbin/init.d/*, SuSEconfig and 
> # cron.daily. Please do NOT change PATH here.
> #
> PATH=/sbin:/bin:/usr/sbin:/usr/bin
> 
> 
> 
> #
> # end of initial rc.config
> #
> 
> 
> #
> # do you want to generate a sendmail-configuration /etc/sendmail.cf from
> # parameters given in /etc/rc.config ("yes") or do you want to generate
> # your /etc/sendmail.cf yourself ("no") ?
> # (you could also use /etc/mail/linux.mc to do so.)
> #
> SENDMAIL_TYPE="no"
> #
> # smarthost - this host gets all outgoing email from us
> # normally used for uucp-connected sites or for dialup connections
> # use "uucp-dom:server.uucp.com" to deliver all email to "server.uucp.com"
> #
> SENDMAIL_SMARTHOST=""
> #
> # sendmail assumes the following space-separated host-names to be
> # the local host (this must just be used for names differrent to the
> # hostname, for e.g. aliases like www.nowhere.com)
> #
> SENDMAIL_LOCALHOST="localhost"
> #
> # do not deliver any email locally, but send all email to another host
> # this can just be used with another system that has the same users on it
> # and you probably also want to set the FROM_HEADER to the other host
> #
> SENDMAIL_RELAY=""
> #
> # with what parameters should sendmail be started?
> # normal sites use "-bd -q30m -om". if you set SENDMAIL_EXPENSIVE and you
> # have a dialup ISDN connection, you probably want to set this to
> # "-bd -om" and run "sendmail -q" from your crontab.
> #
> SENDMAIL_ARGS="-bd -q30m -om"
> #
> # sendmail will only queue email in /var/mqueue and will only start
> # to deliver it if "sendmail -q" is run
> #
> SENDMAIL_EXPENSIVE="no"
> #
> # sendmail will not try to canonify hostnames in your email
> # so much less DNS-queries are send
> # you probably want to enable this on a SENDMAIL_EXPENSIVE system
> #
> SENDMAIL_NOCANONIFY="no"
> 
> LANGUAGE="german"
> 
> --------------6BF7E62982F453A96F04A435
> Content-Type: text/plain; charset=us-ascii; name="route.conf"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline; filename="route.conf"
> 
> #
> # /etc/route.conf
> #
> # In this file you can configure your static routing...
> #
> # This file is read by /sbin/init.d/route. 
> #
> #
> # Destination             Dummy/Gateway   Netmask             Device
> #
> # Examples:
> #
> # Net devices
> # 193.141.17.192          0.0.0.0         255.255.255.192     eth0
> #
> # Gateways
> # default                 Riemann
> # 0.0.0.0                 193.141.17.193
> #
> #
> # Host behind Gateway
> # 193.141.17.142          193.141.17.193  255.255.255.255
> #
> # Net behind a Gateway
> # 193.141.17.145          193.141.17.193  255.255.255.0
> #
> # Multicast route for e.g. eth0. IP multicasting, forwarding and perhaps
> # multicast routing in kernel should be enabled.   More information will
> # be found in the NET-3-HOWTO.     Most people do NOT need this feature.
> #
> # 224.0.0.0       0.0.0.0      240.0.0.0   eth0
> #
> # ISDN (i4l)
> # 193.141.17.0            0.0.0.0         255.255.255.0       isdn0
> # default                 193.141.17.193
> 195.202.141.0  		0.0.0.0        		255.255.255.0  		eth0
> default			195.202.141.2
> 
> --------------6BF7E62982F453A96F04A435
> Content-Type: text/plain; charset=us-ascii; name="route-n_output"
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline; filename="route-n_output"
> 
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 195.202.141.40  0.0.0.0         255.255.255.255 UH    0      0        0 dummy0
> 195.202.141.0   0.0.0.0         255.255.255.0   U     0      0        0 eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        1 lo
> 0.0.0.0         195.202.141.2   0.0.0.0         UG    0      0        0 eth0
> 
> --------------6BF7E62982F453A96F04A435--
> 
> 
> 
Sehr geehrter Herr Dirnberger,

vielen Dank für Ihre Anfrage.

Wir sind immer bemüht, auf jede Frage unserer Kunden einzugehen.

Ihr Anliegen geht jedoch über das hinaus, was wir unseren Kunden
unter der Bezeichnung Installationssupport anbieten.

Bei derartigen Problemstellungen, die über den Installations-
support hinausgehen, bieten wir Ihnen gerne Business-Support an,
den wir Ihnen gesondert in Rechnung stellen.

S.u.S.E. bietet Ihnen die Möglichkeit, jederzeit Business-Support
in Anspruch zu nehmen, ohne vorher einen speziellen Vertrag
abzuschließen.

Der Support kann nach Ihren Wünschen am Telefon, per E-Mail oder
per Fax erfolgen.

Kontakt:

*  Telefon: 09 11 / 3 24 71-56
*  Fax:     09 11 / 3 20 67 27
*  E-Mail:  bsupport@suse.de

Direkte Ansprechpartner:

*  Klaus Franken (kfr@suse.de),     Durchwahl: -39
*  Carsten Höger (choeger@suse.de), Durchwahl: -18

Fragen? / größere Projekte? / Pauschalverträge?

Sprechen Sie uns an! Weitere Informationen finden Sie online auf

*  http://www.suse.de/Supportuebersicht.html




Mit freundlichen Grüßen
   gez. Remo Behn


      \\///
      (.|.)                      Ihr S.u.S.E Support-Team <support@suse.de>
+--oOO-(_)-OOo------------------------------------------------------------+
| Remo Behn              S.u.S.E. GmbH                                    |  
| sray@suse.de           Gebhardtstrasse 2       phone    +49-911-3247130 |
| http://www.suse.de     90762 Fuerth, Germany   fax      +49-911-3206727 |
+-------------------------------------------------------------------------+
+-------------------------------------------------------------------------+
                         S.u.S.E. auf der CeBIT '98! 
                              Besuchen Sie uns!
                             Halle 5, Stand  A61
               Halle 3, Stand C33 (Software AG Partner-Stand)
+-------------------------------------------------------------------------+



powered by LINUX the choice of a gnu generation
linux user group austria;
Suche
Suche
Letzte Änderung:
webmaster@luga.at
September 2010