netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "nano bug" <linnewbye@gmail.com>
To: netdev@vger.kernel.org
Subject: Fwd: source interface ping bug ?
Date: Thu, 2 Aug 2007 23:01:37 +0300	[thread overview]
Message-ID: <d39c36500708021301i6754cb6bh4ba1a2a85092ce3c@mail.gmail.com> (raw)
In-Reply-To: <d39c36500708021258v1b45c3d1q2656bd3cdd9477f7@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 948 bytes --]

---------- Forwarded message ----------
From: nano bug <linnewbye@gmail.com>
Date: Aug 2, 2007 10:58 PM
Subject: Re: source interface ping bug ?
To: Patrick McHardy <kaber@trash.net>


Hello,

Yes I'm running NAT, I have atached the output of the iptables -t nat
-vxnL command and the routing tables

On 7/30/07, Patrick McHardy <kaber@trash.net> wrote:
> nano bug wrote:
> > [...]
> > using source interface :
> >
> > root@darkstar:~/iputils# ./ping -I eth2 87.248.113.14
> > PING 87.248.113.14 (87.248.113.14) from 86.106.19.75 eth2: 56(84) bytes of data.
> >>From 86.106.19.75 icmp_seq=1 Destination Host Unreachable
>
> > root@darkstar:~# tcpdump -i eth2 -vvv -n host 87.248.113.14 and host
> > 86.106.19.75
> > tcpdump: listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes
> > 01:19:24.292911 arp who-has 87.248.113.14 tell 86.106.19.75
>
>
> Are you using (or running) NAT locally? What do your routing tables look
> like?
>

[-- Attachment #2: route_tables --]
[-- Type: application/octet-stream, Size: 2032 bytes --]

root@darkstar:~#
root@darkstar:~#
root@darkstar:~# ip route show
80.97.71.0/24 dev eth0  proto kernel  scope link  src 80.97.71.23
10.10.10.0/24 dev eth1  proto kernel  scope link  src 10.10.10.1
86.106.18.0/23 dev eth2  scope link
127.0.0.0/8 dev lo  scope link
root@darkstar:~# ip rule show
0:      from all lookup local
50:     from all lookup main
100:    from 80.97.71.0/24 lookup 201
101:    from 86.106.18.0/23 lookup 202
102:    from all lookup 222
32766:  from all lookup main
32767:  from all lookup default
root@darkstar:~# ip route show table 201
default via 80.97.71.1 dev eth0  proto static
prohibit default  proto static  metric 1
root@darkstar:~# ip route show table 202
default via 86.106.18.1 dev eth2  proto static
prohibit default  proto static  metric 1
root@darkstar:~# ip route show table 222
default  proto static
        nexthop via 80.97.71.1  dev eth0 weight 1
        nexthop via 86.106.18.1  dev eth2 weight 99
prohibit default  proto static  metric 1
root@darkstar:~# iptables -V
iptables v1.3.8
root@darkstar:~# iptables -t nat -xvnL
Chain PREROUTING (policy ACCEPT 2120 packets, 298134 bytes)
    pkts      bytes target     prot opt in     out     source               destination
       1       48 DNAT       tcp  --  eth2   *       0.0.0.0/0            0.0.0.0/0           tcp dpts:18856:18870 to:172.16.2.1
       0        0 DNAT       udp  --  eth2   *       0.0.0.0/0            0.0.0.0/0           udp dpts:18856:18870 to:172.16.2.1

Chain POSTROUTING (policy ACCEPT 56 packets, 4568 bytes)
    pkts      bytes target     prot opt in     out     source               destination
       2      138 MASQUERADE  all  --  *      *       10.10.10.0/24        0.0.0.0/0
       0        0 MASQUERADE  all  --  *      *       172.16.1.0/24        0.0.0.0/0
       0        0 MASQUERADE  all  --  *      *       172.16.2.0/24        0.0.0.0/0

Chain OUTPUT (policy ACCEPT 55 packets, 4520 bytes)
    pkts      bytes target     prot opt in     out     source               destination
root@darkstar:~#



  parent reply	other threads:[~2007-08-02 20:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27  8:30 source interface ping bug ? nano bug
2007-07-29 11:48 ` nano bug
2007-07-30  8:46   ` nano bug
2007-07-30 16:06     ` Ben Greear
     [not found]       ` <d39c36500708021256p38347eabu14bd731dedb61230@mail.gmail.com>
2007-08-02 20:00         ` Fwd: " nano bug
2007-07-30 16:19 ` Patrick McHardy
     [not found]   ` <d39c36500708021258v1b45c3d1q2656bd3cdd9477f7@mail.gmail.com>
2007-08-02 20:01     ` nano bug [this message]
2007-08-04 17:16       ` nano bug

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=d39c36500708021301i6754cb6bh4ba1a2a85092ce3c@mail.gmail.com \
    --to=linnewbye@gmail.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).