Linux-Networking Digest #933, Volume #11 Sun, 18 Jul 99 17:13:43 EDT
Contents:
two problems with netatalk (SuSE 5.3) (=?ISO-8859-1?Q?Bernd_Gr=FCndling?=)
Dead daemons? (R. Christopher Harshman)
getting Email for domain ("Paul Richards")
Re: Linux Internet Email gateway and MS Exchange (Bernd Eckenfels)
How to permanent add route command to startup sequence? (John H. Chauvin)
Re: NIC card configuration 3c905B-TX ("Bruce Phillips")
Re: How to connect dumb terminals via Lan and more? (Graham Harris)
Slow transfers out but fast coming in ([EMAIL PROTECTED])
Diald goes up every 4-5 min? (rbinning)
Re: phoneline/wireless networking drivers (Joseph Wang)
Installing a D-Link DFE-530TX NIC into Redhat6.0 (Stephen)
US Robotics Modem Question (Robert B. Love)
Re: Auto check for email (Scott Marlowe)
Error: Can't get terminal parameters: I/O error (Netjah)
Re: help.. (Scott Marlowe)
Re: How to permanent add route command to startup sequence? (Scott Marlowe)
linux, PPP, ATT Worldnet - looks like PPP does not start??? ("Elizabeth Larrey
Konstantinov")
Serial Connection ("Sebastian Speiser")
Re: IP masq amd PPPd diald on demad (Nomad)
Block specific IP with ipchains? ([EMAIL PROTECTED])
Q: ISDN Gateway with Linux ("choi")
From: [EMAIL PROTECTED] (=?ISO-8859-1?Q?Bernd_Gr=FCndling?=)
Subject: two problems with netatalk (SuSE 5.3)
Date: Sun, 18 Jul 1999 19:52:51 +0200
Today I finally found some time to install SuSE Linux 5.3 (I know, its
old - my PC is older ;-). I want to install CVS Server that I need to
access from a Macintosh. So I decided to install the predefined "Devel1"
configuration and added only netatalk.
Linux runs, but I have two strange network effects.
a) the two machines do not communicate via TCP/IP. Pinging each other
does not work.
b) netatalk works, but it takes 40 seconds until a volume gets mounted.
Maybe those problems are related, maybe not. Since I am completely new
to any UNIX, I feel somehow lost.
Some infos:
a)
the linux machine is 192.168.6.1, the Mac 192.168.6.2. No connection to
any other network yet. According to the info in SuSE's support database,
the configuration is ok. ifconfig returns very well looking data,
interrupt and IO address are ok. Pinging itself and the loopback device
works.
starting/stopping netatalk does not matter. Enabling/disabling AppleTalk
on the Mac does not help, either.
b)
during the 40 second wait the Mac (G3, German OS 8.6) is frozen. TCP/IP
is always active. When using the chooser to select the linux server, I
get a barber pole dialog called "Verbindungsstatus" (something like
"connection state" in English, I hope). Text inside: "UEberpruefen von:"
("checking:") with no indication what it is going to check, running
forever. If I cancel, I briefly see "reverting to AppleTalk", then I
wait for those 40 seconds. After that, it works.
If I manually add the server's TCP/IP address via the chooser, it gets
shown after "checking" in the dialog mentioned above. Besides that, it
does not make any difference.
The Mac, the cabling and my PC's Ethernet Card are ok: when running NT
4.0 on the PC everthing works fine.
Any ideas?
Bernd.
___
Bernd Gruendling[EMAIL PROTECTED]
Systemberatung Softwaredesign Telefax: +49 5363 20901
Wendenstrasse 87, Wolfsburg, Germany
--
From: R. Christopher Harshman [EMAIL PROTECTED]
Crossposted-To: comp.os.linux.misc,alt.os.linux
Subject: Dead daemons?
Date: Sun, 18 Jul 1999 18:11:12 GMT
I've got a box that I administrate in California (this summer,
I'm in Missouri). It's running kernel 2.2.9 and Slackware 3.5
(heavily modified). I telnet in occasionally (once a day or
so) to make sure everything's more or less kosher, and logfiles
get rotated and emailed to me very night.
A few days ago, the box wasn't responding to telnet or ftp
connections, but ping and apache were still working. I
figured inetd had somehow stopped responding, and remembered
that we had installed 'sshd' after the fact, and that it
was running from /etc/rc.d/rc.local, so I was able to get
in using secure shell. Sure enough, inetd was not listed
among the processes when I did a ps -aux. So, as root,
I fired it back up, and all was well.
Now, yesterday, the messages file that arrived in my inbox
was completely blank (unheard of, even in the summer; there
are always people POP'ing in to check mail, etc), so
I telnetted in to find syslogd not running. No problem,
I su'd to root and fired it back up, and /var/log/messages
is growing accordingly.
But now I'm troubled. What would cause two more or less
reliable pieces of an oth
