On Thu, Aug 03, 2006 at 11:33:25AM +1000, Philip Craig wrote: > >>> All it does is encapsulate the full ethernet header in a gre packet, > >>> rather than only layer 3. That is, currently gre uses ARPHRD_IPGRE, > >>> but bridging requires ARPHRD_ETHER. > >> > >> I am not against making the bridge code smarter to handle other > >> encapsulation. > > > > What if you want to run ethernet directly over a GRE tunnel, without > > using bridging? > > But on the other hand, this method allows you to send both ethernet > and non-ethernet traffic over the same GRE tunnel. Is that useful? > Actually, this feature is what makes the handling of the LLC_SAP_BSPAN > packets simple. > > The patch to bridging is a lot cleaner than the patch to GRE, and it > also sidesteps the userspace configuration issues, so I don't want to > go back to modifying the GRE device.
So now you _need_ bridging in the middle to send ethernet traffic over a GRE tunnel? Ugh. If you really want to send ethernet and non-ethernet traffic over the same tunnel, can't you make multiple devices? If GRE generally transmits BPDUs without ethernet header, the handling for that ought to be in GRE, IMHO. cheers, Lennert - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
