All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Marco Berizzi <pupilla@hotmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: snat local packets and arp
Date: Tue, 15 Jan 2008 17:42:45 +0100	[thread overview]
Message-ID: <478CE285.8050900@trash.net> (raw)
In-Reply-To: <BAY103-DAV6A7F9ABB20DF8DAD84D17B2470@phx.gbl>

Marco Berizzi wrote:
>> Do the routers send arp queries to the Linux box?
> 
> Honestly, I don't know. This is the output running
> tcpdump -pnvi eth0 arp
> 
> 10:54:11.787680 : arp who-has adsl.129 tell adsl.134
> 10:54:11.788293 : arp reply adsl.129 is-at 00:1b:...
> 10:54:34.580798 : arp who-has adsl.129 tell adsl.134
> 10:54:34.581441 : arp reply adsl.129 is-at 00:1b:...
> 10:55:17.420198 : arp who-has adsl.129 tell adsl.134
> 10:55:17.420836 : arp reply adsl.129 is-at 00:1b:...
> 10:56:00.552606 : arp who-has adsl.129 tell adsl.134
> 10:56:00.553231 : arp reply adsl.129 is-at 00:1b:...
> 
> I only see the linux box quering the cisco and not
> viceversa. AFAIK the cisco has been configured by
> the ISP with very high timeout for the arp cache.
> 
> PS: The linux is 2.6.23 with default option except
> arp_filter/rp_filter/proxy_arp set to 1 on eth0


Try disabling rp_filter, that should make it behave similar
for both addresses. With rp_filter, the input routing done
by arp.c fails because the mark is different and it doesn't
go to your special routing table, so it doesn't update the
cache from arp queries from that router.

  reply	other threads:[~2008-01-15 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 10:39 snat local packets and arp Marco Berizzi
2008-01-15 15:57 ` Patrick McHardy
2008-01-15 16:22   ` Marco Berizzi
2008-01-15 16:32     ` Patrick McHardy
2008-01-15 16:40       ` Marco Berizzi
2008-01-15 16:42         ` Patrick McHardy [this message]
2008-01-16  8:46           ` Marco Berizzi

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=478CE285.8050900@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pupilla@hotmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.