Bridge Filter bug on Terminal

2.9.27
RSTP Bridge test

There is a problem when I try to add in the terminal the pppoe-discovery and pppoe-session protocols, they dont exist… but on winbox they do..
So i add them on winbox, and the i export on terminal:

[admin@Gaona Master] interface bridge filter> export
/ interface bridge filter 
add chain=forward mac-protocol=0x8863 action=accept comment="" disabled=no 
add chain=forward mac-protocol=0x8864 action=accept comment="" disabled=no

But as i said i cannot add them on terminal..

[admin@Gaona Master] interface bridge filter> add chain=forward mac-protocol=0x8863 action=accept comment="" disabled=no
invalid value for argument protocol

It’s a bug? or im just stupid :stuck_out_tongue:

Best regards

It’s not a bug. So the choice seems to be pretty limited, yeah? :smiley:

[eugene@SM_BGP] interface bridge filter> add chain forward mac-protocol=       
Protocol name or number

MacProtocol ::= [!]Protocol
  Protocol ::= ProtocolName | ProtocolNumber
    ProtocolName ::= ProtocolName36 | MacProtocol
      MacProtocol ::= arp | ip | ipv6 | ipx | rarp | ...
      ProtocolName36 ::= length
    ProtocolNumber ::= 0..FFFF    (integer number)

[eugene@SM_BGP] interface bridge filter> add chain forward mac-protocol=8863

Best regards,
Eugene

:laughing: Yea, to much limited :stuck_out_tongue: BTW, when I enter the code as you said:

[admin@Gaona Master] interface bridge filter> add chain=forward mac-protocol=8863
[admin@Gaona Master] interface bridge filter> pr
Flags: X - disabled, I - invalid, D - dynamic 
0   chain=forward mac-protocol=0x229F action=accept

Best Regards

:blush:
anyway,

[eugene@SM_BGP] interface bridge filter> add chain forward mac-protocol=34915

Eugene

without the help of excellent OS X calculator I would write the following:

[eugene@SM_BGP] interface bridge filter> add chain forward mac-protocol=[:tonum 0x8863]

Eugene

Aaah, now that sounds more like the old script-Eugene I know… :smiley:

Best regards,
Christian Meis

:smiley: we will probably make a fix for this in 2.10.

:wink: