Linux-Networking Digest #79, Volume #10 Mon, 1 Feb 99 16:13:34 EST
Contents:
Still Trying-PPP (George Lampke)
Re: 2 Linux machines 2 nics and a hub and something is wrong? (Michael Wilson)
Re: Sendmail as a gateway (Raymond Doetjes)
Re: Ping OK, can't FTP/Telnet/Samba (David Kirkpatrick)
Re: Romote "root" login ([EMAIL PROTECTED])
Re: Is Linux right for me? ("Michael Schmeing")
----------------------------------------------------------------------------
From: George Lampke <[EMAIL PROTECTED]>
Subject: Still Trying-PPP
Date: Mon, 01 Feb 1999 12:47:32 -0700
I am still trying to connect Redhat 5.2 to my ISP! Had several
suggestions from both the newgroup and others, but none have worked. I
have included the following: dmesg and /var/log/messages output, ppp-on
and ppp-on-dialer files. I also tried using the pap-secrets file with my
login, password, and domain-name, but with no success, either!
The modem dials output and accepts my responses to 'host', 'login' and
'password' then connects and then get "Serial line is looped back"!!
DMSEG output
Memory: sized by int13 088h
Console: 16 point font, 400 scans
Console: colour VGA+ 80x25, 1 virtual console (max 63)
pcibios_init : BIOS32 Service Directory structure at 0x000fad30
pcibios_init : BIOS32 Service Directory entry at 0xfb1b0
pcibios_init : PCI BIOS revision 2.10 entry at 0xfb1e0
Probing PCI hardware.
Calibrating delay loop.. ok - 599.65 BogoMIPS
Memory: 30824k/32768k available (748k kernel code, 384k reserved, 812k
data)
Swansea University Computer Society NET3.035 for Linux 2.0
NET3: Unix domain sockets 0.13 for Linux NET3.035.
Swansea University Computer Society TCP/IP for NET3.034
IP Protocols: IGMP, ICMP, UDP, TCP
Linux IP multicast router 0.07.
VFS: Diskquotas version dquot_5.6.0 initialized
Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
Checking 'hlt' instruction... Ok.
Linux version 2.0.36 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #1
Tue Oct 13 22:17:11 EDT 1998
Starting kswapd v 1.4.2.2
Serial driver version 4.13 with no serial options enabled
tty00 at 0x03f8 (irq = 4) is a 16550A
Real Time Clock Driver v1.09
Ramdisk driver initialized : 16 ramdisks of 4096K size
hda: Maxtor 7850 AV, 814MB w/64kB Cache, CHS=827/32/63
hdb: Maxtor 85400D5, 5150MB w/256kB Cache, CHS=656/255/63
hdd: WPI CDS-24X, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
Floppy drive(s): fd0 is 1.44M, fd1 is 1.2M
FDC 0 is a post-1991 82077
md driver 0.36.3 MAX_MD_DEV=4, MAX_REAL=8
scsi : 0 hosts.
scsi : detected total.
Partition check:
hda: hda1
hdb: hdb1 hdb2 < hdb5 hdb6 hdb7 >
VFS: Mounted root (ext2 filesystem) readonly.
Adding Swap: 40124k swap-space (priority -1)
sysctl: ip forwarding off
Swansea University Computer Society IPX 0.34 for NET3.035
IPX Portions Copyright (c) 1995 Caldera, Inc.
Appletalk 0.17 for Linux NET3.035
/var/log/messages output
Jan 30 15:13:30 localhost kernel: CSLIP: code copyright 1989 Regents of
the University of California
Jan 30 15:13:30 localhost kernel: PPP: version 2.2.0 (dynamic channel
allocation)
Jan 30 15:13:30 localhost kernel: PPP Dynamic channel allocation code
copyright 1995 Caldera, Inc.
Jan 30 15:13:30 localhost kernel: PPP line discipline registered.
Jan 30 15:13:30 localhost kernel: registered device ppp0
Jan 30 15:13:30 localhost pppd[357]: pppd 2.3.5 started by root, uid 0
Jan 30 15:13:31 localhost chat[358]: timeout set to 3 seconds
Jan 30 15:13:31 localhost chat[358]: abort on (\nBUSY\r)
Jan 30 15:13:31 localhost chat[358]: abort on (\nNO ANSWER\r)
Jan 30 15:13:31 localhost chat[358]: abort on
(\nRINGING\r\n\r\nRINGING\r)
Jan 30 15:13:31 localhost chat[358]: send (rAT^M)
Jan 30 15:13:31 localhost chat[358]: expect (OK)
Jan 30 15:13:31 localhost chat[358]: rAT^M^M
Jan 30 15:13:31 localhost chat[358]: OK
Jan 30 15:13:31 localhost chat[358]: -- got it
Jan 30 15:13:31 localhost chat[358]: send (ATH0^M)
Jan 30 15:13:31 localhost chat[358]: timeout set to 30 seconds
Jan 30 15:13:31 localhost chat[358]: expect (OK)
Jan 30 15:13:31 localhost chat[358]: ^M
Jan 30 15:13:31 localhost chat[358]: ATH0^M^M
Jan 30 15:13:31 localhost chat[358]: OK
Jan 30 15:13:31 localhost chat[358]: -- got it
Jan 30 15:13:31 localhost chat[358]: send (ATDT416-0801^M)
Jan 30 15:13:32 localhost chat[358]: expect (CONNECT)
Jan 30 15:13:32 localhost chat[358]: ^M
Jan 30 15:13:50 localhost chat[358]: ATDT416-0801^M^M
Jan 30 15:13:50 localhost chat[358]: CARRIER 24000^M
Jan 30 15:13:51 localhost chat[358]: ^M
Jan 30 15:13:51 localhost chat[358]: PROTOCOL: LAP-M^M
Jan 30 15:13:51 localhost chat[358]: ^M
Jan 30 15:13:51 localhost chat[358]: COMPRESSION: V.42BIS^M
Jan 30 15:13:51 localhost chat[358]: ^M
Jan 30 15:13:51 localhost chat[358]: CONNECT
Jan 30 15:13:51 localhost chat[358]: -- got it
Jan 30 15:13:51 localhost chat[358]: send (^M)
Jan 30 15:13:51 localhost chat[358]: timeout set to 30 seconds
Jan 30 15:13:51 localhost chat[358]: expect (host:)
Jan 30 15:13:51 localhost chat[358]: 38400/ARQ^M
Jan 30 15:13:53 localhost chat[358]: You have reached Verinet
Communication's Internet Connection!^M
Jan 30 15:13:53 localhost chat[358]: ^M
Jan 30 15:13:53 localhost chat[358]: Customer support can be reached at
[EMAIL PROTECTED] or by calling (970) 416-9
Jan 30 15:13:53 localhost chat[358]: 152^M
Jan 30 15:13:53 localhost chat[358]: At the host prompt type 'shell' for
a Unix shell or 'ppp' for a ppp connection.^M
Jan 30 15:13:53 localhost chat[358]:
Jan 30 15:13:53 localhost chat[358]: ^M
Jan 30 15:13:53 localhost chat[358]: ^M
Jan 30 15:13:53 localhost chat[358]: host:
Jan 30 15:13:53 localhost chat[358]: -- got it
Jan 30 15:13:53 localhost chat[358]: send (ppp^M)
Jan 30 15:13:53 localhost chat[358]: timeout set to 5 seconds
Jan 30 15:13:53 localhost chat[358]: expect (ogin:)
Jan 30 15:13:53 localhost chat[358]: ppp^M
Jan 30 15:13:53 localhost chat[358]: login:
Jan 30 15:13:53 localhost chat[358]: -- got it
Jan 30 15:13:53 localhost chat[358]: send (glampke^M)
Jan 30 15:13:53 localhost chat[358]: timeout set to 5 seconds
Jan 30 15:13:53 localhost chat[358]: expect (assword:)
Jan 30 15:13:53 localhost chat[358]: glampke^M
Jan 30 15:13:53 localhost chat[358]: Password:
Jan 30 15:13:53 localhost chat[358]: -- got it
Jan 30 15:13:53 localhost chat[358]: send (******^M)
Jan 30 15:13:54 localhost pppd[357]: Serial connection established.
Jan 30 15:13:55 localhost pppd[357]: Using interface ppp0
Jan 30 15:13:55 localhost pppd[357]: Connect: ppp0 <--> /dev/cua2
Jan 30 15:13:58 localhost pppd[357]: Serial line is looped back.
Jan 30 15:13:58 localhost pppd[357]: Connection terminated.
Jan 30 15:13:59 localhost pppd[357]: Exit.
Jan 30 15:15:30 localhost kernel: PPP: ppp line discipline successfully
unregistered
ppp-on
#!/bin/sh
#
# Script to initiate a ppp connection. This is the first part of the
# pair of scripts. This is not a secure pair of scripts as the codes
# are visible with the 'ps' command. However, it is simple.
#
# These are the parameters. Change as needed.
TELEPHONE=416-0801 # The telephone number for the connection
ACCOUNT=glampke # The account name for logon
PASSWORD=****** # The password for this account
LOCAL_IP=0.0.0.0 # Local IP address if known. Dynamic = 0.0.0.0
REMOTE_IP=0.0.0.0 # Remote IP address if desired. Normally 0.0.0.0
NETMASK=255.255.255.0 # The proper netmask if needed
HOST=ppp # Enter the type of protocol
#
# Export them so that they will be available at 'ppp-on-dialer' time.
export TELEPHONE ACCOUNT PASSWORD HOST
#
# This is the location of the script which dials the phone and logs
# in. Please use the absolute file name as the $PATH variable is not
# used on the connect option. (To do so on a 'root' account would be
# a security hole so don't ask.)
#
DIALER_SCRIPT=/etc/ppp/ppp-on-dialer
#
# Initiate the connection
#
# I put most of the common options on this command. Please, don't
# forget the 'lock' option or some programs such as mgetty will not
# work. The asyncmap and escape will permit the PPP link to work with
# a telnet or rlogin connection. You are welcome to make any changes
# as desired. Don't use the 'defaultroute' option if you currently
# have a default route to an ethernet gateway.
#
exec /usr/sbin/pppd debug lock modem crtscts /dev/cua2 38400 \
asyncmap 20A0000 kdebug 2 $LOCAL_IP:$REMOTE_IP \
noipdefault netmask $NETMASK defaultroute connect $DIALER_SCRIPT
ppp-on-dialer
#!/bin/sh
#
# This is part 2 of the ppp-on script. It will perform the connection
# protocol for the desired connection.
#
exec chat -v \
TIMEOUT 3 \
ABORT '\nBUSY\r' \
ABORT '\nNO ANSWER\r' \
ABORT '\nRINGING\r\n\r\nRINGING\r' \
'' \rAT \
'OK-+++\c-OK' ATH0 \
TIMEOUT 30 \
OK ATDT$TELEPHONE \
CONNECT '' \
TIMEOUT 30 \
host: $HOST \
TIMEOUT 5 \
ogin: $ACCOUNT \
TIMEOUT 5 \
assword: $PASSWORD
------------------------------
From: Michael Wilson <[EMAIL PROTECTED]>
Subject: Re: 2 Linux machines 2 nics and a hub and something is wrong?
Date: Mon, 1 Feb 1999 16:59:04 +0000
On Sun, 24 Jan 1999, Darren Ford wrote:
>Folks, I am about to go crazy here with problems. I have two machines
>both running Red Hat 5.0. Both have NICs and are recognized during the
>boot process. I reinstalled Red Hat on both machines to get a fresh
>start. During the install I chose to set up networking for each
>machine.
>I want machine one(M1) to be able to connect to a cable modem later on
>so I want it as a gateway.
>
>M1(linux1.blank.net) M2(linux2.blank.net)
>IP = 192.168.9.1 IP = 192.168.9.2
>netmask = 255.255.255.0 netmask = 255.255.255.0
>gateway = 192.168.9.1 gateway = 192.168.9.1
>domain = blank.net domain = blank.net
>
>These machines are both connected to hub. I cannot ping one machine
>from the other but they can ping themselves and their dummy interface.
>
>If I want M1 to be a gateway later on, setting the gateway IP to
>192.168.9.1 is correct right?
>
>Why can't these guys ping each other? I tried adding each of them to
>the others routing table but that didn't work or I didn't do it right.
>When I do a 'route -n' it shows that the entry is there.
>
>Can somebody tell me what I'm doing wrong?
I had this problem a while ago whilst experimenting with IP Masquerading using
a Win98 box into a Linux Box connected to the net, the solution was quite
simple, The NIC that I had in the Linux Box was a clone NE2000 PCI card which
in all fairness initialised on bootup but failed to establish any networking
protocols whilst trying to ping the other machine and vice versa. I would go
to the lengths if you are using a PCI NIC that maybe a change to ISA may solve
the problem. As far as your setup goes with linking two machines to the
Internet via one box, I would suggest a look at the doc entitiled
IP-Masquerade, the setup facility in it worked for me. If you haven't got it,
I can forward it to you no bother.
Regards, Michael
------------------------------
From: Raymond Doetjes <[EMAIL PROTECTED]>
Subject: Re: Sendmail as a gateway
Date: Mon, 01 Feb 1999 20:22:01 +0100
Sendmail will always hold mail, when it is ment for him.
With a sendmail -q @yourdomain.com it wil flush the queue and send the
mail cashed to wich ever server it needs to be. (DO think about your MX
records).
You might also want to buy the book Sendmail from O'reilly. I find it a
very good bible. Unfortuatly I don't have it here, otherwise I would
have been more precise. But I know that the syntax up there is correct.
Raymond Doetjes
------------------------------
From: David Kirkpatrick <[EMAIL PROTECTED]>
Subject: Re: Ping OK, can't FTP/Telnet/Samba
Date: Mon, 01 Feb 1999 10:20:03 +0000
Reply-To: [EMAIL PROTECTED]
What is the result of nbtstat -n on windows and does it match
the domain on linux?
Are you using a non root login to login to Linux or are you
getting that far? When you say you can't telnet or ftp what
error messages are you getting?
Why is workgroup=HOUSEHOLD rather than bogusdomain? What are
the complete names in lmhosts? Is your passwd file setup - man
smbpasswd?
It would be good to see the result of trying to map tmp on
penguin from daddys.
d
jim wrote:
>
> OK, this is driving this newbie nuts.
>
> I fiddled with Linux for a week and got my home network running great. It
> has two Win95 box's and Linux on a 486. Everything worked - FTP,Telnet; I
> could even browse the across the Network Neighborhood using Samba (both Win
> 95 to Linux, and Linux to Win95).
>
> Then one of the Win95's had a NIC which was a little flaky... It'd crash
> the computer once or twice a day. So I replaced it with a different one -
> and everything went to h*ck.
>
> I think the new card is OK. The two Win95 boxes cooperate fully across
> the Network Neighborhood; and I can play Doom 95 using TCP/IP between them.
>
> I can still ping all around (by IP numbers and by names). But I can't FTP
> or Telnet into the Linux Box. (The Linux Box can FTP and Telnet itself).
>
> The Linux box shows up in the Win95 Network Neighborhood, but when I try
> to browse it I get a 'server not available' message.
>
> None of the config files have changed since the time it worked with the
> old NIC. Since this network is so small and unlikely to change, I was doing
> all my name resolving with the hosts & lmhosts files. (i.e., no DNS or
> WINS). As I said, this worked once... And it still works for Ping.
>
> My hosts file (for all three computers... the Linux box is named penguin):
> #------------- Cut Here ----------------------------------------
> 127.0.0.1 localhost
> 192.168.1.1 penguin
> 192.168.1.2 daddys
> 192.168.1.3 mommys
> #------------- Cut Here ----------------------------------------
>
> My lmhosts file (for all three computers):
> #------------- Cut Here ----------------------------------------
> 192.168.1.1 penguin
> 192.168.1.2 daddys
> 192.168.1.3 mommys
> 192.168.1.1 penguin.bogusdomain.bogus
> 192.168.1.2 daddys.bogusdomain.bogus
> 192.168.1.3 mommys.bogusdomain.bogus
> #------------- Cut Here ----------------------------------------
>
> My smb.conf file:
> #------------- Cut Here ----------------------------------------
> #======================= Global Settings
> =====================================
> [global]
>
> # workgroup = NT-Domain-Name or Workgroup-Name
> workgroup = HOUSEHOLD
>
> # server string is the equivalent of the NT Description field
> server string = Samba Jan 14 16:30
>
> # Cause this host to announce itself to local subnets here
> remote announce = 192.168.1.255
>
> #============================ Share Definitions
> ==============================
> [homes]
> comment = Home Directories
> browseable = no
> writable = yes
>
> # This one is useful for people to share files
> [tmp]
> comment = Temporary file space
> path = /tmp
> read only = no
> public = yes
> #------------- Cut Here ----------------------------------------
>
> Somewhere I got a procedure to diagnose Samba problems (OK, it was
> http://us2.samba.org/samba/docs/DIAGNOSIS.html ). The results of the
> ten-step tests:
>
> Test 1. testparm smb.conf -- Seems OK.
>
> Test 2. 'ping penguin' and 'ping daddys' -- As I said, OK.
>
> Test 3. 'smbclient -L penguin' -- Gives the following results:
>
> #------------- Cut Here ----------------------------------------
> Added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0
> Server time is Sun Jan 31 17:48:48 1999
> Timezone is UTC-8.0
> Domain=[HOUSEHOLD] OS=[Unix] Server=[Samba 1.9.18p10]
> security=share
>
> Server=[PENGUIN] User=[root] Workgroup=[HOUSEHOLD] Domain=[HOUSEHOLD]
>
> Sharename Type Comment
> --------- ---- -------
> IPC$ IPC IPC Service (Samba Jan 14 16:30)
> root Disk Home Directories
> tmp Disk Temporary file space
>
> This machine has a browse list:
>
> Server Comment
> --------- -------
> DADDYS Daddy's Dell XPS233
> PENGUIN Samba Jan 14 16:30
>
> This machine has a workgroup list:
>
> Workgroup Master
> --------- -------
> HOUSEHOLD DADDYS
> #------------- Cut Here ----------------------------------------
>
> This all seems great. The Dell XPS233 comment had to have come across the
> net. (Mommy's computer was off when these diagnostics were run.) The
> 'HOUSEHOLD" workgroup is correct, and is set on all three computers.
>
> Test 4. 'nmblookup -B penguin __SAMBA__' -- gives good results:
> #------------- Cut Here ----------------------------------------
> Sending queries to 192.168.1.1
> 192.168.1.1 __SAMBA__<00>
> #------------- Cut Here ----------------------------------------
>
> Test 5. 'nmblookup -B daddys' -- Also seems good:
> #------------- Cut Here ----------------------------------------
> Sending queries to 192.168.1.2
> 192.168.1.2 *<00>
> #------------- Cut Here ----------------------------------------
>
> Test 6. 'nmblookup -d 2 '*' ' -- Still good...
> #------------- Cut Here ----------------------------------------
> Added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0
> Sending queries to 192.168.1.255
> Got a positive name query response from 192.168.1.2 ( 192.168.1.2 )
> Got a positive name query response from 192.168.1.1 ( 192.168.1.1 )
> 192.168.1.2 *<00>
> 192.168.1.1 *<00>
> #------------- Cut Here ----------------------------------------
>
> Test 7. 'smbclient \\\\penguin\\tmp' -- No problems yet.
> #------------- Cut Here ----------------------------------------
> Added interface ip=192.168.1.1 bcast=192.168.1.255 nmask=255.255.255.0
> Server time is Sun Jan 31 17:59:35 1999
> Timezone is UTC-8.0
> Domain=[HOUSEHOLD] OS=[Unix] Server=[Samba 1.9.18p10]
> security=share
> smb: \>
> #------------- Cut Here ----------------------------------------
>
> That was the last test that worked. Test 8 failed, which I'll cover in a
> moment. First, I ran what I'll call Test 7.5 on the Win95 box:
>
> Test 7.5. 'net view' -- gives:
> #------------- Cut Here ----------------------------------------
> Servers available in workgroup HOUSEHOLD.
> Server name Remark
> ----------------------------------------------------------------------------
> -----------------
> \\DADDYS Daddy's Dell XPS233
> \\PENGUIN Samba Jan 14 16:30
> The command was completed successfully.
> #------------- Cut Here ----------------------------------------
>
> Again, the "Samba Jan 14 16:30" came across the net from my smb.conf file.
> Now test 8:
>
> Test 8. 'net view \\PENGUIN' -- gives:
> #------------- Cut Here ----------------------------------------
> Error 53: The computer name specified in the network path cannot be located.
> Make sure you are specifying the computer name correctly, or try again later
> when the remote computer is available.
> #------------- Cut Here ----------------------------------------
>
> That's all for now. Sorry this was so long.
> -Jim
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.os.linux,comp.os.linux.admin,comp.os.linux.help,nl.comp.os.linux
Subject: Re: Romote "root" login
Date: 1 Feb 1999 18:36:49 -0000
Reply-To: [EMAIL PROTECTED]
In nl.comp.os.linux pazuzu <[EMAIL PROTECTED]> wrote:
> I'm sorry, and I'm a bit new at this. Why is it more a security problem
> that people from outside can directly login as root (password guessing?)
> then people login in as guest and do a su -?
for instance -- it requires two sets of 'user/password' combinations to get
su to work. e.g. before you can even do 'su' you'll have to be logged in.
/etc/sudoers controls which user may use su IIRC, so that means that you can
effecively make another wall you'll have to overcome before you even become
root.
--
Grobbebol's Home | Don't give in to spammers. -o)
http://www.xs4all.nl/~bengel | Use your real e-mail address /\
Linux 2.0.36 on an i586/64 MB | on Usenet. _\_v
------------------------------
From: "Michael Schmeing" <[EMAIL PROTECTED]>
Subject: Re: Is Linux right for me?
Date: 01 Feb 1999 12:42:13 +0100
"Eric O'Strander" <[EMAIL PROTECTED]> writes:
> I have a dedicated 486 DX/120 32MB ram and 2 HDD (1 @ 420mb & 1 @ 2.1Gig).
> I just got a cable modem installed this week and want to try to set up a
> Proxy server to share the connection with my other workstations. Is there
> support in Linux to run a proxy service?
Linux is capable of doing so. I run my workstation (a bit newer: AMD
K6-2 350) with Linux, giving the other guy living in my appartement
Internet access by using my computer as a masquerading host. This way
the Internet sees only my computer and any traffic generated by the
other computer(s) is masqued to appear to come from me (that's where
the name comes from). Returning packages are inspected and send to the
other computer if necessary. This is probably what you want to do too.
In addition to this I have WWWOffle running, a http-proxy that is
designed for a dial-up connection: when my computer is not connected
to the Internet it serves only those sites cached locally and
remembers all requests for sites not yet cached. These sites are
fetched the next time I go online. When I am online every request is
passed through to the net and the results are stored locally for
future (offline) requests.
If You have a static connection to the Internet there are other
proxy-servers that are designed for that purpose. I know of two: one
called squid and one that is integrated in the apache httpd. As I do
not have a static connection I don't know how they work (neither how
to operate them nor whether they are stable). I think that if You have
a static connection You might want to set up a http server on Your
computer so I guess that the proxy in apache is a good choice.
> Any tips on pulling this off would
> be very helpful. Not knowing anything about Linux I'm hoping this is a good
> solution for my old machine to come back to service.
As You are new to Linux I would suggest You by a recent
Linux-distribution and some good books about it (the books might not
be necessary if You are already familiar with other UNIX-like OS). I
use the SuSE-Linux 6.0 and it comes with quite a good book too (at
least the german version, I don't know about the english one). I think
the book even describes the basics of masquerading and firewalling (a
way to protect a local network from the Internet, masquerading is a
part of it).
If You need further help, I can give it. As I am currently writing on
my master-thesis (in computer science) I do not have much time left and
so decided to waste time searching some information that You might not
use. If You can give some problem (with a good description of Your
environment: kernel-version, distribution, etc, if possible) send me
an e-mail and I will try to help You.
CU,
Michael
--
Michael Schmeing, Artillerieweg 46, D-26129 Oldenburg
e-mail: [EMAIL PROTECTED]
www: http://www.Informatik.Uni-Oldenburg.DE/~michae2
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list (and comp.os.linux.networking) via:
Internet: [EMAIL PROTECTED]
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Networking Digest
******************************
