qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: andreas.faerber@web.de, Asheesh Laroia <asheesh@creativecommons.org>
Subject: Re: [Qemu-devel] Making qemu use 10.0.3.x not 10.0.2.x
Date: Wed, 06 Feb 2008 13:39:24 +0100	[thread overview]
Message-ID: <47A9AA7C.9030103@redhat.com> (raw)
In-Reply-To: <18345.36535.82205.721504@mariner.uk.xensource.com>

  Hi,

> Using a (once) randomly-chosen default greatly reduces the odds of
> that happening.  Many many people foolishly choose 10.0.{0,1,2,3}.x.
> Many fewer choose (say) 172.30.206.x.  So the fixed qemu default
> should be 172.30.206.x, or some other range also chosen at random.

A few years back I've worked for a web company, wrote the border router
firewall rules, had some rules in there to catch packages with
rfc1918-private addresses in public network.  Watching the statistics
showed that the 172.16/12 range was _much_ less used than 10/8 and
192.168/16.

I think 10/8 to be used by companies alot.  192.168.$smallnumber.0/24
seems to be a quite common default for DSL routers and the like.

Thus picking a random /24 network from 172.16/12 as new default value
has a pretty good chance to vastly reduce the number of clashes with
existing setups.

HTH,
  Gerd

-- 
http://kraxel.fedorapeople.org/xenner/

  parent reply	other threads:[~2008-02-06 12:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05  0:24 [Qemu-devel] Making qemu use 10.0.3.x not 10.0.2.x Asheesh Laroia
2008-02-05  0:44 ` Jonathan Kalbfeld
2008-02-05  0:51 ` Samuel Thibault
2008-02-05 10:32   ` Andreas Schwab
2008-02-05 10:44     ` Samuel Thibault
2008-02-05 11:30     ` Ian Jackson
2008-02-05 12:58       ` Andreas Färber
2008-02-05 15:48         ` Warner Losh
2008-02-05 16:16           ` Eddie Kohler
2008-02-05 17:42           ` Ben Taylor
2008-02-05 19:06             ` Asheesh Laroia
2008-02-05 21:22               ` Ben Taylor
2008-02-05 21:29                 ` Paul Brook
2008-02-05 21:34                   ` Asheesh Laroia
2008-02-05 22:12                     ` Jernej Simončič
2008-02-05 22:24                       ` Asheesh Laroia
2008-02-06  1:40                   ` Jamie Lokier
2008-02-06  3:34                     ` Paul Brook
2008-02-06 10:40             ` Ian Jackson
2008-02-06 11:01               ` andrzej zaborowski
2008-02-06 16:36                 ` Ian Jackson
2008-02-06 12:39               ` Gerd Hoffmann [this message]
2008-02-05 20:09       ` andrzej zaborowski
2008-02-05 20:31         ` Blue Swirl
2008-02-05 21:46       ` Flavio Visentin
2008-02-05  0:56 ` Johannes Schindelin

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=47A9AA7C.9030103@redhat.com \
    --to=kraxel@redhat.com \
    --cc=andreas.faerber@web.de \
    --cc=asheesh@creativecommons.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).