blob: aa852f233199226dedb009899776a0934f7c363d (
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
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
network: 0.843
mistranslation: 0.799
user-level: 0.767
socket: 0.696
KVM: 0.677
ppc: 0.605
device: 0.566
PID: 0.489
architecture: 0.471
virtual: 0.441
vnc: 0.432
semantic: 0.422
register: 0.411
debug: 0.389
x86: 0.384
hypervisor: 0.384
arm: 0.382
performance: 0.361
permissions: 0.330
risc-v: 0.318
VMM: 0.307
boot: 0.292
i386: 0.289
TCG: 0.289
kernel: 0.276
assembly: 0.265
peripherals: 0.245
graphic: 0.242
files: 0.232
user mode network stack - hostfwd not working with restrict=y
I find that explicit hostfwd commands do not seem to work with restrict=yes option, even if the docs clearly state that hostfwd should override restrict setting.
I am using this config:
-net user,name=test,net=192.168.100.0/24,host=192.168.100.44,restrict=y,hostfwd=tcp:127.0.0.1:3389-192.168.100.1:3389
(my guest has static IP address configured as 192.168.100.1/24)
and I cannot log into my guest via rdp. the client hanging indefinitely.
by just changing to "restrict=no" I can log in.
maybe I am doing something wrong, but I cannot figure out what.
running QEMU emulator version 0.14.0 (qemu-kvm-0.14.0)
Did you guys merge back the fix in:
http://lists.gnu.org/archive/html/qemu-devel/2011-11/msg01519.html
?
On Fri, Jun 14, 2013 at 10:59:10AM -0000, Axel Hübl wrote:
> Did you guys merge back the fix in:
>
> http://lists.gnu.org/archive/html/qemu-devel/2011-11/msg01519.html
> ?
This patch has not been applied. CCing Jan Kiszka, slirp maintainer.
Stefan
Patch has been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=b5a87d26e848945eb8
It seems that's problem persist with this patch ( qemu 2.7rc2)
Regards
Sorry for this spam,
it's just a routing problem .
Regards
|