From: shen jing <jshen@cad.zju.edu.cn>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Why 'ping' only succeed in one direction?
Date: Wed, 30 May 2001 08:40:54 +0000 [thread overview]
Message-ID: <marc-lartc-99122225404362@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99114800203883@msgid-missing>
> Thank you very much.
I've checked the file , they have the following content:
/proc/sys/net/ipv4/conf/all/rp_filter : 1
/proc/sys/net/ipv4/conf/default/rp_filter: 0
/proc/sys/net/ipv4/conf/eth0/rp_filter: 0
/proc/sys/net/ipv4/conf/lo/rp_filter: 0
the ip route says:
[root@cad166 lo]# ip route
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.1
210.32.131.0/24 dev eth0 proto kernel scope link src 210.32.131.166
127.0.0.0/8 dev lo scope link
default via 210.32.131.1 dev eth0
default via 210.32.131.1 dev eth0 src 210.32.131.166 metric 1
[root@cad166 lo]#
I don't understand what's the files under all/ and default/ for.
And the tcpdump on linuxbox and snoop on Sun both shows
icmp echo request and icmp echo reply has been received.
But why 'ping 210.32.131.97' always show nothing when executed
on 192.168.1.8?
James Shen
> Hi
> seems ok check /proc/sys/net/ipv4/conf/[*]/rp_filter
> what it does is explained in the adv routing howto almost at the end.
>
> Hope it helps
>
> bye
>
> > ----------------------------------- ( Ethernet)
> >
> >
> > Sun-1 Linux Sun-2
> > 210.32.131.97 192.168.1.1(eth0) 192.168.1.8
> > 210.32.131.166(eth0:0)
> >
> > Routing table :
> >
> > Sun-1: 192.168.1.0/24 ---> 210.32.131.166
> > default -----> 210.32.131.2
> >
> > Linux : default---> 210.32.131.2
> > ( I add no explicit routing table about the twodirect
> > connected network )
> >
> > Sun-2 : default --> 192.168.1.1
>
> On Tuesday 29 May 2001 11:53 am, shen jing wrote:
> > Hi:
> >
> > I'm using a linux box ( Rh7.1 ) as a router which connect two Solaris2.6
> >
> > box.
> > The three computer is interconnected by ethernet, each computer has
> > only on ethernet adapter.
> >
> > The following is my network connection :
> >
> > ----------------------------------- ( Ethernet)
> >
> >
> > Sun-1 Linux Sun-2
> > 210.32.131.97 192.168.1.1(eth0) 192.168.1.8
> > 210.32.131.166(eth0:0)
> >
> > Routing table :
> >
> > Sun-1: 192.168.1.0/24 ---> 210.32.131.166
> > default -----> 210.32.131.2
> >
> > Linux : default---> 210.32.131.2
> > ( I add no explicit routing table about the twodirect
> > connected network )
> >
> > Sun-2 : default --> 192.168.1.1
> >
> > While I exec "ping 192.168.1.8 "on Sun-1, it succeed, with 0% packet
> > loss.
> >
> > But when I exec "ping 210.32.131.97" on Sun-2, the ping always hang
> > with no output, when I interrupt it with "Ctl-C', it shows "100% packet
> > loss".
> >
> > I do tcpdump on linux and snoop on Sun to find out what happened, but
> > all detailed record shows "ICMP echo requect/reply " has been delivered
> > between Sun-1<-->linux, Linux<-->Sun-2
> >
> > And I can telnet/ftp between Sun-1 & Sun-2.
> >
> > Is there someone will do me a favor to explain why this happens ? Is
> > there any configuration error with my linux box ?
> >
> > Thanks in advance and each word will be highly appreciated.
> >
> > James Shen
> >
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-05-30 8:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-29 14:53 [LARTC] Why 'ping' only succeed in one direction? shen jing
2001-05-30 3:04 ` Krepper Guillermo
2001-05-30 8:40 ` shen jing [this message]
2001-05-30 13:54 ` Krepper Guillermo
2001-05-30 20:36 ` Ramin Alidousti
2001-05-30 20:44 ` Ramin Alidousti
2001-05-31 1:56 ` Rodrigo Goya
2001-05-31 2:18 ` Mike Fedyk
2001-05-31 2:25 ` Mike Fedyk
2001-05-31 2:50 ` shen jing
2001-05-31 3:21 ` Juergen
2001-05-31 6:13 ` shen jing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-99122225404362@msgid-missing \
--to=jshen@cad.zju.edu.cn \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox