Linux PPP protocol development
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: What are the correct NETMASKs for multiple PPPoE interfaces in a StaticIP block?
Date: Tue, 15 Apr 2008 13:33:56 +0000	[thread overview]
Message-ID: <18436.44740.954131.304124@gargle.gargle.HOWL> (raw)
In-Reply-To: <b510d0250804140743o4528107dq834a63e4666f549d@mail.gmail.com>

Gerianne McC writes:
> I'm making my primary ppp connection at interface
> 
>        ppp0, IP address = x.x.x.238
> 
> and setting up interface aliases of,
> 
>        ppp0:1, IP address = x.x.x.233
>        ppp0:2, IP address = x.x.x.234
>        ppp0:3, IP address = x.x.x.235
>        ppp0:4, IP address = x.x.x.236
>        ppp0:5, IP address = x.x.x.237

That should work, though it's perhaps not how I'd handle it.

> What should be the NETMASK for the primary 'ppp0'? /29 or /32?
> And for each of the aliases?

They're all /32 -- individual IP addresses.

PPP creates point-to-point interfaces.  It's not a broadcast-type
medium, like Ethernet.  There's no "subnet" as far as the interface is
concerned, but rather just two arbitrary IP nodes connected together.

That's why the link has a "local" address and a "remote" address, and
no "broadcast" address.  It's not a subnet.

> If the right answer if ppp0 -> /29, & ppp0:# -> /32, should I ALSO
> create an alias ppp0:6, IP address = x.x.x.238 (same as ppp0 !?) but
> with a /32?

Setting a /29 on a PPP interface should have no effect.  The system
should be smart enough to know that the right answer is /32.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

  reply	other threads:[~2008-04-15 13:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14 14:43 What are the correct NETMASKs for multiple PPPoE interfaces in a StaticIP block? Gerianne McC
2008-04-15 13:33 ` James Carlson [this message]
2008-04-15 13:52 ` Gerianne McC
2008-04-15 13:59 ` James Carlson
2008-04-15 17:51 ` Gerianne McC
2008-04-15 18:46 ` James Carlson

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=18436.44740.954131.304124@gargle.gargle.HOWL \
    --to=carlsonj@workingcode.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