Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-13 Thread Valdis . Kletnieks
On Sat, 14 Jan 2017 09:58:21 +1100, Mark Andrews said: > In message , Fernando > Gont writes: > > Disagree. Microsoft "reinvented" ping-o-death in IPv6, there have been > > several one-packet crashes disclosed for Cisco's (an the list continues). > > And they would have issued fixes for them. Mac

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-13 Thread Mark Andrews
In message <954a2fbd-580a-044b-07e7-63a0bf1bb...@si6networks.com>, Fernando Gont writes: > On 01/12/2017 11:14 PM, Mark Andrews wrote: > > In message > > > > , Fernando Gont writes: > >> El 12/1/2017 16:32, "Saku Ytti" escribi=C3=B3: > >> > >> On 12 January 2017 at 17:02, Fernando Gont wrote:

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-13 Thread Mark Andrews
In message , Fernando Gont writes: > On 01/12/2017 11:07 PM, Mark Andrews wrote: > > In message > > > > , Fernando Gont writes: > >> El 12/1/2017 16:28, "Mark Andrews" escribi=C3=B3: > >> > >>> In message <11ff128d-2fba-7c26-4a9c-5611433d8...@si6networks.com>, > >>> Fernando Gont writes: > >>

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-13 Thread Fernando Gont
On 01/12/2017 11:14 PM, Mark Andrews wrote: > In message > > , Fernando Gont writes: >> El 12/1/2017 16:32, "Saku Ytti" escribi=C3=B3: >> >> On 12 January 2017 at 17:02, Fernando Gont wrote: >>> That's the point: If you don't allow fragments, but your peer honors >>> ICMPv6 PTB<1280, then dropp

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-13 Thread Fernando Gont
On 01/12/2017 11:07 PM, Mark Andrews wrote: > In message > > , Fernando Gont writes: >> El 12/1/2017 16:28, "Mark Andrews" escribi=C3=B3: >> >>> In message <11ff128d-2fba-7c26-4a9c-5611433d8...@si6networks.com>, Fernando >>> Gont writes: Hi, Saku, On 01/12/2017 11:43 AM, Saku Ytt

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-12 Thread Mark Andrews
In message , Fernando Gont writes: > El 12/1/2017 16:32, "Saku Ytti" escribi=C3=B3: > > On 12 January 2017 at 17:02, Fernando Gont wrote: > > That's the point: If you don't allow fragments, but your peer honors > > ICMPv6 PTB<1280, then dropping fragments creates the attack vector. > > Thanks

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-12 Thread Mark Andrews
In message , Fernando Gont writes: > El 12/1/2017 16:28, "Mark Andrews" escribi=C3=B3: > > > In message <11ff128d-2fba-7c26-4a9c-5611433d8...@si6networks.com>, Fernando > > Gont writes: > > > Hi, Saku, > > > > > > On 01/12/2017 11:43 AM, Saku Ytti wrote: > > > > On 12 January 2017 at 13:19, Fe

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-12 Thread Fernando Gont
El 12/1/2017 16:32, "Saku Ytti" escribió: On 12 January 2017 at 17:02, Fernando Gont wrote: > That's the point: If you don't allow fragments, but your peer honors > ICMPv6 PTB<1280, then dropping fragments creates the attack vector. Thanks. I think I got it now. Best I can offer is that B could

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-12 Thread Fernando Gont
El 12/1/2017 16:28, "Mark Andrews" escribió: In message <11ff128d-2fba-7c26-4a9c-5611433d8...@si6networks.com>, Fernando Gon t writes: > Hi, Saku, > > On 01/12/2017 11:43 AM, Saku Ytti wrote: > > On 12 January 2017 at 13:19, Fernando Gont wrote: > > > > Hey, > > > >> I'm curious about whether f

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-12 Thread Saku Ytti
On 12 January 2017 at 21:53, Fernando Gont wrote: > besides, becaude of ipv6 ehs, you're not really guaranteed to receive e.g. > the tcp header in the embedded payload (the embedded payload could easily be > fixed ipv6 header + ehs). If the CoPP drops what has not been explicitly allowed, then p

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-12 Thread Fernando Gont
Many (most?) Implementations don't even check the embedded port numbers...do tye attacker does not even need to guess the client port. besides, becaude of ipv6 ehs, you're not really guaranteed to receive e.g. the tcp header in the embedded payload (the embedded payload could easily be fixed ipv6

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-12 Thread Saku Ytti
On 12 January 2017 at 17:02, Fernando Gont wrote: > That's the point: If you don't allow fragments, but your peer honors > ICMPv6 PTB<1280, then dropping fragments creates the attack vector. Thanks. I think I got it now. Best I can offer is that B could try to verify the embedded original packet?

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-12 Thread Mark Andrews
In message <11ff128d-2fba-7c26-4a9c-5611433d8...@si6networks.com>, Fernando Gon t writes: > Hi, Saku, > > On 01/12/2017 11:43 AM, Saku Ytti wrote: > > On 12 January 2017 at 13:19, Fernando Gont wrote: > > > > Hey, > > > >> I'm curious about whether folks are normally filtering ICMPv6 PTB<1280

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-12 Thread Fernando Gont
Hi, Saku, On 01/12/2017 11:43 AM, Saku Ytti wrote: > On 12 January 2017 at 13:19, Fernando Gont wrote: > > Hey, > >> I'm curious about whether folks are normally filtering ICMPv6 PTB<1280 >> and/or IPv6 fragments targeted to BGP routers (off-list datapoints are >> welcome). > > Generally may b

Re: ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-12 Thread Saku Ytti
On 12 January 2017 at 13:19, Fernando Gont wrote: Hey, > I'm curious about whether folks are normally filtering ICMPv6 PTB<1280 > and/or IPv6 fragments targeted to BGP routers (off-list datapoints are > welcome). Generally may be understood differently by different people. If generally is defin

ICMPv6 PTBs and IPv6 frag filtering (particularly at BGP peers)

2017-01-12 Thread Fernando Gont
Folks, I'm curious about whether folks are normally filtering ICMPv6 PTB<1280 and/or IPv6 fragments targeted to BGP routers (off-list datapoints are welcome). In any case, you mind find it worth reading to check if you're affected (from Section 2 of recently-published RFC8021): cut here ---