Darren Reed <darr...@netbsd.org> wrote: >> That's cool... >> >> > that are chained together in this fashion. In its current form, BPF >> (v1) is > not that IPv6 friendly. Give me a week or two to back up a >> design with some > code that works (the parser and compiler bit are >> the tricky pieces.) >> >> True. I assume you are adding kind of limited loop capability. Could >> it be unrolled to some depth to work with BPFv1?
> No. For analysing IPv6 you don't need loops, rather you need some much > more complex instructions than BPF's RISC design has at present. Key > to that are "find header number X" or "what is the last header" as okay, I would call these "limited loops", in that they can only iterate through the packet under specific conditions :-) Thank you for working on this. Getting new BPF code widely deployed won't be easy. -- ] Never tell me the odds! | ipv6 mesh networks [ ] Michael Richardson, Sandelman Software Works | network architect [ ] m...@sandelman.ca http://www.sandelman.ca/ | ruby on rails [ _______________________________________________ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers