Linux-Networking Digest #690, Volume #9 Sun, 27 Dec 98 18:13:46 EST
Contents:
Re: NetGear config problem (Dale Miracle)
Re: Networking Linux and Windows (Kevin Martin)
Linux Dialup Server (Josh Gentry)
Re: PPP Dialin with RH 5.2? ("Charles Stack")
How to enable networking support, especiallyTCP/IP??? ("MC Ginting")
Reverse DNS lookup with IP Masquerading (Colin Durocher)
PPP (Looja Tuladhar)
Re: Linux Dialup Server ("Charles Stack")
Re: eql_enslave cannot find libc.so.4? (Kaz Morishita)
Linux Dial-up server (Josh Gentry)
Re: ppp daemon died unexpectedly (Marc)
Re: firewall tool for linux? (Paul B. Brown)
Re: TCP/IP between Linux and Win95 problem... :-( (Stuart R. Fuller)
Re: Connecting to the @Home network/General network configuration (Stuart R. Fuller)
Re: TCP/IP between Linux and Win95 problem... :-( (Stuart R. Fuller)
----------------------------------------------------------------------------
From: Dale Miracle <[EMAIL PROTECTED]>
Subject: Re: NetGear config problem
Date: Sun, 27 Dec 1998 12:32:53 -0500
GenaBlu wrote:
> Hello!
>
> I just installed Linux RedHat 5.1 in a new server (AMD K6/350 MHz/8.2 GB HD/64
> MB RAM). The configuration went very smoothly until I rebooted. I have an
> Ethernet NetGear adapter. I chose the 'tulip' chip set for compatibility, same
> as my other Linux boxes. The IP configuration parameters are accurate. Every
> time I boot, and every few seconds afterward I get the message:
>
> eth0: transmit timed out, status 06061000, CSR12 00000035, resetting...
>
> I obviously can't ping this server nor connect from it to the rest of my net.
> Please help?
>
> Thanks!
>
> G.
I have 3 of those cards running, I used the tulip.c from the driver disk that came
with the card. I didn't have good luck with the tulip.c that comes with the
kernel. You can download the drivers off of netgear's web site @
http://netgear.baynetworks.com/support/
You should see it listed along with their other products.
--
Dale Miracle "No matter where you go, there you are",
System Administrator Oliver's Law of Location
The Edge of Insanity "Real funny Scotty, now beam down my
[EMAIL PROTECTED] clothes"
"I've gone to look for my self, if I return before I get
back keep me here."
------------------------------
From: [EMAIL PROTECTED] (Kevin Martin)
Crossposted-To: alt.os.linux
Subject: Re: Networking Linux and Windows
Date: Sun, 27 Dec 1998 16:19:36 GMT
alt.os.linux snecked -- does it even exist anymore?
In article <[EMAIL PROTECTED]>, it says Todd Smith
<[EMAIL PROTECTED]> wrote:
>I have a windows95 machine and a linux machine. I also have a 2 3com
>10baseT ethernet cards and a hub. I need help getting linux set up to
>use the hub and to be seen on the network by my windows machine.
Three things all going on at once here, Todd. Might help to
break them out separate.
1) Recognizing the card: You need to know the model a bit more precisely,
but it's a safe bet that it'll be supported. You have the usual hooraw
about addresses and IRQ's that any PC hardware is heir to. Stick it into
your Linux box and configure the kernel to realize that it's there.
You also get the fun of installing the card in the Windows box. Not our
problem. (Or as the old cartoon goes, sixty feet of blackboard full of
complicated mathematical scribbling and flowcharts, then a cloud with the
words "And then a MIRACLE happens!" "Uh, Doctor, I think you need to do a
little more work here.")
I did my scribbling at http://www.nic.com/~cannon/Linux/
2) Sharing the Linux and Win resources: the magic word is "SAMBA" or smb.
On the Linux box, look at "man smbmount" and all the documents that it
mentions as being "related."
> I would
>also like my windows machine to dial up to the internet and have linux
>get access to the net from across the network. Thanks for any help
3) NAT, or gatewaying: Your thinking is bass-ackwards, IMHonestO. Make
the Linux box dial out and provide Internet access on demand to your Windows
box with "IP masquerade".
If you insist on doing it the other, unnatural and perverted way, you can
get a commercial product called Sygate that will do it, or a free two-user
license for something called Wingate -- but in that case, you're in the
wrong newsgroup, since neither of those are Linux-specific or even
Linux-oriented. If you want to do it the right way, with the Linux box
doing the heavy lifting, the Web page above should get you on track.
--
Kevin Martin No-spam zone.
<brasscannon No prisoners. No warning shots.
@usa.net>
------------------------------
From: [EMAIL PROTECTED] (Josh Gentry)
Subject: Linux Dialup Server
Date: Sun, 27 Dec 1998 10:49:24 -0800
Folks,
I would expect that lots of people out there are needing to set up Linux
dialup servers. I recently
completed this task, and have written a report of the process. You can find
it at:
http://www.swcp.com/~jgentry/ppp.html
*** Posted from RemarQ - http://www.remarq.com - Discussions Start Here (tm) ***
------------------------------
From: "Charles Stack" <[EMAIL PROTECTED]>
Subject: Re: PPP Dialin with RH 5.2?
Date: Sun, 27 Dec 1998 13:56:08 -0500
I have mgetty and have looked at the documentation..that's why I am asking
for help.
What needs to be modified and how to get mgetty to run?
How do I get mgetty to reactivate after my dialing connection is terminated?
How, after I have logged in, can I assign a TCP/IP address to the
connection?
These are the kind of questions that the mgetty documentation doesn't
answer -- or now clearly enough.
It would be nice if someone wrote a "How-to" on this subject as I see it
posted frequently enough...but seldom see an adequate answer.
I know there are others who have gone through this trial or have the
knowledge and it is is their knowledge that I would like to tap so I can
learn from them.
Charles
William R. Mattil wrote in message <[EMAIL PROTECTED]>...
>Charles Stack wrote:
>>
>> Can someone point me in the right direction on how to configure my linux
box
>> (RH 5.2) for dialin access using ppp? Initially, I'm willing to settle
for
>> static IP's for my dial-in clients (per TTY). Eventually, I may switch
to
>> dynamic IP address. But, static IPs are fine for now.
>>
>> I've tried looking for info on mgetty and I even tried the RH linuxconf's
>> version of a ppp account. The information I found is scanty and the
linux
>> box doesn't answer the incoming call. My kernel has been compiled with
IP
>> Forwarding, IP Aliasing, and IP Mascarading support.
>
>
>All you really need is to find the mgetty package and read the
>documentation.
>It is probably one of the better documented packages available.
>
>Bill
>
>--
>William R. Mattil | Fred Astaire wasn't so great.
>[EMAIL PROTECTED] | Ginger had to do it all backwards
>(972) 399-4106 | and... in high heels.
------------------------------
From: "MC Ginting" <[EMAIL PROTECTED]>
Subject: How to enable networking support, especiallyTCP/IP???
Date: Sun, 27 Dec 1998 22:16:12 GMT
Finally, my PPP connection almost work. But I still have a big problem. I
can not use FTP, telnet, ping etc. Always give me "unknown host" message.
Also, when I type "dmesg |less", I could not find the word "TCP". It gave
the word "CSLIP". I guess my linux kernel does not support TCP service. Does
anybody know how to enable networking support, especially TCP/IP?
Thanks in advance..
MC Ginting
------------------------------
From: Colin Durocher <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Reverse DNS lookup with IP Masquerading
Date: Sun, 27 Dec 1998 22:17:18 GMT
Hi there,
I just networked the computers in my home and set up ip_masquerading so
that the kids' computers could use my cable modem internet access. I'm
now wondering if there is a program available (or alternatively, one I
could write) that will allow me to monitor the names of the websites
that are accessed through that connection. I figure there must be some
way of keeping a list of the external ip addresses that are accessed and
then doing a reverse DNS lookup to find the names. From there, I could
just scan for certain keywords.
Any help would be very much appreciated,
Colin
P.S. please respond by email to [EMAIL PROTECTED]
------------------------------
From: Looja Tuladhar <[EMAIL PROTECTED]>
Subject: PPP
Date: Sun, 27 Dec 1998 11:01:29 -0800
I have this weird error when I use PPP to connect to my ISP (mindspring).
The dialing works fine. The login goes fine. Right after the login works,
the connection dies. Has anyone encountered this, know what might be
happening?
Same thing happens whether I use minicom or the netcfg control panel.
Oh I'm running redhat 5.2 BTW.
Looja Tuladhar Phone: 650-757-8605
850 Campus Dr #107 [EMAIL PROTECTED]
Daly City, CA 94015 http://cs.stanford.edu/~looza
------------------------------
From: "Charles Stack" <[EMAIL PROTECTED]>
Subject: Re: Linux Dialup Server
Date: Sun, 27 Dec 1998 14:10:32 -0500
Thanks, Josh! This is exactly what I've been asking for!
Charles
Josh Gentry wrote in message ...
>Folks,
>
>I would expect that lots of people out there are needing to set up Linux
>dialup servers. I recently
>completed this task, and have written a report of the process. You can
find
>it at:
>
>http://www.swcp.com/~jgentry/ppp.html
>
>
>
>*** Posted from RemarQ - http://www.remarq.com - Discussions Start Here
(tm) ***
------------------------------
Date: Sun, 27 Dec 1998 11:13:33 -0800
From: Kaz Morishita <[EMAIL PROTECTED]>
Subject: Re: eql_enslave cannot find libc.so.4?
Don't know if this helps, but do you have a line:
/usr/i486-linuxaout/lib
in your /etc/ld.so.conf file?
BTW, what version of eql and linux are you using at home and work?
Kaz
On Sun, 27 Dec 1998, Jon & Barry Gilman wrote:
> Hello everyone and Happy Holidays!
>
> I have been beating my head against the wall trying to figure out
> why I get the following message after issuing the command, eql_enslave
> ppp1 mtu xxx (where xxx is the mtu number):
>
> The message reads as follows: libc.so.4 cannot be
> found......
>
> Does anyone know how to get rid of this message? ie. putting this
> library in the right place or re-compiling this utility so it knows
> where to find the library?
>
> Here is a list of what I have tried so far......
> I can use this utility on my home machine so and I have located the
> libc.so.4 library. It is found in /usr/i486-linuxaout.....Therefore, I
> made this directory at work and filled it with the all the libraries
> from my home machine.....As you may have guessed this did not work.
> Next, I tried moving the file into the same directory as the
> utility....Again, no luck.....
>
> So, now I'm out of ideas. HELP! Thanks!
> Sincerely,
> Brian
> Gilman
>
>
>
------------------------------
From: [EMAIL PROTECTED] (Josh Gentry)
Subject: Linux Dial-up server
Date: Sun, 27 Dec 1998 10:47:18 -0800
You asked about a Linux dailup server. I have written a report of how I set
up a Linux daiup as a project
for school. You can read it at
http://www.swcp.com/~jgentry/ppp.html
*** Posted from RemarQ - http://www.remarq.com - Discussions Start Here (tm) ***
------------------------------
From: Marc <[EMAIL PROTECTED]>
Crossposted-To: alt.linux,alt.os.linux
Subject: Re: ppp daemon died unexpectedly
Date: Sun, 27 Dec 1998 22:36:38 GMT
Usually this is caused by the fact that your ISP is using something like an NT
server for remote authentication, NT and certain other boxes have no login
prompt they use the challenge handshake authentication protocol (Trust
microsoft to come up with something like this ;) ) if this is the case then
you need to set up a connection to use CHAP (I'm not exactly sure how to do
it,,I beleive that KPPP allows you to choose CHAP as a authentication method
in the account setup) but that is what was causing that error for me.
unfortunatly the way I solved it was to switch ISP's :)
Hope this helps, I'd be glad to help ya any way I can,,,remove the Z's from my
email address to get my real address !
Marc
Tom Hennen wrote:
> Every time pppd runs I get the error ppp daemon died unexpectedly, it does
> not matter if I use 'netcfg' or 'Kppp' or 'ezppp' I always get that error.
> If anyone can help me I would appreciate it.
>
> (Please respond via e-mail as well, thank you)
> --
> Tom Hennen III
> On TRACK www.on-track.org
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED] (Paul B. Brown)
Crossposted-To: comp.security.firewalls
Subject: Re: firewall tool for linux?
Date: 27 Dec 1998 19:16:56 GMT
James,
Actually, that's a good question. It's a bit tricky because it involves
a number of issues. Let me see if I can make it clear. Hummm . . . where
to begin . . . .
What you are about to read is a synopsis of how our theoretical network is
setup. Plough through it and please ask questions if you do not understand
something.
Our Theoretical Network:
=======================
192.168.1.x 207.54.15.y 207.54.12.x
| | |
------- | | |
| | x=2 v | |
| B |::::::: | |
| | eth0 : | |
------- : ------- | |
: x=1 | | y=6 v v z=5
:::::::| A |::::::::{modem}::::::::{modem}:::::::[TS]
: eth0 | | ppp0
------- : -------
| | eth0 :
| C |:::::::
| | x=3
-------
A = Our firewall
B = A host inside our protected network
C = Another host inside our protected network
x = The fourth octet in our 192.166.1.0/24 private address space
y = The fourth octet in the 207.54.15.0/24 public address space at our ISP
z = The fourth octet in the 207.54.12.x/24 public address space at our ISP
ppp0 = Our modem interface that we use to connect to our ISP
eth0 = Our internal network connectivity interface
TS = Our ISP's Terminal Server
NOTES:
1. All hosts in your private network use the 10BaseT eth0 interface for LAN
connectivity.
2. Your firewall (A) uses an analog connection to the Internet via a modem
and PPP, thus the public interface of the firewall (A) is ppp0. Of
course, you can easily substitute another interface, such as eth1, if
another connection method is used. Cable modems, xDSL routers, Frame
Relay, PtP T1, etc, etc, ad nausium.
3. I assume that we have a static IP address to use that was provided by
our ISP.
That's the picture of how this are. What's next is the routing on each
host in our network so things work at TCP/IP stack layers 1 (physical) and
2 (data link).
Static routes our Firewall (A), interfaces eth0 and ppp0:
========================================================
Destination Gateway Genmask Flags Metric Window Use Iface
207.54.12.5 * 255.255.255.255 UH 0 0 124 ppp0
192.168.1.0 * 255.255.255.0 U 0 0 2 eth0
127.0.0.0 * 255.0.0.0 U 0 0 5 lo
default 207.54.12.5 * UG 0 0 1970 ppp0
Notice that all traffic destined for 192.168.1.0/24 is heading out our
eth0 port. Anything destined for the terminal server on the other side
of our connection is heading out our PPP port. Ignoring the loopback (lo)
interface, all other traffic goes out the ppp0 interface. Make since??
You can setup our loopback interface as follows:
/sbin/ifconfig lo 127.0.0.1
/sbin/route add -net 127.0.0.0
You can setup our eth0 interface as follows:
/sbin/ifconfig eth0 192.168.1.1 \
broadcast 192.168.1.255 \
netmask 255.255.255.0 \
up
/sbin/route add -net 192.168.1.0 netmask 255.255.255.0
Our ppp0 interface and route statements will be setup when we initiate
the ppp connection. Something like this:
================================= ppp=on ==================================
DIALER_SCRIPT=/etc/ppp/ppp-on-dialer
TELEPHONE=555-1212 # The only telephone number
ACCOUNT=username # The account name for logon
PASSWORD=password # The password for this account
LOCAL_IP=207.54.15.6 # Local IP address if known. Dynamic = 0.0.0.0
REMOTE_IP=0.0.0.0 # Remote IP address if desired. Normally 0.0.0.0
NETMASK=255.255.255.0 # The proper netmask if needed
export TELEPHONE ACCOUNT PASSWORD
exec /usr/sbin/pppd debug lock modem crtscts /dev/ttyS1 38400 \
asyncmap 20A0000 escape FF kdebug 0 $LOCAL_IP:$REMOTE_IP \
noipdefault netmask $NETMASK defaultroute connect $DIALER_SCRIPT
===========================================================================
Notice the "defaultroute" variable in the pppd command? That's what sets
up the default route statement. Also notice the REMOTE_IP is 0.0.0.0.
That's because pppd will negotiate this with the pppd on the other side
and set it up automatically. Neat, huh?
============================ ppp=on=dialer ================================
exec chat -v \
TIMEOUT 3 \
ABORT '\nBUSY\r' \
ABORT '\nNO ANSWER\r' \
ABORT '\nRINGING\r\n\r\nRINGING\r' \
'' \rAT \
'OK-+++\c-OK' ATH0 \
TIMEOUT 60 \
OK ATE1Q0S0=0M0DT$TELEPHONE \
CONNECT '' \
ogin:--ogin: $ACCOUNT \
assword: \\q$PASSWORD
===========================================================================
Static routes on host B, interface eth0:
=======================================
Destination Gateway Genmask Flags Metric Window Use Iface
192.168.1.1 * 255.255.255.0 U 0 0 2 eth0
127.0.0.0 * 255.0.0.0 U 0 0 5 lo
default 192.168.1.1 * UG 0 0 1970 eth0
Notice that all traffic heads for the gateway 192.168.1.1.
We can setup our loopback interface as follows:
/sbin/ifconfig lo 127.0.0.1
/sbin/route add -net 127.0.0.0
We can setup our eth0 interface and default route as follows:
/sbin/ifconfig eth0 192.168.1.2 \
broadcast 192.168.1.255 \
netmask 255.255.255.0 \
up
/sbin/route add -net 192.168.1.0 netmask 255.255.255.0
/sbin/route add default gw 192.168.1.1 metric 1
Static routes on host C, interface eth0:
=======================================
Destination Gateway Genmask Flags Metric Window Use Iface
192.168.1.1 * 255.255.255.0 U 0 0 2 eth0
127.0.0.0 * 255.0.0.0 U 0 0 5 lo
default 192.168.1.1 * UG 0 0 1970 eth0
Notice that all traffic heads for the gateway 192.168.1.1.
We can setup our loopback interface as follows:
/sbin/ifconfig lo 127.0.0.1
/sbin/route add -net 127.0.0.0
We can setup our eth0 interface and default route as follows:
/sbin/ifconfig eth0 192.168.1.3 \
broadcast 192.168.1.255 \
netmask 255.255.255.0 \
up
/sbin/route add -net 192.168.1.0 netmask 255.255.255.0
/sbin/route add default gw 192.168.1.1 metric 1
Whew . . . OK . . . that was the tough part. If things are working well,
then we can begin to think of a security policy that will make since in
our situation. Make sure, once the connectivity has been established,
tested, and verified, that you create a security policy. Here is one
that's pretty basic for any small business:
Security Policy:
===============
* Allow only the following outbound TCP connections:
Telnet from 192.168.1.0/24 to 0.0.0.0/0
FTP from 192.168.1.0/24 to 0.0.0.0/0
NNTP from 192.168.1.0/24 to 0.0.0.0/0 (UseNet News)
SNTP from 192.168.1.0/24 to 0.0.0.0/0 (Network Time Protocol)
HTTP from 192.168.1.0/24 to 0.0.0.0/0
SHTTP from 192.168.1.0/24 to 0.0.0.0/0
SSL from 192.168.1.0/24 to 0.0.0.0/0
SMTP from 192.168.1.0/24 to 0.0.0.0/0
Finger from 192.168.1.0/24 to 0.0.0.0/0
Whois from 192.168.1.0/24 to 0.0.0.0/0
* Allow only the following inbound TCP connections:
FTP from 0.0.0.0/0 to 192.168.1.2
SMTP from 0.0.0.0/0 to 192.168.1.2
HTTP from 0.0.0.0/0 to 192.168.1.2
* Allow only the following outbound UDP connections:
SNTP from 192.168.1.0/24 to 0.0.0.0/0
DNS from 192.168.1.0/24 to 0.0.0.0/0
* Allow only the following inbound UDP connections:
SNTP from 0.0.0.0/0 to 192.168.1.0/24
DNS from 0.0.0.0/0 to 192.168.1.0/24
* Allow only the following outbound ICMP connections:
Echo Request from 192.168.1.0/24 to 0.0.0.0/0
Echo Reply from 192.168.1.0/24 to 0.0.0.0/0
Traceroute from 192.168.1.0/24 to 0.0.0.0/0
* Allow only the following inbound ICMP connections:
Echo Request from 0.0.0.0/0 to 192.168.1.0/24
Echo Reply from 0.0.0.0/0 to 192.168.1.0/24
Traceroute from 0.0.0.0/0 to 192.168.1.0/24
* Deny all other inbound and outbound TCP, UDP, and ICMP traffic.
Any from 0.0.0.0/0 to 0.0.0.0/0
NOTES:
=====
1. 0.0.0.0/0: any destination
2. Bear in mind that you must destinguish between TCP, UDP, and ICMP when
making your policies. If you want to get real sophisticated then you
can plan for RIP, RIP2, EGRP, HEGRP, etc, etc, ad nausium.
So, what does this policy boil down to? Basically, the users in our
network can cruise the web, do e-mail, ftp files, read news, keep their
computer's clock accurate, do finger, whois, ping, traceroute, and do
secure transactions on the Internet. Also, we allow DNS to operate.
As a small business, we allow anyone from outside to ftp to our ftp
server (B), web surf on our web site (B), and send e-mail to our users (B).
Everything else is not allowed.
We would now use our packet filter (IP Chains) and our proxy filters (TIS)
to build these rules. You can use the source and destinations as they are
given above to allow/deny the various protocols.
Finally, to answer you question, when you create your policy, you will be
specifying which protocols and hosts/networks are allowed or denied.
If you have any questions. please let me know.
Enjoy! :-)
Paul
===========================================================================
Paul B. Brown [EMAIL PROTECTED]
President
Brown Technologies Network, Inc. http://www.btechnet.com/
Unix Systems Administration "Sailing is a state of mind . . . ."
===========================================================================
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (James Ho) writes:
>On 26 Dec 1998 20:21:56 GMT, [EMAIL PROTECTED] (Paul B. Brown)
>wrote:
>
>Sorry if my question sounds stupid since I am a newbie in
>networking/linux.
>
>For the packet filters, how would I know what source/dest to allow and
>what to deny?
>
>James.
>
>>Jan,
>>
>>There are two types of firewalls. Alone, neither of them are solid
>>protection against a persistant and knowledgable cracker. Together,
>>however, they are formitable. Properly setup, it can defeat pretty much
>>any attack long enough for you to be notified of the attack so you
>>can take action against the perps.
>>
>>Two Firewalls:
>>-------------
>>
>>1 Packet Filters: These firewalls will allow to to reject/allow packets
>> in and out of your network based on source/destination
>> IP addresses and source/destination ports. They work
>> between the data link and IP layers of the TCP/IP
>> stack.
>>
>>2 Proxy Filters.: These firewalls insert a piece of software between the
>> service inside the protected network and the big, bad
>> wolf (Internet). Lets take web services as an example.
>> Your web browser will actually ask the firewall to
>> connect to a site and download the page. The firewall
>> will then pass the page back to you. In this way, you
>> the user, hides behind the firewall so you cannot be
>> touched. These firewalls work at the application layer
>> of the TCP/IP stack.
>>
>>Putting those two types of firewalls together will allow you to create a
>>strong security policy. Use the packet filter to allow only those
>>networks and hosts that are trusted access to and from your proctected
>>network and shutdown all unused ports. Use the proxies to hide the users
>>allowed access through the firewall via the allowed services.
>>
>>They only real question is: Do you want both types of firewalls on loaded
>>or do you want to separate the firewalls into separate boxes. Hummmm.
>>
>>Anyway to actually answer your question: ;->
>>
>>Use IP Chains as the packet filter and either TIS or SOCKS as the Proxy
>>filter.
>>
>>Nuff said? ;->
>>
>>Paul
>>
>>>i need to setup a firewall on a linux machine. the firewall should
>>>be an intelligent packet filter not a proxy.
>>>
>>>question: which package should i take?
>>>
>>>there are:
>>>* the sinus firewall tool (http://www.ifi.unizh.ch/ikm/SINUS/firewall/)
>>>* ipfwadm
>>>* ipchains
>>>* tis ?
>>>* ...
>>>
>>>has anyone made some experience with the packs?
------------------------------
From: [EMAIL PROTECTED] (Stuart R. Fuller)
Subject: Re: TCP/IP between Linux and Win95 problem... :-(
Crossposted-To:
linux.redhat.axp,linux.redhat.install,linux.redhat.list,linux.redhat.misc,comp.os.linux.misc,comp.os.linux.setup
Reply-To: [EMAIL PROTECTED]
Date: Sun, 27 Dec 1998 22:58:34 GMT
Travis Kelley ([EMAIL PROTECTED]) wrote:
: check your network cable itself..how fast is your linux box...I'm assuming that it
: is fast enough to handle the packets...also make sure that you have irq and base
: address settings right on both cards
Also, make sure the W95 box is fast enough to handle the packets. Sheesh!
------------------------------
From: [EMAIL PROTECTED] (Stuart R. Fuller)
Subject: Re: Connecting to the @Home network/General network configuration
Crossposted-To: comp.os.linux.help
Reply-To: [EMAIL PROTECTED]
Date: Sun, 27 Dec 1998 22:58:35 GMT
Stephen Hladek ([EMAIL PROTECTED]) wrote:
: Ifconfig returns the following:
:
: 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:25 errors: 0 dropped:0 overruns:0 frame:0
: TX packets:25 errors:0 dropped:0 overruns:0 carrier: 0 collisions:0
:
: eth0 Link encap:Ethernet HWAddr FF:FF:FF:FF:FF:FF
: inet addr:24.3.137.85 Bcast:24.3.137.255 Mask: 255.255.255.0
: UP BROADCAST RUNNINH MULTICAST MTU:1500 Metric:1
: RX Packets: 0 errors:0 dropped:0 overruns:3825 frame:0
: TX packets:15345 errors:0 dropped:0 overruns:0 carrier:11475
: collisions:3825
: Interrupt:10 Base address:0xb800
:
: When I ping the gateway... it stalls.. until I have to press ctrl-c to exit.
In your original post, you said your IP address was 24.3.137.123. The above
ifconfig output says that your IP address is "inet addr:24.3.137.85". I'd
start by fixing that.
Once that's fixed, I'd be concerned with your HW Addr of all 'F's. Then, I'd
look at your collision rate.
Stu
------------------------------
From: [EMAIL PROTECTED] (Stuart R. Fuller)
Subject: Re: TCP/IP between Linux and Win95 problem... :-(
Crossposted-To:
linux.redhat.axp,linux.redhat.install,linux.redhat.list,linux.redhat.misc,comp.os.linux.misc,comp.os.linux.setup
Reply-To: [EMAIL PROTECTED]
Date: Sun, 27 Dec 1998 22:58:34 GMT
Raymond Dobbs ([EMAIL PROTECTED]) wrote:
: Hint:
:
: Never use 0 anywhere in a machine's assigned IP address
:
: 0 is reserved to indicate a NETWORK WIDE broadcast. Use a 1 -254 =
: instead. 255 is a no-no too...
Actually, it's never use 0 in the host address portion of an IP address. That
is, 192.168.0.1 (with a netmask of 255.255.255.0), but 192.168.1.0 (with the
same netmask) is NOT OK. The latter form is used to reference the network.
Also, having the host address portion of the IP address set to all 1s is the
common way to indicate a network wide broadcast. Using the above example,
192.168.0.255 would be the broadcast address for the 192.168.0 network.
Stu
------------------------------
** 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
******************************
