Hi Murphy > Should be more or less the same. As far as the packet library is concerned, > Ethernet encapsulates VLAN and VLAN in turn encapsulates IP: > eth.payload = vlan > vlan.payload = ip
Ok, nice... it seems to work. My next step will be sending this packet out and see if Open vSwitch 1.11 is able to do so. >> By the way, is item #2 feasible ? How ? > > Within the L2 payload but before the L3? Is this a custom protocol/packet > type/encapsulation? If POX doesn't know it, it'll just result in the raw > bytes being inserted into the chain of packet objects. You could either use > this itself, or you could extend the packet library to understand it. Yep, it's a custom protocol/encapsulation. I agree... the better way surely is writing a packet library extension to deal with it... > Note that all this is happening on the controller and not on the switch... I > hope you're not planning to do such packet processing at a high rate. Sure! It's a experiment, not intended to a production environment. Do you know if OVS 1.11 is capable to insert/remove some bytes between layers headers ? (I know it's a off-topic question, I'm just curious :) ) thanks! Lucas Brasilino
