linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Teh <james.teh@netboxblue.com>
To: linux-ppp@vger.kernel.org
Subject: Problems with proxy arp with multiple addresses on the same interface
Date: Tue, 22 Jan 2008 00:33:00 +0000	[thread overview]
Message-ID: <479539BC.1050303@netboxblue.com> (raw)

Hi all,

The Linux specific get_ether_addr() function in pppd uses ioctl to get 
the netmask for an interface by interface name. Unfortunately, using the 
ip command, multiple addresses don't receive separate interface labels, 
which means that get_ether_addr() can only ever obtain the netmask for 
the first address on each in terface. This causes proxy arp to fail in 
certain cases when there are multiple addresses on the interface in 
question; specifically, when the subnet mask of the first address on the 
interface is smaller than the netmask of the desired address.

This can be worked around by using ip with the "label" parameter to 
label each interface separately, but this is undesirable, as it means 
unique labels need to be generated.

I have created a patch (largely borrowed from BSD) which uses 
getifaddrs() instead of get_ether_addr() to get the netmask. This way, 
the netmask for the specific address of the interface can be obtained.

Is this the appropriate place to submit this patch? I looked through the 
documentation, but found no mention of where patches should be submitted.

--
James Teh
Developer
NetBox Blue

Scanned by the NetBox from NetBox Blue
(http://netboxblue.com/)


             reply	other threads:[~2008-01-22  0:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22  0:33 James Teh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-02-24  5:13 Problems with proxy arp with multiple addresses on the same interface James Teh

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=479539BC.1050303@netboxblue.com \
    --to=james.teh@netboxblue.com \
    --cc=linux-ppp@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).