On 6/8/19 6:16 PM, mmo...@disroot.org wrote:
Well after some more troubleshooting I found the root cause. It seems to
be related with the MTU.
Wireguard by default sets its vif with a MTU of 1420 while the other
AppVms are using a default MTU of 1500 which causes the hanging and
stall in the connection request.
When I set the interfaces of the AppVms to 1420 the problem is solved.
However I wonder if it's possible to preserve this change for any AppVm?
Does anyone knows?
Thank you
The old Qubes R3 firewall could run a user script each time a new vif
(downstream vm) was connected to the proxy vm. Finding a similar hook in
R4 would allow you to set the MTU automatically.
Given that wireguard is becoming popular on routers, and Qubes proxy vms
are basically routers, you might find some good tips for dealing with
this around the web.
--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/e5bc9fdb-3ebc-f4e3-729f-d4de2fe4a383%40posteo.net.
For more options, visit https://groups.google.com/d/optout.
