Linux-Networking Digest #421, Volume #11 Sat, 5 Jun 99 15:13:39 EDT
Contents:
Re: Why pump instead of dhcpc in RH v6.0? [tip for Videotron subscribers] ("Beno�t
Bousquet")
Re: SSH How-To or Guide available? ("Manuel T. Ruiz")
Linu-NT newbie question (El Squid)
Re: Linux and ADSL with GTE ("Hervey Wilson")
Re: ICMP error ("Kai Krakow")
Re: Linux: ICMP Redirect, IP Source Routing unterdruecken (Patrick Schaaf)
Re: Networking Problem ("Dave")
Re: Can't connect to my ISP yet, here's the pppd-output... (Craig W. Noah)
Re: Question:BUG?SPEC?/Directed Broadcast on kernel 2.0.36 (Eric Lawson)
Re: basic network question (Frank Hahn)
Re: BROADCAST on local loopback (Frank Hahn)
----------------------------------------------------------------------------
From: "Beno�t Bousquet" <[EMAIL PROTECTED]>
Subject: Re: Why pump instead of dhcpc in RH v6.0? [tip for Videotron subscribers]
Date: Sat, 5 Jun 1999 13:49:38 -0400
After installing RedHat 6.0 (downloaded from SunSite), my cable modem simply
refused to work - I was experiencing long timeouts, failed initializations,
etc. during bootups. The only way to make it work was to use a painfully
long sequence of reboots and cable modem resets.
I finally downloaded the dhcpcd-1.3.17pl2-1.i386.rpm package and substituted
a call to "/sbin/dhcpcd $DEVICE" in my /etc/sysconfig/network-scripts/ifup
script, and now everything works like a charm (routes are updated
automatically, and so is the resolv.conf file).
I'm a Videotron cable modem subscriber in the Montreal, Quebec area. It
seems pump is incompatible with either their DHCP server or there's
something in my system that behaves strangely with their setup.
Anyhow, I just thought people with similar problems might appreciate the
tip.
--
==================
Beno�t Bousquet
[Remove "nospam" from my e-mail address to reply]
Iain O'Cain <[EMAIL PROTECTED]> wrote in message
news:7j9kt8$[EMAIL PROTECTED]...
>
> Steve Snyder <[EMAIL PROTECTED]> (and some others) wrote:
>
> >What is the advantage of pump over dhcpc?
>
> It's smaller, faster, lighter, and tastes great, according to Red Hat.
>
> What I've found is that AFTER making sure I've got their patched copy,
> which has the same version number on it as the copy shipped with Red
> Hat Linux 6.0, it fails to set IP or any other information. A 5.2
> system with dhcpcd on the same network is fine.
>
> In any case, it doesn't look like pump puts the DHCP-provided
> information anyplace easy to retrieve. I've got to have an ipchains
> script read stuff like the IP address, but it's not clear where I'll
> actually get that.
>
> Good luck with it.
>
> - I
------------------------------
From: "Manuel T. Ruiz" <[EMAIL PROTECTED]>
Subject: Re: SSH How-To or Guide available?
Date: Sat, 05 Jun 1999 19:43:17 +0200
This is a cryptographically signed message in MIME format.
==============ms584A00075805DAF9C71DD3DD
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi Mark !!
What version are you using ? RSA or DSA ?
If you are installing the 1.2 something version, once you have the
binaries, you need to execute the sshd daemon, generate your keys using
ssh-keygen then you'll have two files one called xxx.pub => public key
and xxx => private key.
So if you have generated those keys as root, and you want to use slogin
using root, add the xxx.pub file into $HOME/.ssh/authorized_keys as
follows:
# cat xxx.pub > $HOME/.ssh/authorized_keys
Then you can try:
# slogin machine, by default slogin use the private key located into the
$HOME/.ssh/identity file. You can also try this:
# slogin -i xxx machine
I hope this help,
//Manuel
Mark wrote:
> Does anyone know where I can get a How-To or guide for setting up SSH
> correctly on a Linux box? I have it installed and I *think* I have it
> working womewhat correctly. :) I'm just not full understanding the
> various public and private keys. Thanks in advance for any help.
==============ms584A00075805DAF9C71DD3DD
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
MIIERAYJKoZIhvcNAQcCoIIENTCCBDECAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC
AuowggLmMIICT6ADAgECAgQ28XeiMA0GCSqGSIb3DQEBBQUAMDYxCzAJBgNVBAYTAkVTMQ0w
CwYDVQQKEwRGTk1UMRgwFgYDVQQLEw9GTk1UIENsYXNlIDIgQ0EwHhcNOTkwNTE5MTQwMDUz
WhcNMDAwNDAxMTEwMDAwWjB5MQswCQYDVQQGEwJFUzENMAsGA1UEChMERk5NVDEYMBYGA1UE
CxMPRk5NVCBDbGFzZSAyIENBMQ8wDQYDVQQLEwY1MDAwNzExMDAuBgNVBAMTJ05PTUJSRSBM
T1JBIEVTUEFEQSBST1NBIC0gTklGIDIzMzQ3NDU0UTBcMA0GCSqGSIb3DQEBAQUAA0sAMEgC
QQDCMaAUXiunUeRhaqvuT7feJT9Zi84GcZdFvwDghZ8blanRT0prY/Vu5/EYsh1LmiOaH/Bq
0x5RujBuMtTf0G+ZAgMBAAGjggEAMIH9MBoGA1UdEAQTMBGBDzIwMDAwNDAxMTEwMDAwWjAL
BgNVHQ8EBAMCBaAwEQYJYIZIAYb4QgEBBAQDAgWgMFkGA1UdHwRSMFAwTqBMoEqkSDBGMQsw
CQYDVQQGEwJFUzENMAsGA1UEChMERk5NVDEYMBYGA1UECxMPRk5NVCBDbGFzZSAyIENBMQ4w
DAYDVQQDEwVDUkwyMTAfBgNVHSMEGDAWgBRAmnZEl3QHxKwUyx6NTzpFfDDXYTAdBgNVHQ4E
FgQUFv6WdEl28y/Vfdvo+0VKIt/HrHIwCQYDVR0TBAIwADAZBgkqhkiG9n0HQQAEDDAKGwRW
NC4wAwIDqDANBgkqhkiG9w0BAQUFAAOBgQCUkeXmnJWhMKzFJppgMZee9wCoMsn0TpwWj0Ey
wjEpR4SsLl6Hufjkl7fSCOJEfeHiG3yHj+CR7blShm0ozKgbBaEBXUUqO9TXUbdG5T4r4SOD
O4cBrP0POMl8wGxbP8pDuH1Rrt4rnQgHLI+GQMB0FL33upL6YccwKahKbYN4eDGCASIwggEe
AgEBMD4wNjELMAkGA1UEBhMCRVMxDTALBgNVBAoTBEZOTVQxGDAWBgNVBAsTD0ZOTVQgQ2xh
c2UgMiBDQQIENvF3ojAJBgUrDgMCGgUAoH0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAc
BgkqhkiG9w0BCQUxDxcNOTkwNjA1MTc0MzE3WjAeBgkqhkiG9w0BCQ8xETAPMA0GCCqGSIb3
DQMCAgEoMCMGCSqGSIb3DQEJBDEWBBQc9mGhWNM+Hu0UdnnreICrGbzs4zANBgkqhkiG9w0B
AQEFAARAWvVfasBMEh/J9xopqGVmNHrscFGWOuyLoUh79KkbwIbJS2/Iwf4ORZPQrFGKAdTA
43yyNWxbiQ3xuthvaT4Enw==
==============ms584A00075805DAF9C71DD3DD==
------------------------------
From: El Squid <[EMAIL PROTECTED]>
Subject: Linu-NT newbie question
Date: Sat, 05 Jun 1999 16:50:24 GMT
Hello - I am considering adding a Linux box to my soon to be NT
network. Can someone point me to a FAQ or other reference for
constructing this ?
Thanks in advance,
El-Squid
--
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>> Remember the future, Imagine the Past... >>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
------------------------------
From: "Hervey Wilson" <[EMAIL PROTECTED]>
Subject: Re: Linux and ADSL with GTE
Date: Sat, 5 Jun 1999 11:07:58 -0700
I believe that GTE the Phone Company is a different company to GTE the ISP.
GTE the Phone company provides the physical connection for ADSL and does not
care which ISP you use (aside from some circuit numbers, etc). GTE the ISP
_will_ care about which OS you use simply for support reasons as others have
noted. You might want to consider using a different ISP - you may even get a
better deal.
Hervey.
------------------------------
From: "Kai Krakow" <[EMAIL PROTECTED]>
Subject: Re: ICMP error
Date: Sat, 5 Jun 1999 19:54:14 +0200
Reply-To: "Kai Krakow" <[EMAIL PROTECTED]>
> With my kernel (2.2.5) on my redhat linux box,
> I got always an 'xxx.xxx.xxx.xxx sent an invalid
> ICMP error to a broadcast'.
> To fix it I saw that a file in /proc get a value that I
> would change. This value is surely fixed with some
> configuration tool. I tried linuxconf, I tried to change
> the options in the kernel but nothing work.
> Can someone tell me how can I fix the problem ?
I would be interested in which file you saw...
ciao
Kai
------------------------------
From: [EMAIL PROTECTED] (Patrick Schaaf)
Crossposted-To: de.comm.internet.routing
Subject: Re: Linux: ICMP Redirect, IP Source Routing unterdruecken
Date: 5 Jun 1999 18:11:30 GMT
[EMAIL PROTECTED] (Gert Doering) writes:
>>> Macht "Netflow-Switching" auch so, ist eine nette Idee, skaliert
>>> leider ueberhaupt nicht, wenn man Netze wie das *Internet*
>>> betrachtet, wo mehr als nur "ein paar 1000" Flows / SVCs parallel
>>> ueber einen groesseren Knoten laufen.
>>Gibt es dazu Info? Das kenne ich leider nicht!
>s. anderes Posting - hier noch ein paar mehr Zahlen:
noch ein paar, ohne Aussage, wann sie entstanden sind :-)
IP Flow Switching Cache, 4456448 bytes
28270 active, 37266 inactive, 22427406 added
...
Protocol Total Flows Packets Bytes Packets Active(Sec) Idle(Sec)
======== Flows /Sec /Flow /Pkt /Sec /Flow /Flow
TCP-Telnet 7273 0.2 13 149 3.6 15.6 32.5
TCP-FTP 84324 3.1 12 87 38.4 11.3 26.5
TCP-FTPD 76234 2.8 70 450 199.5 15.6 26.9
TCP-WWW 17127314 640.5 13 624 8918.5 7.7 25.6
Die Kiste sieht etwa die Haelfte der international laufenden Flows unseres
Netzes, sowie alles, was in Richtung DE-CIX laeuft.
>das sind die Flows eines unserer Router - 56 *neue* Flows pro Sekunde.
>Dafuer ist jeweils eine neue VC aufzubauen und wieder abzubauen...
Das taete weh.
Direkt neben obiger Kiste steht eine zweite, die die andere Haelfte
International routet, und fuer die gesamte Einwahl auf die obige durch-
routet.
>(Netflow-Caching von Ciscos skaliert bei uns auch noch wunderbar, aber auf
>den Core-Routern des WiN skaliert es nicht mehr, weil dort die Zahl der
>Flows einfach noch viel groesser ist, und *paeng*).
Kann ich mir vorstellen. Die beiden erwaehnten Router sind 7513er mit RSP4.
Die Kiste, von der obige Zahlen stammen, lief auf etwa 11% CPU usage,
als ganz normaler CEF-netflow-router. Die andere, bei gleicher Hardware,
ist ein tag edge router (Cisco-proprietaer, vor-MPLS). Zu jedem
IBGP-next-hop gibt's einen dynamisch gebastelten ATM-VC, und die Dinger
werden neu verteilt, wenn sich die (ISIS)-Topologie der next-hops aendert.
Das Ding verbriet zur gleichen Zeit wie oben, und bei praktisch gleichem
Durchsatz, nur etwa 3% CPU. Die Labels machen die Entscheidung, wo was
hinsoll, halt erheblich einfacher: 16 bit (label) mit 70 verschiedenen
Werten (next-hops) sind schneller gemappt als 64 bit (IP source/dest,
in Wirklichkeit bei netflow mehr) mit obigen 28000 aktiven Flows.
Es liefen durch jede Kiste etwa 100mbit/s, wenn ich das richtig
abschaetze. Was das bei STM-4 und hoeher bedeutet, sieht man an obigen
Zahlen, denke ich, recht gut. Die Probleme des DFN kann ich somit
gut nachvollziehen.
Das nur mal als Datenpunkt, ueber welche Dynamik ihr hier redet. Und unser
Netz ist sicher nicht das groesste auf dieser Welt.
Gruss
Patrick
------------------------------
From: "Dave" <[EMAIL PROTECTED]>
Subject: Re: Networking Problem
Date: Sat, 5 Jun 1999 14:26:21 -0400
read up man on ip-chains/masq http://howto.linuxberg.com/ or on #Efnet,
join #linuxhelp
Jimmy Tran <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I'm using cable modem. My TCP/IP worked fine w/ my cable modem. But it
> doesn't work anymore since I tried to install a virtual host and
> re-reoute from my internet IP /w my ISP to my local network IP...
> Everything was screwed. I can't get my computer to connect onto the
> internet anymore...is there anyway that I can restore my first seting
> (or default)? I tried to re-compile the kernel, but i didn't do anything
> to the whole network setup.
> Please help me.
> Thanks a lot.
>
> PS: Another thing, I want to be able to share my internet connection w/
> my other boxes. I have 2 other boxes, 1 is linux, and one is win. How
> can I do that? I know the idea is to turn my box right now to a gateway,
> and masqueradign IP...but...obviously, I don't know how to do this very
> well.
------------------------------
From: Craig W. Noah <[EMAIL PROTECTED]>
Subject: Re: Can't connect to my ISP yet, here's the pppd-output...
Date: Sat, 5 Jun 1999 01:39:13 -0500
Crossposted-To:
comp.os.linux.hardware,comp.os.linux.misc,comp.os.linux.setup,comp.os.linux.x
Melle,
From the "Linux System Administrator's Survival Guide" ... it makes a
difference which way the authentication is run. If the local machine has to
authenticate itself, then the local hostname is the client and the server
hostname is the server field. However, if your machine sends the callenge, the
process (and fields) are reversed. The remote hostname is the client and your
local hostname is the server. The examples in the book are:
#The local machine authenticates itself
# client server string addresses
merlin.tpci.com big_guy.big_net.com "I hate DOS"
#This reverses the process
# client server string addresses
big_guy.big_net.com merlin.tpci.com "I hate DOS"
Hope this helps.
Craig Noah
On Fri, 04 Jun 1999, Melle wrote:
>Hi,
>it's me again and the problem is still alive ... I can't connect to my ISP
>running RH5.2.
>But I got the idea of posting the pppd-output, maybe one of you out there
>can do something with it to help me ;-)) It would be great.
>
>Here it is:
>----------------------------------------------------------------------------
>-------------------
>Jun 4 19:19:18 PC pppd[456]: pppd 2.3.5 started by root, uid 0
>Jun 4 19:19:18 PC pppd[456]: Using interface ppp0
>Jun 4 19:19:18 PC pppd[456]: Connect: ppp0 <--> /dev/ttyS3
>Jun 4 19:19:18 PC pppd[456]: sent [LCP ConfReq id=0x1 <magic 0xfba16783>
><pcomp> <accomp>]
>Jun 4 19:19:21 PC pppd[456]: sent [LCP ConfReq id=0x1 <magic 0xfba16783>
><pcomp> <accomp>]
>Jun 4 19:19:21 PC pppd[456]: rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth
>chap 80> <magic 0x7d7f> <pcomp> <accomp>]
>Jun 4 19:19:21 PC pppd[456]: sent [LCP ConfAck id=0x0 <asyncmap 0x0> <auth
>chap 80> <magic 0x7d7f> <pcomp> <accomp>]
>Jun 4 19:19:21 PC pppd[456]: rcvd [LCP ConfAck id=0x1 <magic 0xfba16783>
><pcomp> <accomp>]
>Jun 4 19:19:44 PC pppd[456]: Hangup (SIGHUP)
>Jun 4 19:19:44 PC pppd[456]: Modem hangup
>Jun 4 19:19:44 PC pppd[456]: Connection terminated.
>Jun 4 19:19:45 PC pppd[456]: Exit.
>Jun 4 19:21:22 PC pppd[464]: pppd 2.3.5 started by root, uid 0
>Jun 4 19:21:22 PC pppd[464]: Using interface ppp0
>Jun 4 19:21:22 PC pppd[464]: Connect: ppp0 <--> /dev/ttyS3
>Jun 4 19:21:22 PC pppd[464]: sent [LCP ConfReq id=0x1 <magic 0xebee4560>
><pcomp> <accomp>]
>Jun 4 19:21:25 PC pppd[464]: sent [LCP ConfReq id=0x1 <magic 0xebee4560>
><pcomp> <accomp>]
>Jun 4 19:21:25 PC pppd[464]: rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth
>chap 80> <magic 0x2640> <pcomp> <accomp>]
>Jun 4 19:21:25 PC pppd[464]: sent [LCP ConfAck id=0x0 <asyncmap 0x0> <auth
>chap 80> <magic 0x2640> <pcomp> <accomp>]
>Jun 4 19:21:25 PC pppd[464]: rcvd [LCP ConfAck id=0x1 <magic 0xebee4560>
><pcomp> <accomp>]
>Jun 4 19:21:47 PC pppd[464]: Hangup (SIGHUP)
>Jun 4 19:21:47 PC pppd[464]: Modem hangup
>Jun 4 19:21:47 PC pppd[464]: Connection terminated.
>Jun 4 19:21:48 PC pppd[464]: Exit.
>----------------------------------------------------------------------------
>-------------
>
>I know my provider is using CHAP authentification and that I have to add
>username + password to the /etc/ppp/chap-secrets, but using kppp it tells me
>(I have the German version, the English output may differ):
>
> modem ready
> dialing <number>
> network login
>
>Then (after some 30 seconds) it hangs up the modem. But: I DON'T KNOW WHY!!!
>Please help me, thanx.
>
> Melle
------------------------------
From: Eric Lawson <[EMAIL PROTECTED]>
Subject: Re: Question:BUG?SPEC?/Directed Broadcast on kernel 2.0.36
Date: Sat, 05 Jun 1999 11:40:02 -0700
I was just reading about this at
http://users.quadrunner.com/chuegen/smurf.txt
Perhaps that will answer your questions better than I could.
Eric
------------------------------
From: [EMAIL PROTECTED] (Frank Hahn)
Subject: Re: basic network question
Date: Sat, 05 Jun 1999 18:46:51 GMT
Reply-To: [EMAIL PROTECTED]
On Fri, 04 Jun 1999 20:18:33 +0200, Fabian M�ller <[EMAIL PROTECTED]> wrote:
>If I type the command: route add -host 192.168.10.52 netmask
>255.255.255.255 metric 1
>I see the error message: route: netmask 00000000 does not make sense with
>host route
>
>(You will not believe how often I have seen this message)
>
I have not followed this thread so forgive me if this has been covered.
Here is the /etc/rc.d/rc.inet1 file from my Slackware system. This
file is used to set up networking on my system.
=======================================================================
#! /bin/sh
#
# rc.inet1 This shell script boots up the base INET system.
#
# Version: @(#)/etc/rc.d/rc.inet1 1.01 05/27/93
#
HOSTNAME=`cat /etc/HOSTNAME`
# Attach the loopback device.
/sbin/ifconfig lo 127.0.0.1
/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
# Attach the dummy device.
#/sbin/ifconfig dummy homer.muscanet.com
#/sbin/route add -host homer.muscanet.com
# IF YOU HAVE AN ETHERNET CONNECTION, use these lines below to configure the
# eth0 interface. If you're only using loopback or SLIP, don't include the
# rest of the lines in this file.
# Edit for your setup.
IPADDR="192.168.100.10" # REPLACE with YOUR IP address!
NETMASK="255.255.255.0" # REPLACE with YOUR netmask!
NETWORK="192.168.100.0" # REPLACE with YOUR network address!
BROADCAST="192.168.100.255" # REPLACE with YOUR broadcast address, if you
# have one. If not, leave blank and edit below.
#GATEWAY="" # REPLACE with YOUR gateway address!
# Uncomment the line below to initialize the ethernet device.
/sbin/ifconfig eth0 ${IPADDR} broadcast ${BROADCAST} netmask ${NETMASK}
# Uncomment these to set up your IP routing table.
/sbin/route add -net ${NETWORK} netmask ${NETMASK} eth0
# End of rc.inet1
=======================================================================
I have three computers networked together. One is the above Linux
machine, one is a Windows 95 machine, and one is a Sun Sparc machine.
Hope this helps.
--
Frank Hahn
No problem is so formidable that you can't just walk away from it.
------------------------------
From: [EMAIL PROTECTED] (Frank Hahn)
Subject: Re: BROADCAST on local loopback
Date: Sat, 05 Jun 1999 18:47:04 GMT
Reply-To: [EMAIL PROTECTED]
On Fri, 4 Jun 1999 13:32:32 +0200, Jef <[EMAIL PROTECTED]> wrote:
>I installed Linux (SuSE 6.1).
>when I type ifconfig, I see no BROADCAST on lo .
>Shouldn't that be there,
>and if so: how can I add this feature ?
>
Here is what I get from the output of my ifconfig command:
$ ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1
RX packets:531378 errors:0 dropped:0 overruns:0 frame:0
TX packets:531378 errors:0 dropped:0 overruns:0 carrier:0 coll:0
eth0 Link encap:Ethernet HWaddr 00:40:05:48:67:EE
inet addr:192.168.100.10 Bcast:192.168.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1451774 errors:0 dropped:0 overruns:0 frame:0
TX packets:1606308 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Interrupt:10 Base address:0x300
sl0 Link encap:Serial Line IP
inet addr:192.168.100.10 P-t-P:192.168.100.22 Mask:255.255.255.0
UP POINTOPOINT RUNNING MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:896 errors:0 dropped:0 overruns:0 carrier:0 coll:0
Don't worry about the sl0 device, that is there because of diald.
I am not familiar with SUSE, so you will have to figure the setup
part by yourself. On Slackware, the networking stuff is setup in
/etc/rc.d/rc.inet1. Here is what mine looks like:
=======================================================================
#! /bin/sh
#
# rc.inet1 This shell script boots up the base INET system.
#
# Version: @(#)/etc/rc.d/rc.inet1 1.01 05/27/93
#
HOSTNAME=`cat /etc/HOSTNAME`
# Attach the loopback device.
/sbin/ifconfig lo 127.0.0.1
/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
# Attach the dummy device.
#/sbin/ifconfig dummy homer.muscanet.com
#/sbin/route add -host homer.muscanet.com
# IF YOU HAVE AN ETHERNET CONNECTION, use these lines below to configure the
# eth0 interface. If you're only using loopback or SLIP, don't include the
# rest of the lines in this file.
# Edit for your setup.
IPADDR="192.168.100.10" # REPLACE with YOUR IP address!
NETMASK="255.255.255.0" # REPLACE with YOUR netmask!
NETWORK="192.168.100.0" # REPLACE with YOUR network address!
BROADCAST="192.168.100.255" # REPLACE with YOUR broadcast address, if you
# have one. If not, leave blank and edit below.
#GATEWAY="" # REPLACE with YOUR gateway address!
# Uncomment the line below to initialize the ethernet device.
/sbin/ifconfig eth0 ${IPADDR} broadcast ${BROADCAST} netmask ${NETMASK}
# Uncomment these to set up your IP routing table.
/sbin/route add -net ${NETWORK} netmask ${NETMASK} eth0
# End of rc.inet1
=======================================================================
I have three computers networked together. One is the above Linux
machine, one is a Windows 95 machine, and one is a Sun Sparc machine.
Hope this helps.
--
Frank Hahn
Bipolar, adj.:
Refers to someone who has homes in Nome, Alaska, and Buffalo,
New York
------------------------------
** 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
******************************
