hello,
in MUX PtBindAdapter function, the comment is: // Start a;; VELANS on this
adapt!
what is a VELAN? My understanding to this point was that the MUX creats a
VELAN on multiple adpaters.
can u experts throw some light ont he relation of physical adapters, velans,
and MUX!
ap
what i recall of the MUX sample is that it demonstrates creating multiple
virtual adapters on a single physical adapter. each virtual adapter is
associated with a 802.1Q VLAN (I think VELAN[s] is a typo) tag. if VLAN
tagging is supported on the physical ethernet link (and the switch supports
it), each MUX Virtual Adapter appears to be on a separate Ethernet.
Good Luck,
Dave Cattley
Consulting Engineer
Systems Software Development
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Wednesday, January 24, 2007 6:46 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] velans
hello,
in MUX PtBindAdapter function, the comment is: // Start a;; VELANS on this
adapt!
what is a VELAN? My understanding to this point was that the MUX creats a
VELAN on multiple adpaters.
can u experts throw some light ont he relation of physical adapters, velans,
and MUX!
ap
— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the List
Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
> can u experts throw some light ont he relation of physical adapters, velans, and MUX!
MUX (multiplexer) is NDIS IM driver that, like NDIS IM filter, binds itself to physical adapters
on its lower edge, and, unlike NDIS IM filter, presents itself as an adapter on its upper edge, so that protocol drivers can bind to it the way they bind to physical adapters (filters don’t present themselves as adapters, so that bound protocols believe that they deal directly with underlying physical adapters, rather than with filters).
MUX WDK sample creates multiple virtual network devices on top of a single lower adapter. In particular case of MUX WDK sample, there is only one adapter, so that it is N:1 model, but MUX can be written to implement N:M model. The term “VELAN” in MUX sample is used to denote a Virtual Ethernet LAN adapter implemented by MUX driver.
Anton Bassov