[ale] routing and networking

[Nick Lucent]

On Sat, 10 Apr 1999, Tri wrote:

> I'm using a netgear FA310TX with the tulip driver. Do you see any potential
> problems?

It should work, check ifconfig and check for collisions and errors, if
they are excessive then its bad hardware. Ive only been half way paying
attention to this thread, so I missed quite a bit of it, if you would like
then mail me the problems (offlist) again and Ill try to help you get it
straightened out.

Nick

> Tri
> -----Original Message-----
> From: Nick Lucent <nlucent at mindspring.com>
> To: Tri <merlintm at bellsouth.net>
> Cc: ale at ale.org <ale at ale.org>
> Date: Saturday, April 10, 1999 6:34 PM
> Subject: Re: [ale] routing and networking
> 
> 
> >On Sat, 10 Apr 1999, Tri wrote:
> >
> >This kind of looks like you either have a bad network card, bad cable or
> >bad hub, like maybe the data is being corrupted. I got all those 13 14 15
> >errors once but I think that was a bad driver (ne2kpci). Im currently
> >using tulip on a linksys 10/100 card w/o problems.
> >
> >Nick
> >
> >
> >> I also get this when I ping the other computer:
> >> PING 192.168.1.2 (192.168.1.2): 56 data bytes
> >> 64 bytes from 192.168.1.2: icmp_seq=1 ttl=255 time=0.3 ms
> >> wrong data byte #10 should be 0xa but was 0x9
> >>  13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a
> 2b
> >> 2c 2d 2e 2f 30 31 32
> >>  33 34 35 36 0 0 0 0 0 0 0 0 0 0 0 0
> >> 64 bytes from 192.168.1.2: icmp_seq=2 ttl=255 time=0.3 ms
> >> wrong data byte #14 should be 0xe but was 0xd
> >>  13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a
> 2b
> >> 2c 2d 2e 2f 30 31 32
> >>  33 34 35 36 0 0 0 0 0 0 0 0 0 0 0 0
> >>
> >> --- 192.168.1.2 ping statistics ---
> >> 5 packets transmitted, 2 packets received, 60% packet loss
> >> round-trip min/avg/max = 0.3/0.3/0.3 ms
> >>
> >> Something tells me this isn't right. ;-)
> >>
> >> Tri
> >>
> >> -----Original Message-----
> >> From: Venkatesh Dattathri <venkat at csl.uta.edu>
> >> To: ale at ale.org <ale at ale.org>
> >> Date: Saturday, April 10, 1999 3:49 PM
> >> Subject: Re: [ale] routing and networking
> >>
> >>
> >> >
> >> >Hi Tri,
> >> >
> >> >
> >> >On Sat, 10 Apr 1999, Tri wrote:
> >> >
> >> >> >From Tri:
> >> >> Here's more info about the situation
> >> >>
> >> >> Here is what I get from netstat -nr:
> >> >> Kernel IP routing table
> >> >> Destination     Gateway         Genmask         Flags   MSS Window
> irtt
> >> >> Iface
> >> >> 192.168.1.0     0.0.0.0         255.255.255.0   U                0 0
> >> >> 0  eth0
> >> >>
> >> >> Here's what I get from ifconfig eth0:
> >> >> eth0      Link encap:Ethernet  HWaddr 00:A0:CC:3B:22:5E
> >> >>           inet addr:192.168.1.1  Bcast:192.168.1.255
> Mask:255.255.255.0
> >> >>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >> >>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> >> >>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> >> >>           Collisions:0
> >> >>           Interrupt:10 Base address:0xb000
> >> >>
> >> >
> >> >
> >> >The RX and TX packets should not be 0 . it should be some number, and
> only
> >> >then can you connect to other systems ..( i don't know why it is so or
> >> >what the significance is..)
> >> >
> >> >
> >> >Also, take a look at the attached Howto.. it may help..
> >> >
> >> >> And this might help also, this is my init network script under debian
> >> 2.1:
> >> >>
> >> >> #! /bin/sh
> >> >> ifconfig lo 127.0.0.1
> >> >> route add -net 127.0.0.0 lo
> >> >> ifconfig eth0 192.168.1.1 netmask 255.255.255.0 up
> >> >>
> >> >> I know the route command for eth0 is missing, but the kernel sets one
> up
> >> >> automatically.
> >> >>
> >> >
> >> >I suggest you try having a route add command for eth0 in your init
> script.
> >> >
> >> >
> >> >> Tri
> >> >>
> >> >> -----Original Message-----
> >> >> From: Eric Ayers <eric.ayers at mindspring.com>
> >> >> To: Tri <merlintm at bellsouth.net>
> >> >> Date: Saturday, April 10, 1999 7:50 AM
> >> >> Subject: Re: [ale] routing and networking
> >> >>
> >> >>
> >> >> >Tri wrote:
> >> >> >>
> >> >> >> When I try to telnet into a second computer(192.168.1.2) on my
> >> network,
> >> >> >> telnet returns a message that says it can't reach the host since
> there
> >> is
> >> >> no
> >> >> >> route to the host. However my routing table indicates that indeed
> >> there
> >> >> is a
> >> >> >> route to every machine on the 192.168.1.0 network. I am using
> kernel
> >> >> 2.2.5,
> >> >> >> the route was set automatically by the kernel when I used:
> >> >> >> ifconfig eth0 192.168.1.1 netmask 255.255.255.0 up
> >> >> >> to set up my network card. I am sure that my drivers are loaded
> >> correctly
> >> >> >> and the second machine is also using the same kernel version and
> >> >> configured
> >> >> >> the same way( except for the ip address of course) Any Ideas on why
> >> this
> >> >> is
> >> >> >> happening. I am using the tulip driver.
> >> >> >> Tri
> >> >> >
> >> >> >
> >> >> >why don't you mail the output of:
> >> >> >
> >> >> >netstat -nr
> >> >> >and
> >> >> >ifconfig eth0
> >> >> >
> >> >> >on both machines to the list?
> >> >> >
> >> >>
> >> >
> >> >
> >>
> >
> >
>