| To: | "Eble, Dan" <DanE@xxxxxxxxxx> |
|---|---|
| Subject: | Re: RFC: Cisco HDLC bridging |
| From: | Krzysztof Halasa <khc@xxxxxxxxx> |
| Date: | Thu, 17 Jun 2004 00:49:59 +0200 |
| Cc: | "'netdev@xxxxxxxxxxx'" <netdev@xxxxxxxxxxx> |
| In-reply-to: | <C060DFCD9697A842B3189B458524FDC205D2CD@AIMAIL1.ai.aiinet.com> (Dan Eble's message of "Wed, 16 Jun 2004 08:58:35 -0400") |
| References: | <C060DFCD9697A842B3189B458524FDC205D2CD@AIMAIL1.ai.aiinet.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
"Eble, Dan" <DanE@xxxxxxxxxx> 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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [RFC] Wireless extensions rethink, Jean Tourrilhes |
|---|---|
| Next by Date: | [BK PATCHES] 2.6.x net driver updates, Jeff Garzik |
| Previous by Thread: | RE: RFC: Cisco HDLC bridging, Eble, Dan |
| Next by Thread: | this thing on?, jamal |
| Indexes: | [Date] [Thread] [Top] [All Lists] |