Lines Matching full:tcp

79 e.g. source and destination addresses from Ethernet, IP, or TCP
86 corresponding to a TCP packet that arrived on vport 1::
90     frag=no), tcp(src=49163, dst=80)
94     in_port(1), eth(...), eth_type(0x0800), ipv4(...), tcp(...)
177 definitions.  With this change, a TCP packet in VLAN 10 would have a
180     eth(...), vlan(vid=10, pcp=0), eth_type(0x0800), ip(proto=6, ...), tcp(...)
192 example, why 802.1Q support uses nested attributes.  A TCP packet in
196     ip(proto=6, ...), tcp(...)))
198 Notice how the "eth_type", "ip", and "tcp" flow key attributes are
218 indicates protocol 6 for TCP, but which is truncated just after the IP
219 header, so that the TCP header is missing.  The flow key for this
220 packet would include a tcp attribute with all-zero src and dst, like
223     eth(...), eth_type(0x0800), ip(proto=6, ...), tcp(src=0, dst=0)
232 Unlike a TCP packet with source and destination ports 0, an