Announcement

Collapse
No announcement yet.

mDNS (external)

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    @Some Dude: First of all, welcome to the forums! Before I reply, just want to make it known that I'm a home user too, I don't resell Untangle into businesses or anything like that. I'm not a network engineer either, so forgive or point out any errors!


    Originally posted by some dude View Post
    The request for a mDNS reflector is currently the 4th highest ranked item in the Untangle NG Firewall Feature Requests List.

    As of today, it has 566 votes. Many of the comments (mine included) are requesting the Untangle product management team to provide the community with a better response on both IF as well as WHEN this feature will be implemented as a supported feature. Currently, the tag is simply "Under Consideration", this is a non-answer. The request has been up since August 2018, how much longer do you need to "consider"?
    I hear your frustration, but maybe the fact that request has been on the list since 2018 without being added is all the answer you need? That's not to say that Untangle shouldn't just say "It's never gonna happen" if that's the case, but the truth is that it might... someday - who knows.

    What we need to remember is that Untangle's overwhelming customer base is enterprise and education. So their time is probably being spent working on things that those customers want to see in the product. I should imagine that customers like that (who are spending thousands on licences) have a direct line into the ear of an account manager or real person at Untangle. Perhaps the feature request list is not the only way that what gets done soonest is decided? Just because something is number one, two, three or four on the list, it doesn't mean that it's actually anywhere near being the top on the list of things to do. But yes... to anyone who is interested in those features, Untangle could do a better job of sharing their plans. Do they do a worse job of that than any other company who lets you submit feature requests? I don't know. I'm also not saying that home users don't matter; just that most companies will probably focus on what the majority of their users are asking for - and I don't think Untangle's home users are their majority. To be honest though, if I had to choose, I'd rather Untangle focused on features and improvements that made my network as secure as possible - the kind of features that enterprise customers want in their NGFW.

    If you want to stick IoT devices into a separate VLAN (I've done that too...) then you're kinda saying that putting those devices in their own broadcast domain is a good way to go. If you then realise that now they don't work as intended and you look for a technology to essentially break the separation you put in place, then maybe a VLAN isn't the best answer for those devices? If you're worried about them being attacked and accessing the rest of the devices on that network, then a VLAN is not the only option you've got to stop that.

    Originally posted by some dude View Post
    Based on my own research before purchasing a Home Protect Basic license, as well as the specific comments on this feature request, your main competitors in this space all include support for an mDNS reflector:
    - pfSense / OpnSense
    - Sophos UTM
    - Ubiquiti UDM / EdgeRouter / USG
    In my humble opinion, Untangle beats all of those on the factors that matter in an NGFW way more than mDNS support; so if that's the price I have to pay, so be it. Deep down, that's probably why you went with Untangle too, but sure... there's always room for improvement.

    Originally posted by some dude View Post
    This is a feature that is absolutely necessary for the seamless function of modern networks in many small/medium business as well as home use cases. Every day that passes, more and more IOT devices are being installed in our networks, ease of use is one of the many reasons why this is the case. mDNS is a big part of why these devices achieve the ease of use that is resulting in their market success.
    Indeed. And I too had the same grief trying to get certain IoT devices to play nice over VLANs. I wanted to see how the pros do it and I reached out to a few of my colleagues that install high-end home cinema/automation systems etc. The answer was basically if something needs to be controlled from within a VLAN, then they provide a means of doing that from within the VLAN. So that might be a dedicated control/touchpad, dedicated PCs or rPIs etc etc. mDNS works fine and is easy, convenient in a home setup, but it's considered a workaround.

    Originally posted by some dude View Post
    ...ease of use is the reason why many of us have chosen to put Untangle NG Firewall at the center of our network security.
    The funny thing is, "ease of use", "plug and play", "user-friendly" etc, etc are typically the things that go hand-in-hand with something being less secure. As you've seen... Security tends to get in the way of things "just working".

    Originally posted by some dude View Post
    The fact remains that these IOT devices should be isolated in separate VLANS (which Untangle supports quite easily) except without the mDNS reflector service many of the key use cases for these devices are flat broken.
    Should they be in their own VLAN? Im not attacking you here... Like I said, I've done the same with my IoT devices. I only have one (ChromeCast) that is useless if not in with my trusted devices, but it's not hard to lock that down. Since you mention "the key use cases for these devices" I think it's fair to say that use case was probably never intended to be across VLANs and if it was, then many like Amazon, Philips, Ubiquity have figured out how to make their apps work by essentially going out and in again.

    As I said earlier; Untangle could probably do a better job of keeping the wider community in the loop. And you're right, people can vote with their feet and their dollars too. But in all honesty, if you're looking for a grown-up security product that gives you everything Untangle does, in the way that it does it, (and crucially) at that price - you'd be hard-pressed to find somewhere better to spend those dollars - mDNS or not.

    Comment


    • #17
      mDNS is actively removed from all of my networks, as it has zero place on any of them... it represents a HUGE security fault, and is actually designed to be abused. I have similar issues with uPnP. Since Untangle is a security product, implementing it must be done extremely carefully, lest Untangle be blamed for a poor configuration down the line.

      How about demanding IoT devices that are actually maturely designed and don't need to rely on broken, easily exploited technology? Google is a huge offender here, ChromeCast specifically is HORRIFIC. You'd think a company that runs networks as large as Google's would know how to engineer things properly... sadly they very much don't.

      Also, don't get me started on the products you listed as alternatives... We'll be here until doomsday.

      Finally, Armshouse is correct. Untangle prioritizes features that get them paid, that means they focus on education, then corporate needs. Home users are an afterthought, a marginal customer base. Untangle does seem to be angling to support them more though, but Untangle also has historically had limited resources. So I guess we'll see how the next decade goes. But, and I'll be more blunt... it all boils down to how much Untangle can EARN while selling Home subscriptions. Even the mere potential of earning, will drive investment. Does it exist? I have no idea... I can tell you my own attempts to monetize that entire market have met with nothing but dismal failure.
      Last edited by sky-knight; 02-13-2021, 02:18 PM.
      Rob Sandling, BS:SWE, MCP, Microsoft Certified: Azure Administrator Associate
      NexgenAppliances.com
      Phone: 866-794-8879 x201
      Email: [email protected]

      Comment


      • #18
        Originally posted by sky-knight View Post
        mDNS is actively removed from all of my networks, as it has zero place on any of them... it represents a HUGE security fault, and is actually designed to be abused. I have similar issues with uPnP. Since Untangle is a security product, implementing it must be done extremely carefully, lest Untangle be blamed for a poor configuration down the line.
        In a corporate network, the IT department might be able to ban IoT devices (or manage them in a secure way that requires a lot of manual work so that they can still do their job) - but that does not work for home networks where a "mostly secure, home user friendly" solution is needed.

        Maybe IT professionals simply don't care about those of us who use Untangle in a home network, but let's not forget that Untangle is actively licensed and advertised for home use - there are 2 different Home subscription plans now.

        So since we cannot avoid IoT devices in at least one environment that is supported by Untangle, putting IoT devices on a separate VLAN + mDNS at least seems "more secure" than not doing that, right?

        So unless you have a better idea I do think that Untangle should finally add that highly requested feature (among many others).

        Also this is an honest question, if there is a better solution I want to know about it because I want to move the IoT devices in my home onto a separate VLAN while not breaking/degrading the user experience / their function.
        Last edited by cholzer; 04-28-2021, 01:56 AM.

        Comment


        • #19
          Actually... it isn't "supported by Untangle".

          It's SOLD by Untangle, but support specifically is booted to these forums. Where people like me help with volunteer time.

          This is semantics, but it's very important to understand. I don't speak for Untangle, but I will reiterate... they're going to invest in changes that are likely to get them paid more. That means more attention to larger customers than smaller ones... UNLESS the home sub becomes so absurdly popular it cannot be ignored. It's a high volume, low margin product! If the volume gets high enough, you'll see investment made!

          I just just once again reiterate, it's not easy to get that volume.
          Rob Sandling, BS:SWE, MCP, Microsoft Certified: Azure Administrator Associate
          NexgenAppliances.com
          Phone: 866-794-8879 x201
          Email: [email protected]

          Comment


          • #20
            Originally posted by sky-knight View Post
            If the volume gets high enough, you'll see investment made!

            I just just once again reiterate, it's not easy to get that volume.
            As far as I can tell there is no marketing effort to home users. Without marketing it will never grow. Word of mouth is all I have ever seen for untangle, home or otherwise. Well other than their junk mail. lol

            Comment


            • #21
              Originally posted by donhwyo View Post
              As far as I can tell there is no marketing effort to home users. Without marketing it will never grow. Word of mouth is all I have ever seen for untangle, home or otherwise. Well other than their junk mail. lol
              I can't comment on that much because exactly none of the marketing I've ever attempted has ever worked.

              But I do chuckle at people complaining about the Home subscription prices when Netgear is making a killing selling Orbi.
              Rob Sandling, BS:SWE, MCP, Microsoft Certified: Azure Administrator Associate
              NexgenAppliances.com
              Phone: 866-794-8879 x201
              Email: [email protected]

              Comment


              • #22
                LoL

                Comment


                • #23
                  Originally posted by sky-knight View Post
                  But I do chuckle at people complaining about the Home subscription prices when Netgear is making a killing selling Orbi.
                  A subscription for "a router" is a new concept for many people.

                  But everyone I showed what I do with untangle in my home did see the benefit they get from the apps included in the Home plans and never complained (to me) about the costs again afterwards.

                  I got a good amount of people to use Untangle for their home and they are all very happy with it.

                  Personally I just miss 2 things. CAKE for QoS/SQM and I want to do something about those IoT devices - a "solution" that is feasible for a home environment.
                  Last edited by cholzer; 04-28-2021, 11:04 PM.

                  Comment


                  • #24
                    Originally posted by datstma View Post
                    Just figured this one out :-)
                    Hey Stefan, can you help me out?

                    I just tried this on a test install.
                    eth1 is 192.168.2.0
                    eth1.10 is 192.168.10.0

                    I did not setup any firewall rules to block traffic between the networks

                    Via the IP I can access any device across the networks.

                    But the Sonos app can't see the sonos speakers on the other network, the YT app see the TV on the other network and windows fails to discover the network printer when it is on the other network.

                    So this does not appear to work for me but I don't know what I did wrong since I followed your steps.

                    Code:
                    [root @ untangle] ~ # sudo systemctl status avahi-daemon
                    ● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
                       Loaded: loaded (/lib/systemd/system/avahi-daemon.service; enabled; vendor preset: enabled)
                       Active: active (running) since Fri 2021-07-02 17:26:43 CEST; 6min ago
                     Main PID: 469 (avahi-daemon)
                       Status: "avahi-daemon 0.7 starting up."
                        Tasks: 2
                       Memory: 1.9M
                       CGroup: /system.slice/avahi-daemon.service
                               ├─469 avahi-daemon: running [untangle.local]
                               └─481 avahi-daemon: chroot helper
                    
                    Jul 02 17:26:43 untangle.example.com avahi-daemon[469]: No service file found in /etc/avahi/services.
                    Jul 02 17:26:43 untangle.example.com avahi-daemon[469]: Network interface enumeration completed.
                    Jul 02 17:26:43 untangle.example.com avahi-daemon[469]: Server startup complete. Host name is untangle.local. Local service cookie is 1450311942.
                    Jul 02 17:26:43 untangle.example.com systemd[1]: Started Avahi mDNS/DNS-SD Stack.
                    Jul 02 17:26:52 untangle.example.com avahi-daemon[469]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.2.1.
                    Jul 02 17:26:52 untangle.example.com avahi-daemon[469]: New relevant interface eth1.IPv4 for mDNS.
                    Jul 02 17:26:52 untangle.example.com avahi-daemon[469]: Registering new address record for 192.168.2.1 on eth1.IPv4.
                    Jul 02 17:26:52 untangle.example.com avahi-daemon[469]: Joining mDNS multicast group on interface eth1.10.IPv4 with address 192.168.10.1.
                    Jul 02 17:26:52 untangle.example.com avahi-daemon[469]: New relevant interface eth1.10.IPv4 for mDNS.
                    Jul 02 17:26:52 untangle.example.com avahi-daemon[469]: Registering new address record for 192.168.10.1 on eth1.10.IPv4.

                    Code:
                    [server]
                    #host-name=foo
                    #domain-name=local
                    #browse-domains=0pointer.de, zeroconf.org
                    use-ipv4=yes
                    use-ipv6=yes
                    allow-interfaces=eth1,eth1.10
                    #deny-interfaces=eth0
                    #check-response-ttl=no
                    #use-iff-running=no
                    #enable-dbus=yes
                    #disallow-other-stacks=no
                    #allow-point-to-point=no
                    #cache-entries-max=4096
                    #clients-max=4096
                    #objects-per-client-max=1024
                    #entries-per-entry-group-max=32
                    ratelimit-interval-usec=1000000
                    ratelimit-burst=1000
                    
                    [wide-area]
                    enable-wide-area=yes
                    
                    [publish]
                    #disable-publishing=no
                    #disable-user-service-publishing=no
                    #add-service-cookie=no
                    #publish-addresses=yes
                    publish-hinfo=no
                    publish-workstation=no
                    #publish-domain=yes
                    #publish-dns-servers=192.168.50.1, 192.168.50.2
                    #publish-resolv-conf-dns-servers=yes
                    #publish-aaaa-on-ipv4=yes
                    #publish-a-on-ipv6=no
                    
                    [reflector]
                    enable-reflector=yes
                    #reflect-ipv=no
                    
                    [rlimits]
                    #rlimit-as=
                    #rlimit-core=0
                    #rlimit-data=8388608
                    #rlimit-fsize=0
                    #rlimit-nofile=768
                    #rlimit-stack=8388608
                    #rlimit-nproc=3
                    Last edited by cholzer; 07-02-2021, 08:51 AM.

                    Comment


                    • #25
                      I'm chiming in here because, after several years of enjoying Untangle, the lack of VLAN mDNS support is frustrating.

                      I've read through pretty much all forum topics discussing mDNS and despite a clear desire from Untangle users to have it implemented, the developers choose not to.

                      I find it interesting that the reason not to is because it's a security issue but uPNP is still implemented and with a few clicks within the untangle GUI you can compromise your system (incorrect port forwarding or access rules, WebGUI/ssh enabled to wan, etc). Heck, just inputting a compromised DNS server into your interface settings could introduce a whole host of issues.

                      It would be great if Untangle would come out formally and say either 1) They refuse to implement it, ever 2) They don't know how to correctly implement it or 3) They've implemented it and use it at your own risk. Maybe even disable it on untangle appliances to further CYA.

                      Just 2 cents from a 99.9% happy untangle user that just wants mDNS across VLANs.

                      Comment


                      • #26
                        Originally posted by technologiq View Post
                        I'm chiming in here because, after several years of enjoying Untangle, the lack of VLAN mDNS support is frustrating.

                        I've read through pretty much all forum topics discussing mDNS and despite a clear desire from Untangle users to have it implemented, the developers choose not to.

                        I find it interesting that the reason not to is because it's a security issue but uPNP is still implemented and with a few clicks within the untangle GUI you can compromise your system (incorrect port forwarding or access rules, WebGUI/ssh enabled to wan, etc). Heck, just inputting a compromised DNS server into your interface settings could introduce a whole host of issues.

                        It would be great if Untangle would come out formally and say either 1) They refuse to implement it, ever 2) They don't know how to correctly implement it or 3) They've implemented it and use it at your own risk. Maybe even disable it on untangle appliances to further CYA.

                        Just 2 cents from a 99.9% happy untangle user that just wants mDNS across VLANs.
                        I'm good for a solid rant, I've been known to write a few myself. But you should know that forums are a TERRIBLE place to get good information unless you consider the source first.

                        Here, have some actual information from someone with a small amount of knowledge: https://untanglengfirewall.featureupvote.com/
                        Rob Sandling, BS:SWE, MCP, Microsoft Certified: Azure Administrator Associate
                        NexgenAppliances.com
                        Phone: 866-794-8879 x201
                        Email: [email protected]

                        Comment


                        • #27
                          Done, thank you.

                          Comment


                          • #28
                            One more or one hundred will not make it happen unless they start listening to their customers again. Heck they haven't taken up a free offer of help.
                            https://untanglengfirewall.featureup...ncy-management

                            Comment

                            Working...
                            X
                            😀
                            🥰
                            🤢
                            😎
                            😡
                            👍
                            👎