From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Eble, Dan" <DanE@aiinet.com>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: RFC: Cisco HDLC bridging
Date: Thu, 17 Jun 2004 00:49:59 +0200 [thread overview]
Message-ID: <m3zn73i0dk.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <C060DFCD9697A842B3189B458524FDC205D2CD@AIMAIL1.ai.aiinet.com> (Dan Eble's message of "Wed, 16 Jun 2004 08:58:35 -0400")
"Eble, Dan" <DanE@aiinet.com> writes:
> Ah, yes. But if the device does not have ARPHRD_ETHER the bridge driver
> will not allow it to be used as a port.
Correct. And while we can "fix" the bridge and other things, it's
still not enough.
> This is the sethdlc syntax I have chosen to create and destroy the hdlcXeth0
> device:
>
> sethdlc hdlc0 cisco proto <type> [ enable | disable ]
>
> Where <type> is 0x6558 for bridged ethernet packets (or maybe "ether", but I
> have not put that in yet). I figure this will be useful to enable and
> disable other protocols too.
Ok. I'd prefer "ether", though.
--
Krzysztof Halasa, B*FH
next prev parent reply other threads:[~2004-06-16 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 12:58 RFC: Cisco HDLC bridging Eble, Dan
2004-06-16 22:49 ` Krzysztof Halasa [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-14 13:40 Eble, Dan
2004-06-16 11:13 ` Krzysztof Halasa
2004-06-11 13:01 Eble, Dan
2004-06-11 21:29 ` Krzysztof Halasa
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=m3zn73i0dk.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=DanE@aiinet.com \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).