This is what I did and it works although i don't understand:
I commented HWADDR in ifcfg-eth0 and restarted the network ,no go ,it took an inet-6 address and network was unreachable
then i did
root@XenU# ifconfig eth0 down
root@XenU# ifconfig eth0 172.21.104.201
up =====(i chose a purely random Inet-4 addr in my subnet )
and lo i was connected to the network ,and my broadcast and netmask is different from Domain-0
i simply dont understand how this is working and i am not too good in network fundamentals(all services httpd,sshd,etc..are working fine now)
root@XenU# ifconfig
eth0 Link encap:Ethernet HWaddr AA:00:00:46:84:E0
inet addr:172.21.104.201 Bcast:172.21.255.255 Mask:255.255.0.0
inet6 addr: fe80::a800:ff:fe46:84e0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2453 errors:0 dropped:0 overruns:0 frame:0
TX packets:122 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:247257 (241.4 KiB) TX bytes:15740 (15.3 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)
================================================================================
[root@localhost Dom-0 ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0B:DB:55:7C:26
i
net addr:172.21.104.220 Bcast:172.21.104.255 Mask:255.255.255.0
inet6 addr: fe80::20b:dbff:fe55:7c26/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:20554 errors:0 dropped:0 overruns:0 frame:0
TX packets:1991 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2123657 (2.0 MiB) TX bytes:324885 (317.2 KiB)
Base address:0xecc0 Memory:ff8e0000-ff900000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2500 errors:0 dropped:0 overruns:0 frame:0
TX packets:2500 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:164727 (160.8 KiB) TX bytes:164727 (160.8 KiB)
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:84 errors:0 dropped:0 overruns:0 frame:0
TX packets:1981 errors:0 dropped:151 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13496 (13.1 KiB) TX bytes:189499 (185.0 KiB)
xen-br0 Link encap:Ethernet HWaddr 00:0B:DB:55:7C:26
inet addr:172.21.104.220 Bcast:172.21.104.255 Mask:255.255.255.255
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5038 errors:0 dropped:0 overruns:0 frame:0
TX packets:1802 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:379544 (370.6 KiB) TX bytes:288410 (281.6 KiB)
On Thu, 2005年08月18日 at 07:07 -0400, Derrik Pates wrote:
Digvijoy Chatterjee wrote:
> network restart doesnt help either :
>
> [root@localhost ~]# service network restart
> Shutting down interface eth0: Device eth0 has different MAC address
> than expected, ignoring.
> [FAILED]
> Shutting down loopback interface: [ OK ]
> Bringing up loopback interface: [ OK ]
> Bringing up interface eth0:
> Determining IP information for eth0... failed.
> [FAILED]
You've just pointed out your own problem. Fedora/RH/CentOS network init
scripts associate the original MAC address with the network
configuration in /etc/sysconfig/network-scripts/ifcfg-eth*, and won't
touch an interface that doesn't match. Either (a) set a static MAC in
your domain configs and fix it in the interface config file, or (b)
comment out or remove the line (which starts with 'HWADDR=', I think),
and this problem will disappear.
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users