Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Avahi with IPv6 bug

    Scheduled Pinned Locked Moved pfSense Packages
    26 Posts 5 Posters 3.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • dennypageD
      dennypage @IsaacFL
      last edited by

      @isaacfl said in Avahi with IPv6 bug:

      Right now, I have a rule that passes ipv6 Link_Local_Address to Multicast. If someone else were to come in and see this, they would think "That's not legal. You can't pass Link Local addresses, out of the subnet" so I put a comment, required by Avahi on the rule. Maybe that is only way.

      Let's pop up a level. Can you explain what it is you are trying to accomplish with using Avahi? Is it providing information about the firewall itself? Or is it allowing dns-sd to function across subnets?

      IsaacFLI 1 Reply Last reply Reply Quote 0
      • IsaacFLI
        IsaacFL @dennypage
        last edited by

        @dennypage said in Avahi with IPv6 bug:

        @isaacfl said in Avahi with IPv6 bug:

        Right now, I have a rule that passes ipv6 Link_Local_Address to Multicast. If someone else were to come in and see this, they would think "That's not legal. You can't pass Link Local addresses, out of the subnet" so I put a comment, required by Avahi on the rule. Maybe that is only way.

        Let's pop up a level. Can you explain what it is you are trying to accomplish with using Avahi? Is it providing information about the firewall itself? Or is it allowing dns-sd to function across subnets?

        I think it is just dns across subnets, but not sure. I am trying to get all of the Apple based home automation type things to work across the subnets. I have my iphones, ipads, appletvs wirelessly connected to one subnet. I have my thermostats, garage door openers, smart switches etc. in a different subnet. My windows pcs and printers in a 3rd subnet.

        So with Avahi working properly I can print something from the iPhone in one subnet to printer in a different subnet. Also Apple TV can play a movie from a PC which is running iTunes.

        It does seem to be working with Avahi, but I notice it is falling back to ipv4 a lot. Whereas before I subnetted the devices it was ipv6 exclusively. So trying to isolate the issues.

        1 Reply Last reply Reply Quote 0
        • IsaacFLI
          IsaacFL @jimp
          last edited by

          @jimp said in Avahi with IPv6 bug:

          It's more broken to reappropriate existing macros and terms to include things they should not.

          Anyone who saw a rule with a destination of "multicast" and actually thought it would leave the segment needs reeducated. That's not confusing at all. (And in the future with something like PIM might actually be allowed)

          I guess it is possible using a global address to multicast across the internet using ipv6. Beyond my skills on how to do that though.

          1 Reply Last reply Reply Quote 0
          • dennypageD
            dennypage
            last edited by

            I stand corrected. I do have some devices that are using link local addresses only even though global addresses have been assigned.

            1 Reply Last reply Reply Quote 0
            • C
              costanzo @jimp
              last edited by

              @jimp said in Avahi with IPv6 bug:

              The choices really are:

              Someone could manually make a rule on their own as-is with minimal risk aside from maybe shooting their own foot with setting a gateway (what we have now).

              So, is this how one would manually make a rule to address this? I created this on each subnet that Avahi has set under interfaces.

              2019-07-12_12-23-50.jpg

              A 1 Reply Last reply Reply Quote 1
              • A
                axel77 @costanzo
                last edited by axel77

                @costanzo That's about what I made mine but also added source fe80:: as /10 with port 5353

                Screenshot 2019-08-19 at 8.30.49 PM.png

                1 Reply Last reply Reply Quote 1
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.