Hello Stuart, I'm sorry for disturbance. Indeed, PF was the cause of dropping packets with IP option.
Thank you! 2014-07-17 14:56 GMT+04:00 Stuart Henderson <st...@openbsd.org>: > On 2014/07/17 14:43, Alexander Okonnikov wrote: > > Hello, > > > > Description: > > There is bridge interface is created on the host with two ports. > An > > IP packet with Router Alert option is coming on one of bridge port, but > is > > not forwarded to another bridge port. Other IP packets (without this IP > > option or, perhaps, without any IP option) are successfully forwarded by > > the bridge. > > > > How-To-Repeat: > > Bridge interface is created, and two (or more) ports are added to > > this bridge. After that IP packet with Router Alert option is coming on > one > > of the ports of the bridge (in my case I use RSVP Path message for test > as > > far as this kind of message contains Router Alert option in an IP > header). > > This message is not forwarded to outgoing bridge port, but dropped > > somewhere inside host. Other IP traffic (without Router Alert option) is > > forwarded successfully at the same time. Packets with Router Alert > option > > are being captured on ingress port and on bridge interface, but are not > > present on egress port. > > Is the packet being blocked by PF? > > If not, please paste output from tcpdump -eXs1500 of a sample dropped > packet (to bugs@ not me personally, inline in the message body), or put > a pcap online somewhere and send a link to that. > > -- Best regards, Alexander Okonnikov
