Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
20.1 Legacy Series
»
mDNS stopped working since upgrading to 20.1.3
« previous
next »
Print
Pages: [
1
]
Author
Topic: mDNS stopped working since upgrading to 20.1.3 (Read 6112 times)
alh
Full Member
Posts: 123
Karma: 6
mDNS stopped working since upgrading to 20.1.3
«
on:
April 04, 2020, 11:30:59 am »
Two weeks ago I upgraded an OPNsense installation from 19.7 to the latest 20.1.3. Since then printers cannot be found using Bonjour/mDNS anymore if they are in a different network. mDNS repeater plugin is installed and appears to be running fine (there is nothing in the logs that suggests otherwise) but the devices don't appear on the clients.
Any idea how to troubleshoot/fix this?
Logged
alh
Full Member
Posts: 123
Karma: 6
Re: mDNS stopped working since upgrading to 20.1.3
«
Reply #1 on:
April 06, 2020, 11:23:04 am »
For now I solved it by using a Linux box and the avahi package. Any chance of getting an avahi package to OPNsense similar to pfsense?
Logged
fabian
Hero Member
Posts: 2769
Karma: 200
OPNsense Contributor (Language, VPN, Proxy, etc.)
Re: mDNS stopped working since upgrading to 20.1.3
«
Reply #2 on:
April 06, 2020, 06:59:17 pm »
Probably not - avahi has too many dependencies.
Logged
Gauss23
Hero Member
Posts: 766
Karma: 39
Re: mDNS stopped working since upgrading to 20.1.3
«
Reply #3 on:
May 03, 2020, 07:55:25 pm »
Hi,
I´m using OPNSense now as a replacement for a pfSense. I have the same problems with mDNS-repeater. The project itself looks quite unmaintained.
mDNS-repeater forgets i.e. a HP printer. Printer is powered up and is available on all selected interfaces for around 5 minutes. After that period the connection gets lost. Restarting the Bonjour service on the HP printer makes it working for another 5 minutes.
Avahi makes a much better impression to me. I installed avahi on a Ubuntu 20 box and let it monitor all vlans which have need for mDNS traffic forwarding. Works out of the box without those 5 minute timeouts. Will try to install it from the opnsense-ports. But I don´t want to break anything on my OPNSense.
Is there a chance to get avahi as a plugin? Or at least some investigation why the mDNS-repeater is not working correctly? I want to get rid of this pointless Ubuntu box.
What would be needed to investigate this further?
Best regards
Logged
„The S in IoT stands for Security!“
fabian
Hero Member
Posts: 2769
Karma: 200
OPNsense Contributor (Language, VPN, Proxy, etc.)
Re: mDNS stopped working since upgrading to 20.1.3
«
Reply #4 on:
May 03, 2020, 08:46:47 pm »
the problem with avahi is, that it pulls in a bunch of dependencies, which was the reason, why we used mdns-repeater. There is another plugin in development, which forwards multicast.
Logged
Gauss23
Hero Member
Posts: 766
Karma: 39
Re: mDNS stopped working since upgrading to 20.1.3
«
Reply #5 on:
May 04, 2020, 11:25:14 am »
Thank you for the fast answer. Now I´m keen on the new plugin
Logged
„The S in IoT stands for Security!“
franco
Administrator
Hero Member
Posts: 17659
Karma: 1611
Re: mDNS stopped working since upgrading to 20.1.3
«
Reply #6 on:
May 04, 2020, 11:29:25 am »
See here
https://forum.opnsense.org/index.php?topic=15910.msg77513#msg77513
Logged
Gauss23
Hero Member
Posts: 766
Karma: 39
Re: mDNS stopped working since upgrading to 20.1.3
«
Reply #7 on:
May 04, 2020, 12:55:52 pm »
That looks promising. Will try it out today.
Thank you very much!
Logged
„The S in IoT stands for Security!“
Gauss23
Hero Member
Posts: 766
Karma: 39
Re: mDNS stopped working since upgrading to 20.1.3
«
Reply #8 on:
May 04, 2020, 09:06:14 pm »
My feedback: new plugin is working good so far.
The recommended options for mDNS include a source-address spoof of 1.1.1.1 (which means set the outgoing interface ip as origin). With this option set it´s like with mDNS-repeater: timeouts after 5 minutes. Leaving source empty solves this for me. No timeouts. Printer is always available at all networks, which are included in the service. 1.1.1.2 isn´t working at all for me. No connection.
Perfect.
As I have no ChromeCast devices this isn´t a deal-breaker for me.
Am I the only one with those 5 minute timeouts with 1.1.1.1 set?
Thank you Fabian and Franco! Great support, great product!
Logged
„The S in IoT stands for Security!“
franco
Administrator
Hero Member
Posts: 17659
Karma: 1611
Re: mDNS stopped working since upgrading to 20.1.3
«
Reply #9 on:
May 04, 2020, 09:28:34 pm »
Martin and Michael put in the effort to get this included. Credit where credit is due.
We will make the new plugin stable with an upcoming 20.1.x release.
Cheers,
Franco
Logged
Gauss23
Hero Member
Posts: 766
Karma: 39
Re: mDNS stopped working since upgrading to 20.1.3
«
Reply #10 on:
May 05, 2020, 10:12:53 am »
Of course: thank you Martin and Michael for this great plugin!
Logged
„The S in IoT stands for Security!“
marjohn56
Hero Member
Posts: 1701
Karma: 179
Re: mDNS stopped working since upgrading to 20.1.3
«
Reply #11 on:
May 05, 2020, 11:29:17 am »
And Berto, he also had an input.
Logged
OPNsense 24.7
-
Qotom Q355G4
- ISP -
Squirrel 1Gbps
.
Team Rebellion Member
- If we've helped you remember to applaud
Gauss23
Hero Member
Posts: 766
Karma: 39
Re: mDNS stopped working since upgrading to 20.1.3
«
Reply #12 on:
May 05, 2020, 01:42:31 pm »
We won´t forget Berto! Thanks!
Logged
„The S in IoT stands for Security!“
IsaacFL
Full Member
Posts: 217
Karma: 8
Re: mDNS stopped working since upgrading to 20.1.3
«
Reply #13 on:
June 08, 2020, 08:15:04 pm »
I seem to see a lot of requests for Avahi. I don't understand the hesitancy to create an Avahi package. None of the other solutions proposed here work with ipv6?
Avahi seems to be supported by everywhere (including freebsd) but opnsense and it does work in an ipv6 environment. Avahi seems to be currently updated and supported.
I just would like to get Airprint to work across subnets in ipv6 with Apple products. So open to other suggestions.
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
20.1 Legacy Series
»
mDNS stopped working since upgrading to 20.1.3