All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gernot Hillier <gernot.hillier@siemens.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: [Qemu-trivial] [PATCH] doc: slirp supports ICMP echo if enabled in Linux
Date: Thu, 10 Jul 2014 16:01:25 +0200	[thread overview]
Message-ID: <53BE9CB5.4060503@siemens.com> (raw)


Since QEMU 0.15, slirp (user mode networking) supports ping to the
Internet, see e6d43cfb1f9

Signed-off-by: Gernot Hillier <gernot.hillier@siemens.com>
---
  qemu-doc.texi | 14 +++++++++++---
  1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/qemu-doc.texi b/qemu-doc.texi
index 551619a..fc6e57d 100644
--- a/qemu-doc.texi
+++ b/qemu-doc.texi
@@ -1205,9 +1205,17 @@ In order to check that the user mode network is 
working, you can ping
  the address 10.0.2.2 and verify that you got an address in the range
  10.0.2.x from the QEMU virtual DHCP server.

-Note that @code{ping} is not supported reliably to the internet as it
-would require root privileges. It means you can only ping the local
-router (10.0.2.2).
+Note that ICMP traffic in general does not work with user mode networking.
+@code{ping}, aka. ICMP echo, to the local router (10.0.2.2) shall work,
+however. If you're using QEMU on Linux >= 3.0, it can use unprivileged ICMP
+ping sockets to allow @code{ping} to the Internet. The host admin has 
to set
+the ping_group_range in order to grant access to those sockets. To 
allow ping
+for the users group (GID 100):
+
+@example
+
+echo 100 100 > /proc/sys/net/ipv4/ping_group_range
+@end example

  When using the built-in TFTP server, the router is also the TFTP
  server.
-- 
1.8.4



WARNING: multiple messages have this Message-ID (diff)
From: Gernot Hillier <gernot.hillier@siemens.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: [Qemu-devel] [PATCH] doc: slirp supports ICMP echo if enabled in Linux
Date: Thu, 10 Jul 2014 16:01:25 +0200	[thread overview]
Message-ID: <53BE9CB5.4060503@siemens.com> (raw)


Since QEMU 0.15, slirp (user mode networking) supports ping to the
Internet, see e6d43cfb1f9

Signed-off-by: Gernot Hillier <gernot.hillier@siemens.com>
---
  qemu-doc.texi | 14 +++++++++++---
  1 file changed, 11 insertions(+), 3 deletions(-)

diff --git a/qemu-doc.texi b/qemu-doc.texi
index 551619a..fc6e57d 100644
--- a/qemu-doc.texi
+++ b/qemu-doc.texi
@@ -1205,9 +1205,17 @@ In order to check that the user mode network is 
working, you can ping
  the address 10.0.2.2 and verify that you got an address in the range
  10.0.2.x from the QEMU virtual DHCP server.

-Note that @code{ping} is not supported reliably to the internet as it
-would require root privileges. It means you can only ping the local
-router (10.0.2.2).
+Note that ICMP traffic in general does not work with user mode networking.
+@code{ping}, aka. ICMP echo, to the local router (10.0.2.2) shall work,
+however. If you're using QEMU on Linux >= 3.0, it can use unprivileged ICMP
+ping sockets to allow @code{ping} to the Internet. The host admin has 
to set
+the ping_group_range in order to grant access to those sockets. To 
allow ping
+for the users group (GID 100):
+
+@example
+
+echo 100 100 > /proc/sys/net/ipv4/ping_group_range
+@end example

  When using the built-in TFTP server, the router is also the TFTP
  server.
-- 
1.8.4

             reply	other threads:[~2014-07-10 15:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 14:01 Gernot Hillier [this message]
2014-07-10 14:01 ` [Qemu-devel] [PATCH] doc: slirp supports ICMP echo if enabled in Linux Gernot Hillier
2014-07-18  5:40 ` [Qemu-trivial] " Michael Tokarev
2014-07-18  5:40   ` [Qemu-devel] " Michael Tokarev

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=53BE9CB5.4060503@siemens.com \
    --to=gernot.hillier@siemens.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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.