qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Gerlich <olig9@gmx.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Connecting vde and LAN
Date: Tue, 12 Jul 2005 22:31:54 +0200	[thread overview]
Message-ID: <42D428BA.6070907@gmx.de> (raw)
In-Reply-To: <42D41D52.6090306@axe.homelinux.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ross Kendall Axe schrieb:
> Oliver Gerlich wrote:
> 
>>>The "problem" is that I start vde_switch and the bridging not at boot,
>>>but when I want to run Qemu. So then I have to restart Samba to bind to
>>>to br0 instead of eth0. Not so much of a problem though... Only I don't
>>>know what other services already rely on eth0 as my network interface :)
> 
> 
> You've got the 'Bind interfaces only' option turned on in Samba haven't
> you? Turn it off and your problem will disappear.
> 
> As to what other programs care about interfaces appearing/disappearing,
> run 'netstat -ltup' to see who's listening where. Anything listening on
> '*:portnumber' probably doesn't care.

Thanks for your ideas; but I try to run every service bound to specific
interfaces (lo and/or eth0), so I don't get into problems when attaching
eg. a direct internet connection or WLAN.

> 
> Ross

Oliver


_______________________________________________
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFC1Ci4TFOM6DcNJ6cRAhJGAJ9yluJJa7l5ujrBCh2o2yOn+YJrPQCdF5+r
6+jDiKiDfnFD7b7oxty7ENY=
=KppC
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-07-12 21:10 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-10 12:27 [Qemu-devel] Connecting vde and LAN Oliver Gerlich
2005-07-10 16:42 ` Henrik Nordstrom
2005-07-10 17:37   ` Jim C. Brown
2005-07-10 18:23     ` Oliver Gerlich
2005-07-10 18:58       ` Jim C. Brown
2005-07-11  2:21     ` Henrik Nordstrom
2005-07-11  2:33       ` Jim C. Brown
2005-07-11  7:50         ` Henrik Nordstrom
2005-07-11 15:02           ` Jim C. Brown
2005-07-11 23:01             ` Jim C. Brown
2005-07-12  2:49               ` Henrik Nordstrom
2005-07-12 22:25                 ` Jim C. Brown
2005-08-04 10:14                   ` Henrik Nordstrom
2005-08-05 16:54                     ` Jim C. Brown
2005-08-10 19:07                       ` Jim C. Brown
2005-08-11 14:56                         ` Henrik Nordstrom
2005-08-11 16:24                           ` Oliver Gerlich
2005-08-11 16:56                             ` Jim C. Brown
2005-08-12 10:02                               ` Henrik Nordstrom
2005-08-12 18:07                                 ` Jim C. Brown
2005-08-11 17:00                             ` Paul Brook
2005-08-12  0:11                               ` Herbert Poetzl
2005-08-12  9:53                             ` Henrik Nordstrom
2005-07-10 17:48   ` Oliver Gerlich
2005-07-11  1:36     ` Henrik Nordstrom
2005-07-12 19:43     ` Ross Kendall Axe
2005-07-12 20:31       ` Oliver Gerlich [this message]
2005-07-13  3:02         ` Ross Kendall Axe
2005-07-10 18:27   ` Bakul Shah

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=42D428BA.6070907@gmx.de \
    --to=olig9@gmx.de \
    --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).