Here is the original poster's /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0
BOOTPROTO='static'
IPADDR='myaddresshere'
NETMASK='255.255.255.0'
ONBOOT=yes
TYPE=Ethernet
Here is one that works for us:
DEVICE=eth0
IPADDR=xxx.xxx.xxx.xxx
NETMASK=xxx.xxx.xxx.xxx
NETWORK=xxx.xxx.xxx.xxx
BROADCAST=xxx.xxx.xxx.xxx
GATEWAY=xxx.xxx.xxx.xxx
ONBOOT=yes
TYPE=Ethernet
<<<<<<<<<
I would say the original poster's lack of a gateway for the machine would cause
traffic never to leave it's local subnet..making it unavailable to the world.
Use a more complete network configuration every time, and you shouldn't have
those problems.
You also need to make sure that you have nameserver entries in your
/etc/resolv.conf.
I'm still in testing mode on the 1.1.1 VM appliance.. although I have plans to
move into testing on the newest one. My production system is still running
0.93, as I'm not done creating all the devices in the other one yet. (but..the
VM has been running now for months without incident.)
I hope this is helpful!
--Todd
joe4 wrote:
I think Zenoss makes the appliance available for testing because people have
problems with the install or do not have a Linux box. It does not showcase how
the install or stability will be on a real install.
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=9049#9049
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
