Re: bridge_output() without m_buf_tag

2015-06-24 Thread Martin Pieuchot
On 17/06/15(Wed) 14:07, Martin Pieuchot wrote: On 08/06/15(Mon) 15:58, Martin Pieuchot wrote: Diff below moves bridge_output() to if_output(). It fixes the case I already described some weeks ago where you have a physical interface in a bridge and a vlan on top of it which is not in the

Re: bridge_output() without m_buf_tag

2015-06-17 Thread Martin Pieuchot
On 08/06/15(Mon) 15:58, Martin Pieuchot wrote: Diff below moves bridge_output() to if_output(). It fixes the case I already described some weeks ago where you have a physical interface in a bridge and a vlan on top of it which is not in the bridge. It also change the loop prevention code to

bridge_output() without m_buf_tag

2015-06-08 Thread Martin Pieuchot
Diff below moves bridge_output() to if_output(). It fixes the case I already described some weeks ago where you have a physical interface in a bridge and a vlan on top of it which is not in the bridge. It also change the loop prevention code to use M_PROTO1 like in the input path. Tests,