blob: fff32237a86876a62e75d4a1ccf00ec6a9a3407e (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
virtual: 0.939
device: 0.844
network: 0.781
performance: 0.720
graphic: 0.712
PID: 0.684
vnc: 0.674
debug: 0.587
VMM: 0.576
socket: 0.539
semantic: 0.514
permissions: 0.504
risc-v: 0.503
architecture: 0.480
boot: 0.438
files: 0.428
peripherals: 0.389
i386: 0.383
register: 0.368
hypervisor: 0.368
KVM: 0.358
arm: 0.337
x86: 0.323
mistranslation: 0.308
ppc: 0.308
user-level: 0.269
TCG: 0.227
assembly: 0.192
kernel: 0.184
Qemu slirp connectivity lost when host enters vpn(openvpn or wireguard)
Description of problem:
No connectivity after host enters a vpn, tested with valid openvpn
and wireguard.
Steps to reproduce:
1. Open the vpn.
2. Open a virtual machine using slirp
3. Ping 8.8.8.8(if you can...)
Additional information:
The bug is independent on the order of execution, if you start the vm
to see it works, and run the vpn script, the connectivity in the vm
will drop, and come back when the tunneled connection is over.
|