rene_mobile’s avatarrene_mobile’s Twitter Archive—№ 7,815

        1. TIL: The "Advertise" flag in @mikrotik_com RouterOS for a configured IPv6 address stands for advertising the *prefix* in RA and dynamically creates an ND prefix entry. First I thought @opnsense had stability issues in IPv6 route advertisement in combination with DHCPv6 PD.
          Permalink On twitter.com Twitter logo rene_mobile’s avatar ❤️ 1 Favorite Mood 0
      1. …in reply to @rene_mobile
        While I haven't completely ruled out that I am also victim to the problems described at reddit.com/r/mikrotik/comments/kxqqk0/routeros_648_ipv6_issue_with_vlanfiltered_bridges/gjg8f4p/?context=3, my current - seemingly stable - setup is not to disable "Hardware Offload" for the relevant ports, but to add an IPv6 address to the Mikrotik bridge.
        Permalink On twitter.com Twitter logo rene_mobile’s avatar Mood -3 🙁
    1. …in reply to @rene_mobile
      Having the bridge itself run an ND process to respond to its own IPv6 address seems to solve all forwarding issues for now - but as mentioned in the first tweet, without the "Advertise" flag on the address definition...
      Permalink On twitter.com Twitter logo rene_mobile’s avatar Mood +1 🙂
  1. …in reply to @rene_mobile
    I celebrated too soon - the IPv6 RA issues are back. Now tried disabling offload options on @opnsense, as I am becoming more certain that it is actually the culprit here. RA requests and replies are seen by other hosts on the same VLAN, just @opnsense doesn't seem to react. Why?
    On twitter.com Twitter logo rene_mobile’s avatar Mood +3 🙂