On Mon, May 06, 2002 at 01:05:37PM -0400, Ramin Alidousti wrote: > On Mon, May 06, 2002 at 12:55:10PM -0400, Scottie wrote: > > > Don't know why this isn't working. > > > > eth0=10.0.0.117 > > eth1=192.168.0.10
<snip rules> > > eth0: > > 17:15:34.240233 66.162.8.121.1187 > 192.168.0.17.5800: S > > 982124692:982124692(0) win 32120 > > 17:15:34.249384 66.162.8.121.1187 > 192.168.0.17.5800: S > > 982124692:982124692(0) win 32120 > > 17:15:34.251384 192.168.0.17.5800 > 66.162.8.121.1187: S > > 1073543365:1073543365(0) ack 982124693 win 17520 > > 17:15:34.253385 66.162.8.121.1187 > 192.168.0.17.5800: R win 0 > > Here, 66.162.8.121 sends a reset. Why? IIRC hosts send a RST when they close the connection. It's to stop the other end getting around to answering one of the previous SYNs. <snip SYNs leaving eth1 correctly, as above, but without reply> > > Anyone have any wisdom for me? Possibly, run tcpdump or equivalent on 192.168.0.17 and see what's getting there, and whether it is replying, if at all. Also check the routing tables, I've a feeling it's either eating the packets due to firewalling, or because it doesn't know where to send the replies to due to incorrect routing. -- FunkyJesus System Administration Team
