On Jul 20, 2008, at 4:56 PM, Paolo Pedaletti wrote:

Ciao Uri:

Does using a different ifname help ?
PROXY:  ifname=tap2 and dmz2
WEBAPP: ifname=tap1 and dmz1
DB:     ifname=tap0 and dmz0

no, it doesn't.

always
destination host unreachable

Also check route on guests.

yes, they are correct, the default to external network eth0 while all
eth1 10.0.2.0/24 internal

nothing. :-(

someone has tried a working setup for 2 network connections, one
"public" and one "private" ?

Paolo,

Not quite sure what you mean by your public/private labels. I have a working setup with 2 network connections for several of my KVM guests.

I've got one interface that uses tun/tap devices attached to bridge br0 which also contains the eth0 connection on the host and these guests typically get their IP addresses via DHCP. These guests use interface names starting with tap. For a few of the guests, they have an additional interface that is attached to bridge br1 which connects to my public IP switch. These guests have static address assignments as I only have a handful of external static IPs and these interfaces are named with dmz at the front. The KVM host doesn't have an IP address assigned on the interface that connects to the outside world as I don't really want it to be reachable directly.

It works beautifully, but doesn't use user networking like the startup commands you posted. However, when I went back and looked at your ifup script and the first config you posted, you probably aren't really trying to use user networking for the eth1 interface. You should try replacing the '-net user,' with '-net tap,' on your dmz interfaces and see if that doesn't solve your problem. I use the e1000 nic emulation instead of the rtl8139 (which gave me all kinds of problems about 25 KVM releases ago).

I can post or email you my working config info if you really need it, but I think you are really close to getting this working.

Lynn Kerby
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to