On Thu, May 12, 2022 at 8:55 AM Aaron Conole wrote:
>
> Ben Pfaff writes:
>
> > Hi Aaron! This will move the following fields from the L4 segment to
> > the L3 segment:
> >
> > struct in6_addr nd_target; /* IPv6 neighbor discovery (ND) target. */
> > struct eth_addr arp_sha;/* ARP/N
Ben Pfaff writes:
> Hi Aaron! This will move the following fields from the L4 segment to
> the L3 segment:
>
> struct in6_addr nd_target; /* IPv6 neighbor discovery (ND) target. */
> struct eth_addr arp_sha;/* ARP/ND source hardware address. */
> struct eth_addr arp_tha;/* A
Hi Aaron! This will move the following fields from the L4 segment to
the L3 segment:
struct in6_addr nd_target; /* IPv6 neighbor discovery (ND) target. */
struct eth_addr arp_sha;/* ARP/ND source hardware address. */
struct eth_addr arp_tha;/* ARP/ND target hardware address.
During flow processing, the flow wildcards are checked as a series of
stages, and these stages are intended to carry dependencies in a single
direction. When the neighbor discovery processing, for example, was
executed there is an incorrect dependancy chain - we need fields from
stage 4 to determi
