[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] VM nic not taking IP address (fwd)



I wouldn't normally send a generic sys admin type response to the list,
but when people install broken challenge/response systems, there isn't
much alternative.

---------- Forwarded message ----------
Date: Thu, 24 Nov 2005 22:53:00 -0800 (PST)
From: Tom Brown <tbrown@xxxxxxxxxxxxx>
To: Alan Murrell <lists@xxxxxxxxxx>
Subject: Re: [Xen-users] VM nic not taking IP address


sounds like the domU doesn't know it is supposed to configure the extra
two nics... I do all my config by hand and would be looking for

   [root@cf2 /etc/sysconfig/network-scripts]# ls ifcfg-eth*
   ifcfg-eth0
   [ on your box there should be an ifcfg-eth1 and ifcfg-eth2
   files]

but you may admin your system differently .... on redhat there tends to be
an ifup script, does ifup eth1 do anything? and what does the output from
"/etc/rc.d/init.d/network start" look like?

-Tom


On Thu, 24 Nov 2005, Alan Murrell wrote:

> I have a DomU as a firewall (using the Dom0 kernel).  I hid the three
> nics from Dom0 and assigned them to the firewall VM.  The firewall VM
> sees the three nics no problem.  Eth0 comes up and grabs an IP
> automatically from my DHCP server, however eth1 and eth2 are configured
> with static IPs but they do not come up with an IP:
>
> Here is my 'ifconfig':
>
> [root@fw01 ~]# ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:E0:18:E1:A0:68
>           inet addr:192.168.10.252  Bcast:192.168.10.255
> Mask:255.255.255.0
>           UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:928 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:529 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:99207 (96.8 KiB)  TX bytes:104766 (102.3 KiB)
>           Interrupt:20
>
> eth1      Link encap:Ethernet  HWaddr 00:00:D1:1C:0E:67
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Interrupt:23 Base address:0xc800
>
> eth2      Link encap:Ethernet  HWaddr 00:00:D1:1C:0E:68
>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Interrupt:23 Base address:0xc400
>
>
> I have also tried setting my eth1 and eth2 to DHCP and plugging each one
> into my network, but they will not pick up an IP address from my DHCP
> server.
>
> When these cards are unhidden from Dom0, they work no problem (IPs show
> up on them, can get IP address from DHCP server, etc.)
>
> I am not sure what the problem may be, and would appreciate any
> suggestions on where else to check?
>
> TIA.
>
> -Alan
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
>


----------------------------------------------------------------------
tbrown@xxxxxxxxxxxxx   | What I like about deadlines is the lovely
http://BareMetal.com/  | whooshing they make as they rush past.
web hosting since '95  | - Douglas Adams



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.