You don’t even need one. You are connecting to a device (Mikrotik) which has an IP in the same network-range.
Even if you take a wrong one like 10.50.50.27, it would never be used in your case :
PC = 10.50.50.253 mask 255.255.255.0
Mikrotik = 10.50.50.254
“you should only check the firewall INPUT-chain (INPUT = traffic targetted at router itself, Winbox for example). Make sure you have some rule allowing ether7 (or source-IP 10.10.10.0/24) to target the the RouterOS control plane.”
To do this firewall rule, I go to IP → Firewall → Filter Rules → Add →
Chain: Input
Src Address: 10.10.10.0/24
In. Interface List: all
Action: accept
Is this correct? Also, what is the purpose of this, does this simply stop other PCs from accessing this ethernet port? For example, lets say a PC with IP address 50.50.50.1 tried to access ether7 port. It would block them because the source-IP is not 10.10.10.0/24?
(1) Try this instead AFTERimplementing steps 2 and beyond!
IP address: 10.10.10.5
Subnet mask: 255.255.255.0
Default gateway: 10.10.10.254
DNS: 10.10.10.254
Secondary DNS: 8.8.4.4
(2) Why do you have interfaces list of TRUSTED and MANAGE when you only have one subnet??
Okay I see ether7 is part of MANAGE which is not a bad idea…
(3) YOu should remove this as its a left over from default config…
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan
(4) The idea of the trusted subnet is also to use the associated interfaces in a couple of spots so you should do this as well. The idea being you want to use one interface list entry for the input chain to access the router and the interface list to use twice elsewhere. We dont want to lump in ether7 with the rest of the LAN interface and its associated firewall rules, but just the input chain one etc…
SO add interface=bridge list=MANAGE
Thus you should do this after: /ip neighbor discovery-settings
set discover-interface-list=MANAGE
THEN it will be matter of firewall rules to match!!
(5) From: add action=drop chain=input comment=“defconf: drop all not coming from LAN”
in-interface-list=!LAN
TO: add action=accept chain=input in-interface-list=MANAGE **** scr-address-list=Authorized
add action=accept chain=input in-interface-list=LAN dst-port=53 protocol=tcp
add action=accept chain=input in-interface-list=LAN dst-port=53 protocol=udp
add action=drop chain=input comment=“Drop all else”
Optional but I recommend it since you only have one subnet is to limit the access to the router for config purposes to only specific IP addresses
/ip firewall address lsit { assumes you have set the below to fixed static leases! }
add address=10.10.10.5/32 list=Authorized comment=“ether7 access”
add address=Admin-Desktop-IP list=Authorized
add address=Admin-laptoip-IP list=Authorized
add address=Admin-lpad-IP list=Authorized
add address=Admin-smartphone-IP list=Authorized
(6) From: add action=drop chain=forward comment=
“defconf: drop all from WAN not DSTNATed” connection-nat-state=!dstnat
connection-state=new in-interface-list=WAN
TO: add action=accept chain=forward in-interface-list=LAN out-interface-list=WAN
add action=accept chain=forward connection-nat-state=dstnat
add action=drop chain=forward comment=“Drop all else”
(7) From: /tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN
TO
/tool mac-server
set allowed-interface-list=NONE { this is not a secure protocol and thus dont use }
/tool mac-server mac-winbox
set allowed-interface-list=MANAGE
+++++++++++++++++++++++++++++++++++++++++++++
In summary the confusion you have between the bridge, the lan interface and the manage/trusted is what is causing the issues.
Above is the straightforward approach to get you working safely.