Regarding frames towards the Mikrotik itself, hw=yes should not cause any trouble. However, if you have hardware acceleration enabled on ether7 ( hw=yes), the frames forwarded between ether7 and any other port on the same switch chip where hw=yes too bypass the CPU so the bridge filter cannot affect them. Max-message-age=20s forward-delay=15s transmit-hold-count=6 vlan-filtering=yes ether-type=0x8100 pvid=1įrame-types=admit-all ingress-filtering=no > interface bridge settings print ) i want to set a static IP for that device based on MAC Address so i searched on how to do it and worked for me for the first devices and like a charm. Protocol-mode=rstp fast-forward=yes igmp-snooping=no auto-mac=no admin-mac=xx:xx:xx ageing-time=5m priority=0x8000 i am still learning how to use Mikrotik (hEX S) features i was planning to let DHCP server give IPs as normal, and for some special devices (for any reason could be my devices could be kids devices could be a guest. Name="bridge" mtu=auto actual-mtu=1500 l2mtu=1598 arp=enabled arp-timeout=auto mac-address=B8:69:F4:xx:xx:xx The bridge where I've tried it looks as follows: Maybe some bridge settings or fast forward can affect to this. I tried both options, but I haven't idea why this rule isn't working.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |