-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 27 Aug 2001, Peter Jay Salzman wrote:
> make sure you understand that tcpdump tells you which direction the
> packets are going. basically, what you're looking for is:
>
> 1. ping packets coming from the internal machine being received by the gw's
> internal nic.
>
> if that works, you're looking for...
>
> 2. the ping packets leaving the gw's external nic bound for the internet.
>
> if that works, you're looking for...
>
> 3. the echo packets coming back to the gw's external nic
>
> if that works, you're looking for...
>
> 4. the echo packets leaving the gw's internal nic.
>
> if that works, you're looking for...
>
> 5. echo packets being received by the internal machine.
>
>
> which of these steps is broken?
It seems the 3rd step is broken. I run tcpdump on both gateway
and an external machine.
On gateway, tcpdump capture the echo request package, but no
reply packages.
On external machine, tcpdump capture both request and reply
packages. The src ip of request packages is the internal ip.
If I ping gateway from the external machine directly, both
tcpdump capture all request and reply packages.
Maybe it's because the internal ip of the reply packages make
it be dropped on some router?
Jimmy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (IRIX)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjuK2uQACgkQZ1kuLJJ1tnJg4gCeIzLmMUSLOYnjbF1gExaPED6A
NsoAn2kn5xvcI5M8OF7+sxYLha9qNY6U
=1qKV
-----END PGP SIGNATURE-----
