Re: still no luck with ethernet between 2 computers

[matthschulz <matthschulz1@worldnet.att.net>]

Am Montag, 25. Dezember 2000 14:21 schrieben Sie:
> Matthias Schulz wrote:
> > But eth seems not to be able to resolve that matthschulzg is 192.168.0.1.
> > Yes it is in /etc/hosts though just as
> > 192.168.0.1     matthschulzg            . Is  this correct?
>
> take out the period if it is in /etc/hosts. also it may help(although it
> can break
> normal internet usage). 
It's not there. But it is not the problem either. I commented out the line 
for 192.168.0.1     matthschulzg and then tcpdump gave me the correct 
IP-address instead of the hostname - so 192.168.0.3 resolves 192.168.0.1 
correct into matthschulzg.
> edit /etc/nsswitch.conf and find the line that
> says hosts:
> on it, and remove everything after the word hosts: except the word
> files. not all
> programs use this file but maybe inetd does. or you can try removing
> tcp_wrappers
> from inetd by deleting the part of the line that has /usr/sbin/tcpd (or
> whatever its called) and restart inetd to see if that does it.
Did it, rebooted no change.

Used tcpdump -vvv in the meantime.

with plip:
21:18:36.347694 192.168.0.1.1027 > 192.168.0.3.telnet: S 
3184875831:3184875831(0) win 32120 <mss 1460,sackOK,timestamp 740469[|tcp]> 
(DF) [tos 0x10] (ttl 64, id 43)
21:18:36.347828 192.168.0.3.telnet > 192.168.0.1.1027: S 
3210480529:3210480529(0) ack 3184875832 win 32120 <mss 1460,sackOK,timestamp 
416764[|tcp]> (DF) (ttl 64, id 47)
...

with eth:
21:19:52.417077 matthschulzg.1028 > 192.168.0.3.telnet: S 
3274468432:3274468432(0) win 32120 <mss 1460,sackOK,timestamp 748077[|tcp]> 
(DF) [tos 0x10] (ttl 64, id 64)
21:19:55.407388 matthschulzg.1028 > 192.168.0.3.telnet: S 
3274468432:3274468432(0) win 32120 <mss 1460,sackOK,timestamp 748377[|tcp]> 
(DF) [tos 0x10] (ttl 64, id 65)
21:19:57.407107 arp who-has 192.168.0.3 tell matthschulzg
21:19:57.407124 arp reply 192.168.0.3 is-at 39:48:39:48:39:48


Should the (ttl 64, id 43)(plip) vs. (ttl 64, id 65)(eth) have to do with 
that?
Remember with plip it works fine - with eth not -- On the same machines!!!!!
Ping works fine with both!!!!!
That's real strange to me. I was thinking: just put the eth-cards in and 
replace the plip-hardwarelink with something else You will not have to 
struggle with networksettings at all. I was terribly wrong!!!!
BTW the eth-cards decided to work in 100Mbit-mode, anything wrong about that??

I'm about to give up and continue to use plip, but the parport switched 
around with the dataswitch really sucks.

Thanks for Your help anyway.

Matth

Matth