My response is that configuring the router is not about vlan details, its about understanding what you really want to do?
So dont search for a specific technical functionality, to fix a problem that is not described, because it will not be a fruitful discussion…
This approach leads to whackamole and twenty additional questions as we unravel the mystery of your mind.
Lay out the requirements clearly without any config talk.
a. identify devices/users and groups of devices/users including admin
b. identify what traffic each should be able to accomplish
c. identify what traffic they should not be able to accomplish
Provide a network diagram…down to port specific vlans conceptualized…
Then a config will fall out naturally. Anything else is trying to stuff square pegs into round holes. The router is very malleable and can be setup many ways, however to provide a clean, efficient optimal path means you need to provide context and understand your own plan in sufficient detail to communicate it to us.
For the moment, no particular architecture, I already have a network in place (Fw/pFsense router).
I am in the learning phase of the Mikrotik universe.
I try to understand the basic configuration (Vlan, DHCP etc…)
To summarize, I’m testing with a single machine to get an ip in one of the following networks/vlans tests (no sucess):
Vlan 55 (mode bridge) : eth3 & 4
Vlan 56 (not in bridge) : Ether 6
Vlan 99 (mode bridge) : Eth 12 & 13
Here is my use case, there is nothing else (+ an uplink to a switch, but which is used only when I cut my hand in the tests), not even internet,
it remains only the comprehension of a vlan and DHCP configuration.
When I will have understood how it works, I will think about replacing the pfsense but I’m not there at all
After several attempts, I can not understand why a simple untagged port does not allow to distribute an ip.
So yes I read the posts, and use the search engine.
But considering the number of posts on the subject (routerOS config bridge/vlan) not sure that it is so simple
problem solved !
Something must have been wrong with the firmware.
A netinstall procedure with downgrade to 7.6 and DHCP is working in 2 minutes.
Thanks anyway for the answers.