I have 8 ports and I would like most of them to talk to each other and be part of the LAN.

Port 8 is WAN
Port 2 connects to the LAN and works

Anything I plug into ports 1 and 3-7 do not connect into the LAN. I thought a local bridge would work but I can't figure out how to do this. It seems like Interface Lists might be the answer, but I can't find a working tutorial.

I'm sure this is really trivial. Can anybody help?

PS. The reason WAN is port 8 and not port 1 is that I want the 2.5G port 1 to be part of the LAN.

Post your config
/export file=anynameyouwish (minus router serial number and any public WANIP information

YOu need to detail which ports should not be able to reach to other ports
You need to detail which ports should be able to reach other ports (which ones)

Config attached. I want all ports except WAN, including the SFP+ port, to act like a regular dumb switch and all talk to each other. Only port 8 should be treated differently as the WAN port. After I've got this working I'll convert 2 of the ports to a bonded LAG port, but I've done that before.

Thanks is advance.

I don't do bridges in RouterOS, but even I can answer that one. You created the bridge and only put port 2 into the bridge. You need to add the rest of the ports ( except the WAN port 8 ) into the bridge.
Other problems may exist with the bridge but as I said, I don't do bridges in RouterOS so I am really weak on setting them up.

Too funny, you only put ether2 on the bridge you need the rest......

/interface bridge port
add bridge=local interface=ether1
add bridge=local interface=ether2
add bridge=local interface=ether3
add bridge=local interface=ether4
add bridge=local interface=ether5
add bridge=local interface=ether6
add bridge=local interface=ether7

Would modify your input rules slightly and fix order.......
/ip firewall filter
add action=accept chain=input comment="accept established, related" \
connection-state=established,related
add action=drop chain=input connection-state=invalid
[b]add action=accept chain=input comment="accept ICMP" protocol=icmp[/b]
add action=accept chain=input comment="Accept LAN traffic" in-interface=local
add action=drop chain=input comment="block everything else"

As for the forward chain same same.....
add action=fasttrack-connection chain=forward comment="Fasttrack not IPSEC" \
connection-mark=!ipsec connection-state=established,related hw-offload=\
yes
add action=accept chain=forward connection-state=established,related,untracked
add action=drop chain=forward comment="Drop Invalid" connection-state=invalid \
log-prefix=invalid
add action=accept chain=forward disabled=yes in-interface=local \ { enable it if you want internet traffic }
out-interface=Vodafone
add action=accept chain=forward connection-nat-state=dstnat disabled=yes { enable it if you do want port forwarding }
action=drop chain=forward comment="Drop all Else"
++++++++++++++++++++++++++++++++++++++++++++++++++

Notes:
- ICMP jumping is for the birds, not required and can get in the way of legit traffic and importantly testing.
- bogons should not be used by folks not knowing why and how they work........... which is clearly the case here....... ( copying and pasting "good ideas" from youtube should be avoided )

As for the ports seeing each other, they should by the fact they are on the same bridge and thus connected at layer 2.

Many thanks to both for the replies. I tried a few things close to this but hadn’t got it quite right

...You created the bridge and only put port 2 into the bridge. You need to add the rest of the ports ( except the WAN port 8 ) into the bridge....

To dazzaling69:

Think of a bridge as of virtual switch with no ports which could be used to connect devicese and pass traffic to them.
Just a box with no connectors except power plug.
You have to assign real ports to that bridge or you can assign virtual ones (IP-IP or EOIP ore GRE tunnels, VETH etc.).
Then it behaves as a typical "dumb" switch ...from the very wide perspective.