All of lore.kernel.org
 help / color / mirror / Atom feed
From: prochazka nicolas <prochazka.nicolas@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 829455] Re: user mode network stack - hostfwd not working with restrict=y
Date: Thu, 11 Aug 2016 10:50:17 -0000	[thread overview]
Message-ID: <20160811105017.23077.87593.malone@soybean.canonical.com> (raw)
In-Reply-To: 20110819134228.9593.2808.malonedeb@gac.canonical.com

It seems that's problem persist with this patch ( qemu 2.7rc2)
Regards

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/829455

Title:
  user mode network stack - hostfwd not working with restrict=y

Status in QEMU:
  Fix Released

Bug description:
  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)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/829455/+subscriptions

  parent reply	other threads:[~2016-08-11 10:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19 13:42 [Qemu-devel] [Bug 829455] [NEW] user mode network stack - hostfwd not working with restrict=y Luca Andreucci
2013-06-14 10:59 ` [Qemu-devel] [Bug 829455] " Axel Hübl
2013-06-17 15:34   ` Stefan Hajnoczi
2013-06-18 14:31     ` Jan Kiszka
2016-06-23  8:53 ` T. Huth
2016-08-11 10:50 ` prochazka nicolas [this message]
2016-08-11 11:43 ` prochazka nicolas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160811105017.23077.87593.malone@soybean.canonical.com \
    --to=prochazka.nicolas@gmail.com \
    --cc=829455@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.