From: Guy Van Den Bergh <guy.vandenbergh@pandora.be>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] pointopoint flag
Date: Sun, 25 Mar 2001 21:34:18 +0000 [thread overview]
Message-ID: <marc-lartc-98555616415657@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98529443625692@msgid-missing>
Gregory Maxwell wrote:
> On Sun, Mar 25, 2001 at 09:29:30PM +0200, Guy Van Den Bergh wrote:
>
>>
>> Even if you have a crossconnect cable between two hosts or routers, the medium inbetween is still broadcast and not
>> point-to-point.
>>
>> I know this discussion is going way too far into semantics, but as far as I know there is no such thing as point-to-point mode of ethernet.
>
>
> You can disable arp and set static arp entries. Do that, plus a crossover cable
> and full-duplex, and I'd have a very hard time calling your ethernet
> anything but point-to-point. :)
The point was that it is a lot more complex than simply adding a route
to the device instead of to the nexthop.
Let's remember that ethernet is by nature a broadcast medium and if you
want it to behave like a point-to-point link you will have to be
careful. Adding static arp entries has some drawbacks which you do not
have on real point-to-point links.
In the end you are still trying to let a broadcast medium behave like a
point-to-point link. Nothing more and nothing less.
Guy
_______________________________________________
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-03-25 21:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-22 20:53 [LARTC] pointopoint flag mike stjohn
2001-03-22 22:20 ` Guy Van Den Bergh
2001-03-24 21:47 ` bert hubert
2001-03-25 18:07 ` Guy Van Den Bergh
2001-03-25 19:29 ` Guy Van Den Bergh
2001-03-25 19:52 ` bert hubert
2001-03-25 20:48 ` Gregory Maxwell
2001-03-25 21:34 ` Guy Van Den Bergh [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-98555616415657@msgid-missing \
--to=guy.vandenbergh@pandora.be \
--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.