From: "Greg Varga" <gvarga@bvcompuworks.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Unnumbered
Date: Fri, 22 Jun 2001 16:37:29 +0000 [thread overview]
Message-ID: <marc-lartc-99322791215748@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99319611106908@msgid-missing>
On Fri, 22 Jun 2001 10:55:41 +0200 (CEST), M.F. PSIkappa wrote:
>> > No, it's incorrect, unnumberd allow you to connect 2 router without IP
>> > adresses.
>> >
>> > 192.168.0.1/24 [cisco]unnumbered-----unnumberd[cisco] 192.168.2.1/24
>> >
>> > It's special case of point-to-point connection. In linux if I make
>> > point-to-point connection I have to assign any IP on both endpoint of
>> > connection.
>>
>> What is the difference with
>>
>> 192.168.0.1/24 [linux] 192.168.0.1 ------- 192.168.2.1 [linux] 192.168.2.1/24
>>
>> if I may be so bold to ask? Yes, the routing effects may be different, and I
>> mentioned that might be a problem, but the unnumbered thing looks like a
>> cisco-specific hack...
>
>Difference is in traceroute. Unnumbered is invisible, if I assign IP I see
>it in traceroute, but I can make hack that make this connection invisible,
>but it's rfc break ...
This is correct, in the workings... But I don't think it really breaks
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.
--Greg.
-------------------------------------
Greg Varga
Owner: Digital Realities
http://www.digital.realities.com
604.576.2219
Lead Programmer of MUTAG
http://www.bvcompuworks.com/mutag
Network Administrator
-------------------------------------
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-06-22 16:37 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 [this message]
2001-06-22 16:55 ` Ramin Alidousti
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-99322791215748@msgid-missing \
--to=gvarga@bvcompuworks.com \
--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