First of all it story comes from bad Mikrotik DNS, that can not handle more then ~10k entries for spam filter. OK, replacing it by pi.hole with crazy performance gain. Then printserver that Mikrotik can not handle at all. Ok, installing cups and raspberry sharing printers by mDNS. Ok, trying to make normal VPN from Mikrotik and no way to establish connection to protonvpn (Mikrotik have tiny part of standard, that it VPN supports). Ok, installing OpenVPN on pi, successful connect to proton. Speed is better then on 16 core Mikrotik . OK, redirecting pefixes to raspberry and it does not work without hairpin NAT. Ok, moving raspberry to another subnet+vlan, now VPN works fine and Iam loosing printers. Damn…
On a Mac, there is a command “dns-sd -Z” that outputs the LAN’s DNS records from mDNS broadcast, into a DNS zone file that can be use in a DNS server. I presume some similar tool exists for Win/Linux. Only issue is Mikrotik’s DNS doesn’t support one of the DNS type (PTR), so those records have to go into some other DNS server (perhaps Pi-Hole, but I haven’t tested)
I’m new here, just waiting on the arrival of my new Mikrotik router which I was really excited about… am I to understand that in (almost) 2023 mDNS is NOT a feature of Mikrotik routers?? I have a house full of IOT devices and use Home Assistant to bridge everything beautifully to homekit for me. All my IOT devices, cameras etc. My plan was to get a good router and actually segment everything into separate LANs. Im coming from pfsense, am I going to regret this decision?
Did you buy something that you can run a container on? If not then yes you’re going to regret this purchase. It has been made clear certain things mdns, fixing ipv6 on their wireguard implementation etc are just not in the cards. You can of course do it yourself with a container on mikrotik for mdns or like so many things in this ecosystem. Get another device and do the lifting for the nice to have features you won’t find here.
Brooding it over, mDNS allows information to flow from on vlan to another.
This may be not secure by design, this may be the explanation why Mikrotik does not plan to support it.
Brooding it over, mDNS allows information to flow from on vlan to another.
This may be not secure by design, this may be the explanation why Mikrotik does not plan to support it.
[/quote]
I can also expose winbox ports to the internet, have no firewall. All terrible security choices but the decision is left to me. mDNS is a standard found everywhere else. Seems broken by design to say we won’t support this for security reasons. That’s a decision that the user must make just like having sane firewall rules for their environment
That didn’t prevent MikroTik from supporting port forwarding or UPnP. And evidently MikroTik doesn’t even support upnp2 (miniupnpd) which offers more secure options. see this thread UPnP security questions
So using the security card isn’t a valid excuse for not allowing a user to choose to use an insecure “feature”. I don’t think anyone is requesting the option to be the default.
disclaimer: I don’t use port forwarding, upnp, upnp2 or mdns repeater or reflector on my ER-X, but they are all options that are available.
This is a bit like the major broswers no longer supporting “weak” SSL/TLS options at all. And forcing users that have legacy equipment that does not support the newer versions to use http or an old version of the browser that will allow an exclusion for a specific site. When you look at the options of poor security or no security, which is better?
I think I might be one of the most likely of this forum’s members to go around waving the “security” flag, and even I will tell you that a flat refusal to support mDNS forwarding on security grounds is bogus.
mDNS forwarding is a routing decision made by the network’s manager. Routing is what routers do, per the admin’s instructions.
mDNS is no more a “security risk” than is PIM-SM. Yes, it should be off by default, but it should be available, left up to the admin to employ properly when enabled.
I’m not certain about that. I still think this approach is worth trying.
If you’re wondering why I don’t try it and report back, it’s because on the networks I manage that have mDNS devices, I don’t (yet) use VLANs, so I don’t run into the problem in the first place.
I believe coupling that switch rule with suitable inter-VLAN routing rules should allow mDNS based negotiations to transit VLANs. If not, I’d like to know why.
Here’s one: AirPrint in a corporate environment. It’s convenient in BYOD shops to let people print from their iPhones or whatever, but if you think printers that haven’t received firmware updates for 10 years belong on the employee WiFi LAN, you’re either insane or not paying attention to security. Isolating the two with VLANs but allowing one-way print requests is entirely sensible.
Here’s another: screen-sharing to conference room displays. The plan to put a bad-ass LED wall in the boardroom might give the CEO a fuzzy, but if you tell him he can’t have it because there’s a Chinese ODM board at the heart of it that’s as full of holes as a block of Jarlsberg, he’s gonna buy the video wall anyway and then yell at IT when he can’t show his charts and graphs at the next board meeting because someone with a clue put the video wall on a different VLAN than the WiFi.
This is a very good example of the threat model I would like to protect against in my network setup. Most of us have an increasing number of (IoT) devices which run very obscure software stacks. A random bulb bought from eBay is a very example, but also, technically, there is nothing preventing Google to send a software update to my Chromecast and turn it into a spoofer. Having such a device completely free to roam in my network seems unnecessary and undesirable.
How would I do this? How do I setup my iPhone or Android phone to participate in more than one VLANs?
Indeed, ideally we want an IoT device to be segregated from everything else and allowed only the traffic that is expected from it. For example, an IoT device (e.g., a smart bulb) which uses MQTT should only be allowed to connect to the MQTT server via the relevant port. No other traffic needs to be allowed. In this example, RouterOS has sufficient support for me to implement this. The bulb is in the IoT vlan and the MQTT server is either in the IoT vlan and the firewall/routing rules allows me to access the MQTT server, or the MQTT server has access to both VLANs. Regardless of whether such an L3 segregation (via routing and firewall rules) is overly complicated or not, it is perfectly possible with features already supported by RouterOS (/ip/firewall and /ip/route).
Unfortunately, this is not as easy with devices that implement some form of autodiscovery via protocols such as mDNS, because these protocols assume that they are in the some broadcast domain.
L2 segregation is also possible in RouterOS but at the moment the way it is implemented (IEEE 802.1Q) makes it a binary decision (either no or complete segregation). Two devices either live in different VLANs and there is not broadcast between the two (e.g., mDNS, DHCP requests), or they live in the same VLAN and all broadcast messages are seen across the entire VLAN. I think the feature we’re asking for here is a tool to repeat mDNS broadcasts across VLANs.
Sorry for my late reply. On Debian installed “mdns-scan” package, which returns the PTR addresses, example:
mdns-scan
…
XXXX._spotify-connect._tcp.local
avahi-resolve --name allows to map the hostname to its IP addresses.
Debian also offers “mdnsd” package:
embeddable Multicast DNS Daemon
This is a standalone mDNS-SD daemon for small systems. Although still
limited in functionality it can announce services like FTP, HTTP, and
SSH and respond to scanning (enumeration) requests from tools like
mdns-scan.