I'm running Debian Woody, and am trying to access an application which is listening on a TCP/IP socket. The app is just a small http server, and I'm using a web browser to access it.
I know the app is listening on the expected port, because if I connect using a browser on the same machine that the server is running on, everything works fine. If I try to get to the same app from a different machine, though, I get "the connection was refused". If I run tcpdump on the server I see that using the browser on the local machine to access the service generates 11 packets over the expected port (via lo). The remote access generates only two packets (via eth0), one coming in with the the request, and the other (i guess) saying "the connection was refused". If I ask iptables what filtering is active, is tells me that everything is accepted. I've checked the nat filter and mangle tables. Clearly I'm missing something dead simple here. I have read the HOWTO for iptables and for IP in general, but I'm just not seeing the solution. Any hints, tips (or complete answers :-)) would be most appreciated. Thanks. BTW, here is the output from the tcpdump showing the bouncing request. Here is the tcpdump of the wally:~# tcpdump port 10045 tcpdump: listening on eth0 18:31:17.162927 alice.set.badgerse.com.53433 > wally.set.badgerse.com.10045: S 1628653908:1628653908(0) win 5840 <mss 1460,sackOK,timestamp 181054829 0,nop,wscale 0> (DF) 18:31:17.163010 wally.set.badgerse.com.10045 > alice.set.badgerse.com.53433: R 0:0(0) ack 1628653909 win 0 (DF) 2 packets received by filter 0 packets dropped by kernel -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
