blob: d10976f5b680d1329485cb79eca9de64d4d510fe (
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
43
44
45
|
socket: 0.872
network: 0.805
device: 0.660
vnc: 0.601
performance: 0.586
semantic: 0.559
graphic: 0.553
register: 0.443
user-level: 0.429
risc-v: 0.389
ppc: 0.372
i386: 0.350
PID: 0.346
architecture: 0.330
peripherals: 0.312
VMM: 0.293
mistranslation: 0.293
files: 0.286
permissions: 0.273
debug: 0.271
boot: 0.269
x86: 0.267
kernel: 0.267
arm: 0.256
hypervisor: 0.252
TCG: 0.204
virtual: 0.179
assembly: 0.171
KVM: 0.097
Multicast VPN TTL hardcoded at 1
The multicast VPN opens sockets with the default TTL of 1 and there doesn't appear to be an option anywhere that will allow you to increase that.
This limits the usability of the VPN to the local network where the host server lives.
Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
This is for an ancient version of QEMU and no doubt a network approach that is long since obsolete.
Probably best to close it as an edge case. If I run into it again I'll re-raise.
Ok, thanks, so I'll close this now.
|