From: Ramin Alidousti <ramin@UU.NET>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Unnumbered
Date: Fri, 22 Jun 2001 16:55:27 +0000 [thread overview]
Message-ID: <marc-lartc-99322898219185@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99319611106908@msgid-missing>
On Fri, Jun 22, 2001 at 09:37:29AM -0700, Greg Varga wrote:
> This is correct, in the workings... But I don't think it really breaks
> the RFC's...
It has nothing to do with the RFC's.
>
> Anyways this is the diffrence:
>
> All networks prefixed with "10.0"...
>
> Numbered:
> ----- 10.0.1.1/24 [[[Linux Box]]] 10.0.0.100/24 -----Ethernet-----
> 10.0.2.1/24 [[[Linux Box]]] 10.0.0.200/24 -----
>
> Unnumbered:
> ----- 10.0.1.1/24 [[[Linux Box]]] -----P to P----- [[[Linux Box]]]
> 10.0.0.200/24 -----
>
> As you can see, the unnumbered is a Point to Point connection, and acts
> more like a "bridge"...
>
> Actually, if you want to do an Unnumbered connection with two Ethernet
> Interfaces, thats exactly how I would set it up... as a Bridge. Either
> that or use PPPoE and that should be able to do something simular.
>
> >Yes, it's cisco specific hack.
>
> No this is not true... Alot of the Point to Point (IE: Dial-Up, ISDN)
> type Internet Connections use Unnumbered Connections. There are a
> large number of companies that support these type of connections.
You are correct, Greg. Unnumbered interfaces are (mostly) ptp interfaces.
When setting up a ptp interface you should usually use one /30 in a
traditional way. Now, for a ptp connection there is only one IP entity
at the other end and it doesn't have to be one out of a /30. Any IP
address will do. That's why they usually use the loopback IP (or the
IP of another interface) to identify the Unnumbered interface.
I'm not sure how this can be done with linux. But I think that pppd
program does not require you to waste one /30 for the link. The server
side can send one /32 to the client side and announce another IP (eg,
the IP of its ethernet interface) as the peer IP of the ppp link. At
least this is what's happening when you dial in to a NAS.
Ramin
>
> --Greg.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-06-22 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 7:47 [LARTC] Unnumbered M.F. PSIkappa
2001-06-22 8:00 ` Arthur van Leeuwen
2001-06-22 8:31 ` M.F. PSIkappa
2001-06-22 8:34 ` Arthur van Leeuwen
2001-06-22 8:55 ` M.F. PSIkappa
2001-06-22 8:55 ` Jasper Spaans
2001-06-22 8:59 ` Dmytro O. Redchuk
2001-06-22 9:00 ` Arthur van Leeuwen
2001-06-22 16:37 ` Greg Varga
2001-06-22 16:55 ` Ramin Alidousti [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=marc-lartc-99322898219185@msgid-missing \
--to=ramin@uu.net \
--cc=lartc@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