[Bug 240135] Correctness issue in IPv6 extension headers input processing routines

2019-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240135 Bjoern A. Zeeb changed: What|Removed |Added Status|New |Open Assignee|n...@free

[Bug 240135] Correctness issue in IPv6 extension headers input processing routines

2019-08-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240135 Conrad Meyer changed: What|Removed |Added CC||c...@freebsd.org Assignee

Re: PF support for IPv6 Extension Headers

2015-06-11 Thread Kristof Provost
(From a very quick look at the code) On 2015-06-10 20:57:02 (-0300), Fernando Gont wrote: > What's the level f support of PF wrt IPv6 Extension Headers? > It's pretty limited. There's code for a few specific header types (fragment, routing, AH, hopopts and dstopts) but

PF support for IPv6 Extension Headers

2015-06-10 Thread Fernando Gont
Folks, What's the level f support of PF wrt IPv6 Extension Headers? pf.conf(5) talks about an implicit block rule for packets employing the routing header, but I've not been able to find anything about e.g., * Filtering packets on a per-EH-type-occurrence (e.g. "block packets

IPv6 Extension Headers

2011-02-08 Thread Colin O'Keeffe
Hi, I'm looking for some guidance on implementing extension headers in the kernel for outgoing packets and processing incoming packets. Is anybody available to discuss it with me (on or off the mailing list) to help me get the ball rolling. Thanks___

Re: IPv6 Extension Headers

2005-06-28 Thread Brooks Davis
On Wed, Jun 29, 2005 at 11:10:50AM +0530, Srinivas Goud wrote: > Hello All, > I am new bee to this group. > I am working on IPv6 Extension headers. I am confused with freeBSD > implementation and RFC2460 specification for Destination options. > > My interpretation from RFC2

IPv6 Extension Headers

2005-06-28 Thread Srinivas Goud
Hello All, I am new bee to this group. I am working on IPv6 Extension headers. I am confused with freeBSD implementation and RFC2460 specification for Destination options. My interpretation from RFC2460 is that, If a packet consists of hop-by-hop and destination extension headers