Is the “trunk link” connected to ether1 using a native vlan 10? i.e. a “hybrid” in MikroTik terminology.
If so, make a backup (because I have not tried this myself) and copy it to a pc you can restore from.
Also export and save.
Go into safe mode, just in case you loose connection to the hEX
Then try setting the following for vlan-id 10
/interface bridge port
set bridge=bridge interface=ether1 pvid=10
/interface bridge vlan
set bridge=bridge untagged=bridge,ether1,ether4,ether5 vlan-ids=10
Here is my thought process, please let me know where it is incorrect.
You have specified that you want the bridge interface to get an ip address from a dhcp server that is on the native (untagged) vlan 10 that is connected to ether1. Since the bridge is untagged, and you have set the bridge pvid to 10, when the hEX S wants to connect to get an ip address, it will send a dhcp discover broadcast on the bridge device, and because it has pvid 10, it will send the broadcast out vlan 10 ports, and ether1 also has pvid 10 and is untagged on egress, so the dhcp server on the untagged vlan will receive the broadcast.
I don’t think the bridge woutd have to have pvid 10, unless ether1 was tagged for vlan 10, and the dhcp server was on vlan 10 (perhaps connected to an access port for vlan 10 on a switch connected via a trunck port to the trunk port on hEX ether1).
I also don’t understand why the bridge needs to be connected to vlans other than 10, as long as the hEX is just acting as a switch with a management interface on vlan 10. But I am ROS noob, so I am willing to learn why it would be needed. At least that’s the way I understand the VLAN Example - Trunk and Access Ports section of Bridge VLAN Filtering