Linux-Networking Digest #775, Volume #11 Sat, 3 Jul 99 23:13:49 EDT
Contents:
Re: IP Addressing Question ("David Means")
Re: Remote login problems in custom RedHat env... (Bryan)
Re: Question about firewall configuration ("David Means")
Re: PPP over Ethernet SW (Jonathan Guthrie)
Re: ppp rights ("Gregory D. Horne")
Re: Using mail via an NT Proxy ("Andrey Smirnov")
Only 1 SMB Server Allowed ("Casey Bralla")
Re: Anyone know how to post to linux.samba? (Frank Hahn)
Re: Remote Printing? (Frank Hahn)
Why are transceivers so expensive? (Christopher R. Barry)
Re: New information... (Jonathan Guthrie)
Re: zmodem with cu (Jonathan Guthrie)
SMB services stopped working. (Denning Langston)
Configuring Linux proxy (Grant Malcolm)
Help! Identd and mIRC for Win98 don't work together! (Marc Murphy)
----------------------------------------------------------------------------
From: "David Means" <[EMAIL PROTECTED]>
Subject: Re: IP Addressing Question
Date: 4 Jul 1999 01:23:40 GMT
One should draw a distinction between what "can be made to work", and what
is "best
practice". I believe that you could, with enough effort, make the scheme
you have outlined
function more or less the way I guess you want it to, but the mind boggles
at the
prospect of writing the masquerading ruleset to make it all go right.
The first problem that you might want to solve is the separation of boxes
into two groups:
those that need to be visible to the Internet (and therefore need real,
public IP addresses),
and those that are basically workstations or private servers. Machines in
the second class
can be assigned "private" IP addresses, per RFC 1597). Machines in the
first class will
need unique addresses; it is good practice to make each subnet
geographically contiguous,
so you may need to subnet that Class C block (198.175.182.x), and assign
part of it to
System A, and part to System B, or some such scheme.
Having worked this out, I recommend that you next deal with masquerading the
private
addresses onto (and back off of) the public network. Excellent sources for
this are
all over the 'Net; my favorite is http://members.home.net/ipmasq/
Once that configuration is working and stable, you may want to tighten down
the
security for the private machines (and take a look at the publicly-accesible
ones, too),
to avoid unpleasant intrusions.
Good luck with all this.
Drew M. Mooney <[EMAIL PROTECTED]> wrote in message
news:7ll91t$rbj$[EMAIL PROTECTED]...
> I'm in the process of interconnecting system lans between two customer
> locations, and have a concern over IP addressing with two of them.
>
> System A is basically a standalone LAN [actually a bunch of UNIX boxes
that
> support a wireless telecomm system] that we've connected to our customer's
> LAN by dual homing the gateway machine. "Remote" access used to be limited
> to dialup - now customer users can access all hosts via the dual-homed
> gateway.
>
> backbone network 198.175.182.0 [plain old class C]
>
> all A hosts use 198.175.182.2 as their default gateway
>
> the gateway host is dual-homed:
> 198.175.182.2 on eth0
> 172.22.0.141 on eth2 mask 255.255.255.240
> bcst 172.22.0.143
>
> the gateway host uses 172.22.0.129 [network 172.22.0.128's router] as its
> default route.
>
> Name service on 198.175.182.0 hosts is provided by /etc/hosts.
> We have not implemented DNS or any other service.
>
> DNS is used on the 172.22.0.128 [and associated subnets] net.
>
>
>
> System B [this is the possibly tricky part] is also what used to be a
> stand-alone LAN that we've connected to our customers network.
>
> Network architecture [number, type, and function of hosts] is an exact
> duplicate of network A. To simplify technical support from offsite, we
> typically use standardized host IP addresses when deploying these
networks.
> So network B is also on 198.175.182.0, AND host IPs on the network are
> duplicates of network A's functional equivalents.
>
> All network B hosts use 198.175.182.2 as default gateway.
>
> Gateway host is dual-homed:
> 198.175.182.2 on eth0
> 172.22.15.141 on eth2 mask 255.255.255.240
> bcst 172.22.15.143
>
> Gateway host B uses 172.22.15.129 as default route.
>
> Name service on the 198.175.182.0 hosts is /etc/hosts.
> DNS is used on 172.22.15.128 network [and associated subnets].
>
> Network 172.22.15.128's router connects to router in remote city [Network
> A's home] via 56k DDS.
>
>
> Questions:
>
> 1. Do we need to renumber one of the 198.175.182.0 networks to avoid
> confusion amongst the users [and routers] that live in the 172.22.0.0
> domains?
>
> Or....
> 2. Can we resolve potential confusion by merely assigning unique hostnames
> to NetworkA and NetworkB hosts, and let /etc/hosts and DNS sort it all out
> for themselves? [at present, the "standardization" between NetA and NetB
> applies to hostnames _and_ IP addresses]
>
>
> TIA to all respondents.
>
> -Drew
>
>
>
>
------------------------------
Date: Sat, 03 Jul 1999 20:45:10 +0000
From: Bryan <[EMAIL PROTECTED]>
Crossposted-To:
comp.os.linux.development.system,comp.os.linux.misc,comp.os.linux.security
Subject: Re: Remote login problems in custom RedHat env...
> DNS is disabled on this box. I've even gone as far as to remove the resolv.conf
> file.
That's what I meant. It can't do a reverse lookup (as mentioned in
another reply).
> Besides, tcpdump shows that the box is able to send acks to whatever
> remote machine is involved.
I would hope so. That's ethernet protocol. ;)
> Also remember that all established connections can
> reach any host via telnet, ftp, rlogin, etc... (as long as they're in the hosts
> table of course).
It may still be trying to perform reverse lookups. There is somewhere
where you tell it how to look up names on the network, and you can
configure the order (hosts, NIS, DNS, etc.) I'm assuming that's been
set to only use /etc/hosts...
> As for the network card, this problem has been replicated on
> three other identical systems to rule out just that.
You're saying you got the exact same problem on the other three
identical computers? Did they use the exact same brand of network card,
or different types? (Different NICs rules out driver problem; different
machines rules out bad NIC problem.) You might have a driver problem if
all NICs are identical. Try to replicate it in unidentical machines,
using the same NIC and drivers, or on identical machines with different
NICs.
> Network traffic is non-existent on this box. I've even prevented misc. services such
>> as sendmail from starting to make sure to no avail. Thanks for your responses
>though.
>
Then it should be easy to tail the logs and watch tcpdump
simultaneously, provided that the aforementioned NIC and driver tests
fail to prove anything.
> Wally
> [EMAIL PROTECTED]
>
-- Bryan Scott
-- CTR Online Systems Administration
> Bryan wrote:
>
> > Jon Skeet wrote:
> > >
> > > [EMAIL PROTECTED] wrote:
> > >
> > > > I have an unusual problem with telnet, rlogin, ftp and any other
> > > > program which requires logging in remotely. The system specs are: 400Mhz
> > > > Pentium Pro, 256MB RAM, onboard Intel etherexpress pro 10/100Mbs network
> > > > card, 2 serial ports, running a custom Red Hat 5.2 kernel. Four kernel
> > > > header files were modified to allow for a 3072 process limit ( fs.h,
> > > > limits.h, posix_types.h, /usr/include/gnu/types.h ). The machine will
> > > > boot and run fine for about 10 minutes then any form of remote log in
> > > > (even rcp and rsh) will hang after it successfully connects to the
> > > > system just before it gives you the opportunity to provide your login
> > > > name and/or password. On telnet you can even see the "Connected to
> > > > <host>" message. Any connection made before this problem occurs is fine
> > > > and has full capabilities. I can get out of the box using any method I
> > > > choose (telnet, ftp, etc). The oddest thing about this problem is that
> > > > all other inetd services are unaffected. They continue to respond to
> > > > request on their respective ports without fail. A tcpdump on the machine
> > > > will show telnet, rlogin, etc ... activity. They send their initial acks
> > > > and replies but don't complete their initialization procedures.
> > >
> > > Is it feasible that the problem is in reverse host lookup? I know telnetd
> > > checks that the host that is telnetting to it is valid before going ahead
> > > with the connection; it's possible that rcp does the same. If so,
> > > possibly your DNS is going wrong...
> > >
> >
> > I agree; it could be reverse DNS or no DNS at all.
> >
> > Another idea: Network card burps...
> >
> > How much activity is there once the system is up? I had a Netgear
> > 10/100 card in my box with one of the original DEC tulip chips (they've
> > since created their own proprietary set due to DEC's discontinuation of
> > the 21something series), and it would come up with some overrun problems
> > at high NFS loads. I finally swapped it with a newer one I had bought
> > for a Windows box, and the old card works fine in the Windows box, and
> > the new one works beautifully in the Linux box (gotta love 100Mbps).
> > (Probably some inconsistencies with the tulip driver and that older
> > chipset..)
> > .
> > Which kernel version are you using? You can use the 2.2.x kernel series
> > on Redhat 5.2. A custom RedHat 5.2 kernel sounds like you used th
> > 2.0.36 kernel that came with it.
> >
> > 2.2.5 runs really stable on three of my 5.2 machines. I'm suggesting a
> > kernel and network card driver upgrade because even if you turn off
> > networking, like you said you're doing, the card may still be on the
> > fritz, and there may be a compatibility issue with the EtherExpress
> > Pro. (Is that intel or 3com? 3com's drivers were semi-broken in
> > 2.0.36...)
> >
> > > --
> > > Jon Skeet - [EMAIL PROTECTED]
> > > http://www.pobox.com/~skeet/
> >
> > -- Bryan Scott
> > -- CTR Online Systems Administration
> > (remove the NOSPAM. for email)
------------------------------
From: "David Means" <[EMAIL PROTECTED]>
Subject: Re: Question about firewall configuration
Date: 4 Jul 1999 01:34:11 GMT
You surely DO want to have the default policy be deny
or else the rules are mostly ineffective. To permit all ICMP
messages (of which PING is one), the following two rules should be
included in whatever file you are using to set up your firewall rules:
/sbin/ipfwadm -I -a accept -P icmp
/sbin/ipfwadm -O -a accept -P icmp
Jaroslaw Kolacz <[EMAIL PROTECTED]> wrote in message
news:kPkf3.5299$[EMAIL PROTECTED]...
> Hello all!
>
> I am using a linux machine as a firewall. Everything is working ok with
one
> exception: I have some problems with ping.
>
> on any LAN computer (with Win98):
> - ping another LAN computer: OK
> - ping any host in internet: timeout
> - ping linux firewall: timeout
>
> on the linux computer:
> - ping another LAN computer: OK
> - ping any host in internet: OK
> - ping linux firewall or the loopback interface: "ping: sendto: Operation
> not permitted"
>
> After changing the default input and output policy from "deny" to "accept"
> everything is working OK but i want to use "deny" as default.
>
> What should i change to fix this problem? Can any linux expert give me an
> example how to configure the firewall with ipfwadm (only for the ICMP
> protocol)?
> I have already tried some configurations, but i was not able to correct
the
> problem.
>
> Thanx.
> Jarek
>
>
------------------------------
From: Jonathan Guthrie <[EMAIL PROTECTED]>
Crossposted-To: comp.protocols.ppp,comp.unix.bsd.freebsd.misc
Subject: Re: PPP over Ethernet SW
Date: 4 Jul 1999 01:00:11 GMT
In comp.os.linux.networking Pascal Gienger <[EMAIL PROTECTED]> wrote:
> Ethernet is a layer under IP. So PPP-over-Ethernet is _NOT_ PPP over IP.
> PPP is a container for point-to-point links with the possibility to carry
> some protocols in it (IP, IPX, ...).
> Ethernet also can carry multiple protocols.
> PPP_over_Ethernet seems to be there to convert a broadcast-possible-network
> into a real point-to-point-one.
The whole point behind PPPoE is to give an ISP control over their
Ethernet-connected downstream connections in a fashion similar to dialup
modems. People are looking for a way to make DSL (and similar
technologies) as easy to control as dialup connections are now.
You see, the information about a downstream account includes an expiration
date. With a PPP connection, each attempt to connect (usually) is
accompanied by an attempt to authenticate. If the user attempts to
connect after the account is expired, the authentication doesn't proceed
and the connection is dropped so the customer's access is removed until he
can make some arrangement with the ISP. That removal of access happens
automatically without need for the ISP to do anything.
If you have, say, a straight IP-over-DSL connection, there is never any
need to do an authentication and so there is no convenient point of
control. Instead, unless you do something like PPPoE, you have to
proactively change a router's configuration to disconnect a customer.
This is a lot higher burden on the provider than simply letting unpaid-for
accounts expire and reactivating those who want to continue buying
service.
Since a DSL connection is truly point-to-point, and since I've only seen
PPPoE talked about in connection with DSL, it is obvious to me that the
authentication/expiration issue is what truly drives any push to PPPoE,
not trying to restrict users to connecting one computer to the Ethernet at
the opposite end.
Of course, there are other things that you can use PPPoE for, I just
haven't seen anyone suggest that it be used for that. Perhaps this is
because I haven't been looking too hard.
--
Jonathan Guthrie ([EMAIL PROTECTED])
Brokersys +281-895-8101 http://www.brokersys.com/
12703 Veterans Memorial #106, Houston, TX 77014, USA
------------------------------
From: "Gregory D. Horne" <[EMAIL PROTECTED]>
Subject: Re: ppp rights
Date: Sat, 03 Jul 1999 19:41:43 -0400
Jeff German wrote:
> I am unable to allow a general user to stop or start the ppp daemon. I
> am running redhat 6.0. I used linuxconf to allow any user to activate or
> deactivate the interface. I get this message when a non-root user tries
> to stop ppp, "rm: cannot unlink `/var/run/ppp-ppp0.dev': Permission
> denied". What am I doing wrong? I want a regular user to telnet in and
> stop and start the pppd daemon.
>
> Thanks Jeff German
First, why would you want to allow a regular non-root user the ability to
start and stop the ppp daemon? This would introduce a severe security risk
to your Linux box and potentially to your entire network.
Second, what are the current permissions for the pppd?
Regards,
Gregory D. Horne
Information Technology Architect
Internetworking Engineer
The Network Laboratorium (NetLab)
------------------------------
From: "Andrey Smirnov" <[EMAIL PROTECTED]>
Subject: Re: Using mail via an NT Proxy
Date: Sat, 3 Jul 1999 18:40:41 -0700
You will need to configure your Linux station to be socks proxy client.
Check OnLine documentation on Proxy server.
Good luck!
Jim Ryan wrote in message ...
>I have NT Proxy server 2.0 running at home. I want to be able to send
>mail from a Linux client via the proxy to the Internet. I want to do
>this from a command line (mutt), not x. I also want to know if there is
>a way to set this up from the command line, in other words, without going
>into x. I know how to set the browser.
>--
>Thanks,
>Jim
>Please CC: by mail
------------------------------
From: "Casey Bralla" <[EMAIL PROTECTED]>
Subject: Only 1 SMB Server Allowed
Date: Sat, 03 Jul 1999 08:40:07 -0700 (PDT)
Reply-To: "Casey Bralla" <[EMAIL PROTECTED]>
I'm trying to run 2 SMB servers on my intranet (which also has a Win98
client). Both are accessable if I explicitly link to them. (ie: "NET
USE" commands work just fine), but neither apear on a browse list if
both of them are running. If only 1 is running, it appears just fine.
I've mucked around with the "domain master" & "local master"
parameters, to no avail. (I don't really understand them anyway.) Can
anybody offer a suggestion of where to continue my investigation?
------------------------------
From: [EMAIL PROTECTED] (Frank Hahn)
Subject: Re: Anyone know how to post to linux.samba?
Date: Sun, 04 Jul 1999 01:52:06 GMT
Reply-To: [EMAIL PROTECTED]
On Fri, 02 Jul 1999 18:24:22 GMT, Dale Walker <[EMAIL PROTECTED]> wrote:
>I'm trying to post a query to linux.samba but I don't have permission
>to send stuff. Does anyone know how to get permission for the
>newsgroup.
>
Are you positive that there is a linux.samba newsgroup? I
am not familiar with it.
--
Frank Hahn
If I had a plantation in Georgia and a home in Hell, I'd sell the
plantation and go home.
-- Eugene P. Gallagher
------------------------------
From: [EMAIL PROTECTED] (Frank Hahn)
Subject: Re: Remote Printing?
Date: Sun, 04 Jul 1999 01:52:12 GMT
Reply-To: [EMAIL PROTECTED]
On Sun, 25 Jul 1999 00:37:14 -0700, Ted Groans <[EMAIL PROTECTED]> wrote:
>Can anyone direct me to a good tutorial, or reference that describes
>printing to a remote printer using SMB?
>
Did you check the Samba source file archive? In the examples/printing
directory (or something close to that), there is a script and directions
in the file that explain quite a bit what you need to do.
I assume you want to print from the Linux side to a printer connected
to a Windows machine.
--
Frank Hahn
This sentence contradicts itself -- no actually it doesn't.
-- Hofstadter
------------------------------
Crossposted-To: comp.dcom.lans.ethernet
Subject: Why are transceivers so expensive?
From: [EMAIL PROTECTED] (Christopher R. Barry)
Date: Sun, 04 Jul 1999 02:19:28 GMT
I've got a Linux box and an old Symbolics Lisp Machine that uses a
transceiver to allow it to be connected to my two-node BNC mini-LAN
which is IP masqued to the net.
Occasionally, the connection between them just fails. Ping ceases to
work, and my graphical network traffic monitor shows zero activity.
But when I try to connect from one host to the other the transceiver
still blinks its lights as though things were working. Sometimes
things magically start working again but most of the time they
don't. It's really weird and frustrating.
The fact that things magically work sometimes but most of the time
don't make me think its a hardware problem. I thought I'd begin by
replacing the transceiver (which is really large and old looking) but
the cheapest one I can find is $50. Why are they so expensive, and
since the transceiver still lights up when I try to do things do any
of you know of a way to debug the connection at a lower-level (like
via hardware addresses or something...)?
Thanks,
Christopher
------------------------------
From: Jonathan Guthrie <[EMAIL PROTECTED]>
Subject: Re: New information...
Date: 4 Jul 1999 01:16:37 GMT
Daniel Mitchell <[EMAIL PROTECTED]> wrote:
> Okay, there's been a new development. Remember how I told you that I was
> having problems with adding +pap to my /options file? Well I got that to
> work alright but it made little difference. It did alter the pppd output so
> that now it reads:
> sent [LCP ConfReq id=0xi <auth pap> <magic ...> <pcomp> <accomp>]
> That <auth pap> term is what's new.
Well, +pap does mean that you want to authenticate using PAP and so it
would be reasonable to expect an LCP ConfReq to request PAP authentication
by including it in these message.
> After reading Unruh's guide at http://axion.physics.ubc.ca/ppp-linux.html
> (which I enjoyed for personal reasons: I too am studying physics) I am
> unsure what to make of the "all had bit 7 set to 0" error.
You know that a character has 8 bits, right? Well, if a serial line isn't
8-bits clean, then all characters will have their most significant bit
(bit 7) reset (set to 0). It's saying that it thinks the line is not
8-bit clean.
> According to Unruh, this means that I should be sending a username and
> password to my ISP by means of a command prompt in a terminal. However, as
> I previously stated, this is impossible because dialing into my ISP from a
> terminal, and this true for both Win98 dialup and Minicom, does not result
> in a command prompt. All I get is a flashing cursor.
> Unruh did mention that some ISPs require both a login and PAP, and I suppose
> that this could be the case. If it is, then is seems that I must first use
> PAP and *then* login because of the structure of the pppd output and the
> problem that I'm having with the terminal approach. Unfourtunately, I have
> no idea how to do this. : )
You can't authenticate using PAP and *then* login. These things don't
work that way. If hitting "enter" a few times in the terminal window
doesn't bring up a login prompt, then it would appear that this isn't a
case where you have to login and then authenticate using PAP. I'm not
sure how to tell you to proceed. My initial reaction is to tell you to
make sure that the serial port is opened with the parameters of 8-N-1, but
I don't think there is any way for pppd to open a serial port.
Perhaps something is changing the DTE-DCE (Data Terminal Equipment-Data
Communications Equipment or computer-to-modem) data rate and so the other
end isn't recognizing the characters that are coming across as being from
PPP packets. The fact that (from what I remember of one of your previous
posts) the other end seems to not send anything to you argues against
going straight into PPP. Are you sure you got the right phone number?
Oh, and some nice person sent me email saying that 99.999% of all Internet
connections require authentications using CHAP rather than PAP. While I
doubt that the percentage is that high, it is possible that you could need
to set up CHAP. However, you would get responses from the server
indicating that it doesn't do PAP (ConfReq NAK's) rather than nothing.
--
Jonathan Guthrie ([EMAIL PROTECTED])
Brokersys +281-895-8101 http://www.brokersys.com/
12703 Veterans Memorial #106, Houston, TX 77014, USA
------------------------------
From: Jonathan Guthrie <[EMAIL PROTECTED]>
Subject: Re: zmodem with cu
Date: 4 Jul 1999 01:34:05 GMT
Gene Heskett <[EMAIL PROTECTED]> wrote:
> Gene Heskett sends Greetings to Jonathan Guthrie;
>> With that said, rz/sz really doesn't help that fellow much.
>> Instead, he needs the lrzsz package and the man pages therein.
>> Further, he has to figure out how to run programs locally with
>> cu. (I've not used cu in years.)
> Well, I must confess that my last contact with it, other than useing it
> against the seriously broken versions we have on the amiga over a null
> modem cable, (busted perms handling anybody?) was compiling it for os9
> level 2 on a trs-80 color computer 3, where it ran at about 380 cps due
> to the character oriented nature, and its call to the crc routine for
> every character handled.
I first used rzsz to do transfers to and from the Vax at Iowa State more
than ten years ago. (I could get Kermit to almost work, but it wasn't
worth the effort.) It's been years, but I still remember how smoothly it
went. I never used a Coco-3, but my old Coco-1 could barely handle ANY
serial communications over 120 CPS under OS-9. (The C library was broken
so I couldn't write an OS-9 terminal emulator in C. I tried rebuilding
it, but I couldn't get that to work. Eventually, I gave up.)
Were you using a table-driven CRC generator or a bitwise CRC generator? A
table-driven CRC generator (check out the ones at
http://www.snippets.org/) can calculate CRCs about an order-of-magnitude
faster than bitwise CRC's, but at the cost of 512 bytes of RAM for CRC-16
and 1024 bytes of RAM for CRC-32. There is also a "bytewise" CRC
calculation that does one XOR for each set bit in the polynomial (rather
than 8 per character) and so, for CRC-16 is faster than bitwise but which
doesn't need the storage for the table. (There are more than 7 bits set
in the CRC-32 polynomial so that technique doesn't get you anything for
CRC-32.)
> Yeah, well, time does march on, and I can be safely ignored in most
> cases. But, I do like to comment on those parts where "I've been there,
> and done that". Can I plead Old Fart Syndrome? :-)
If you want. However, you should realize that I wasn't trying to do
anything but point out that the issue is more one of integration with cu
than with getting a zmodem program for Linux.
--
Jonathan Guthrie ([EMAIL PROTECTED])
Brokersys +281-895-8101 http://www.brokersys.com/
12703 Veterans Memorial #106, Houston, TX 77014, USA
------------------------------
From: Denning Langston <[EMAIL PROTECTED]>
Subject: SMB services stopped working.
Date: Sat, 03 Jul 1999 19:40:21 -0700
OK. I upgraded from RH 5.1 to 6.0.
I had everything working well in 5.1, including samba.
Now
/etc/rc.d/init.d/smb stop
Shows that SMB has failed and
ps * | grep mbd
Shows only that nmbd is running. I have been trying to get smb
services back up but am having no luck. I know that the answer is
here somewhere, but I have been trying too hard for too long to see
the answer anymore.
A samba guru would be a great person to run across right about now.
HELP!!
------------------------------
From: Grant Malcolm <[EMAIL PROTECTED]>
Subject: Configuring Linux proxy
Date: Sun, 04 Jul 1999 10:36:24 +0800
A bunch of Win95 stations networked to an NT server connected to the
'net via a Linux proxy dialing in to a local ISP - all set up and
running fine.
However, only web browsing and email access available from the
workstations :(
No ICQ or other access.
The guru who put the network together is unavailable. Where do i start
looking? Can someone point me to the right how.to or manual?
Cheers
Grant
------------------------------
From: Marc Murphy <[EMAIL PROTECTED]>
Subject: Help! Identd and mIRC for Win98 don't work together!
Date: Sun, 04 Jul 1999 02:38:33 GMT
I have RedHat 6.0. I am using IP masquerading as described in the HOWTO
at
www.linuxberg.com.
My Linux box is allowing a Win98 machine to connect to the Net, and it
works
well except the Identd requests when trying to use mIRC keep failing. I
can
use XChat fine on the Linux box.
How do I make Identd usable for the Win98 programs?
Please e-mail me and point me in the right direction!
------------------------------
** 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
******************************
