hi ya curtis
do my silly question is.. where is the machine called 10.0.1.1
that does not reply to pings ??
- if you know where 10.0.1.1 is... do the same set of commands
again ( route -nv, ifconfig -v, ipchains -L, etc
- the 10.0.1.1 machine should be able to ping itself
and should be ble to ping the local LAN and outside world
i am not 100% sure... but you might wanna turn off "null ipchains" rules
or at least have it pass all up ..
am assuming this is NOT the firewall and if it is... you're missing
all of the fw rules
c ya
alvin
On Thu, 10 Oct 2002, Curtis wrote:
> > hi ya curtis
> >
> > what is the output of
> >
> > root# route -nv
> Debian3800:~# route -nv
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 10.0.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 0.0.0.0 10.0.1.254 0.0.0.0 UG 0 0 0 eth0
>
> > root# ifconfig -v
> Debian3800:~# ifconfig -v
> eth0 Link encap:Ethernet HWaddr 00:10:A4:D2:DE:91
> inet addr:10.0.1.5 Bcast:10.0.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:30267475 errors:0 dropped:0 overruns:0 frame:0
> TX packets:157542 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:3128132587 (2.9 GiB) TX bytes:40244900 (38.3 MiB)
> Interrupt:11 Base address:0x4800
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:26119 errors:0 dropped:0 overruns:0 frame:0
> TX packets:26119 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:14695650 (14.0 MiB) TX bytes:14695650 (14.0 MiB)
>
> >
> > root# ipchains -L
> Debian3800:~# 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# ping 10.0.1.1
> > ( a local ping of itself should always work even w/o a cable )
> Debian3800:~# ping 10.0.1.1
> PING 10.0.1.1 (10.0.1.1): 56 data bytes
> (nothing else)
>
> >
> > am assuming you didn't manually turn off ping replies on the one host
> Right. Other computers can ping it.
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
