this post was submitted on 19 Jan 2025
3 points (80.0% liked)

Qubes OS

101 readers
2 users here now

Qubes OS is a security-focused desktop operating system that aims to provide security through isolation. Isolation is provided through the use of virtualization technology. This allows the segmentation of applications into secure virtual machines called qubes. Virtualization services in Qubes OS are provided by the Xen hypervisor.

founded 2 years ago
MODERATORS
 

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?

Edit 1: So ive done some more debugging and determined that it is an issue with not receiving RA frames specify over wifi. I have found this thread and it seems that they are experiencing the exact same symptoms as I am. This leads me to believe it is a firmware/kernal issue. I'm running 6.6.48-1.qubes.fc37.x86_64 and my wifi card is MT7922A22M i cant find anyhting relevent except this

Edit 2: it is an issue specifically with using a Debian template for sys-net. My temporary solution has simply been to use a Fedora template instead.

top 5 comments
sorted by: hot top controversial new old
[–] jet@hackertalks.com 3 points 1 month ago (1 children)

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

[–] muntedcrocodile@lemm.ee 3 points 1 month ago (1 children)

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 3 points 1 month ago (1 children)

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?

[–] muntedcrocodile@lemm.ee 2 points 1 month ago (1 children)

OK so I tried a wired connection and its works perfectly so I guess its an issue with my wireless adapter. Seems its a Framework issue not a QubesOS issue?

[–] jet@hackertalks.com 2 points 1 month 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