On Sat, May 4, 2013 at 3:28 PM, Arun Khan <knu...@gmail.com> wrote: > On Sat, May 4, 2013 at 11:37 AM, s0lid <s0lid101...@gmail.com> wrote: >> i got this from tcpdump while pinging my gateway >> >> 14:06:31.172753 ARP, Request who-has 192.168.1.1 tell 192.168.1.106, length >> 28 >> 14:06:31.173851 ARP, Reply 192.168.1.1 is-at 40:4a:03:d6:ac:a9, length 46 >> 14:06:50.602659 IP 192.168.1.106 > 192.168.1.1: ICMP echo request, id >> 2563, seq 1, length 64 >> 14:06:51.611094 IP 192.168.1.106 > 192.168.1.1: ICMP echo request, id >> 2563, seq 2, length 64 >> 14:06:52.620045 IP 192.168.1.106 > 192.168.1.1: ICMP echo request, id >> 2563, seq 3, length 64 >> 14:06:53.626974 IP 192.168.1.106 > 192.168.1.1: ICMP echo request, id >> 2563, seq 4, length 64 > > Check if netmask is setup correctly in the server config (/sbin/ifconfig > eth1).
netmask looks fine root@debian:~# ifconfig eth1 eth1 Link encap:Ethernet HWaddr 08:00:27:59:31:76 inet addr:192.168.1.106 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::a00:27ff:fe59:3176/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:63 errors:0 dropped:0 overruns:0 frame:0 TX packets:103 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9615 (9.3 KiB) TX bytes:10143 (9.9 KiB) > > Can you do a static IP config for the server and check? Yes, same result with static. > > Any firewall rules in your gateway, to trap ping requests from a sub > net? (a shot in the dark). no firewall running root@debian:~# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination root@debian:~# -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANZ3Tp2w2N5C6ohfo-uEpQfVJu2d=b7jy2miid2gub7a624...@mail.gmail.com