Linux-Networking Digest #473, Volume #12 Sat, 4 Sep 99 16:13:37 EDT
Contents:
Re: Ethernet to Token-Ring Bridge (Jeff Sumner)
Re: Help.... Selectively disaling Masq (Bernd Eckenfels)
Re: Ethernet to Token-Ring Bridge (Jeff Sumner)
Intermittent No Route to Host (J Nickson)
Re: ipchains & ftp (The Dude)
Re: ipmasq and dial on demand, RedHat 6.0 (Stefan Ekman)
Re: NIC probs ([EMAIL PROTECTED])
Re: Automating redial (Frank Hahn)
SneakerNet woes... (Laughters_domain)
IP Forwarding Feedback and Help Needed ([EMAIL PROTECTED])
Re: PPP over Ethernet? (Tom Eastep)
----------------------------------------------------------------------------
From: Jeff Sumner <[EMAIL PROTECTED]>
Subject: Re: Ethernet to Token-Ring Bridge
Date: Sat, 04 Sep 1999 19:19:01 +0000
If you find someone that has done a translating bridge, please let me
know too! THAT would be useful- it would be nice to get rid of the
ancient 8209/8229's we have a work...
JD
[EMAIL PROTECTED] wrote:
> Is there anyone in the Linux Community that has
> successfully setup a Ethernet to Token-Ring
> Bridge? If so could you please steer me in the
> right direction.
>
> ri
>
> Sent via Deja.com http://www.deja.com/
> Share what you know. Learn what you don't.
--
Friends don't let friends use Windows
Amigos nao permite seu amigos usar Janelas!
------------------------------
From: Bernd Eckenfels <[EMAIL PROTECTED]>
Subject: Re: Help.... Selectively disaling Masq
Date: 4 Sep 1999 19:22:42 GMT
Chris Anderson <[EMAIL PROTECTED]> wrote:
> 192.168.192.x but NOT 192.168.88.0/24. I can ping 192.168.88.250
> of course. Proxy ARP is enabled on both ppp.options files, and
> diff only shows the host names as being different.
Have you checked that proxy arp works? you should run a tcpdump on a host in
the 192.168.88.x subnet, to see if the packets from your ppp host are
arriving, and if the answer arp requests are answered by the ppp host. Of
course you can set up an manual proxy arp entry on your ppp server.
Greetings
Bernd
------------------------------
From: Jeff Sumner <[EMAIL PROTECTED]>
Subject: Re: Ethernet to Token-Ring Bridge
Date: Sat, 04 Sep 1999 19:24:08 +0000
Don't forget RIF's, the routing information fields that T-R has, babynet
doesn't...
The packet size issue is dealt with by everyone I can think of that does
translational bridging quite simply dropping any packet that is over ethernet
size (though it is nice seeing 18k packets on a network sniffer). IPX doesn't
like to cross the more primitive older bridges either as the bit's don't get
cannonalized in both the MAC header and the IPX header...
JD
[EMAIL PROTECTED] wrote:
> On Fri, 02 Jul 1999 21:34:02 GMT, Bill Pitz <[EMAIL PROTECTED]> wrote:
> >>[EMAIL PROTECTED] gave us the interesting posting of:
> >> Is there anyone in the Linux Community that has
> >> successfully setup a Ethernet to Token-Ring
> >> Bridge? If so could you please steer me in the
> >> right direction.
> >
> >That would work the same as any other bridge. Check the Bridge and
> >Bridge+Firewall HOWTOs at the Linux Documentation Project...
> >There are also some other resources available at www.linux.org
>
> There are LOTS of things different about Ethernet and Token Ring - it is
> not just the physical and electrical side of life. If you really need to
> bridge those two together then look at Cisco and the translational
> bridging that you can do - even then it is of only limited use.
>
> Do what the other guy says and use a router to communciate - lots easier.
>
> Ethernet has lots of fram formats :
>
> Ethernet II
> 802.3 (using 802.2 encaps)
> SNAP
> Novell IPX RAW or 802.3 RAW
>
> Packet size is th next fun bit - Ethernet around 1599 bytes, Token ring has
> much larger depending on ring speed !
>
> Then you also have the problem of the MAC address being arse about face (back
> to front for non aussies).
>
> You can do it ......
>
> >
> >Basically, you need an ethernet board and a token ring board. Run
> >the bridging configuration tool, or just setup the two networks on
> >different machines. Either way would work.
> >
> >Linux views the network devices all the same when it's routing/forwarding/
> >bridging so you could bridge lots of things... (ethernet, ppp, hdlc,
> >token ring, etc..)
> >
> >-Bill
> >--
> >Bill Pitz [EMAIL PROTECTED]
> >Silicon Valley North, Inc. www.svn.net
> >Internet and World Wide Web Services (707) 781-9999
> >
>
> --------------
--
Friends don't let friends use Windows
Amigos nao permite seu amigos usar Janelas!
------------------------------
Date: Sat, 04 Sep 1999 15:34:44 -0400
From: J Nickson <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Intermittent No Route to Host
Dialing out to my ISP Netscape 3.04 give this about 80% of the time.
Config: Vanilla.....
RH 6.0 e-commerce
Pentium II 233 64M Ram, 18G disk
Zoom V.34
Ping can get to my ISP, sover.net, and the DNS, 209.198.87.40, but not
to netscape.com.
I've checked the DSN a hundred times (I could still be wrong) and since
I did get through to itsamac.com (boulder) once (of five tries) I think
it is something else. Ping resolves name to IP addresses anyway, just
never gets a returned packet.
Thanks
J Nickson [EMAIL PROTECTED]
------------------------------
From: The Dude <[EMAIL PROTECTED]>
Subject: Re: ipchains & ftp
Date: Sat, 04 Sep 1999 15:36:02 -0400
Try modprobe ip_masq_ftp.o
The Dude
On Sat, 04 Sep 1999 16:27:08 GMT, "Dan" <[EMAIL PROTECTED]> wrote:
>I'm new to Linux.
>
>I've installed Mandrake 6.0 on a pentium pc at home that is serving as a
>gateway to connect to the internet.One of my friend's friend, came over one
>night and configure the firewall and ip-maskerading.
>Everything works fine except for 2 things. The first one is when we're using
>Norton Anti-Virus live-update function, it not going through the firewall.
>And the second thing is ftp is only working to go out,
>I can't download anything.
>
>Can anyone help me? Please?
>
>Newbie.
>
------------------------------
From: Stefan Ekman <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: ipmasq and dial on demand, RedHat 6.0
Date: Sat, 04 Sep 1999 19:43:06 GMT
Balatro wrote:
>
> I'm using RedHat 6.0 on a baby server at home. Ipmasq was
> cake to set up and get working. HOWEVER, I manually have to fire off
> the ppp0 script and then shut it down when I'm done (I used the
> control-panel application to configure the dialup).
>
> Is there any simple way to get dial on demand with an
> inactivity timeout. Ultimately, I'd like it to fire up and dial out
> when my PC fires off a request outside the internal subnet, then hang
> up after XX seconds of inactivity on the line. That saves me the
> trouble of telnetting in and launching/closing the ppp connection.
>
> Any help or suggestions would be greatlly appreciated!
Download
diald16-0.16.5a-2.i386.rpm
diald16-config-0.16.5a-2.i386.rpm
Install and check configfiles in /etc/diald
Works like a charm here!
/Stefan
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: NIC probs
Date: Sat, 04 Sep 1999 19:44:46 GMT
Compile 8390.c as a module. You will get 8390.o. Then insmod 8390.o.
After that insmod ne.o irq=10 io=0x110 (whatever). This might just work.
Otherwise recompile the kernel with these drivers built-into it.
In article <[EMAIL PROTECTED]>,
Mike Kelly <[EMAIL PROTECTED]> wrote:
> I've been trying to install my ne2000 nic in caldera2.2. I try loading
> the ne module and it says that i need to also load 8390 as well. When
it
> tries to load 8390 for me, it then tells me "The kernel driver 8390
has
> niether been installed as a loadable module on this sytem, nor has it
> been compiled into the kernel." I have tried to recompile w/ 8390
> included but can't find where it is in the config. When loading ne I
> have let it attempt to autoprobe in addition to specifying which IRQ
and
> IO port it's at. Someone told me to use modprobe ne which gave me the
> following message: /lib/modules/2.2.5/net/ne.o:init_module Device or
> resource busy. Please, if you know anything that could help, please.
I'm
> getting desparate, i need this box up by midweek otherwise bad things
> will happen to me :o(.
>
> Thanks in advance.
>
> Mike
>
>
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: [EMAIL PROTECTED] (Frank Hahn)
Subject: Re: Automating redial
Date: Sat, 04 Sep 1999 01:09:43 GMT
Reply-To: [EMAIL PROTECTED]
On Thu, 02 Sep 1999 15:33:53 GMT, ksvenbak <[EMAIL PROTECTED]> wrote:
>My problem is sometimes when I try to connect to my ISP, the number is
>busy, and I have to try a few times before I can get a connection and
>login. How can I automate the ppp script to redial x number of times and
>stop, if the number of redials exceeds a certain number?
>
There is probably a script already on your system. On my Slackware
system, it is called "redialer".
If you don't have it, try downloading the source file for pppd. It
can be found here:
ftp://cs.anu.edu.au/pub/software/pub/
The last time I checked, the script was included.
--
Frank Hahn
McGowan's Madison Avenue Axiom:
If an item is advertised as "under $50", you can bet it's not
$19.95.
------------------------------
From: Laughters_domain <[EMAIL PROTECTED]>
Subject: SneakerNet woes...
Date: Sat, 04 Sep 1999 19:53:31 GMT
Whats's up everyone?
I'm running RH 6 on 1 machine/winnt 4.0 sp5 on a another and win98
on another. I have a little 8 port hub. All are connected to the hub,
all are on a 192.168.1.X ip/255.255.255.0. The two win machines ping
each other no prob. I can't get the Linux to ping anyone else but
itself. Under netgfg & it show etho with the right IP. prot =none (?)
{sambas next 4 me} atboot=yes and active=active. Ive switched patch
cords, NIC still notta. What am I missing?
Thanks
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Subject: IP Forwarding Feedback and Help Needed
Date: Sat, 04 Sep 1999 19:45:47 GMT
Hello all,
I'm hoping somebody out there will take a few minutes of their time and
help me out. I'm just learning how to set up Firewalls & Routers in
Linux and I'm running into difficulties likely caused by inexperience in
the networking field (dammit Jim, I'm a software engineer, not a network
guy!). Here's what I'm trying to do:
1) Create a Linux firewall that blocks out just about everything but
http, mail and ftp.
2) On the same box, create a router the forwards packets from the
internet to my internal network and vice-versa
3) Allow external sites to view my http server which will reside inside
my firewall.
4) Allow email to be sent to (and checked) from outside the firewall.
The Email server will also be inside the firewall.
The network consists of a Linux RH6 server as the firewall/router. He
has 2 3Com Nics. One is the internal network and is set up with the IP
address of 192.168.2.1. The other is multi-homed with the address of the
Email/Web server and its own static IP Address.
The rest of the network consists of a RH 5.2 Mail/Web server, a Windows
98 box and a Windows NT box.
All of the internal boxes work great (they can browse with Netscape
and download via FTP) and the router works like a champ.
I got FTP to work by loading the appropriate kernel module (IP_MASQ_FTP
if memory serves).
Here's where I need a little help:
1) I've included my rc.firewall script at the end of this post. Would
someone mind looking over it and seeing if I missed anything stupid. I
don't really know enough about cracking to know if I'm beeing too open
or if I'm really just hurting myself. This script was given to me by a
friend and I understand most of it, but not all...
2) I can't get anyone from the outside to be able to see my Email/Web
server. The IP address of the web server is hosted on the router's
external NIC as 207.225.36.107. The web server's real (internal) address
is 192.168.2.10. Nothing I've tried has worked. I know
there's documentation, but the problem that I'm running into is that the
docs pretty much assume you know what you're doing in the first place :)
Thanks in advance!
David
#!/bin/sh
#
# IPCHAINS-FIREWALL V1.6-MASQUERADE
#
# ----------------------------------------- Ipchains Firewall and MASQ
Script -
#
# Original script by Ian Hall-Beyer ([EMAIL PROTECTED])
#
# Contributors:
# terminus ([EMAIL PROTECTED]) (ICQ & DHCP, @home testing)
# ----------------------------------------------------------------
Interfaces -
# Local Interface
# This is the interface that is your link to the world
LOCALIF="eth0"
# Internal Interface
# This is the interface for your local network
# NOTE: INTERNALNET is a *network* address. All host bits should be 0
INTERNALNET="192.168.2.1/24"
# ------------------------------------------------------- Variable
definition -
#
# Set the location of ipchains.
IPCHAINS="/sbin/ipchains"
# You shouldn't need to change anything in the rest of this section
LOCALIP=`ifconfig $LOCALIF | grep inet | cut -d : -f 2 | cut -d \ -f 1`
LOCALMASK=`ifconfig $LOCALIF | grep Mask | cut -d : -f 4`
LOCALNET="$LOCALIP/$LOCALMASK"
echo "Internal: $INTERNALNET"
echo "External: $LOCALNET"
REMOTENET="0/0"
# -------------------------------------- Flush everything, start from
scratch -
echo -n "Flushing rulesets.."
# Incoming packets from the outside network
$IPCHAINS -F input
echo -n "."
# Outgoing packets from the internal network
$IPCHAINS -F output
echo -n "."
# Forwarding/masquerading
$IPCHAINS -F forward
echo -n "."
echo "Done!"
# ---------------------------------- Allow all connections within the
network -
echo -n "Internal.."
#$IPCHAINS -A input -s $INTERNALNET -d $INTERNALNET -j ACCEPT
#$IPCHAINS -A output -s $INTERNALNET -d $INTERNALNET -j ACCEPT
echo -n ".."
echo "Done!"
# -------------------------------------------------- Allow loopback
interface -
$IPCHAINS -A input -i lo -s 0/0 -d 0/0 -j ACCEPT
$IPCHAINS -A output -i lo -s 0/0 -d 0/0 -j ACCEPT
echo -n ".."
echo "Done!"
# --------------------------------------------------------------
Masquerading -
echo -n "Masquerading.."
# don't masquerade internal-internal traffic
$IPCHAINS -A forward -s $INTERNALNET -d $INTERNALNET -j ACCEPT
echo -n "."
# don't Masquerade external interface direct
$IPCHAINS -A forward -s $LOCALNET -d $REMOTENET -j ACCEPT
echo -n "."
# masquerade all internal IP's going outside
$IPCHAINS -A forward -s $INTERNALNET -d $REMOTENET -j MASQ
echo -n "."
# set Default rule on MASQ chain to Deny
$IPCHAINS -P forward DENY
echo -n "."
# --------------------- Allow all connections from the network to the
outside -
$IPCHAINS -A input -s $INTERNALNET -d $REMOTENET -j ACCEPT
$IPCHAINS -A output -s $INTERNALNET -d $REMOTENET -j ACCEPT
echo -n ".."
echo "Done!"
# ----------------------------------Set telnet, www and FTP for minimum
delay -
# This section manipulates the Type Of Service (TOS) bits of the
# packet. For this to work, you must have CONFIG_IP_ROUTE_TOS enabled
# in your kernel
echo -n "TOS flags.."
$IPCHAINS -A output -p tcp -d 0/0 www -t 0x01 0x10
$IPCHAINS -A output -p tcp -d 0/0 telnet -t 0x01 0x10
$IPCHAINS -A output -p tcp -d 0/0 ftp -t 0x01 0x10
echo -n "..."
# Set ftp-data for maximum throughput
$IPCHAINS -A output -p tcp -d 0/0 ftp-data -t 0x01 0x08
echo -n "."
echo "Done!"
# ---------------------------------------------------------- Trusted
Networks -
# Add in any rules to specifically allow connections from hosts/nets
that
# would otherwise be blocked.
# echo -n "Trusted Networks.."
# $IPCHAINS -A input -s [trusted host/net] -d $LOCALNET <ports> -j
ACCEPT
# echo -n "."
# echo "Done!"
# ----------------------------------------------------------- Banned
Networks -
# Add in any rules to specifically block connections from hosts/nets
that
# have been known to cause you problems. These packets are logged.
# echo -n "Banned Networks.."
# This one is generic
# $IPCHAINS -A input -l -s [banned host/net] -d $LOCALNET <ports> -j
DENY
# echo -n "."
# To block out the entire 195.195 network use:
# $IPCHAINS -A input -l -s 195.195.0.0 -d $LOCALNET -j DENY
# This one blocks ICMP attacks
# $IPCHAINS -A input -l -b -i $LOCALIF -p icmp -s [host/net] -d
$LOCALNET -j DEN
Y
# echo -n "."
# echo "Done!"
# ------------------------------------------------------ @home-specific
rules -
# This @home stuff is pretty specific to me (terminus). I get massive
port
# scans from my neighbors and from pokey admins at @home, so I just got
harsh
# and blocked all their stuff, with a few exceptions, listed below.
#
# If someone out there finds out the ip ranges of JUST tci@home, let me
know
# so i don't end up blocking ALL cablemodems like it's doing now.
echo -n "Cable Modem Nets.."
# so we can check mail, use the proxy server, hit @home's webpage.
# you will want to set these to your local servers, and uncomment them
# $IPCHAINS -A input -p tcp -s ha1.rdc1.wa.home.com -d $LOCALNET
1023:65535 -j A
CCEPT
# $IPCHAINS -A input -p tcp -s mail.tcma1.wa.home.com -d $LOCALNET
1023:65535 -j
ACCEPT
# $IPCHAINS -A input -p tcp -s www.tcma1.wa.home.com -d $LOCALNET
1023:65355 -j
ACCEPT
# $IPCHAINS -A input -p tcp -s proxy.tcma1.wa.home.com -d $LOCALNET
1023:65535
-j ACCEPT
# echo -n "...."
# so we can resolve the above hostnames, allow dns queries back to us
# $IPCHAINS -A input -p tcp -s ns1.home.net -d $LOCALNET 1023:65535 -j
ACCEPT
# $IPCHAINS -A input -p tcp -s ns2.home.net -d $LOCALNET 1023:65535 -j
ACCEPT
# $IPCHAINS -A input -p udp -s ns1.home.net -d $LOCALNET 1023:65535 -j
ACCEPT
# $IPCHAINS -A input -p udp -s ns2.home.net -d $LOCALNET 1023:65535 -j
ACCEPT
# echo -n ".."
# linux ipchains building script page (I think)
# $IPCHAINS -A input -p tcp -s 24.128.61.117 -d $LOCALNET 1023:65535 -j
ACCEPT
# echo -n "."
# Non-@home users may want to leave this uncommented, just to block all
# the wannabe crackers. Add any @home hosts you want to allow BEFORE
this line.
# Blast all other @home connections into infinity and log them.
$IPCHAINS -A input -l -s 24.0.0.0/8 -d $LOCALNET -j DENY
echo -n "."
echo "Done!"
# ---------------------------- Specific port blocks on the external
interface -
# This section blocks off ports/services to the outside that have
# vulnerabilities. This will not affect the ability to use these
services
# within your network.
echo -n "Port Blocks.."
# NetBEUI/Samba
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 139 -j DENY
$IPCHAINS -A input -p udp -s $REMOTENET -d $LOCALNET 139 -j DENY
echo -n "."
# Microsoft SQL
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 1433 -j DENY
$IPCHAINS -A input -p udp -s $REMOTENET -d $LOCALNET 1433 -j DENY
echo -n "."
# Postgres SQL
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 5432 -j DENY
$IPCHAINS -A input -p udp -s $REMOTENET -d $LOCALNET 5432 -j DENY
echo -n "."
# Network File System
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 2049 -j DENY
$IPCHAINS -A input -p udp -s $REMOTENET -d $LOCALNET 2049 -j DENY
echo -n "."
# X Displays :0-:2-
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 5999:6003 -j DENY
$IPCHAINS -A input -p udp -s $REMOTENET -d $LOCALNET 5999:6003 -j DENY
echo -n "."
# X Font Server :0-:2-
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 7100 -j DENY
$IPCHAINS -A input -p udp -s $REMOTENET -d $LOCALNET 7100 -j DENY
echo -n "."
# Back Orifice (logged)
$IPCHAINS -A input -l -p tcp -s $REMOTENET -d $LOCALNET 31337 -j DENY
$IPCHAINS -A input -l -p udp -s $REMOTENET -d $LOCALNET 31337 -j DENY
echo -n "."
# NetBus (logged)
$IPCHAINS -A input -l -p tcp -s $REMOTENET -d $LOCALNET 12345:12346 -j
DENY
$IPCHAINS -A input -l -p udp -s $REMOTENET -d $LOCALNET 12345:12346 -j
DENY
echo -n "."
echo "Done!"
# --------------------------------------------------- High Unprivileged
ports -
# These are opened up to allow sockets created by connections allowed by
# ipchains
echo -n "High Ports.."
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 1023:65535 -j
ACCEPT
$IPCHAINS -A input -p udp -s $REMOTENET -d $LOCALNET 1023:65535 -j
ACCEPT
echo -n "."
echo "Done!"
# ------------------------------------------------------------ Basic
Services -
echo -n "Services.."
# ftp-data (20) and ftp (21)
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 20 -j ACCEPT
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 21 -j ACCEPT
echo -n ".."
# ssh (22)
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 22 -j ACCEPT
echo -n "."
# telnet (23)
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 23 -j ACCEPT
echo -n "."
# smtp (25)
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 25 -j ACCEPT
echo -n "."
# DNS (53)
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 53 -j ACCEPT
$IPCHAINS -A input -p udp -s $REMOTENET -d $LOCALNET 53 -j ACCEPT
echo -n ".."
# DHCP on LAN side (to make @Home DHCP work) (67/68)
# $IPCHAINS -A input -i $INTERNALIF -p udp -s $REMOTENET -d
255.255.255.255/24 67 -j ACCEPT
# $IPCHAINS -A output -i $INTERNALIF -p udp -s $REMOTENET -d
255.255.255.255/24 68 -j ACCEPT
# echo -n ".."
# http (80)
$IPCHAINS -A input -p tcp -s $REMOTENET -d $LOCALNET 80 -j ACCEPT
# echo -n "."
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: Tom Eastep <[EMAIL PROTECTED]>
Subject: Re: PPP over Ethernet?
Date: Sat, 04 Sep 1999 18:06:51 +0000
Hartmann Schaffer wrote:
>
> In article <7qpjaj$5p7$[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] writes:
> > Hi,
> >
> > How can I direct PPP to Ethernet device driver, so
> > I can have PPP over , say Ethernet?
>
> Why would you want to?
>
Many ISPs that offer ADSL are requiring PPP over ethernet (PPPoE). Also,
PPPoE would be required to build a PPTP client for Linux that would work
over ADSL and cable modems. I don't believe that there is a current
solution -- I'd love to be proven wrong though...
-Tom
--
Tom Eastep \ Opinions expressed here
[EMAIL PROTECTED] \ are my own and not
Shoreline, Washington USA \ those of my employer
Work: [EMAIL PROTECTED] \________________________
------------------------------
** 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
******************************
