Am Sonntag, 24. Dezember 2000 12:59 schrieb Nate Amsden: > try commenting out everything in /etc/hosts.deny > > and putting: > > ALL : [EMAIL PROTECTED] > > in /etc/hosts.allow
Did it, no luck. > unix/linux seems to not to like to work in an enviornment where there is > no > DNS resolution, or more specifically name resolution in general > (i imagine there isn't in your case), if you want everything > to work perfectly i suggest you configure BIND with a dummy domain and > set your machines up to use it.(my dummy domain is ".aphro" and i have > machine names like internal-gate.aphro and desktop.aphro) > I dug myself deeper into this and I think it has to do with name-resolution. Using tcpdump I found: With plip: tcpdump: listening on plip0 13:10:31.369092 192.168.0.1 > 192.168.0.3: icmp: echo request 13:10:31.369157 192.168.0.3 > 192.168.0.1: icmp: echo reply 13:10:32.366987 192.168.0.1 > 192.168.0.3: icmp: echo request 13:10:32.367002 192.168.0.3 > 192.168.0.1: icmp: echo reply 13:10:33.366838 192.168.0.1 > 192.168.0.3: icmp: echo request 13:10:33.366851 192.168.0.3 > 192.168.0.1: icmp: echo reply 13:10:34.366719 192.168.0.1 > 192.168.0.3: icmp: echo request 13:10:34.366734 192.168.0.3 > 192.168.0.1: icmp: echo reply 13:10:37.095157 192.168.0.1.1026 > 192.168.0.3.telnet: S 2339045101:2339045101(0) win 32120 <mss 1460,sackOK,timestamp 28651[|tcp]> (DF) [tos 0x10] 13:10:37.095194 192.168.0.3.telnet > 192.168.0.1.1026: S 2365710079:2365710079(0) ack 2339045102 win 32120 <mss 1460,sackOK,timestamp 32804[|tcp]> (DF) 13:10:37.098295 192.168.0.1.1026 > 192.168.0.3.telnet: . ack 1 win 32120 <nop,nop,timestamp 28652 32804> (DF) [tos 0x10] 13:10:37.102226 192.168.0.3.1025 > 192.168.0.1.auth: S 2359395261:2359395261(0) win 32120 <mss 1460,sackOK,timestamp 32805[|tcp]> (DF) ... With eth: tcpdump: listening on eth0 13:14:57.314195 matthschulzg > 192.168.0.3: icmp: echo request 13:14:57.314235 192.168.0.3 > matthschulzg: icmp: echo reply 13:14:58.312838 matthschulzg > 192.168.0.3: icmp: echo request 13:14:58.312855 192.168.0.3 > matthschulzg: icmp: echo reply 13:14:59.312689 matthschulzg > 192.168.0.3: icmp: echo request 13:14:59.312698 192.168.0.3 > matthschulzg: icmp: echo reply 13:15:00.312569 matthschulzg > 192.168.0.3: icmp: echo request 13:15:00.312579 192.168.0.3 > matthschulzg: icmp: echo reply 13:15:02.313442 arp who-has matthschulzg tell 192.168.0.3 13:15:02.313737 arp reply matthschulzg is-at 0:e0:98:72:89:1d 13:15:04.423686 matthschulzg.1028 > 192.168.0.3.telnet: S 2610607868:2610607868(0) win 32120 <mss 1460,sackOK,timestamp 55388[|tcp]> (DF) [tos 0x10] 13:15:07.421669 matthschulzg.1028 > 192.168.0.3.telnet: S 2610607868:2610607868(0) win 32120 <mss 1460,sackOK,timestamp 55688[|tcp]> (DF) [tos 0x10] 12 packets received by filter 0 packets dropped by kernel The only difference I can see is 192.168.0.1.1026 vs. matthschulzg.1028. The 1026 and 1028 are the prcessnumbers on 192.168.0.1 right? So they are just to ignore!? 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? Where can I find some detailed info about arp? Matth
