I have a second NIC in my machine that I am using to create a subnet for a cluster of Xen VMs on my machine. Nothing really needs to be connected to this interface as no traffic ever needs to leave the subnet (all the Xen VMs are on the same physical machine). However, if I don't have a cable connected, the interface thinks it can't do anything and won't try to route any packets. The setup works fine when a cable is connected. Any suggestions always appreciated!

link|improve this question
I may have found an alternate solution to this problem that I'll try out at the office tomorrow. – Michael Mior Jan 25 '10 at 2:48
I was able to add a second IP to one of my NICs and this seems to be working. My problem now is that it doesn't work unless I bring up the interface again after the machine has been booted. That is, I am now using the interfaces eth1:0 and eth1:1 with xend-config.sxp using the line (network-script 'network-bridge netdev=eth1') Unless I do ifup eth1:0 after the machine is started, I can't access the external network. – Michael Mior Jan 25 '10 at 15:09
feedback

4 Answers

Will a loopback plug work for you?

SuperLooper Loopback Plug

link|improve this answer
Hmm, this might actually work. Not the kind of solution I was expecting, but a cool idea :) – Michael Mior Jan 25 '10 at 2:48
feedback
up vote 1 down vote accepted

I finally solved the problem by creating an alias of my NIC so I had two different IPs. I still need to configure the necessary iptables rules, but it seems to be working fine.

link|improve this answer
feedback

Can't you create a virtual host-only network within Xen?

link|improve this answer
feedback

You need use own virtual bridge interfaсe, xenbr1 for example. Read about: Xen Networking.

link|improve this answer
Unfortunately this doesn't solve my problem. – Michael Mior Jan 25 '10 at 2:47
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.