TCP/IP Problem (strange)

TCP/IP Problem (strange)

Post by <notwork.. » Sat, 09 Oct 1999 04:00:00



Continuing problems.

Two boxes, one RH 6.0 one Slackware(old)/Win95. Both with Linksys Etherfast
10/100 NICs.

RH = 192.168.0.1
Win95 = 192.168.0.2

Having got the NIC to work in RH, I set the various networking params on
both boxes and tried a ping. No Luck.

So I fired up TCPDump on RH.  If I ping from Win95 (I used win95 for
testing, it's more expendable than the Slackware setup)  
I can see Arp req. for 192.168.0.1 go out and be answered by RH - however
Win95 obviously doesn't get reply, and hence ping fails.
If I ping from RH all I see are arp req. for 192.168.0.2 which are
never replied to.

The same happens if I fire the Win95 box up as Linux, but I'm much less
willing  to mess with the routing on that box, as it has a very nice
working diald, and my net connection, which I don't want to break.

Here's the IFConfig from the RH Box:

eth0      Link encap:Ethernet  HWaddr 00:A0:CC:34:89:47  
          inet addr:192.168.0.1  Bcast:192.168.0.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:186 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:10 Base address:0xf800

and its' Routing table.

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.0.1     *               255.255.255.255 UH    0      0        0
eth0
192.168.0.0     *               255.255.255.0   U     0      0        0
eth0
127.0.0.0       *               255.0.0.0       U     0      0        0 lo

Interestingly IFConfig for lo seems to increment TX & RX when I ping from
RH - so are some packets ending up on loopback by mistake???

Argh!

Help,Comments, Suggestions and more help welcomed.

------------------  Posted via CNET Linux Help  ------------------
                    http://www.searchlinux.com

 
 
 

1. strange TCP/IP connection problem with PPP in 2.1.5

I'm having a strange problem connecting between two FreeBSD 2.1.5
machines over a PPP link and I'm looking for some help.

I have an ethernet connected machine, and a second machine on a PPP
dialin connection through an Annex terminal server.  I can ping
from either end, but when I try to make a TCP/IP connection via
telnet, rsh or rlogin, the connection doesn't quite work.  The
symptoms seem to be that the Send-Q (from "netstat -a") seems to
build up a little bit:

Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)
tcp        0     37  PPP-dial.telnet        ether1.1043            ESTABLISHED

Proto Recv-Q Send-Q  Local Address          Foreign Address        (state)
tcp        0     27  ether1.uwaterloo.1043  PPP-dial.uwaterl.telne ESTABLISHED

and eventually the connection dies with

    select: protocol failure in circuit setup

(from rsh for example).

I can connect from non-FreeBSD machines just fine.  If I connect both
machines to the ethernet, it works fine.  I've tried 3 different machines,
and two different dialins in various combinations, with the same problems.
It seems to only happen between an ether FreeBSD and a PPP FreeBSD (at
least as far as I can determine).

Any suggestions, similar experiences, or information pointers would be much
appreciated.

Thanks!

John Sellens

2. can't compile libg++2.5.3

3. Strange TCP/IP problem

4. Drive Recommendations?

5. fnmatch() library call?

6. KDE start up????????

7. Help: Strange Tcp/Ip/Sun Ultra problem

8. Strange TCP/IP problem

9. strange problem with tcp/ip

10. Strange tcp/ip transfer problem

11. Ricochet MODEM in Linxu / Strange TCP-IP problems...