<div dir="ltr">You can also bridge L2 over OpenVPN.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 30, 2015 at 11:07 PM, Bill McGonigle <span dir="ltr"><<a href="mailto:bill@bfccomputing.com" target="_blank">bill@bfccomputing.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">How much "ethernet" on the bridge is working? I happened to run across<br>
this topic yesterday where it would have been really handy to bridge a<br>
VLAN trunk across a wifi bridge, but almost everything that says that<br>
it's "layer 2 transparent" is really just doing ARP proxy/masquerading<br>
of a sort, which works OK for stuff that happens to fit into WiFi<br>
framing but not other stuff.<br>
<br>
To do real layer 2 bridging seems to require doing L2 over L3 (L2TPv3,<br>
EoIP, VPLS, or eoMPLS) but that requires a cooperating endpoint, which<br>
you don't have, so it can't be that. Aside: when I get a chance I'd<br>
like to get a config worked out to have an easily deployable L2TPv3<br>
bridge on a pair of openwrt boxes, for when the next thing breaks.<br>
<br>
-Bill<br>
<span class=""><br>
<br>
On 11/13/2015 11:39 AM, Joshua Judson Rosen wrote:<br>
> I've noticed that VirtualBox and some other VM packages include<br>
> functionality to bridge in-VM network interfaces onto the external<br>
> network through a network interface on the host machine. I get how this works<br>
> for ethernet, but it seems like they make it work for Wi-Fi, too;<br>
> given that Wi-Fi frames don't actually carry enough information to<br>
> to do bridging at the station (client) end, how the heck does this<br>
> actually work?<br>
><br>
> The only technique with which I'm really familiar, for bridging ethernet<br>
> through an 802.11(b|a|g|n) client interface, involves running the<br>
> radio in a non-standard 4-address mode, which requires support<br>
> on the AP at the other end of the wireless link; I'm fairly certain<br>
> that's not what the VM systems are doing, because they appear to<br>
> work with bog standard APs. So what _are_ they doing? Creating<br>
> a second (hidden?) interface on VM host with identical MAC address<br>
> to the interface inside the VM, and mirroring traffic between them?<br>
> Faking it by sniffing and relaying packets at layer 3? Something else?<br>
> Maybe something about this actually did get into a companion IEEE<br>
> standard that I'm not familiar with?<br>
><br>
<br>
<br>
--<br>
</span>Bill McGonigle, Owner<br>
BFC Computing, LLC<br>
<a href="http://bfccomputing.com/" rel="noreferrer" target="_blank">http://bfccomputing.com/</a><br>
Telephone: +1.855.SW.LIBRE<br>
Email, IM, VOIP: <a href="mailto:bill@bfccomputing.com">bill@bfccomputing.com</a><br>
VCard: <a href="http://bfccomputing.com/vcard/bill.vcf" rel="noreferrer" target="_blank">http://bfccomputing.com/vcard/bill.vcf</a><br>
Social networks: bill_mcgonigle/bill.mcgonigle<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
gnhlug-discuss mailing list<br>
<a href="mailto:gnhlug-discuss@mail.gnhlug.org">gnhlug-discuss@mail.gnhlug.org</a><br>
<a href="http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/" rel="noreferrer" target="_blank">http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/</a><br>
</div></div></blockquote></div><br></div>