Could you clarify exactly what happens to the paint metadata for a packet when
that packet exits a Click switch and goes out on the wire as an Ethernet frame?
Specifically, is Click's paint metadata stored in the Ethernet frame? If so,
precisely where is it stored in the frame? If it isn't store
Thanks Bob and Aaron for the replies.
The problem with ToS is that it might be modified by routers in the path of
the packet.
Collisions can also be problematic when an intermediate network uses tagged
VLAN. Consider this, I have three OF networks connected via single links
A---BC. Also, all
I think collisions are only problematic when you cannot disambiguate them.
For example, packets coming from servers connected to different switch ports
can be disambiguated based on ingress port, irrespective of their IP or
Ethernet headers.
Another example is NAT boxes - behind the NAT, every
You can set the ToS bits in the packet to mark it. Though if you go through
a router these values most likely won't be retained.
Aaron
On Fri, Nov 2, 2012 at 5:36 PM, Abhishek Chanda wrote:
> Hi all,
>
> Is there a way to insert custom metadata in a packet (other than the match
> tuple) that can
Hi all,
Is there a way to insert custom metadata in a packet (other than the match
tuple) that can then be extracted in a switch? Specifically, I am looking
for something like Click's Paint element that allows marking packets with a
'color'. Later, another network element can look at the color and
