<< | Thread Index | >> ]    [ << | Date Index | >> ]

To: <cipe-l,AT,inka,DOT,de>
Subject: Re: Broadcast and CIPE-Win32
From: "Hans Steegers" <J.Steegers,AT,chello,DOT,nl>
Date: Tue, 15 Jul 2003 15:36:54 +0200
Reply-to: "Hans Steegers" <steegers,AT,steegers,DOT,nl>

If CIPE-Win32 implements a psuedo Ethernet interface, _maybe_ this works:

Hans Steegers.

-----Original Message-----
From: Damion K. Wilson <dwilson,AT,ibl,DOT,bm>
To: Mark Smith <mark.smith,AT,avcosystems,DOT,co,DOT,uk>
Cc: cipe-l,AT,inka,DOT,de <cipe-l,AT,inka,DOT,de>
Date: Tuesday, July 15, 2003 3:20 PM
Subject: Re: Broadcast and CIPE-Win32

>Broadcasts do work, and CIPE-Win32 implements a psuedo Ethernet interface
>(with faked MAC's), but I don't know what's required for Ethernet bridging.
>It certainly wasn't in the design criteria :-)
>On Tuesday 15 July 2003 06:14 am, Mark Smith wrote:
>> Simply, CIPE acts as a transparent direct connection as if two ethernet
>> adapters were physically attached to each other.  Usually, broadcast
>> traffic is not sent across segments in this fashion, whether they are
>> CIPE or over a physical adapter.  I don't have the details, but I know
>> for Linux supports ethernet bridging.  However, I do not believe this has
>> been supported for Win32 - DKW would know.
>> I doubt this helps, but it might be something for others to comment on.
>Message sent by the cipe-l,AT,inka,DOT,de mailing list.
>Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
>Other commands available with "help" in body to the same address.
>CIPE info and list archive:

<< | Thread Index | >> ]    [ << | Date Index | >> ]