You can subscribe to this list here.
2010 |
Jan
|
Feb
|
Mar
(40) |
Apr
|
May
(1) |
Jun
(8) |
Jul
(9) |
Aug
(2) |
Sep
(9) |
Oct
(8) |
Nov
(23) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
(1) |
May
(3) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(4) |
Dec
(1) |
2012 |
Jan
(1) |
Feb
(23) |
Mar
(6) |
Apr
(1) |
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(3) |
Oct
|
Nov
(1) |
Dec
(3) |
2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
(5) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
(1) |
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(4) |
Oct
|
Nov
(11) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(3) |
From: <ope...@li...> - 2011-06-22 03:19:55
|
Stable version of OpenNode 1.1 ISO installer and hypervisor node is now available together with new and updated OpenVZ OVF templates library. OpenNode 1.1 stable release (build 38) is available as a ISO installer download or as a yum based upgrade to existing OpenNode installations. Changes since OpenNode 1.1 RC1: * Temporarely disabled opennode-repo rpm dependecy for opennode rpm - in order to enable system upgrades from older versions because of the file conflict between opennode-repo and older opennode rpm packages Notable OpenNode 1.1 changes: Upgraded kernel to ovzkernel-2.6.18-238.9.1.el5.028stab089.1 Updated KVM to kvm-83-224.asys.3.x86_64.rpm Updated vzctl to 3.0.27-1 Updated vzdump to 1.2-12 Rebased OpenNode base system to CentOS 5.6 Initial OVF templates support in OpenNode CLI Utility (both for KVM and OpenVZ) Updated and new (Fedora 14, OpenSUSE 11.2/11.3/11.4) OpenVZ OVF templates are available for download through local OpenNode CLI Utility Out-of-box OpenNode Management Server support Minimum disk size requirement for advanced autopartitioning has been reduced to 25GB. NB! OpenNode can be installed with disk sizes less than 25GB - but then manual partitioning might be needed or accepting a default and simple partitioning scheme with single root partition on top of LVM. OpenNode 1.1 stable release (build 38) is available as a ISO installer download or as a yum based upgrade to existing OpenNode installations. Changes since OpenNode 1.1 RC1: Temporarely disabled opennode-repo rpm dependecy for opennode rpm - in order to enable system upgrades from older versions because of the opennode yum repo file conflict between opennode-repo and older opennode rpm packages Notable OpenNode 1.1 changes since 1.0: Upgraded kernel to ovzkernel-2.6.18-238.9.1.el5.028stab089.1 Updated KVM to kvm-83-224.asys.3.x86_64.rpm Updated vzctl to 3.0.27-1 Updated vzdump to 1.2-12 Rebased OpenNode base system to CentOS 5.6 Initial OVF templates support in OpenNode CLI Utility (both for KVM and OpenVZ) Updated and new (Fedora 14, OpenSUSE 11.2/11.3/11.4) OpenVZ OVF templates are available for download through local OpenNode CLI Utility Out-of-box OpenNode Management Server support Minimum disk size requirement for advanced autopartitioning has been reduced to 25GB. NB! OpenNode can be installed with disk sizes less than 25GB - but then manual partitioning might be needed or accepting a default and simple partitioning scheme with single root partition on top of LVM. Please follow these upgrade instructions if upgrading from OpenNode 1.0 stable or 1.1 beta1 systems: #Stop all running VM-s - if any #Make sure you have opennode stable repo enabled in /etc/yum.repos.d/opennode.repo file cd /etc/pki/rpm-gpg/ wget http://opennode.activesys.org/CentOS/5/opennode/RPM-GPG-KEY-ActiveSys rpm --import http://download.openvz.org/RPM-GPG-Key-OpenVZ cp -p /etc/yum.repos.d/opennode.repo /tmp/ yum update opennode cp -p /tmp/opennode.repo /etc/yum.repos.d/ yum install opennode-repo yum update ln -sf /opt/opennode/bin/opennode /usr/bin/opennode mkdir -p /storage/images mkdir -p /storage/iso mkdir -p /storage/templates/kvm/deploy mkdir -p /storage/templates/openvz/deploy reboot Cheers, -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
From: <ope...@li...> - 2011-05-31 23:41:51
|
Release candidate version of OpenNode 1.1 ISO installer and hypervisor node is now available together with new and updated OpenVZ OVF templates library. OpenNode 1.1 RC1 (build 37) is available as a ISO installer download or as a yum based upgrade to existing OpenNode installations - which is provided through opennode-test repo during Release Candidate phase. Changes: Upgraded kernel to ovzkernel-2.6.18-238.9.1.el5.028stab089.1 Updated KVM to kvm-83-224.asys.3.x86_64.rpm Updated vzctl to 3.0.27-1 Updated vzdump to 1.2-12 Rebased OpenNode base system to CentOS 5.6 Initial OVF templates support in OpenNode CLI Utility (both for KVM and OpenVZ) Updated and new (Fedora 14, OpenSUSE 11.2/11.3/11.4) OpenVZ OVF templates are available for download through local OpenNode CLI Utility Out-of-box OpenNode Management Server support Minimum disk size requirement for advanced autopartitioning has been reduced to 25GB. NB! OpenNode can be installed with disk sizes less than 25GB - but then manual partitioning might be needed or accepting a default and simple partitioning scheme with single root partition on top of LVM. For yum upgrades to existing OpenNode installations please do the following: switch to opennode-test yum repository (enable opennode-test repo in /etc/yum.repos.d/opennode file and disable opennode repo) execute: yum update Cheers, -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
From: <ope...@li...> - 2011-05-26 16:14:30
|
Nowadays much people face with the health problems. This pharmacy is a great opportunity for them.... http://www.cormoranomarina.it/friends_links.php?ezisiteid=03ib4 |
From: <ope...@li...> - 2011-05-20 14:40:48
|
opennode-oms-1.0-16 rpm package has been released in order to address vnc console startup issue with newer Chrome webbrowsers. It seems that newer Google Chrome browsers have more strict javascript execution instructions and were causing vnc console startup issue - opennode-oms-1.0-16 rpm containes fixes in order to solve that problem. For opennode-oms package upgrade please log into your OpenNode Management Server installation (through ssh or vzctl enter) and execute: yum upgrade opennode-oms -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
From: <ope...@li...> - 2011-04-28 00:37:57
|
OpenVZ OVF OS templates for OpenNode 1.1 have been updated on activesys.org and are ready for download. Please download and update OpenVZ OVF templates with OpenNode 1.1 CLI Utility. Please also note that there has been a small template filename format change - we are adding "asys" string to base filename from now on. If you are running OpenNode 1.0 stable you need to upgrade to OpenNode 1.1 beta - in order to download and deploy OVF packed OpenVZ templates. For upgrading please see the following howto document: http://opennode.activesys.org/documentation/howtos/upgrading-opennode-10-stable-to-11-beta/ Provided templates: centos-5.5-i386-asys centos-5.5-x86_64-asys debian-5.0-i386-asys debian-5.0-x86_64-asys fedora-13-i386-asys fedora-13-x86_64-asys suse-11.1-i386-asys suse-11.1-x86_64-asys ubuntu-10.04-i386-asys ubuntu-10.04-x86_64-asys ubuntu-10.10-i386-asys ubuntu-10.10-x86_64-asys centos-5.5-i386-asys centos-5.5-x86_64-asys debian-5.0-i386-asys debian-5.0-x86_64-asys fedora-13-i386-asys fedora-13-x86_64-asys suse-11.1-i386-asys suse-11.1-x86_64-asys ubuntu-10.04-i386-asys ubuntu-10.04-x86_64-asys ubuntu-10.10-i386-asys ubuntu-10.10-x86_64-asys Fedora 14 and SuSE 11.2, 11.3 OpenVZ OVF templates are on pipeline - released as soon as we get newer ovzkernel (028stab089.1) into opennode-test repository - because these templates are dependant on features included in newer ovzkernels (starting from 028stab085.3) and require newer vzutils (3.0.26). Ovzkernel 028stab089.1 and vzutils 3.0.26 are in experimental opennode-dev-11 repo for now and after some initial testing they will be moved into opennode-test repo for wider audience betatesting - until OpenNode 1.1 stable release will happen. -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
From: <ope...@li...> - 2011-03-09 23:36:08
|
We have done a backport of NEXT3 filesystem kernel module for RHEL 5 OpenVZ enabled kernel included in OpenNode - both next3 kernel module and patched (+ newer version of) e2fsprogs rpm packages are now available from opennode-test repo for testing. NEXT3(R) is a clone of the Ext3 filesystem with built-in support for snapshots. NEXT3 features Backward and forward compatible with Ext3 - converting from EXT3 to NEXT3 and back is easy and possible Snapshots use available file system disk space - no need for dedicated free disk blocks like LVM No upper limit on number or size of snapshots - no need for snapshot size pre-allocation like LVM Minimal performance overhead when snapshots exists For NEXT3 installation and usage please see this howto document: http://opennode.activesys.org/documentation/howtos/next3-snapshots/ -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
From: <ope...@li...> - 2011-02-05 01:29:35
|
OpenNode Management Server provides a JSON-RPC API interface for third-party software/systems integration and possible WUI/GUI/CLI clients implementation. OMS API reference can be found here: opennode.activesys.org/documentation/api-documentation/ OpenNode Management Console eg "Funcman" is our reference client implementation using this JSON-RPC API. Other client implementations are possible and highly encouraged. Cheers, -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
From: <ope...@li...> - 2011-01-20 21:13:38
|
opennode-1.1-16 rpm is available from opennode-test repo containing mainly bugfixes - for details please see changelog below: Changes since opennode-1.1-15: bug when registering to OMS from the same node where OMS is running no cancel or back button in ovz template deploy dialogue when entering min/max values required directory structure creation and verification for opennode compliance opennode-1.1 beta rpm switches back to opennode stable repo - should not repleace user choice to use opennode-test repo no /storage/iso folder after opennode rpm install bug when registering to OMS from the same node where OMS is running no cancel or back button in ovz template deploy dialogue when entering min/max values required directory structure creation and verification for opennode compliance opennode-1.1 beta rpm switches back to opennode stable repo - should not repleace user choice to use opennode-test repo no /storage/iso folder after opennode rpm install For update please verify that you are using opennode-test repo and execute: yum update opennode -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
From: <ope...@li...> - 2010-12-14 23:18:47
|
Im pleased to announce that first public (alpha1) preview release of OpenNode Management Server (OMS) is now available - its download and installation is provided through a local OpenNode CLI Utility (requires latest OpenNode-1.1 beta1 package). OMS alpha1 version is not yet ready for production use - but it also should not be destructive to your test environment :-) Please read and follow OpenNode Management Server Install Howto for deploy time instructions. OpenNode Management Server User Guide should provide you with the needed information in order to get you going. For community support please visit OpenNode Support Forum and use OpenNode public mailing lists. Commercial support options and OpenNode development services are provided by Active Systems LLC. OpenNode Management Server installation requirements: OMS host and client nodes must be updated to latest OpenNode 1.1 beta1 (opennode-1.1-15 rpm) For an alpha1 OMS VM test instance at least 1GB free memory and 10GB free disk space under /vz is needed for now NB! You should use only FQDN hostnames for OMS and OpenNode server hostnames and they must be resolvable For installing the latest opennnode 1.1 beta 1 rpm package please do the following: switch to opennode-test yum repository (enable opennode-test repo in /etc/yum.repos.d/opennode file and disable opennode repo) do yum upgrade opennode (which should pull latest opennode-1.1-15 or greater rpm from opennode-test repo) Known issues and limitations of OMS alpha1 release OMS Web Console is still pretty "funky" at the moment - might be slow on updates, no proper feedback to user during some operations (especially on hosts import procedures), random VM status changes between vmlist refreshes, etc. OMS Web Console SSH console pop-up window might open too fast - because of no ssh proxy console yet on other side producing a browser error - please just refresh the SSH console window and then SSH console loads properly We do not support OpenVZ veth networking management inside OMS Web Console yet - but OpenVZ VMs with veth networking are allowed (just do manual setup for veth) Currently we only support installing KVM VM-s from bootable ISO image with OMS Web Console - but you can try KVM VM templates functionality with local OpenNode-1.1 CLI Utility There seems to be a problem with some ISO installers other than Windows boot CD - when creating KVM VM from ISO No ISO image management yet - ISO images must be manually loaded into every OpenNode host under /storage/iso folder - if no such folder exists please create it manually No VM templates management through OMS Web Console yet - please use local OpenNode CLI Utility for VM templates management Currently KVM VM stop button issues KVM VM destroy command instead of more graceful (but also often non-working) shutdown - that is intentional While OpenVZ VM management seems to be fairly stable - KVM management features are not so throughly tested There are probably more issues - so be prepared :-) Cheers, -- ---------------------------------------------- Andres Toomsalu, an...@ac... CEO, Active Systems LLC |
From: <ope...@li...> - 2010-11-09 14:09:31
|
Ping directly to IP address for google fails as well. I did stop iptables on the main node and the VM was still not able to ping outside. I also stopped iptables inside the VM and the same thing happened. You mentioned venet twice. Let's say I don't want to use venet and only use veth how should the create script below should change? vzctl create 504 --ostemplate centos-5-x86_64 vzctl set 504 --ipadd 10.100.100.137 --save vzctl set 504 --nameserver 10.100.100.137 --save vzctl set 504 --hostname ct4.domain --save vzctl set 504 --diskspace 10G:11G --save vzctl set 504 --diskinodes 900000:910000 --save vzctl set 504 --quotatime 600 --save vzctl start 504 vzctl set 504 --userpasswd root:1234 vzctl exec 504 ps ax Thanks |
From: <ope...@li...> - 2010-11-09 07:46:55
|
Please do execute on hardware node 'service iptables stop' (verify that now iptables -L shows empty chains) and try networking from VM again - as said earlier default firewalling rules do not allow dns for venet. ---------------------------------------------- Andres Toomsalu, an...@ac... ope...@li... wrote: > Thanks for the continued support Andres. > > Let's start from the beginning and have a full snapshot. Following is > posting of both inside the VM and at the main node. > (code separated by ****) > > ********************************************************************************************************************************************* > Code Used to create the VM > ------------------------------------------ > vzctl create 504 --ostemplate centos-5-x86_64 > vzctl set 504 --ipadd 10.100.100.137 --save > vzctl set 504 --nameserver 10.100.100.137 --save > vzctl set 504 --hostname ct4.domain --save > vzctl set 504 --diskspace 10G:11G --save > vzctl set 504 --diskinodes 900000:910000 --save > vzctl set 504 --quotatime 600 --save > vzctl start 504 > vzctl set 504 --userpasswd root:1234 > vzctl exec 504 ps ax > > > > ********************************************************************************************************************************************** > Code used to lunch VM: > ----------------------------------- > > Inside VM: > [root@ct4 /]# ifconfig > 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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > venet0 Link encap:UNSPEC HWaddr > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 > Mask:255.255.255.255 > UP BROADCAST POINTOPOINT RUNNING NOARP 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:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > venet0:0 Link encap:UNSPEC HWaddr > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > inet addr:10.100.100.137 P-t-P:10.100.100.137 > Bcast:10.100.100.137 Mask:255.255.255.255 > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > > [root@ct4 /]# iptables -L > Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > [root@ct4 /]# ping google.com <http://google.com> > ping: unknown host google.com <http://google.com> > [root@ct4 /]# ping 10.100.100.1 > PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. > > --- 10.100.100.1 ping statistics --- > 19 packets transmitted, 0 received, 100% packet loss, time 18001ms > > > ********************************************************************************************************************************* > At the main Node: > ---------------------------- > [root@virtN ~]# ifconfig > eth0 Link encap:Ethernet HWaddr 00:25:90:1A:A7:72 > inet6 addr: fe80::225:90ff:fe1a:a772/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:12 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:1002 (1002.0 b) TX bytes:468 (468.0 b) > Memory:faee0000-faf00000 > > eth1 Link encap:Ethernet HWaddr 00:25:90:1A:A7:73 > inet addr:10.100.100.141 Bcast:10.100.100.255 > Mask:255.255.255.0 > inet6 addr: fe80::225:90ff:fe1a:a773/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:60 errors:0 dropped:0 overruns:0 frame:0 > TX packets:76 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:6439 (6.2 KiB) TX bytes:10143 (9.9 KiB) > Memory:fafe0000-fb000000 > > 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:3 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:336 (336.0 b) TX bytes:336 (336.0 b) > > venet0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:4572 (4.4 KiB) > > virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:192.168.122.1 Bcast:192.168.122.255 > Mask:255.255.255.0 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) > > [root@virtN ~]# > [root@virtN ~]# iptables -L > Chain INPUT (policy ACCEPT) > target prot opt source destination > ACCEPT udp -- anywhere anywhere udp > dpt:domain > ACCEPT tcp -- anywhere anywhere tcp > dpt:domain > ACCEPT udp -- anywhere anywhere udp > dpt:bootps > ACCEPT tcp -- anywhere anywhere tcp > dpt:bootps > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > ACCEPT all -- anywhere 192.168.122.0/24 > <http://192.168.122.0/24> state RELATED,ESTABLISHED > ACCEPT all -- 192.168.122.0/24 <http://192.168.122.0/24> > anywhere > ACCEPT all -- anywhere anywhere > REJECT all -- anywhere anywhere > reject-with icmp-port-unreachable > REJECT all -- anywhere anywhere > reject-with icmp-port-unreachable > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > [root@virtN ~]# > [root@virtN ~]# route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref > Use Iface > 10.100.100.50 * 255.255.255.255 UH 0 0 > 0 venet0 > 10.100.100.49 * 255.255.255.255 UH 0 0 > 0 venet0 > 10.100.100.139 * 255.255.255.255 UH 0 0 > 0 venet0 > 10.100.100.137 * 255.255.255.255 UH 0 0 > 0 venet0 > 10.100.100.0 * 255.255.255.0 U 0 0 > 0 eth1 > 192.168.122.0 * 255.255.255.0 U 0 0 > 0 virbr0 > 169.254.0.0 * 255.255.0.0 U 0 0 > 0 eth1 > default 155-redbox.loca 0.0.0.0 UG 0 0 > 0 eth1 > [root@virtN ~]# > [root@virtN ~]# ping google.com <http://google.com> > PING google.com <http://google.com> (173.194.32.104) 56(84) bytes of data. > 64 bytes from yyz06s05-in-f104.1e100.net > <http://yyz06s05-in-f104.1e100.net> (173.194.32.104): icmp_seq=1 > ttl=57 time=1.02 ms > 64 bytes from yyz06s05-in-f104.1e100.net > <http://yyz06s05-in-f104.1e100.net> (173.194.32.104): icmp_seq=2 > ttl=57 time=0.996 ms > 64 bytes from yyz06s05-in-f104.1e100.net > <http://yyz06s05-in-f104.1e100.net> (173.194.32.104): icmp_seq=3 > ttl=57 time=0.988 ms > > --- google.com <http://google.com> ping statistics --- > 3 packets transmitted, 3 received, 0% packet loss, time 2000ms > rtt min/avg/max/mdev = 0.988/1.002/1.023/0.029 ms > [root@virtN ~]# > [root@virtN ~]# > [root@virtN ~]# ping 10.100.100.1 > PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. > 64 bytes from 10.100.100.1 <http://10.100.100.1>: icmp_seq=1 ttl=64 > time=0.419 ms > 64 bytes from 10.100.100.1 <http://10.100.100.1>: icmp_seq=2 ttl=64 > time=0.455 ms > > --- 10.100.100.1 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 1000ms > rtt min/avg/max/mdev = 0.419/0.437/0.455/0.018 ms > [root@virtN ~]# > [root@virtN ~]# vzctl enter 504 > entered into CT 504 > [root@ct4 /]# ping google.com <http://google.com> > ping: unknown host google.com <http://google.com> > > Thanks, > Bruce > > > > On Mon, Nov 8, 2010 at 3:32 PM, <ope...@li... > <mailto:ope...@li...>> wrote: > > Have you tried to ping some other IP addresses from outside world > - default iptables rules on CentOS will block DNS traffic for > OpenVZ VM-s. > iptables -L output should show no rules in iptables chains in > order DNS to work for VM-s - or you must setup correct rules for > venet0 device to allow DNS traffic. > > -- > ---------------------------------------------- > Andres Toomsalu, an...@ac... <mailto:an...@ac...> > > > > > On 08.11.2010, at 6:49, ope...@li... > <mailto:ope...@li...> wrote: > >> Hello, >> >> I have followed the guide to create a VM from CentOS_5.5_x64 and >> assigned it IP 10.100.100.50 which is within the range of my DHCP >> router. I can ping the router and the router can ping the VM but >> there is no connection to outside world (e.g google.com >> <http://google.com/> is unreachable). I have noted that route for >> veneth has not populated when the interface started. Is there any >> specific reason to that? What can I do to get this running? >> >> *** I also get "SIOCADDRT: Network is unreachable" when I do >> service network restart. >> >> Following is all the output: >> >> [root@virtN /]# ifconfig >> 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:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> venet0 Link encap:UNSPEC HWaddr >> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 >> inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 >> Mask:255.255.255.255 >> UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 >> RX packets:99 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:115 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:7795 (7.6 KiB) TX bytes:9107 (8.8 KiB) >> >> venet0:0 Link encap:UNSPEC HWaddr >> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 >> inet addr:10.100.100.50 P-t-P:10.100.100.50 >> Bcast:10.100.100.50 Mask:255.255.255.255 >> UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 >> >> [root@virtN /]# route >> Kernel IP routing table >> Destination Gateway Genmask Flags Metric Ref >> Use Iface >> 192.0.2.0 * 255.255.255.0 U 0 0 >> 0 venet0 >> 169.254.0.0 * 255.255.0.0 U 0 0 >> 0 venet0 >> default 192.0.2.1 0.0.0.0 UG 0 0 >> 0 venet0 >> [root@virtN /]# ping 10.100.100.1 >> PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. >> 64 bytes from 10.100.100.1 <http://10.100.100.1/>: icmp_seq=1 >> ttl=63 time=0.316 ms >> 64 bytes from 10.100.100.1 <http://10.100.100.1/>: icmp_seq=2 >> ttl=63 time=0.497 ms >> >> --- 10.100.100.1 ping statistics --- >> 2 packets transmitted, 2 received, 0% packet loss, time 999ms >> rtt min/avg/max/mdev = 0.316/0.406/0.497/0.092 ms >> [root@virtN /]# ping google.com <http://google.com/> >> PING google.com <http://google.com/> (173.194.32.104) 56(84) >> bytes of data. >> >> --- google.com <http://google.com/> ping statistics --- >> 3 packets transmitted, 0 received, 100% packet loss, time 1999ms >> >> [root@virtN /]# service network restart >> Shutting down interface venet0: [ OK ] >> Shutting down loopback interface: [ OK ] >> Bringing up loopback interface: [ OK ] >> Bringing up interface venet0: SIOCADDRT: Network is unreachable >> [ OK ] >> >> >> Thanks, >> Bruce >> ------------------------------------------------------------------------------ >> The Next 800 Companies to Lead America's Growth: New Video Whitepaper >> David G. Thomson, author of the best-selling book "Blueprint to a >> Billion" shares his insights and actions to help propel your >> business during the next growth cycle. Listen Now! >> http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ >> OpenNode-users mailing list >> Ope...@li... >> <mailto:Ope...@li...> >> https://lists.sourceforge.net/lists/listinfo/opennode-users > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > <mailto:Ope...@li...> > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > ------------------------------------------------------------------------ > > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > |
From: <ope...@li...> - 2010-11-09 07:32:50
|
Hello As a side note, maybe I missed in the earlier communication in the mail list, but have you tried to ping google.com's physical IP-address (173.194.32.104, 74.125.39.99) inside the OpenVZ CT to establish whether it is only a DNS problem or a larger-scale network malfunction. Best regards, Danel |
From: <ope...@li...> - 2010-11-09 05:33:57
|
Hello As a side note, maybe I missed in the earlier communication in the mail list, but have you tried to ping google.com's physical IP-address (173.194.32.104, 74.125.39.99) inside the OpenVZ CT to establish whether it is only a DNS problem or a larger-scale network malfunction. Best regards, Danel On 09.11.2010, at 6:11, ope...@li... wrote: > Thanks for the continued support Andres. > > Let's start from the beginning and have a full snapshot. Following is posting of both inside the VM and at the main node. > (code separated by ****) > > ********************************************************************************************************************************************* > Code Used to create the VM > ------------------------------------------ > vzctl create 504 --ostemplate centos-5-x86_64 > vzctl set 504 --ipadd 10.100.100.137 --save > vzctl set 504 --nameserver 10.100.100.137 --save > vzctl set 504 --hostname ct4.domain --save > vzctl set 504 --diskspace 10G:11G --save > vzctl set 504 --diskinodes 900000:910000 --save > vzctl set 504 --quotatime 600 --save > vzctl start 504 > vzctl set 504 --userpasswd root:1234 > vzctl exec 504 ps ax > > > > ********************************************************************************************************************************************** > Code used to lunch VM: > ----------------------------------- > > Inside VM: > [root@ct4 /]# ifconfig > 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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255 > UP BROADCAST POINTOPOINT RUNNING NOARP 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:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > inet addr:10.100.100.137 P-t-P:10.100.100.137 Bcast:10.100.100.137 Mask:255.255.255.255 > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > > [root@ct4 /]# iptables -L > Chain INPUT (policy ACCEPT) > target prot opt source destination > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > [root@ct4 /]# ping google.com > ping: unknown host google.com > [root@ct4 /]# ping 10.100.100.1 > PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. > > --- 10.100.100.1 ping statistics --- > 19 packets transmitted, 0 received, 100% packet loss, time 18001ms > > > ********************************************************************************************************************************* > At the main Node: > ---------------------------- > [root@virtN ~]# ifconfig > eth0 Link encap:Ethernet HWaddr 00:25:90:1A:A7:72 > inet6 addr: fe80::225:90ff:fe1a:a772/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:12 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:1002 (1002.0 b) TX bytes:468 (468.0 b) > Memory:faee0000-faf00000 > > eth1 Link encap:Ethernet HWaddr 00:25:90:1A:A7:73 > inet addr:10.100.100.141 Bcast:10.100.100.255 Mask:255.255.255.0 > inet6 addr: fe80::225:90ff:fe1a:a773/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:60 errors:0 dropped:0 overruns:0 frame:0 > TX packets:76 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:6439 (6.2 KiB) TX bytes:10143 (9.9 KiB) > Memory:fafe0000-fb000000 > > 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:3 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:336 (336.0 b) TX bytes:336 (336.0 b) > > venet0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:4572 (4.4 KiB) > > virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) > > [root@virtN ~]# > [root@virtN ~]# iptables -L > Chain INPUT (policy ACCEPT) > target prot opt source destination > ACCEPT udp -- anywhere anywhere udp dpt:domain > ACCEPT tcp -- anywhere anywhere tcp dpt:domain > ACCEPT udp -- anywhere anywhere udp dpt:bootps > ACCEPT tcp -- anywhere anywhere tcp dpt:bootps > > Chain FORWARD (policy ACCEPT) > target prot opt source destination > ACCEPT all -- anywhere 192.168.122.0/24 state RELATED,ESTABLISHED > ACCEPT all -- 192.168.122.0/24 anywhere > ACCEPT all -- anywhere anywhere > REJECT all -- anywhere anywhere reject-with icmp-port-unreachable > REJECT all -- anywhere anywhere reject-with icmp-port-unreachable > > Chain OUTPUT (policy ACCEPT) > target prot opt source destination > [root@virtN ~]# > [root@virtN ~]# route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 10.100.100.50 * 255.255.255.255 UH 0 0 0 venet0 > 10.100.100.49 * 255.255.255.255 UH 0 0 0 venet0 > 10.100.100.139 * 255.255.255.255 UH 0 0 0 venet0 > 10.100.100.137 * 255.255.255.255 UH 0 0 0 venet0 > 10.100.100.0 * 255.255.255.0 U 0 0 0 eth1 > 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 > 169.254.0.0 * 255.255.0.0 U 0 0 0 eth1 > default 155-redbox.loca 0.0.0.0 UG 0 0 0 eth1 > [root@virtN ~]# > [root@virtN ~]# ping google.com > PING google.com (173.194.32.104) 56(84) bytes of data. > 64 bytes from yyz06s05-in-f104.1e100.net (173.194.32.104): icmp_seq=1 ttl=57 time=1.02 ms > 64 bytes from yyz06s05-in-f104.1e100.net (173.194.32.104): icmp_seq=2 ttl=57 time=0.996 ms > 64 bytes from yyz06s05-in-f104.1e100.net (173.194.32.104): icmp_seq=3 ttl=57 time=0.988 ms > > --- google.com ping statistics --- > 3 packets transmitted, 3 received, 0% packet loss, time 2000ms > rtt min/avg/max/mdev = 0.988/1.002/1.023/0.029 ms > [root@virtN ~]# > [root@virtN ~]# > [root@virtN ~]# ping 10.100.100.1 > PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. > 64 bytes from 10.100.100.1: icmp_seq=1 ttl=64 time=0.419 ms > 64 bytes from 10.100.100.1: icmp_seq=2 ttl=64 time=0.455 ms > > --- 10.100.100.1 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 1000ms > rtt min/avg/max/mdev = 0.419/0.437/0.455/0.018 ms > [root@virtN ~]# > [root@virtN ~]# vzctl enter 504 > entered into CT 504 > [root@ct4 /]# ping google.com > ping: unknown host google.com > > Thanks, > Bruce > > > > On Mon, Nov 8, 2010 at 3:32 PM, <ope...@li...> wrote: > Have you tried to ping some other IP addresses from outside world - default iptables rules on CentOS will block DNS traffic for OpenVZ VM-s. > iptables -L output should show no rules in iptables chains in order DNS to work for VM-s - or you must setup correct rules for venet0 device to allow DNS traffic. > > -- > ---------------------------------------------- > Andres Toomsalu, an...@ac... > > > > > On 08.11.2010, at 6:49, ope...@li... wrote: > >> Hello, >> >> I have followed the guide to create a VM from CentOS_5.5_x64 and assigned it IP 10.100.100.50 which is within the range of my DHCP router. I can ping the router and the router can ping the VM but there is no connection to outside world (e.g google.com is unreachable). I have noted that route for veneth has not populated when the interface started. Is there any specific reason to that? What can I do to get this running? >> >> *** I also get "SIOCADDRT: Network is unreachable" when I do service network restart. >> >> Following is all the output: >> >> [root@virtN /]# ifconfig >> 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:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 >> inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255 >> UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 >> RX packets:99 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:115 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:0 >> RX bytes:7795 (7.6 KiB) TX bytes:9107 (8.8 KiB) >> >> venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 >> inet addr:10.100.100.50 P-t-P:10.100.100.50 Bcast:10.100.100.50 Mask:255.255.255.255 >> UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 >> >> [root@virtN /]# route >> Kernel IP routing table >> Destination Gateway Genmask Flags Metric Ref Use Iface >> 192.0.2.0 * 255.255.255.0 U 0 0 0 venet0 >> 169.254.0.0 * 255.255.0.0 U 0 0 0 venet0 >> default 192.0.2.1 0.0.0.0 UG 0 0 0 venet0 >> [root@virtN /]# ping 10.100.100.1 >> PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. >> 64 bytes from 10.100.100.1: icmp_seq=1 ttl=63 time=0.316 ms >> 64 bytes from 10.100.100.1: icmp_seq=2 ttl=63 time=0.497 ms >> >> --- 10.100.100.1 ping statistics --- >> 2 packets transmitted, 2 received, 0% packet loss, time 999ms >> rtt min/avg/max/mdev = 0.316/0.406/0.497/0.092 ms >> [root@virtN /]# ping google.com >> PING google.com (173.194.32.104) 56(84) bytes of data. >> >> --- google.com ping statistics --- >> 3 packets transmitted, 0 received, 100% packet loss, time 1999ms >> >> [root@virtN /]# service network restart >> Shutting down interface venet0: [ OK ] >> Shutting down loopback interface: [ OK ] >> Bringing up loopback interface: [ OK ] >> Bringing up interface venet0: SIOCADDRT: Network is unreachable >> [ OK ] >> >> >> Thanks, >> Bruce >> ------------------------------------------------------------------------------ >> The Next 800 Companies to Lead America's Growth: New Video Whitepaper >> David G. Thomson, author of the best-selling book "Blueprint to a >> Billion" shares his insights and actions to help propel your >> business during the next growth cycle. Listen Now! >> http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ >> OpenNode-users mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opennode-users > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users |
From: <ope...@li...> - 2010-11-09 04:12:09
|
Thanks for the continued support Andres. Let's start from the beginning and have a full snapshot. Following is posting of both inside the VM and at the main node. (code separated by ****) ********************************************************************************************************************************************* Code Used to create the VM ------------------------------------------ vzctl create 504 --ostemplate centos-5-x86_64 vzctl set 504 --ipadd 10.100.100.137 --save vzctl set 504 --nameserver 10.100.100.137 --save vzctl set 504 --hostname ct4.domain --save vzctl set 504 --diskspace 10G:11G --save vzctl set 504 --diskinodes 900000:910000 --save vzctl set 504 --quotatime 600 --save vzctl start 504 vzctl set 504 --userpasswd root:1234 vzctl exec 504 ps ax ********************************************************************************************************************************************** Code used to lunch VM: ----------------------------------- Inside VM: [root@ct4 /]# ifconfig 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:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP 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:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.100.100.137 P-t-P:10.100.100.137 Bcast:10.100.100.137 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 [root@ct4 /]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination [root@ct4 /]# ping google.com ping: unknown host google.com [root@ct4 /]# ping 10.100.100.1 PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. --- 10.100.100.1 ping statistics --- 19 packets transmitted, 0 received, 100% packet loss, time 18001ms ********************************************************************************************************************************* At the main Node: ---------------------------- [root@virtN ~]# ifconfig eth0 Link encap:Ethernet HWaddr 00:25:90:1A:A7:72 inet6 addr: fe80::225:90ff:fe1a:a772/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1002 (1002.0 b) TX bytes:468 (468.0 b) Memory:faee0000-faf00000 eth1 Link encap:Ethernet HWaddr 00:25:90:1A:A7:73 inet addr:10.100.100.141 Bcast:10.100.100.255 Mask:255.255.255.0 inet6 addr: fe80::225:90ff:fe1a:a773/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:60 errors:0 dropped:0 overruns:0 frame:0 TX packets:76 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:6439 (6.2 KiB) TX bytes:10143 (9.9 KiB) Memory:fafe0000-fb000000 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:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:336 (336.0 b) TX bytes:336 (336.0 b) venet0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:18 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:4572 (4.4 KiB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) [root@virtN ~]# [root@virtN ~]# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT udp -- anywhere anywhere udp dpt:bootps ACCEPT tcp -- anywhere anywhere tcp dpt:bootps Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere 192.168.122.0/24 state RELATED,ESTABLISHED ACCEPT all -- 192.168.122.0/24 anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-port-unreachable REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain OUTPUT (policy ACCEPT) target prot opt source destination [root@virtN ~]# [root@virtN ~]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.100.100.50 * 255.255.255.255 UH 0 0 0 venet0 10.100.100.49 * 255.255.255.255 UH 0 0 0 venet0 10.100.100.139 * 255.255.255.255 UH 0 0 0 venet0 10.100.100.137 * 255.255.255.255 UH 0 0 0 venet0 10.100.100.0 * 255.255.255.0 U 0 0 0 eth1 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 169.254.0.0 * 255.255.0.0 U 0 0 0 eth1 default 155-redbox.loca 0.0.0.0 UG 0 0 0 eth1 [root@virtN ~]# [root@virtN ~]# ping google.com PING google.com (173.194.32.104) 56(84) bytes of data. 64 bytes from yyz06s05-in-f104.1e100.net (173.194.32.104): icmp_seq=1 ttl=57 time=1.02 ms 64 bytes from yyz06s05-in-f104.1e100.net (173.194.32.104): icmp_seq=2 ttl=57 time=0.996 ms 64 bytes from yyz06s05-in-f104.1e100.net (173.194.32.104): icmp_seq=3 ttl=57 time=0.988 ms --- google.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.988/1.002/1.023/0.029 ms [root@virtN ~]# [root@virtN ~]# [root@virtN ~]# ping 10.100.100.1 PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. 64 bytes from 10.100.100.1: icmp_seq=1 ttl=64 time=0.419 ms 64 bytes from 10.100.100.1: icmp_seq=2 ttl=64 time=0.455 ms --- 10.100.100.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 0.419/0.437/0.455/0.018 ms [root@virtN ~]# [root@virtN ~]# vzctl enter 504 entered into CT 504 [root@ct4 /]# ping google.com ping: unknown host google.com Thanks, Bruce On Mon, Nov 8, 2010 at 3:32 PM, <ope...@li...>wrote: > Have you tried to ping some other IP addresses from outside world - default > iptables rules on CentOS will block DNS traffic for OpenVZ VM-s. > iptables -L output should show no rules in iptables chains in order DNS to > work for VM-s - or you must setup correct rules for venet0 device to allow > DNS traffic. > > -- > ---------------------------------------------- > Andres Toomsalu, an...@ac... > > > > > On 08.11.2010, at 6:49, ope...@li... wrote: > > Hello, > > I have followed the guide to create a VM from CentOS_5.5_x64 and assigned > it IP 10.100.100.50 which is within the range of my DHCP router. I can ping > the router and the router can ping the VM but there is no connection to > outside world (e.g google.com is unreachable). I have noted that route for > veneth has not populated when the interface started. Is there any specific > reason to that? What can I do to get this running? > > *** I also get "SIOCADDRT: Network is unreachable" when I do service > network restart. > > Following is all the output: > > [root@virtN /]# ifconfig > 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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > venet0 Link encap:UNSPEC HWaddr > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 > Mask:255.255.255.255 > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > RX packets:99 errors:0 dropped:0 overruns:0 frame:0 > TX packets:115 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:7795 (7.6 KiB) TX bytes:9107 (8.8 KiB) > > venet0:0 Link encap:UNSPEC HWaddr > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > inet addr:10.100.100.50 P-t-P:10.100.100.50 Bcast:10.100.100.50 > Mask:255.255.255.255 > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > > [root@virtN /]# route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 192.0.2.0 * 255.255.255.0 U 0 0 0 > venet0 > 169.254.0.0 * 255.255.0.0 U 0 0 0 > venet0 > default 192.0.2.1 0.0.0.0 UG 0 0 0 > venet0 > [root@virtN /]# ping 10.100.100.1 > PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. > 64 bytes from 10.100.100.1: icmp_seq=1 ttl=63 time=0.316 ms > 64 bytes from 10.100.100.1: icmp_seq=2 ttl=63 time=0.497 ms > > --- 10.100.100.1 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 999ms > rtt min/avg/max/mdev = 0.316/0.406/0.497/0.092 ms > [root@virtN /]# ping google.com > PING google.com (173.194.32.104) 56(84) bytes of data. > > --- google.com ping statistics --- > 3 packets transmitted, 0 received, 100% packet loss, time 1999ms > > [root@virtN /]# service network restart > Shutting down interface venet0: [ OK ] > Shutting down loopback interface: [ OK ] > Bringing up loopback interface: [ OK ] > Bringing up interface venet0: SIOCADDRT: Network is unreachable > [ OK ] > > > Thanks, > Bruce > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > > http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > > |
From: <ope...@li...> - 2010-11-08 23:58:48
|
OpenNode Support Forum is now available from http://opennode.activesys.org/forum/ Cheers, -- ---------------------------------------------- Andres Toomsalu, an...@ac... |
From: <ope...@li...> - 2010-11-08 20:32:16
|
Have you tried to ping some other IP addresses from outside world - default iptables rules on CentOS will block DNS traffic for OpenVZ VM-s. iptables -L output should show no rules in iptables chains in order DNS to work for VM-s - or you must setup correct rules for venet0 device to allow DNS traffic. -- ---------------------------------------------- Andres Toomsalu, an...@ac... On 08.11.2010, at 6:49, ope...@li... wrote: > Hello, > > I have followed the guide to create a VM from CentOS_5.5_x64 and assigned it IP 10.100.100.50 which is within the range of my DHCP router. I can ping the router and the router can ping the VM but there is no connection to outside world (e.g google.com is unreachable). I have noted that route for veneth has not populated when the interface started. Is there any specific reason to that? What can I do to get this running? > > *** I also get "SIOCADDRT: Network is unreachable" when I do service network restart. > > Following is all the output: > > [root@virtN /]# ifconfig > 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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255 > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > RX packets:99 errors:0 dropped:0 overruns:0 frame:0 > TX packets:115 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:7795 (7.6 KiB) TX bytes:9107 (8.8 KiB) > > venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > inet addr:10.100.100.50 P-t-P:10.100.100.50 Bcast:10.100.100.50 Mask:255.255.255.255 > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > > [root@virtN /]# route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 192.0.2.0 * 255.255.255.0 U 0 0 0 venet0 > 169.254.0.0 * 255.255.0.0 U 0 0 0 venet0 > default 192.0.2.1 0.0.0.0 UG 0 0 0 venet0 > [root@virtN /]# ping 10.100.100.1 > PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. > 64 bytes from 10.100.100.1: icmp_seq=1 ttl=63 time=0.316 ms > 64 bytes from 10.100.100.1: icmp_seq=2 ttl=63 time=0.497 ms > > --- 10.100.100.1 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 999ms > rtt min/avg/max/mdev = 0.316/0.406/0.497/0.092 ms > [root@virtN /]# ping google.com > PING google.com (173.194.32.104) 56(84) bytes of data. > > --- google.com ping statistics --- > 3 packets transmitted, 0 received, 100% packet loss, time 1999ms > > [root@virtN /]# service network restart > Shutting down interface venet0: [ OK ] > Shutting down loopback interface: [ OK ] > Bringing up loopback interface: [ OK ] > Bringing up interface venet0: SIOCADDRT: Network is unreachable > [ OK ] > > > Thanks, > Bruce > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users |
From: <ope...@li...> - 2010-11-08 18:35:28
|
Please post also output of 'iptables -L' command from host (hardware) node console - and it does not hurt if you do the same inside VM also. And please note that you can't have DHCP with OpenVZ VM that has venet networking - if you want your VM to do dhcp request then you must use veth type networking with OpenVZ VM. -- ---------------------------------------------- Andres Toomsalu, an...@ac... On 08.11.2010, at 17:53, ope...@li... wrote: > I will look into my router to see if the MAC address are registered to receive static IPs but I doubt that. I don't want to re-install this but I can run the "setup" utility and remove the * for DHCP infront of eth0 and eth1 but I think that would disable the network totally wouldn't it? > > What would be the default entries in /etc/networking/interface or any other file to make this default? > > Thanks again. > > On Mon, Nov 8, 2010 at 10:43 AM, <ope...@li...> wrote: > This is certainly not default OpenNode networking setup - as on OpenNode > you should have vmbr0 bridge device which holds box main IP address. > Physical devices like eth0, eth1 - they should not be configured at all > - instead eth0 should be vmbr0 bridge member by default. > That said - I think you should be able to get networking to work your > way also - but something must be wrong with your default gateway probably. > > ---------------------------------------------- > Andres Toomsalu, an...@ac... > > > > > ope...@li... wrote: > > You are right, I did not touch the host network config as I noted that > > the post-install config which was regarding re-sizing and not network. > > However, from the main node I can ping Google just fine. Here is what > > I have there (I am not sure where the virbr0 192.x.x.x range comes > > from but everything else seems to be good. Oh, and eth0 doesn't have > > an IP and I don't know why.): > > > > [root@virtN ~]# ifconfig > > eth0 Link encap:Ethernet HWaddr 00:25:90:1A:A7:72 > > inet6 addr: fe80::225:90ff:fe1a:a772/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:159 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:100 > > RX bytes:9822 (9.5 KiB) TX bytes:468 (468.0 b) > > Memory:faee0000-faf00000 > > > > eth1 Link encap:Ethernet HWaddr 00:25:90:1A:A7:73 > > inet addr:10.100.100.80 Bcast:10.100.100.255 > > Mask:255.255.255.0 > > inet6 addr: fe80::225:90ff:fe1a:a773/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:636 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:838 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:100 > > RX bytes:62453 (60.9 KiB) TX bytes:91507 (89.3 KiB) > > Memory:fafe0000-fb000000 > > > > 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:3 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:336 (336.0 b) TX bytes:336 (336.0 b) > > > > venet0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:460 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 b) TX bytes:23136 (22.5 KiB) > > > > virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > inet addr:192.168.122.1 Bcast:192.168.122.255 > > Mask:255.255.255.0 > > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) > > > > [root@virtN ~]# route > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref > > Use Iface > > 10.100.100.50 * 255.255.255.255 UH 0 0 > > 0 venet0 > > 10.100.100.49 * 255.255.255.255 UH 0 0 > > 0 venet0 > > 10.100.100.0 * 255.255.255.0 U 0 0 > > 0 eth1 > > 192.168.122.0 * 255.255.255.0 U 0 0 > > 0 virbr0 > > 169.254.0.0 * 255.255.0.0 U 0 0 > > 0 eth1 > > default 151-redbox.loca 0.0.0.0 UG 0 0 > > 0 eth1 > > [root@virtN ~]# ping google.com <http://google.com> > > PING google.com <http://google.com> (173.194.32.104) 56(84) bytes of data. > > 64 bytes from yyz06s05-in-f104.1e100.net > > <http://yyz06s05-in-f104.1e100.net> (173.194.32.104): icmp_seq=1 > > ttl=57 time=1.08 ms > > 64 bytes from yyz06s05-in-f104.1e100.net > > <http://yyz06s05-in-f104.1e100.net> (173.194.32.104): icmp_seq=2 > > ttl=57 time=0.995 ms > > > > --- google.com <http://google.com> ping statistics --- > > 2 packets transmitted, 2 received, 0% packet loss, time 1000ms > > rtt min/avg/max/mdev = 0.995/1.038/1.082/0.054 ms > > > > Thanks, > > Bruce > > > > On Mon, Nov 8, 2010 at 4:35 AM, <ope...@li... > > <mailto:ope...@li...>> wrote: > > > > Did you post ifconfig and route output only as shown inside VM > > probably? > > Please provide also ifconfig and route output from OpenNode shell - I > > think you have not configured host (vmbr0 on hardware node) networking > > properly regarding 10.100.100.0 subnet. > > > > Cheers, > > > > ---------------------------------------------- > > Andres Toomsalu, an...@ac... <mailto:an...@ac...> > > > > > > > > > > ope...@li... > > <mailto:ope...@li...> wrote: > > > Hello, > > > > > > I have followed the guide to create a VM from CentOS_5.5_x64 and > > > assigned it IP 10.100.100.50 which is within the range of my DHCP > > > router. I can ping the router and the router can ping the VM but > > there > > > is no connection to outside world (e.g google.com > > <http://google.com> <http://google.com> > > > is unreachable). I have noted that route for veneth has not > > populated > > > when the interface started. Is there any specific reason to > > that? What > > > can I do to get this running? > > > > > > *** I also get "SIOCADDRT: Network is unreachable" when I do service > > > network restart. > > > > > > Following is all the output: > > > > > > [root@virtN /]# ifconfig > > > 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:0 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:0 > > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > > > > venet0 Link encap:UNSPEC HWaddr > > > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > > > inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 > > > Mask:255.255.255.255 > > > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > > > RX packets:99 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:115 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:0 > > > RX bytes:7795 (7.6 KiB) TX bytes:9107 (8.8 KiB) > > > > > > venet0:0 Link encap:UNSPEC HWaddr > > > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > > > inet addr:10.100.100.50 P-t-P:10.100.100.50 > > > Bcast:10.100.100.50 Mask:255.255.255.255 > > > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > > > > > > [root@virtN /]# route > > > Kernel IP routing table > > > Destination Gateway Genmask Flags Metric Ref > > > Use Iface > > > 192.0.2.0 * 255.255.255.0 U 0 0 > > > 0 venet0 > > > 169.254.0.0 * 255.255.0.0 U 0 0 > > > 0 venet0 > > > default 192.0.2.1 0.0.0.0 UG 0 0 > > > 0 venet0 > > > [root@virtN /]# ping 10.100.100.1 > > > PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. > > > 64 bytes from 10.100.100.1 <http://10.100.100.1>: icmp_seq=1 ttl=63 > > > time=0.316 ms > > > 64 bytes from 10.100.100.1 <http://10.100.100.1>: icmp_seq=2 ttl=63 > > > time=0.497 ms > > > > > > --- 10.100.100.1 ping statistics --- > > > 2 packets transmitted, 2 received, 0% packet loss, time 999ms > > > rtt min/avg/max/mdev = 0.316/0.406/0.497/0.092 ms > > > [root@virtN /]# ping google.com <http://google.com> > > <http://google.com> > > > PING google.com <http://google.com> <http://google.com> > > (173.194.32.104) 56(84) bytes of data. > > > > > > --- google.com <http://google.com> <http://google.com> ping > > statistics --- > > > 3 packets transmitted, 0 received, 100% packet loss, time 1999ms > > > > > > [root@virtN /]# service network restart > > > Shutting down interface venet0: [ OK ] > > > Shutting down loopback interface: [ OK ] > > > Bringing up loopback interface: [ OK ] > > > Bringing up interface venet0: SIOCADDRT: Network is unreachable > > > [ OK ] > > > > > > > > > Thanks, > > > Bruce > > > > > ------------------------------------------------------------------------ > > > > > > > > ------------------------------------------------------------------------------ > > > The Next 800 Companies to Lead America's Growth: New Video > > Whitepaper > > > David G. Thomson, author of the best-selling book "Blueprint to a > > > Billion" shares his insights and actions to help propel your > > > business during the next growth cycle. Listen Now! > > > http://p.sf.net/sfu/SAP-dev2dev > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > OpenNode-users mailing list > > > Ope...@li... > > <mailto:Ope...@li...> > > > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > > > > > ------------------------------------------------------------------------------ > > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > > David G. Thomson, author of the best-selling book "Blueprint to a > > Billion" shares his insights and actions to help propel your > > business during the next growth cycle. Listen Now! > > http://p.sf.net/sfu/SAP-dev2dev > > _______________________________________________ > > OpenNode-users mailing list > > Ope...@li... > > <mailto:Ope...@li...> > > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > > > > ------------------------------------------------------------------------ > > > > ------------------------------------------------------------------------------ > > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > > David G. Thomson, author of the best-selling book "Blueprint to a > > Billion" shares his insights and actions to help propel your > > business during the next growth cycle. Listen Now! > > http://p.sf.net/sfu/SAP-dev2dev > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > OpenNode-users mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users |
From: <ope...@li...> - 2010-11-08 15:53:45
|
I will look into my router to see if the MAC address are registered to receive static IPs but I doubt that. I don't want to re-install this but I can run the "setup" utility and remove the * for DHCP infront of eth0 and eth1 but I think that would disable the network totally wouldn't it? What would be the default entries in /etc/networking/interface or any other file to make this default? Thanks again. On Mon, Nov 8, 2010 at 10:43 AM, <ope...@li...>wrote: > This is certainly not default OpenNode networking setup - as on OpenNode > you should have vmbr0 bridge device which holds box main IP address. > Physical devices like eth0, eth1 - they should not be configured at all > - instead eth0 should be vmbr0 bridge member by default. > That said - I think you should be able to get networking to work your > way also - but something must be wrong with your default gateway probably. > > ---------------------------------------------- > Andres Toomsalu, an...@ac... > > > > > ope...@li... wrote: > > You are right, I did not touch the host network config as I noted that > > the post-install config which was regarding re-sizing and not network. > > However, from the main node I can ping Google just fine. Here is what > > I have there (I am not sure where the virbr0 192.x.x.x range comes > > from but everything else seems to be good. Oh, and eth0 doesn't have > > an IP and I don't know why.): > > > > [root@virtN ~]# ifconfig > > eth0 Link encap:Ethernet HWaddr 00:25:90:1A:A7:72 > > inet6 addr: fe80::225:90ff:fe1a:a772/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:159 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:100 > > RX bytes:9822 (9.5 KiB) TX bytes:468 (468.0 b) > > Memory:faee0000-faf00000 > > > > eth1 Link encap:Ethernet HWaddr 00:25:90:1A:A7:73 > > inet addr:10.100.100.80 Bcast:10.100.100.255 > > Mask:255.255.255.0 > > inet6 addr: fe80::225:90ff:fe1a:a773/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:636 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:838 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:100 > > RX bytes:62453 (60.9 KiB) TX bytes:91507 (89.3 KiB) > > Memory:fafe0000-fb000000 > > > > 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:3 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:336 (336.0 b) TX bytes:336 (336.0 b) > > > > venet0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:460 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 b) TX bytes:23136 (22.5 KiB) > > > > virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > > inet addr:192.168.122.1 Bcast:192.168.122.255 > > Mask:255.255.255.0 > > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) > > > > [root@virtN ~]# route > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref > > Use Iface > > 10.100.100.50 * 255.255.255.255 UH 0 0 > > 0 venet0 > > 10.100.100.49 * 255.255.255.255 UH 0 0 > > 0 venet0 > > 10.100.100.0 * 255.255.255.0 U 0 0 > > 0 eth1 > > 192.168.122.0 * 255.255.255.0 U 0 0 > > 0 virbr0 > > 169.254.0.0 * 255.255.0.0 U 0 0 > > 0 eth1 > > default 151-redbox.loca 0.0.0.0 UG 0 0 > > 0 eth1 > > [root@virtN ~]# ping google.com <http://google.com> > > PING google.com <http://google.com> (173.194.32.104) 56(84) bytes of > data. > > 64 bytes from yyz06s05-in-f104.1e100.net > > <http://yyz06s05-in-f104.1e100.net> (173.194.32.104): icmp_seq=1 > > ttl=57 time=1.08 ms > > 64 bytes from yyz06s05-in-f104.1e100.net > > <http://yyz06s05-in-f104.1e100.net> (173.194.32.104): icmp_seq=2 > > ttl=57 time=0.995 ms > > > > --- google.com <http://google.com> ping statistics --- > > 2 packets transmitted, 2 received, 0% packet loss, time 1000ms > > rtt min/avg/max/mdev = 0.995/1.038/1.082/0.054 ms > > > > Thanks, > > Bruce > > > > On Mon, Nov 8, 2010 at 4:35 AM, <ope...@li... > > <mailto:ope...@li...>> wrote: > > > > Did you post ifconfig and route output only as shown inside VM > > probably? > > Please provide also ifconfig and route output from OpenNode shell - I > > think you have not configured host (vmbr0 on hardware node) > networking > > properly regarding 10.100.100.0 subnet. > > > > Cheers, > > > > ---------------------------------------------- > > Andres Toomsalu, an...@ac... <mailto:an...@ac...> > > > > > > > > > > ope...@li... > > <mailto:ope...@li...> wrote: > > > Hello, > > > > > > I have followed the guide to create a VM from CentOS_5.5_x64 and > > > assigned it IP 10.100.100.50 which is within the range of my DHCP > > > router. I can ping the router and the router can ping the VM but > > there > > > is no connection to outside world (e.g google.com > > <http://google.com> <http://google.com> > > > is unreachable). I have noted that route for veneth has not > > populated > > > when the interface started. Is there any specific reason to > > that? What > > > can I do to get this running? > > > > > > *** I also get "SIOCADDRT: Network is unreachable" when I do > service > > > network restart. > > > > > > Following is all the output: > > > > > > [root@virtN /]# ifconfig > > > 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:0 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:0 > > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > > > > venet0 Link encap:UNSPEC HWaddr > > > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > > > inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 > > > Mask:255.255.255.255 > > > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 > Metric:1 > > > RX packets:99 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:115 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:0 > > > RX bytes:7795 (7.6 KiB) TX bytes:9107 (8.8 KiB) > > > > > > venet0:0 Link encap:UNSPEC HWaddr > > > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > > > inet addr:10.100.100.50 P-t-P:10.100.100.50 > > > Bcast:10.100.100.50 Mask:255.255.255.255 > > > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 > Metric:1 > > > > > > [root@virtN /]# route > > > Kernel IP routing table > > > Destination Gateway Genmask Flags Metric Ref > > > Use Iface > > > 192.0.2.0 * 255.255.255.0 U 0 0 > > > 0 venet0 > > > 169.254.0.0 * 255.255.0.0 U 0 0 > > > 0 venet0 > > > default 192.0.2.1 0.0.0.0 UG 0 0 > > > 0 venet0 > > > [root@virtN /]# ping 10.100.100.1 > > > PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. > > > 64 bytes from 10.100.100.1 <http://10.100.100.1>: icmp_seq=1 > ttl=63 > > > time=0.316 ms > > > 64 bytes from 10.100.100.1 <http://10.100.100.1>: icmp_seq=2 > ttl=63 > > > time=0.497 ms > > > > > > --- 10.100.100.1 ping statistics --- > > > 2 packets transmitted, 2 received, 0% packet loss, time 999ms > > > rtt min/avg/max/mdev = 0.316/0.406/0.497/0.092 ms > > > [root@virtN /]# ping google.com <http://google.com> > > <http://google.com> > > > PING google.com <http://google.com> <http://google.com> > > (173.194.32.104) 56(84) bytes of data. > > > > > > --- google.com <http://google.com> <http://google.com> ping > > statistics --- > > > 3 packets transmitted, 0 received, 100% packet loss, time 1999ms > > > > > > [root@virtN /]# service network restart > > > Shutting down interface venet0: [ OK ] > > > Shutting down loopback interface: [ OK ] > > > Bringing up loopback interface: [ OK ] > > > Bringing up interface venet0: SIOCADDRT: Network is unreachable > > > [ OK ] > > > > > > > > > Thanks, > > > Bruce > > > > > > ------------------------------------------------------------------------ > > > > > > > > > ------------------------------------------------------------------------------ > > > The Next 800 Companies to Lead America's Growth: New Video > > Whitepaper > > > David G. Thomson, author of the best-selling book "Blueprint to a > > > Billion" shares his insights and actions to help propel your > > > business during the next growth cycle. Listen Now! > > > http://p.sf.net/sfu/SAP-dev2dev > > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > OpenNode-users mailing list > > > Ope...@li... > > <mailto:Ope...@li...> > > > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > > > > > > ------------------------------------------------------------------------------ > > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > > David G. Thomson, author of the best-selling book "Blueprint to a > > Billion" shares his insights and actions to help propel your > > business during the next growth cycle. Listen Now! > > http://p.sf.net/sfu/SAP-dev2dev > > _______________________________________________ > > OpenNode-users mailing list > > Ope...@li... > > <mailto:Ope...@li...> > > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > > > > ------------------------------------------------------------------------ > > > > > ------------------------------------------------------------------------------ > > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > > David G. Thomson, author of the best-selling book "Blueprint to a > > Billion" shares his insights and actions to help propel your > > business during the next growth cycle. Listen Now! > > http://p.sf.net/sfu/SAP-dev2dev > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > OpenNode-users mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > |
From: <ope...@li...> - 2010-11-08 15:44:01
|
This is certainly not default OpenNode networking setup - as on OpenNode you should have vmbr0 bridge device which holds box main IP address. Physical devices like eth0, eth1 - they should not be configured at all - instead eth0 should be vmbr0 bridge member by default. That said - I think you should be able to get networking to work your way also - but something must be wrong with your default gateway probably. ---------------------------------------------- Andres Toomsalu, an...@ac... ope...@li... wrote: > You are right, I did not touch the host network config as I noted that > the post-install config which was regarding re-sizing and not network. > However, from the main node I can ping Google just fine. Here is what > I have there (I am not sure where the virbr0 192.x.x.x range comes > from but everything else seems to be good. Oh, and eth0 doesn't have > an IP and I don't know why.): > > [root@virtN ~]# ifconfig > eth0 Link encap:Ethernet HWaddr 00:25:90:1A:A7:72 > inet6 addr: fe80::225:90ff:fe1a:a772/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:159 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:9822 (9.5 KiB) TX bytes:468 (468.0 b) > Memory:faee0000-faf00000 > > eth1 Link encap:Ethernet HWaddr 00:25:90:1A:A7:73 > inet addr:10.100.100.80 Bcast:10.100.100.255 > Mask:255.255.255.0 > inet6 addr: fe80::225:90ff:fe1a:a773/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:636 errors:0 dropped:0 overruns:0 frame:0 > TX packets:838 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:100 > RX bytes:62453 (60.9 KiB) TX bytes:91507 (89.3 KiB) > Memory:fafe0000-fb000000 > > 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:3 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:336 (336.0 b) TX bytes:336 (336.0 b) > > venet0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:460 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:23136 (22.5 KiB) > > virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:192.168.122.1 Bcast:192.168.122.255 > Mask:255.255.255.0 > inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) > > [root@virtN ~]# route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref > Use Iface > 10.100.100.50 * 255.255.255.255 UH 0 0 > 0 venet0 > 10.100.100.49 * 255.255.255.255 UH 0 0 > 0 venet0 > 10.100.100.0 * 255.255.255.0 U 0 0 > 0 eth1 > 192.168.122.0 * 255.255.255.0 U 0 0 > 0 virbr0 > 169.254.0.0 * 255.255.0.0 U 0 0 > 0 eth1 > default 151-redbox.loca 0.0.0.0 UG 0 0 > 0 eth1 > [root@virtN ~]# ping google.com <http://google.com> > PING google.com <http://google.com> (173.194.32.104) 56(84) bytes of data. > 64 bytes from yyz06s05-in-f104.1e100.net > <http://yyz06s05-in-f104.1e100.net> (173.194.32.104): icmp_seq=1 > ttl=57 time=1.08 ms > 64 bytes from yyz06s05-in-f104.1e100.net > <http://yyz06s05-in-f104.1e100.net> (173.194.32.104): icmp_seq=2 > ttl=57 time=0.995 ms > > --- google.com <http://google.com> ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 1000ms > rtt min/avg/max/mdev = 0.995/1.038/1.082/0.054 ms > > Thanks, > Bruce > > On Mon, Nov 8, 2010 at 4:35 AM, <ope...@li... > <mailto:ope...@li...>> wrote: > > Did you post ifconfig and route output only as shown inside VM > probably? > Please provide also ifconfig and route output from OpenNode shell - I > think you have not configured host (vmbr0 on hardware node) networking > properly regarding 10.100.100.0 subnet. > > Cheers, > > ---------------------------------------------- > Andres Toomsalu, an...@ac... <mailto:an...@ac...> > > > > > ope...@li... > <mailto:ope...@li...> wrote: > > Hello, > > > > I have followed the guide to create a VM from CentOS_5.5_x64 and > > assigned it IP 10.100.100.50 which is within the range of my DHCP > > router. I can ping the router and the router can ping the VM but > there > > is no connection to outside world (e.g google.com > <http://google.com> <http://google.com> > > is unreachable). I have noted that route for veneth has not > populated > > when the interface started. Is there any specific reason to > that? What > > can I do to get this running? > > > > *** I also get "SIOCADDRT: Network is unreachable" when I do service > > network restart. > > > > Following is all the output: > > > > [root@virtN /]# ifconfig > > 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:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > > venet0 Link encap:UNSPEC HWaddr > > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > > inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 > > Mask:255.255.255.255 > > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > > RX packets:99 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:115 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:7795 (7.6 KiB) TX bytes:9107 (8.8 KiB) > > > > venet0:0 Link encap:UNSPEC HWaddr > > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > > inet addr:10.100.100.50 P-t-P:10.100.100.50 > > Bcast:10.100.100.50 Mask:255.255.255.255 > > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > > > > [root@virtN /]# route > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref > > Use Iface > > 192.0.2.0 * 255.255.255.0 U 0 0 > > 0 venet0 > > 169.254.0.0 * 255.255.0.0 U 0 0 > > 0 venet0 > > default 192.0.2.1 0.0.0.0 UG 0 0 > > 0 venet0 > > [root@virtN /]# ping 10.100.100.1 > > PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. > > 64 bytes from 10.100.100.1 <http://10.100.100.1>: icmp_seq=1 ttl=63 > > time=0.316 ms > > 64 bytes from 10.100.100.1 <http://10.100.100.1>: icmp_seq=2 ttl=63 > > time=0.497 ms > > > > --- 10.100.100.1 ping statistics --- > > 2 packets transmitted, 2 received, 0% packet loss, time 999ms > > rtt min/avg/max/mdev = 0.316/0.406/0.497/0.092 ms > > [root@virtN /]# ping google.com <http://google.com> > <http://google.com> > > PING google.com <http://google.com> <http://google.com> > (173.194.32.104) 56(84) bytes of data. > > > > --- google.com <http://google.com> <http://google.com> ping > statistics --- > > 3 packets transmitted, 0 received, 100% packet loss, time 1999ms > > > > [root@virtN /]# service network restart > > Shutting down interface venet0: [ OK ] > > Shutting down loopback interface: [ OK ] > > Bringing up loopback interface: [ OK ] > > Bringing up interface venet0: SIOCADDRT: Network is unreachable > > [ OK ] > > > > > > Thanks, > > Bruce > > > ------------------------------------------------------------------------ > > > > > ------------------------------------------------------------------------------ > > The Next 800 Companies to Lead America's Growth: New Video > Whitepaper > > David G. Thomson, author of the best-selling book "Blueprint to a > > Billion" shares his insights and actions to help propel your > > business during the next growth cycle. Listen Now! > > http://p.sf.net/sfu/SAP-dev2dev > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > OpenNode-users mailing list > > Ope...@li... > <mailto:Ope...@li...> > > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > <mailto:Ope...@li...> > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > ------------------------------------------------------------------------ > > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > |
From: <ope...@li...> - 2010-11-08 15:33:16
|
You are right, I did not touch the host network config as I noted that the post-install config which was regarding re-sizing and not network. However, from the main node I can ping Google just fine. Here is what I have there (I am not sure where the virbr0 192.x.x.x range comes from but everything else seems to be good. Oh, and eth0 doesn't have an IP and I don't know why.): [root@virtN ~]# ifconfig eth0 Link encap:Ethernet HWaddr 00:25:90:1A:A7:72 inet6 addr: fe80::225:90ff:fe1a:a772/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:159 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:9822 (9.5 KiB) TX bytes:468 (468.0 b) Memory:faee0000-faf00000 eth1 Link encap:Ethernet HWaddr 00:25:90:1A:A7:73 inet addr:10.100.100.80 Bcast:10.100.100.255 Mask:255.255.255.0 inet6 addr: fe80::225:90ff:fe1a:a773/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:636 errors:0 dropped:0 overruns:0 frame:0 TX packets:838 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:62453 (60.9 KiB) TX bytes:91507 (89.3 KiB) Memory:fafe0000-fb000000 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:3 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:336 (336.0 b) TX bytes:336 (336.0 b) venet0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:460 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:23136 (22.5 KiB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) [root@virtN ~]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.100.100.50 * 255.255.255.255 UH 0 0 0 venet0 10.100.100.49 * 255.255.255.255 UH 0 0 0 venet0 10.100.100.0 * 255.255.255.0 U 0 0 0 eth1 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 169.254.0.0 * 255.255.0.0 U 0 0 0 eth1 default 151-redbox.loca 0.0.0.0 UG 0 0 0 eth1 [root@virtN ~]# ping google.com PING google.com (173.194.32.104) 56(84) bytes of data. 64 bytes from yyz06s05-in-f104.1e100.net (173.194.32.104): icmp_seq=1 ttl=57 time=1.08 ms 64 bytes from yyz06s05-in-f104.1e100.net (173.194.32.104): icmp_seq=2 ttl=57 time=0.995 ms --- google.com ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 0.995/1.038/1.082/0.054 ms Thanks, Bruce On Mon, Nov 8, 2010 at 4:35 AM, <ope...@li...>wrote: > Did you post ifconfig and route output only as shown inside VM probably? > Please provide also ifconfig and route output from OpenNode shell - I > think you have not configured host (vmbr0 on hardware node) networking > properly regarding 10.100.100.0 subnet. > > Cheers, > > ---------------------------------------------- > Andres Toomsalu, an...@ac... > > > > > ope...@li... wrote: > > Hello, > > > > I have followed the guide to create a VM from CentOS_5.5_x64 and > > assigned it IP 10.100.100.50 which is within the range of my DHCP > > router. I can ping the router and the router can ping the VM but there > > is no connection to outside world (e.g google.com <http://google.com> > > is unreachable). I have noted that route for veneth has not populated > > when the interface started. Is there any specific reason to that? What > > can I do to get this running? > > > > *** I also get "SIOCADDRT: Network is unreachable" when I do service > > network restart. > > > > Following is all the output: > > > > [root@virtN /]# ifconfig > > 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:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > > venet0 Link encap:UNSPEC HWaddr > > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > > inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 > > Mask:255.255.255.255 > > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > > RX packets:99 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:115 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > RX bytes:7795 (7.6 KiB) TX bytes:9107 (8.8 KiB) > > > > venet0:0 Link encap:UNSPEC HWaddr > > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > > inet addr:10.100.100.50 P-t-P:10.100.100.50 > > Bcast:10.100.100.50 Mask:255.255.255.255 > > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > > > > [root@virtN /]# route > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref > > Use Iface > > 192.0.2.0 * 255.255.255.0 U 0 0 > > 0 venet0 > > 169.254.0.0 * 255.255.0.0 U 0 0 > > 0 venet0 > > default 192.0.2.1 0.0.0.0 UG 0 0 > > 0 venet0 > > [root@virtN /]# ping 10.100.100.1 > > PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. > > 64 bytes from 10.100.100.1 <http://10.100.100.1>: icmp_seq=1 ttl=63 > > time=0.316 ms > > 64 bytes from 10.100.100.1 <http://10.100.100.1>: icmp_seq=2 ttl=63 > > time=0.497 ms > > > > --- 10.100.100.1 ping statistics --- > > 2 packets transmitted, 2 received, 0% packet loss, time 999ms > > rtt min/avg/max/mdev = 0.316/0.406/0.497/0.092 ms > > [root@virtN /]# ping google.com <http://google.com> > > PING google.com <http://google.com> (173.194.32.104) 56(84) bytes of > data. > > > > --- google.com <http://google.com> ping statistics --- > > 3 packets transmitted, 0 received, 100% packet loss, time 1999ms > > > > [root@virtN /]# service network restart > > Shutting down interface venet0: [ OK ] > > Shutting down loopback interface: [ OK ] > > Bringing up loopback interface: [ OK ] > > Bringing up interface venet0: SIOCADDRT: Network is unreachable > > [ OK ] > > > > > > Thanks, > > Bruce > > ------------------------------------------------------------------------ > > > > > ------------------------------------------------------------------------------ > > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > > David G. Thomson, author of the best-selling book "Blueprint to a > > Billion" shares his insights and actions to help propel your > > business during the next growth cycle. Listen Now! > > http://p.sf.net/sfu/SAP-dev2dev > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > OpenNode-users mailing list > > Ope...@li... > > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > |
From: <ope...@li...> - 2010-11-08 09:57:33
|
Did you post ifconfig and route output only as shown inside VM probably? Please provide also ifconfig and route output from OpenNode shell - I think you have not configured host (vmbr0 on hardware node) networking properly regarding 10.100.100.0 subnet. Cheers, ---------------------------------------------- Andres Toomsalu, an...@ac... ope...@li... wrote: > Hello, > > I have followed the guide to create a VM from CentOS_5.5_x64 and > assigned it IP 10.100.100.50 which is within the range of my DHCP > router. I can ping the router and the router can ping the VM but there > is no connection to outside world (e.g google.com <http://google.com> > is unreachable). I have noted that route for veneth has not populated > when the interface started. Is there any specific reason to that? What > can I do to get this running? > > *** I also get "SIOCADDRT: Network is unreachable" when I do service > network restart. > > Following is all the output: > > [root@virtN /]# ifconfig > 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:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > venet0 Link encap:UNSPEC HWaddr > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 > Mask:255.255.255.255 > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > RX packets:99 errors:0 dropped:0 overruns:0 frame:0 > TX packets:115 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:7795 (7.6 KiB) TX bytes:9107 (8.8 KiB) > > venet0:0 Link encap:UNSPEC HWaddr > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > inet addr:10.100.100.50 P-t-P:10.100.100.50 > Bcast:10.100.100.50 Mask:255.255.255.255 > UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 > > [root@virtN /]# route > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref > Use Iface > 192.0.2.0 * 255.255.255.0 U 0 0 > 0 venet0 > 169.254.0.0 * 255.255.0.0 U 0 0 > 0 venet0 > default 192.0.2.1 0.0.0.0 UG 0 0 > 0 venet0 > [root@virtN /]# ping 10.100.100.1 > PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. > 64 bytes from 10.100.100.1 <http://10.100.100.1>: icmp_seq=1 ttl=63 > time=0.316 ms > 64 bytes from 10.100.100.1 <http://10.100.100.1>: icmp_seq=2 ttl=63 > time=0.497 ms > > --- 10.100.100.1 ping statistics --- > 2 packets transmitted, 2 received, 0% packet loss, time 999ms > rtt min/avg/max/mdev = 0.316/0.406/0.497/0.092 ms > [root@virtN /]# ping google.com <http://google.com> > PING google.com <http://google.com> (173.194.32.104) 56(84) bytes of data. > > --- google.com <http://google.com> ping statistics --- > 3 packets transmitted, 0 received, 100% packet loss, time 1999ms > > [root@virtN /]# service network restart > Shutting down interface venet0: [ OK ] > Shutting down loopback interface: [ OK ] > Bringing up loopback interface: [ OK ] > Bringing up interface venet0: SIOCADDRT: Network is unreachable > [ OK ] > > > Thanks, > Bruce > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > ------------------------------------------------------------------------ > > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > |
From: <ope...@li...> - 2010-11-08 04:50:14
|
Hello, I have followed the guide to create a VM from CentOS_5.5_x64 and assigned it IP 10.100.100.50 which is within the range of my DHCP router. I can ping the router and the router can ping the VM but there is no connection to outside world (e.g google.com is unreachable). I have noted that route for veneth has not populated when the interface started. Is there any specific reason to that? What can I do to get this running? *** I also get "SIOCADDRT: Network is unreachable" when I do service network restart. Following is all the output: [root@virtN /]# ifconfig 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:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:99 errors:0 dropped:0 overruns:0 frame:0 TX packets:115 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:7795 (7.6 KiB) TX bytes:9107 (8.8 KiB) venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:10.100.100.50 P-t-P:10.100.100.50 Bcast:10.100.100.50 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 [root@virtN /]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.0.2.0 * 255.255.255.0 U 0 0 0 venet0 169.254.0.0 * 255.255.0.0 U 0 0 0 venet0 default 192.0.2.1 0.0.0.0 UG 0 0 0 venet0 [root@virtN /]# ping 10.100.100.1 PING 10.100.100.1 (10.100.100.1) 56(84) bytes of data. 64 bytes from 10.100.100.1: icmp_seq=1 ttl=63 time=0.316 ms 64 bytes from 10.100.100.1: icmp_seq=2 ttl=63 time=0.497 ms --- 10.100.100.1 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms rtt min/avg/max/mdev = 0.316/0.406/0.497/0.092 ms [root@virtN /]# ping google.com PING google.com (173.194.32.104) 56(84) bytes of data. --- google.com ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms [root@virtN /]# service network restart Shutting down interface venet0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface venet0: SIOCADDRT: Network is unreachable [ OK ] Thanks, Bruce |
From: <ope...@li...> - 2010-11-07 15:03:06
|
Thanks, I will try that today. May I know what exact changes were made? Yes, Sourceforge is good for downloads only but their forum is just boring and cluttered. Suggestion for a forum engine: http://www.simplemachines.org/ Pfsense forum uses them and it works great. Thanks, Bruce On Sun, Nov 7, 2010 at 5:11 AM, <ope...@li...>wrote: > This opennode CLI PATH problem should be now corrected in new 1.0 and 1.1 > opennode rpms - just do 'yum upgrade opennode' > I think we will put up dedicated support forum soon - althou opennode > sourceforge page already has one that nobody uses :-) > > Cheers, > -- > ---------------------------------------------- > Andres Toomsalu, an...@ac... > > > > > > On 07.11.2010, at 1:18, ope...@li... wrote: > > Thanks. I would really like to contribute if there is a Wiki or a support > forum. These little things can really make life easier for everyone if > documented. > > Thanks for the input. > > > On Sat, Nov 6, 2010 at 6:35 PM, <ope...@li...>wrote: > >> When doing yum upgrade opennode cli utility might be removed from PATH >> environment variable - we will fix this in next 1.1 beta. >> You can still run opennode CLi utility by executing on console: >> /opt/opennode/bin/opennode >> >> >> Cheers, >> -- >> ---------------------------------------------- >> Andres Toomsalu, an...@ac... >> >> >> >> On 07.11.2010, at 0:07, ope...@li... wrote: >> >> Thanks for the quick and detailed response. So, the beta version 1.1 is >> not the one with Web UI then I am assuming. >> >> I got into the regular console using FUNC. I did the beta upgrade and >> restarted the machine. Now, the prompt for login reads virtN and >> the management utility is gone. I guess I should go back to the stable >> version. >> >> I am really looking forward to the Web UI as without it, it's the graphs >> and stats are very useful. >> >> Regards, >> Bruce >> >> On Sat, Nov 6, 2010 at 5:59 PM, <ope...@li...>wrote: >> >>> Hello, >>> >>> I hope the following answers your questions. >>> >>> >>> If you choose Exit in the OpenNode Management Utility you are returned to >>> the regular terminal where you can do all the common linux management. >>> >>> The console that opens under the Management button is the virsh >>> management console for managing virtual machines over the libvirt API. The >>> coming OpenNode 1.1 version supports virsh console shortcut buttons for both >>> OpenVZ and KVM. >>> >>> Web UI will be hopefully released in the coming weeks when last tweaks >>> are carried out. Then you will have and option in the OpenNode Management >>> Utility to download, install and configure the Web UI. And also we will >>> provide all the necessary guidelines on our dedicated OpenNode webpage. >>> >>> >>> Best regards, >>> Danel >>> >>> On 06.11.2010, at 23:46, ope...@li... wrote: >>> >>> > >>> > >>> > Hi Everyone, >>> > >>> > I am new to the list and running away from Proxmox due to it's really >>> messy structure. I have seem some screen shots of OpenNode and I am liking >>> it already. I hope it does work for me. I am mostly looking to install >>> Asterisk/CentOS on containers. >>> > >>> > I have installed the 1.0 stable version from the .iso and I see that it >>> has not picked up an IP from my DHCP router. I do have access to the system >>> but the utility window comes up right away and when I go into Management >>> console it seems like a limited console which doesn't even have "ifconfig". >>> > >>> > 1- How can I make sure both NIC ports are up and getting IPs? - I saw >>> them starting successfully during boot process. >>> > 2- How can I get to the Web UI to launch instances? or is that in the >>> beta version? If so, I am interested to upgrade. What is the procedure? >>> Since, I don't TRUE access to the root I can't even use the Yum repository. >>> > >>> > Thanks >>> > >>> > >>> ------------------------------------------------------------------------------ >>> > The Next 800 Companies to Lead America's Growth: New Video Whitepaper >>> > David G. Thomson, author of the best-selling book "Blueprint to a >>> > Billion" shares his insights and actions to help propel your >>> > business during the next growth cycle. Listen Now! >>> > >>> http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ >>> > OpenNode-users mailing list >>> > Ope...@li... >>> > https://lists.sourceforge.net/lists/listinfo/opennode-users >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> The Next 800 Companies to Lead America's Growth: New Video Whitepaper >>> David G. Thomson, author of the best-selling book "Blueprint to a >>> Billion" shares his insights and actions to help propel your >>> business during the next growth cycle. Listen Now! >>> http://p.sf.net/sfu/SAP-dev2dev >>> _______________________________________________ >>> OpenNode-users mailing list >>> Ope...@li... >>> https://lists.sourceforge.net/lists/listinfo/opennode-users >>> >> >> >> ------------------------------------------------------------------------------ >> The Next 800 Companies to Lead America's Growth: New Video Whitepaper >> David G. Thomson, author of the best-selling book "Blueprint to a >> Billion" shares his insights and actions to help propel your >> business during the next growth cycle. Listen Now! >> >> http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ >> OpenNode-users mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opennode-users >> >> >> >> >> ------------------------------------------------------------------------------ >> The Next 800 Companies to Lead America's Growth: New Video Whitepaper >> David G. Thomson, author of the best-selling book "Blueprint to a >> Billion" shares his insights and actions to help propel your >> business during the next growth cycle. Listen Now! >> http://p.sf.net/sfu/SAP-dev2dev >> _______________________________________________ >> OpenNode-users mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opennode-users >> >> > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > > http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > > |
From: <ope...@li...> - 2010-11-07 10:11:34
|
This opennode CLI PATH problem should be now corrected in new 1.0 and 1.1 opennode rpms - just do 'yum upgrade opennode' I think we will put up dedicated support forum soon - althou opennode sourceforge page already has one that nobody uses :-) Cheers, -- ---------------------------------------------- Andres Toomsalu, an...@ac... On 07.11.2010, at 1:18, ope...@li... wrote: > Thanks. I would really like to contribute if there is a Wiki or a support forum. These little things can really make life easier for everyone if documented. > > Thanks for the input. > > > On Sat, Nov 6, 2010 at 6:35 PM, <ope...@li...> wrote: > When doing yum upgrade opennode cli utility might be removed from PATH environment variable - we will fix this in next 1.1 beta. > You can still run opennode CLi utility by executing on console: > /opt/opennode/bin/opennode > > > Cheers, > -- > ---------------------------------------------- > Andres Toomsalu, an...@ac... > > > > On 07.11.2010, at 0:07, ope...@li... wrote: > >> Thanks for the quick and detailed response. So, the beta version 1.1 is not the one with Web UI then I am assuming. >> >> I got into the regular console using FUNC. I did the beta upgrade and restarted the machine. Now, the prompt for login reads virtN and the management utility is gone. I guess I should go back to the stable version. >> >> I am really looking forward to the Web UI as without it, it's the graphs and stats are very useful. >> >> Regards, >> Bruce >> >> On Sat, Nov 6, 2010 at 5:59 PM, <ope...@li...> wrote: >> Hello, >> >> I hope the following answers your questions. >> >> >> If you choose Exit in the OpenNode Management Utility you are returned to the regular terminal where you can do all the common linux management. >> >> The console that opens under the Management button is the virsh management console for managing virtual machines over the libvirt API. The coming OpenNode 1.1 version supports virsh console shortcut buttons for both OpenVZ and KVM. >> >> Web UI will be hopefully released in the coming weeks when last tweaks are carried out. Then you will have and option in the OpenNode Management Utility to download, install and configure the Web UI. And also we will provide all the necessary guidelines on our dedicated OpenNode webpage. >> >> >> Best regards, >> Danel >> >> On 06.11.2010, at 23:46, ope...@li... wrote: >> >> > >> > >> > Hi Everyone, >> > >> > I am new to the list and running away from Proxmox due to it's really messy structure. I have seem some screen shots of OpenNode and I am liking it already. I hope it does work for me. I am mostly looking to install Asterisk/CentOS on containers. >> > >> > I have installed the 1.0 stable version from the .iso and I see that it has not picked up an IP from my DHCP router. I do have access to the system but the utility window comes up right away and when I go into Management console it seems like a limited console which doesn't even have "ifconfig". >> > >> > 1- How can I make sure both NIC ports are up and getting IPs? - I saw them starting successfully during boot process. >> > 2- How can I get to the Web UI to launch instances? or is that in the beta version? If so, I am interested to upgrade. What is the procedure? Since, I don't TRUE access to the root I can't even use the Yum repository. >> > >> > Thanks >> > >> > ------------------------------------------------------------------------------ >> > The Next 800 Companies to Lead America's Growth: New Video Whitepaper >> > David G. Thomson, author of the best-selling book "Blueprint to a >> > Billion" shares his insights and actions to help propel your >> > business during the next growth cycle. Listen Now! >> > http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ >> > OpenNode-users mailing list >> > Ope...@li... >> > https://lists.sourceforge.net/lists/listinfo/opennode-users >> >> >> ------------------------------------------------------------------------------ >> The Next 800 Companies to Lead America's Growth: New Video Whitepaper >> David G. Thomson, author of the best-selling book "Blueprint to a >> Billion" shares his insights and actions to help propel your >> business during the next growth cycle. Listen Now! >> http://p.sf.net/sfu/SAP-dev2dev >> _______________________________________________ >> OpenNode-users mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opennode-users >> >> ------------------------------------------------------------------------------ >> The Next 800 Companies to Lead America's Growth: New Video Whitepaper >> David G. Thomson, author of the best-selling book "Blueprint to a >> Billion" shares his insights and actions to help propel your >> business during the next growth cycle. Listen Now! >> http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ >> OpenNode-users mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opennode-users > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users |
From: <ope...@li...> - 2010-11-06 23:18:51
|
Thanks. I would really like to contribute if there is a Wiki or a support forum. These little things can really make life easier for everyone if documented. Thanks for the input. On Sat, Nov 6, 2010 at 6:35 PM, <ope...@li...>wrote: > When doing yum upgrade opennode cli utility might be removed from PATH > environment variable - we will fix this in next 1.1 beta. > You can still run opennode CLi utility by executing on console: > /opt/opennode/bin/opennode > > > Cheers, > -- > ---------------------------------------------- > Andres Toomsalu, an...@ac... > > > > On 07.11.2010, at 0:07, ope...@li... wrote: > > Thanks for the quick and detailed response. So, the beta version 1.1 is not > the one with Web UI then I am assuming. > > I got into the regular console using FUNC. I did the beta upgrade and > restarted the machine. Now, the prompt for login reads virtN and > the management utility is gone. I guess I should go back to the stable > version. > > I am really looking forward to the Web UI as without it, it's the graphs > and stats are very useful. > > Regards, > Bruce > > On Sat, Nov 6, 2010 at 5:59 PM, <ope...@li...>wrote: > >> Hello, >> >> I hope the following answers your questions. >> >> >> If you choose Exit in the OpenNode Management Utility you are returned to >> the regular terminal where you can do all the common linux management. >> >> The console that opens under the Management button is the virsh management >> console for managing virtual machines over the libvirt API. The coming >> OpenNode 1.1 version supports virsh console shortcut buttons for both OpenVZ >> and KVM. >> >> Web UI will be hopefully released in the coming weeks when last tweaks are >> carried out. Then you will have and option in the OpenNode Management >> Utility to download, install and configure the Web UI. And also we will >> provide all the necessary guidelines on our dedicated OpenNode webpage. >> >> >> Best regards, >> Danel >> >> On 06.11.2010, at 23:46, ope...@li... wrote: >> >> > >> > >> > Hi Everyone, >> > >> > I am new to the list and running away from Proxmox due to it's really >> messy structure. I have seem some screen shots of OpenNode and I am liking >> it already. I hope it does work for me. I am mostly looking to install >> Asterisk/CentOS on containers. >> > >> > I have installed the 1.0 stable version from the .iso and I see that it >> has not picked up an IP from my DHCP router. I do have access to the system >> but the utility window comes up right away and when I go into Management >> console it seems like a limited console which doesn't even have "ifconfig". >> > >> > 1- How can I make sure both NIC ports are up and getting IPs? - I saw >> them starting successfully during boot process. >> > 2- How can I get to the Web UI to launch instances? or is that in the >> beta version? If so, I am interested to upgrade. What is the procedure? >> Since, I don't TRUE access to the root I can't even use the Yum repository. >> > >> > Thanks >> > >> > >> ------------------------------------------------------------------------------ >> > The Next 800 Companies to Lead America's Growth: New Video Whitepaper >> > David G. Thomson, author of the best-selling book "Blueprint to a >> > Billion" shares his insights and actions to help propel your >> > business during the next growth cycle. Listen Now! >> > >> http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ >> > OpenNode-users mailing list >> > Ope...@li... >> > https://lists.sourceforge.net/lists/listinfo/opennode-users >> >> >> >> ------------------------------------------------------------------------------ >> The Next 800 Companies to Lead America's Growth: New Video Whitepaper >> David G. Thomson, author of the best-selling book "Blueprint to a >> Billion" shares his insights and actions to help propel your >> business during the next growth cycle. Listen Now! >> http://p.sf.net/sfu/SAP-dev2dev >> _______________________________________________ >> OpenNode-users mailing list >> Ope...@li... >> https://lists.sourceforge.net/lists/listinfo/opennode-users >> > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > > http://p.sf.net/sfu/SAP-dev2dev_______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > > > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > OpenNode-users mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/opennode-users > > |