From: Jasper Spaans <jasper@spaans.ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Unnumbered
Date: Fri, 22 Jun 2001 08:55:55 +0000 [thread overview]
Message-ID: <marc-lartc-99320026219005@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99319611106908@msgid-missing>
On Fri, Jun 22, 2001 at 10:31:04AM +0200, M.F. PSIkappa wrote:
> > The routing effects I cannot correctly comment on, as I'm not sufficiently
> > versed in IOS to fully grasp the effects of ip unnumbered
>
> 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.
So, in effect, you're changing the behaviour of your (level 3) port to a
level 2 port, i.e., a switch, and add some filtering features to it, or am I
missing something?
In that case, you might get away by configuring the two pairs of ports as
ethernet bridge ports, and only assign IP-addresses to the two outer
interfaces as in the diagram above.
Not sure whether all shaping and firewalling tricks will work in that case
though. Anyone got a comment on that?
Regards,
--
Q_. Jasper Spaans <j@sp3r.net>
`~\ http://jsp.ds9a.nl/
Mr /\ Tel/Fax: +31-84-8749842
Zap Move '.sig' for great justice!
_______________________________________________
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 8: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 [this message]
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
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-99320026219005@msgid-missing \
--to=jasper@spaans.ds9a.nl \
--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 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.