I have a network set up something like the following:

Device A <---> Router A <---> Router B <---> Device B

where Router A is a tp-link Archer AX73, and Router B is a tp-link Archer C7. Router B is flashed with OpenWRT, and Router A is using stock firmware. Router B is set up to be a wireless bridge between Router A’s network, and its own (it was set up using this guide).

What I am wondering is if Device A can find, say, Device B.local, using Avahi (assuming Device A, and Device B both have Avahi installed, and running), over this bridged network. So far, I haven’t been able to get it to work, so I’m wondering if it is possible at all. I have read that Avahi only works on a local network, but I was wondering if it could be bridged.

UPDATE (2024-01-16T01:28Z):

The issues that I mentioned in this post have since been solved. The majority of the issues stemmed from the fact that the relay software that I was using, relayd, doesn’t support ipv6. All the tests that I was conducting were defaulting to ipv6, so it was appearing like the bridge was failing unpredictably. Since that realization was made, and countermeasures were enacted, the problem was solved.

  • eutampieri@feddit.it
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    10 months ago

    No, not at all 🙂. I’m referring to a configuration in which the two routers are linked through another subnet (using a separate link between the two) and this link is the point to point link. You usually assign a /30 so you can have an address for each router. ~This way the traceroute shows three hops instead of just two.~ However, since you’ve already told us that this is not your setup, what I’m saying shouldn’t matter to you. If you’re curious though, let’s keep talking :)

    Edit: striked mistake

    • Kalcifer@sh.itjust.worksOP
      link
      fedilink
      arrow-up
      1
      ·
      10 months ago

      Interesting, where does the 3rd hop come from? Wouldn’t the routing table just point from one router to the other – so 2 hops?

      • eutampieri@feddit.it
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        10 months ago

        Traceroute from device in subnet A to device in subnet B

        • Router A
        • Router B
        • Device B

        Note that the only way to do that in only two hops is to have the same router handle both subnets, contrary to what I said earlier.

          • eutampieri@feddit.it
            link
            fedilink
            arrow-up
            1
            ·
            10 months ago

            Hmmm it seems that router B there should be a bridge. However, how comfortable are you with routing in general?

            • Kalcifer@sh.itjust.worksOP
              link
              fedilink
              arrow-up
              2
              ·
              9 months ago

              However, how comfortable are you with routing in general?

              Ha, depends what you mean by that. If you mean manually specifying routes in a router, I think I generally understand it, but I am not at all confident in my abilities.

              • eutampieri@feddit.it
                link
                fedilink
                arrow-up
                2
                ·
                9 months ago

                Exactly that. Router A

                ip address add 192.168.1.1/24 dev eth1
                ip address add 10.0.0.1/30 dev eth2
                ip route add 192.168.2.0/24 via 10.0.0.2
                

                Router B

                ip address add 192.168.2.1/24 dev eth1
                ip address add 10.0.0.2/30 dev eth2
                ip route add 192.168.1.0/24 via 10.0.0.1
                

                Does this make it more clear?

                • Kalcifer@sh.itjust.worksOP
                  link
                  fedilink
                  arrow-up
                  2
                  ·
                  9 months ago

                  Does this make it more clear?

                  Yes, thank you! Usually, however, most of my issues seem to stem from knowing where configs are, what tools to use for what, or where to find things in the router user interface, etc.