All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Bill Fink <billfink@mindspring.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: ppp and routing table rules.
Date: Fri, 02 Mar 2007 23:22:20 -0800	[thread overview]
Message-ID: <45E9222C.4090504@candelatech.com> (raw)
In-Reply-To: <20070303005455.86dd8059.billfink@mindspring.com>

Bill Fink wrote:
> On Thu, 01 Mar 2007, Ben Greear wrote:
>
>   
>> Ben Greear wrote:
>>
>> I am sending udp packets through ppp400, and I see them appear on ppp401 
>> as expected.
>>
>> The thing that is bothering me is that all I see on rddVR4 (172.1.2.1) 
>> is arps for 172.1.2.2, but the 'tell' IP is that of the
>> originating ppp400 link, not the IP of rddVR4, as I expected:
>>
>> 21:47:16.119640 arp who-has 172.1.2.2 tell 11.1.1.3
>> 21:47:17.119371 arp who-has 172.1.2.2 tell 11.1.1.3
>> 21:47:18.119254 arp who-has 172.1.2.2 tell 11.1.1.3
>> 21:47:19.273118 arp who-has 172.1.2.2 tell 11.1.1.3
>>
>> Unless I'm missing something dumb, a similar setup with all ethernet-ish 
>> network devices
>> works fine.
>>
>> I have also enabled arp filtering:
>> # Only answer ARPs if it is for the IP on our own interface.
>> echo 2 > /proc/sys/net/ipv4/conf/all/arp_ignore
>> and for every device used in these routing tables:
>> echo 1 > /proc/sys/net/ipv4/conf/[dev]/arp_filter
>>
>> Any idea what I need to do in order to make  the source IP for the ARP 
>> packet correct?
>>     
>
> Wouldn't that be controlled by arp_announce?
>   

Yes, after trawling through the code I found that one, and setting it to '2'
seems to have fixed everything.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com> 
Candela Technologies Inc  http://www.candelatech.com



      reply	other threads:[~2007-03-03  7:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-02  4:46 ppp and routing table rules Ben Greear
2007-03-02  6:29 ` Ben Greear
2007-03-03  5:54   ` Bill Fink
2007-03-03  7:22     ` Ben Greear [this message]

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=45E9222C.4090504@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=billfink@mindspring.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 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.