"Rogier R. Mulhuijzen" wrote:
I found this while experimenting with both "legacy" bridge and ng_bridge.
The bridging code doesn't check its activation everywhere so when I started
using an ng_bridge node I started getting weird errors.
Patch is rather simple, can someone submit this?
I'm
At 00:48 3-2-01 -0800, Julian Elischer wrote:
"Rogier R. Mulhuijzen" wrote:
I found this while experimenting with both "legacy" bridge and ng_bridge.
The bridging code doesn't check its activation everywhere so when I started
using an ng_bridge node I started getting weird errors.