Quoting Stef Coene <stef.coene@docum.org>: ... snip ... But you have to make sure that the box you are trying to ping, has a route to you. So it knows where to send the answer to the ping. If i't doesn't know, you have to add a route on the target box or masqueing the packets. The hosts on the other side have default gateways, which are the interfaces of the linux-router. ... snip ... > tcpdump is not installed on this box. And the > iptables rules are disabled. In other words they > are all set to accept. If I use the iptables > command you suggest, will it actually log > anything? ipables -A INPUT -j LOG gives in /var/log/messages : Mar 24 16:16:03 lieve kernel: IN=eth0 OUT= MAC=00:a0:c9:1a:9c:eb:00:50:da:d0:d8:95:08:00 SRC=192.168.1.101 DST=192.168.1.100 LEN=164 TOS=0x00 PREC=0x00 TTL=64 ID=64662 DF PROTO=TCP SPT=3234 DPT=6000 WINDOW=63712 RES=0x00 ACK PSH URGP=0 Stef Okay, I don't know anything about iptables syntax, and very little about ipchains syntax either. I'll do that. Should I do the samething for the other chains (FORWARD, ACCEPT)? Thanks, kelly
