From the docu I sort of get that I need to specify the relay IN THE SERVER, it's the first time I've seed this requirement so I'm a hundred. I tried just changing the interface of my existing DHCP servers but it refused to do so because it was already a server in there, I'm paraphrasing.
It doesn't seem so hard except there's a typo, and since this earlier requirement was introduced I'm not not sure which is it, then I remembered about the whole circuit ID and option eighty-something and got me a little more apprehensive about clicking on stuff and break again the network. This is what says in the docs:
I think it's in the second line. In the meantime I removed my ultra-permissive allow all firewall rules and just added a single allow rule input chain, so if I got it right it should allow for CHR-hosted services (like DHCP) but won't actually route. The router has an active interface on every VLAN as the new main router, an regular L3 switch, so far it's there haven't been any issues, but IPv6 is handled by another set of devices this devices have to ton of tools to prevent routing loops so it might already be working harder than it needs to.needed, the counter in the input chain is a little too high for local services: Could you confirm if I'm the right place?? That is, all I need it to add relay addresses on each DHCP server so they can all share a single interface to be relayed. Just smash the keyboard and I'll take it as a yes. :) Thanks!/ip pool add name=Local1-Pool ranges=192.168.1.11-192.168.1.100
/ip pool add name=Local1-Pool ranges=192.168.2.11-192.168.2.100
[admin@DHCP-Server] ip pool> print
# NAME RANGES
0 Local1-Pool 192.168.1.11-192.168.1.100
1 Local2-Pool 192.168.2.11-192.168.2.100
[admin@DHCP-Server] ip pool>