Have narrowed down the issue to some point between the router reviving a request from my sys-net for an slaac frame or dhcp and my sys-net receiving nothing back. My other devices work fine with getting ips via dhcpv6 or slaac so pretty sure not a router issue. Can anyone help?

  • jet@hackertalks.com
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 days ago

    Packet dump on each virtual interface and see where the response gets dropped… That’s the best I got

    • I’ve already tried that. I did sudo tcpdump -i <interface> -n -vv -s 0 -c 100 -W 100 ip6 for each interface then in a seperate shell ran sudo dhclient -6 -v <interface> and sudo rdisc6 <interface>. I could capture my system soliciting the router but was not getting any response.

      ik it looks like a router issue but other devices are working fine getting globally routed ip’s as they should.

      • jet@hackertalks.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        3 days ago

        Can you use another machine to look at the raw packets on the line leaving your qubes box?

        Maybe some VxLAN setup on your router?

          • jet@hackertalks.com
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 hour ago

            Good job on narrowing it down. I’m not sure I’m ready to blame the framework adapter just yet. it’s still possible the ipv6 issue is somewhere in the ap stack, examining the packets is the gold standard.

            But yeah, it seems the most likely problem would be the sys-net wifi drivers