Linux-Networking Digest #382, Volume #10          Thu, 4 Mar 99 22:13:50 EST

Contents:
  Re: Machine name themes - what do you use? (Carlisle Branch)
  Second NIC installs and then gets transmit error (Don Heffernan)
  NAT Support ("Allen")
  bootp: "cannot load bootblock from disk" (Michael Wahler)
  Re: Ftp problem, root cannot login across telnet (Rick Onanian)
  Problem with stalling during ftp transfers ([EMAIL PROTECTED])
  IPCP: timeout sending Config-Requests ([EMAIL PROTECTED])
  Can I have a shared modem in Lunux ("Aaron Dershem")
  Re: email address (redline)
  Re: Road Runner Question (Josh Miller)
  Re: ethernet dec21143 problems (Peter Samuelson)
  Re: monitoring network (Jim Richardson)
  Re: Network Monitoring Script (Yan Seiner)
  Re: The truth about the Pentium III chip and ID --- **boycott info** ("Todd 
Bandrowsky")
  Logging/blocking specific ports ("Charles Stack")
  Sudden failure! ("Fly")
  Re: Network Programming question (Kishore)
  problem with net conf ([EMAIL PROTECTED])
  Re: Help with my 3Com905-TX ("Joe Filla")

----------------------------------------------------------------------------

From: [EMAIL PROTECTED] (Carlisle Branch)
Crossposted-To: comp.unix.solaris
Subject: Re: Machine name themes - what do you use?
Date: Thu, 04 Mar 1999 02:44:25 GMT

Hurricanes  --   Hugo, Bonnie, Andrew, Hazel, Etc....   



On 3 Mar 1999 13:56:35 -0000, [EMAIL PROTECTED] (Paul Scott)
wrote:

>In article <[EMAIL PROTECTED]>,
>Tony Waters  <[EMAIL PROTECTED]> wrote:
>>
>>ok, I wasn't going to participate, but it seems no one else names
>>boxes like I do...
>>
>
>
>Same here... If anyones still reading this anyway.
>
>We use sounds.
>
>E.G:
>
>kaboom, kapow for powerful machines
>sniffle for a 486/66
>whirr and clunk are printers
>smash and crunch are laptops
>
>etc. 
>
>Can't see why we'd ever run out, except for the ability to spell some
>particularly biological noises...
>
>
>Paul Scott
>
>[EMAIL PROTECTED]
>


------------------------------

From: [EMAIL PROTECTED] (Don Heffernan)
Subject: Second NIC installs and then gets transmit error
Date: Fri, 05 Mar 1999 01:17:50 GMT

>From my subject line you might accurately guess that I am new to
Linux.  I want to enable a seciond NIC for all the usual reasons.  I'm
booting RH 5.2.  eth0 installs properly and works fine.  eth1 appears
to have intalled properly (to my inexperienced eye, looking at the
output of ifconfig) but I can't communicate with it.  From the HOWTO I
concluded thath I might need a reference to eth1 in conf.modules, but
that didn't help.  I looked at the dmesg  and see that eth0 is
initiated and then eth1 is initiated the same way (except for MAC
address, i/o and irq).  Following the eth1 initiation message,
however, I see the following:

eth1: transmit timed out, tx_status 00 status e000
   Flags;  bus-master 1, full 1; dirty 44 current 60.
   Transmit List 000000000 vs. 01505bdo

what then follows are 15 lines of ?tramsmits? all ending in status
00000056

finally, the folllowing line appears:

eth1:  Resetting the Tx ring pointer.

I can't find any references to this in the Ethernet HOWTO FAQ.  Does
anyone have any suggestions that would be intelligible to a marginally
trainable dilletante?

If so, thanks in advance.

Don Heffernan


------------------------------

From: "Allen" <[EMAIL PROTECTED]>
Subject: NAT Support
Date: Thu, 4 Mar 1999 17:16:26 -0800

Does Linux support NAT?

Thanks.
Allen



------------------------------

From: Michael Wahler <[EMAIL PROTECTED]>
Subject: bootp: "cannot load bootblock from disk"
Date: Wed, 03 Mar 1999 16:23:52 +0100

I tried to build a diskless Linux workstation. I installed bootp and
tftp on the
server and made a floppy boot image from the netboot package. Trying to
boot with the floppy disk, the client gets its IP address and the
location of
the bootimage kernel file from the server (so bootp seems to work). It
is
also possible to manually get the bootimage file with tftp from the
server.
But the computer responds with the message "Cannot load bootblock from
disk. Please insert boot disk and press any key". Then the PC reboots.

Please help me to get rid of this problem.

Michael Wahler


------------------------------

From: Rick Onanian <[EMAIL PROTECTED]>
Subject: Re: Ftp problem, root cannot login across telnet
Date: Wed, 03 Mar 1999 10:25:09 -0500

[EMAIL PROTECTED] wrote:
> No matter how secure you think you are you should get into the
> habit of not telnet'ing and ftp'ing as root. You should do it as
> a normal use and then su to root. Root passwords are too easily
> sniffed as they're sent plain text.

Aren't they just as easily sniffed when you su?

Just wondering...

-- 
  rick - a guy in search of raw (ISO) cd images of SuSE and Slackware
===============
My opinions don't exist, and as such, are not anyone elses. I do not 
represent anyone, not even myself, and especially not my employer.
---
Looking for a 1968 Camaro SS convertible, black interior, 
beat-up rustbucket that is in need lots of restoration and TLC.
---
Reply to me at either thc <at sign here> psynet <dot> net or 
rick <at sign> mail <dot> artmold <dot> com

------------------------------

From: [EMAIL PROTECTED]
Subject: Problem with stalling during ftp transfers
Date: Thu, 04 Mar 1999 02:49:35 GMT

I'm experiencing a rather unusual problem with ftp downloads.

When I'm downloading certain large (~2 MB) files, the transfer stalls
indefinitely after transfering only a small amount of data (~40-80 k).  Every
time I try to download the file using that machine, it does the same thing. 
It exhibits that behavior even when I try to download the file from a mirror
site. It also appears to do the same thing under every client I try (ncftp,
Lynx, ftp, Netscape).  Upon flipping over to another VC and running netstat
-i, I notice that the number of RX-ERR packets has jumped up after every
incident.

I'm using a ppp dialup connection with a 56k modem, running Red Hat Linux 5.1
and kernel 2.2.1 (although this happened under 2.0.34 as well).  Any ideas?

-Bradford Hovinen

============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own    

------------------------------

From: [EMAIL PROTECTED]
Crossposted-To: linux.redhat.ppp
Subject: IPCP: timeout sending Config-Requests
Date: Fri, 05 Mar 1999 01:37:06 GMT

Hi everybody !
Until the last month, I was running kernel 2.0.36 and pppd 2.2.0f-5 in my
computer and everything works fine. The only strange thing was the message:

     Connect: ppp0 <--> /dev/cua2
->>> Unknown protocol (0x802b) received <<<- !!!!!!!!!
and, after this:
     local  IP address XXX.XXX.XXX.XXX
     remote IP address XXX.XXX.XXX.XXX
and then, everything starts to work, (ping, telnet, internet connections, etc,
etc, etc).

This month, I upgrade my kernel to 2.2.2 and pppd to 2.3.5 in my computer
and, using the same connection script:

pppd connect  'chat -v "" ATDPXXXXXXX CONNECT "" ogin: usertest sword: *******
User: network' /dev/cua2 115200 debug modem crtscts defaultroute

I couldn't connect. My modem is a USRobotics Courrier X2 V.Everything 56K and
the another guy is a USRobotics NetServer that just talk PPP protocol and
without any kind of compression method enabled. The only obs is the fact that
I expect my IP from it. All the messages showed in file /var/log/messages
when I'm trying to connect with new pppd (2.3.5) and the new kernel (2.2.2)
are:

Feb 19 08:15:29 localhost kernel: CSLIP: code copyright 1989 Regents of the
University of California Feb 19 08:15:29 localhost kernel: PPP: version 2.2.0
(dynamic channel allocation) Feb 19 08:15:29 localhost kernel: PPP Dynamic
channel allocation code copyright 1995 Caldera, Inc. Feb 19 08:15:29
localhost kernel: PPP line discipline registered. Feb 19 08:15:29 localhost
kernel: registered device ppp0 Feb 19 08:15:29 localhost pppd[524]: pppd
2.3.5 started by root, uid 0 Feb 19 08:15:30 localhost chat[525]: send
(ATDPXXXXXXX^M) Feb 19 08:15:31 localhost chat[525]: expect (CONNECT) Feb 19
08:15:31 localhost chat[525]: Feb 19 08:16:06 localhost chat[525]:
ATDPXXXXXXX^M^M Feb 19 08:16:06 localhost chat[525]: CONNECT Feb 19 08:16:06
localhost chat[525]:  -- got it Feb 19 08:16:06 localhost chat[525]: send
(^M) Feb 19 08:16:06 localhost chat[525]: expect (ogin:) Feb 19 08:16:06
localhost chat[525]:  26400/ARQ/V34/LAPM/V42BIS^M Feb 19 08:16:06 localhost
chat[525]: ^M Feb 19 08:16:06 localhost chat[525]: Welcome to USRobotics^M
Feb 19 08:16:06 localhost chat[525]:  The Intelligent Choice in Information
Access^M Feb 19 08:16:11 localhost chat[525]: login: Feb 19 08:16:11
localhost chat[525]:  -- got it Feb 19 08:16:11 localhost chat[525]: send
(usertest^M) Feb 19 08:16:11 localhost chat[525]: expect (sword:) Feb 19
08:16:11 localhost chat[525]:  usertest^M Feb 19 08:16:11 localhost
chat[525]: Password: Feb 19 08:16:11 localhost chat[525]:  -- got it Feb 19
08:16:11 localhost chat[525]: send (*******^M) Feb 19 08:16:11 localhost
chat[525]: expect (User:) Feb 19 08:16:11 localhost chat[525]:  ^M Feb 19
08:16:11 localhost chat[525]: Login/Network User: Feb 19 08:16:11 localhost
chat[525]:  -- got it Feb 19 08:16:11 localhost chat[525]: send (network^M)
Feb 19 08:16:11 localhost pppd[524]: Serial connection established. Feb 19
08:16:12 localhost pppd[524]: Using interface ppp0 Feb 19 08:16:12 localhost
pppd[524]: Connect: ppp0 <--> /dev/cua2 Feb 19 08:16:45 localhost pppd[524]:
IPCP: timeout sending Config-Requests Feb 19 08:16:46 localhost pppd[524]:
Hangup (SIGHUP) Feb 19 08:16:46 localhost pppd[524]: Modem hangup Feb 19
08:16:46 localhost pppd[524]: Connection terminated. Feb 19 08:16:47
localhost pppd[524]: Exit. Feb 19 08:18:29 localhost kernel: PPP: ppp line
discipline successfully unregistered

I don't know if this is important, but in my kernel I don't enabled IPX or
AppleTalk protocols; ppp suport was built in the kernel and the "original"
distribution used to install the new kernel, ppp-2.3.5 was RedHat 5.2.

ANY kind of help will be VERY, VERY, VERY appreciate !

Claudio Cuqui <[EMAIL PROTECTED]>
System Analyst - TELETRIM COMPANY
Sao Paulo - Brazil
Voice: +55 11 534-0806
       +55 11 9916-2061
FAX:   +55 11 5506-9182

============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own    

------------------------------

From: "Aaron Dershem" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Can I have a shared modem in Lunux
Date: Wed, 3 Mar 1999 09:48:35 -0600

Can I set up a home network and put the modem in the Linux server, but have
a Win98 machine use the modem on a dial-on-demand system?  I'd like to call
my ISP using Win98, but have the modem on the Linux server.  Does that make
sense?  I'm using RH 5.2, if that helps any.

Thanks,

Aaron Dershem.



------------------------------

From: redline <[EMAIL PROTECTED]>
Subject: Re: email address
Date: Thu, 04 Mar 1999 03:16:50 GMT

sorry forgot to update

redline wrote:

> PLEASE help me im gonna go totally crazy ive been working on this for 4
> days now i have a toshiba tecra 700 in a docking station i am trying to
> at least get one network card working i have the 3c509b in the pci slot
> of the docking station and the 589 (pcmcia)in the lap top anyway i cant
> get any of them to work can some create or show me a place where i can
> get a howto to do this step by step to get it to work
> Thanks
> Going completeley nuts
>
> Please reply by email


------------------------------

From: Josh Miller <[EMAIL PROTECTED]>
Subject: Re: Road Runner Question
Date: Thu, 04 Mar 1999 20:55:53 -0500
Reply-To: [EMAIL PROTECTED]

You shouldn't really have any problems... I did it all the time while I was on RR and 
was even able
to telnet in (and export and x display) from anywhere on the net.

Just give your RR box a static IP (if it's on the same hub as the dhcp windows boxes, 
give it
something in the 192.168.?.? range... it's reserved for non-internet networks). Then 
just telnet to
that IP.

If you want to telnet to it by it's hostname, add an entry in c:\windows\hosts file 
with the IP addy
of the linux box and it's hostname, then you can telnet by the name in the windows 
host file, or
connect any other way (ping hostname, ftp hostname, telnet hostname....)

there is a chance that your linux box is set up to deny all outside access, or the 
network card
isn't set up right, or any number of setup things.

You'll also probably want to use tcp/ip. 

If your talking about seeing the linux box in the "network neighborhood", I have no 
clue. You'd
probably have to run the samba client and set it up right... but I haven't messed with 
that, I've
only done the opposite (used samba to see the windows shared files)

best of luck,

Josh I.


[EMAIL PROTECTED] wrote:
> 
> hey all....i have a linux machine running samba for all 3 of my users to
> connect to, but that's only of we assign ourselves static IP's.  We are
> using Time Warner's Road Runner for Internet access which uses DHCP to
> assign IP's to our machines.  But, we are only allowed 3IP's, so the
> Linux machine doesn't log into road runner.  I was wondering why my
> win-blows machines can't see the Linux box, even via IPX?  I can't log
> into road runner, plus i really don't want to make the Linux machine a
> Proxy because it is too slow (I think).  Is there any way for us to see
> the Linux machine without using samba, or logging into road runner?
> Thanks for your help.
> 
> BK

------------------------------

From: [EMAIL PROTECTED] (Peter Samuelson)
Crossposted-To: comp.os.linux.development.system
Subject: Re: ethernet dec21143 problems
Date: 3 Mar 1999 21:34:24 -0600
Reply-To: Peter Samuelson <[EMAIL PROTECTED]>

[asdf <[EMAIL PROTECTED]>]
> I'm having problems in getting my network card to work.  [...] It's a
> built-in card, it's supposed to be DEC21143 based.

Quoting the Tulip FAQ (http://www.bmen.tulane.edu/~siekas/faq.html):

  6. I am having problems with my 21143?
  Get the latest driver!

Said driver can be downloaded from Donald's site:

  ftp://cesdis.gsfc.nasa.gov/pub/linux/drivers/test/tulip.c

and compiled using the instructions at:

  http://www.bmen.tulane.edu/~siekas/build.html

HTH.
-- 
Peter Samuelson
<sampo.creighton.edu!psamuels>

------------------------------

From: [EMAIL PROTECTED] (Jim Richardson)
Subject: Re: monitoring network
Date: 4 Mar 1999 02:59:45 GMT
Reply-To: [EMAIL PROTECTED]

On 1 Mar 1999 04:36:30 GMT, 
 AME, in the persona of <[EMAIL PROTECTED]>,
 brought forth the following words...:

>
>Hi all,
>
>I have a server and a client both running on a cobalt box running Linux.
>How can I monitor the activity taking place between the two?  Is there a
>program for that?
>
>Thanks
>
>--
>Ayman Elsaedi
>

iptraf, should be easy to find.

------------------------------

From: Yan Seiner <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.misc
Subject: Re: Network Monitoring Script
Date: Wed, 03 Mar 1999 21:51:49 -0500

Why not just set your firewall to log?  Or do you need additinal info?

Yan

Brian Ferris wrote:

>      I am using a RedHat 5.2 server to masquerade an 80+ user office
> to provide Internet access.  A major sticking point with my boss is
> that the machine must be able to log Internet usage among employees.
>     I have tackled this problem from a number of angles and I finally
> decided that I would write a shell script to handle the job (I mainly
> chose this because I wanted to learn shell programming).  The script
> is a follows (it is run out of my home directory <bferris> right now
> so files are based there)...
>
> #!/bin/sh
> # This script monitors Internet usage by monitoring the
> /proc/net/ip_masquerade file.  This file
> # stores info in the following format...
> # type (TCP,UDP,etc.)    source_ip:port    dest_ip:port    masq_port
> # Ip addresses are in hex format.  Linux uses this file to keep track
> of which ports it masqued
> #addresses to.
>
> tcp_only="TCP"
>
> # I use a temporary file <addition> to store the results of the
> script.  The first thing added to this
> # file is the date.
> echo $(date) > /home/bferris/addition
>
> #I use a read to pull the type, source_ip, and dest_ip from
> /proc/net/ip_masquerade
> while read type source dest rest; do
>
>         # I check to see if the type is TCP since I only want this
> type
>         if [ $type = $tcp_only ]; then
>
>                 # I wrote a quick and dirty cpp prog to convert the
> hex IP address into the regular x.x.x.x format
>                 source=$(/usr/local/bin/hextodec $source)
>                 dest=$(/usr/local/bin/hextodec $dest)
>
>                 # To avoid having to make a nslookup call for every
> IP, I created a list of addresses and
>                 # their host names in the host_list file.  If the
> address hasn't been added to the list yet...
>                 if dest_name=$(grep $dest /home/bferris/host_list) ;
> then
>                         adder="$source $dest_name"
>                 else
>                         # ... I make a nslookup to find the server
> name.
>                         dest_name=$(nslookup $dest | grep Na | cut -c
> 7-)
>                         # If the lookup doesn't come up with anything,
> the name becomes unknown
>                         if [ -z $dest_name ]; then
>                                 dest_name="Unknown"
>                         fi
>                         adder="$source $dest $dest_name"
>
>                         # Since this server wasn't in the host_list
> file, I add it
>                         echo $dest $dest_name >> host_list
>                 fi
>
>                 # I check to see if I have added the $adder to the
> addition file yet.  I do this because
>                 # a website can be masq as many as ten times to the
> same IP in a normal ip_masquerade
>                 # listing.  There is no point in adding it ten times
> so I just add it once.
>                 if ! grep -q "$adder" /home/bferris/addition ; then
>                         echo $adder >> /home/bferris/addition
>                 fi
>
>         fi
> done < /proc/net/ip_masquerade
>
> # When I'm all done, I have a time stamped file that lists who's been
> using the net.  This file
> # can be appended to the final log file which I will then let my boss
> look at so he can deal out
> # sweet justice.
> more /home/bferris/addition
>
> <EOF>
>
>     First, let me say that all I know about shell scripting came from
> this project.  This script works but I have a feeling that there might
> be a better, more efficient way of getting the same results.  This
> script would currently have to be run by cron every once in a while to
> properly log.  With that in mind, I will now ask all my questions
>     -Is this script the answer or am I barking up the wrong tree?
>     -Should I do something with CPP that would run 100x faster?
>     -Should I just bite the bullet and install a proxy like squid
> which does logging too?
>     -Should I do something crazy like install my own local DNS server
> and do logging here (I want to set up a DNS for fun anway...)?
>
>     I know that is a lot of questions so any thoughts the world has on
> the subject is much appreciated.  Besides, the whole thing can
> definitely be chocked up as a learning experience if nothing comes of
> it.
>
> Thanks,
> Brian Ferris
>
>
>
>




------------------------------

From: "Todd Bandrowsky" <[EMAIL PROTECTED]>
Crossposted-To: 
comp.lang.perl.misc,comp.lang.python,comp.lang.tcl,comp.mail.sendmail,comp.os.linux.setup,comp.os.ms-windows.advocacy
Subject: Re: The truth about the Pentium III chip and ID --- **boycott info**
Date: Wed, 3 Mar 1999 20:37:13 -0500


Oh please, spare the misrepresentation.  Sun Microsystems, you know, the
holy good guys, have had the concept of a software accessible unique
identifier in all of their hardware.  Corporate America wants to track
people, and Sun has been giving them that technology for years.  If you are
going to boycott Intel, then you should boycott Sun too.

JoHn DoH <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
>I beg to differ but MAC addressess are not made for spying on us they
>are for network location and such.  No on knows that I own a certain
>MAC  address (unlike Intel that wants you to register after getting the
>PIII).  I think it is a bad move on intel's part but those that accept
>it are doomed to get shafted.  Your ass not mine (I will keep my PI any
>day running).  Sorry for the crossposting just got a little annoyed and
>wanted it to be righted in all places of being.
>
> -DoH
>
>Kano wrote:
>>
>> Oh come on. Many other standard devices (ethernet cards, for example)
have their
>> own unique serial numbers that software can use at will. Get over it.
>>
>> -kl
>>
>> Boycott Swintel <[EMAIL PROTECTED]> wrote in message
>> news:[EMAIL PROTECTED]...
>> >Take the Pentium III Boycott Survey
>
>--
>JoHn 'DoH' KeLm
>http://www.johndoh.cjb.net
>"People are too stupid to realize they are" - DoH



------------------------------

From: "Charles Stack" <[EMAIL PROTECTED]>
Subject: Logging/blocking specific ports
Date: Wed, 3 Mar 1999 23:07:25 -0500

Can anyone tell me how I can block requests on certain ports and log those
requests?

Specifically, I'd like to block all but Apache (on port 80) while still
allowing local access to all services.

TIA,

Charles



------------------------------

From: "Fly" <[EMAIL PROTECTED]>
Subject: Sudden failure!
Date: Thu, 4 Mar 1999 20:28:26 -0600

I've been happily using my IP Masquerading server for a couple of weeks. All
of a sudden it stops working!

I can't ping 10.0.0.1 - I can ping 10.0.0.2. If I remove the NIC for
10.0.0.2, I can ping 10.0.0.1.

Am I having hardware problems? I exchanged the NIC for 10.0.0.1 today and
still got the same problem. The NIC's diags say both cards are OK. Linux
finds them on boot and ifconfig says they are there. The cards are ISA
D-Link 10bT NICS.

Any ideas?!



------------------------------

From: Kishore <[EMAIL PROTECTED]>
Subject: Re: Network Programming question
Date: 5 Mar 1999 02:31:32 GMT


Andy wrote:
> Could anyone tell me where i can find decent info on writing a small ftp
> server?
> 
> Would prefer on-line docs, but would consider a book if not.
> 
> Cheers
> 
> p0g
> 
There is a book in Unix Network Programming by Richard Stevens
which helps a lot.
And for FTP even TCP/IP by Comer is a very good book too

==================  Posted via SearchLinux  ==================
                  http://www.searchlinux.com

------------------------------

From: [EMAIL PROTECTED]
Subject: problem with net conf
Date: Fri, 05 Mar 1999 03:36:02 GMT

I'm having problems configuring a 486 with 8 meg of ram to act as a
gateway between two networks.  It will be used as a demonstration of
networking rather than a 'working' router.
eth0 will be 192.168.0.6 IRQ10 base 0x300
eth1 will be 192.168.1.6 IRQ5   base 0X320
 Anyway, I've got RedHat 5.1 installed, I know that both network cards
are working OK and the network is running.  After install I can ping
to and from eth0 so I run netconf to set up the second NIC and from
then on I'm in rouble.
Prior to exiting netconf I review the changes which are reported as:
        /etc/rc.d/rc3.d/S10 network reload
        /etc/rc.d/rc3.d/S50 inet restart
        /etc/rc.d/rc3.d/S85 gpm restart
At this stage I can still ping eth0 OK but... when I reboot I see the
message 'delaying eth0 initalization'
          'delaying eth1 initalization'
Now when I ping I get a network unreachable error.
Running ifconfig eth0 192.168.0.6 netmask 255.255.255.0 up generates
        'SIOCSIFADDR Operation not supported by device'
        'SIOCIFNETMASK Operation not supported by device'
Running route add 192.168.0.6 eth0 generates
        'SIOCADDRT Operation not supported by device'

So I mst be doing something wrong but I don't know what.  Any help or
suggestions would be very much appreciated; I'm going round in circles
with this one.

Thank you all in advance!

Cheers

Keith Clethero

------------------------------

From: "Joe Filla" <[EMAIL PROTECTED]>
Subject: Re: Help with my 3Com905-TX
Date: Wed, 3 Mar 1999 21:08:50 -0800

Thanks Tim. I had already done so but forgot to mention it. My IP is
192.168.1.10
eth0 shows up in netcfg with this information but still the dreaded "Network
is unreachable"




------------------------------


** 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
******************************

Reply via email to