Hi,
now I tried with two VMs on the same host, but I can ping from VM to VM
... This looks like the Hook doesn't work.
I also have a talk to some IPTABLE experts they think that this isn't
working because the ICMP drop is based on Network Layer 3 and IPTABLES
is working on Layer 2...
Hi,
ICMP is working at layer 3, and is one of the IP associated protocols. So
IP-table, is the right filtering technology, ebtables is mainly for the link
layer.
Could you confirm that there is no other program setting fw rules? Also
could you check a ping from other host (a vm in other host or
Hi Christoph,
regarding the firewall hook, I've reviewed the rules and simulated your
scenario and it's the expected behaviour. The ping should work from the
worker node running the vm to the vm, but it won't from other vms, which is
the purpose of the filter. Could you please start another VM
Hi Carlos,
this doesn't work for me... I uncomment this options and restart the one
daemon.
Then I create a virtual Machine with following Template:
https://pastee.org/j6f3d
After commenting out Default requiretty in /etc/sudoers
creation and inserting IPTABLES rule works but have no
I send the Email to fast... some more information...
I run the novnc.sh skript an this also works fine!
I tested Firefox 5.0.1, 4.x.x, 3.6.18
And Chrome 12.xxx
noVNC directory is /srv/cloud/one/share/noVNC and read / writeable from
all hosts.
VM is running no on Master... It's on another
Hi @all,
I got the following error on Starting sunstone-server with
OpenNebula 3.0 Beta1.
http://pastebin.com/SdBJZSc5
My System is a 64-Bit Scientific Linux 6.0
Selinux disabled
iptables disabled
One networkinterface as bridge
Following Gems are installed:
daemons (1.1.4)
eventmachine
Am 27.07.2011 11:14, schrieb Héctor Sanjuán:
Hi Christoph,
it seems the ruby gem 'sequel' is not present in your system. This gem
is needed by the monitoring system (requirements in [1], also seems you
are missing sqlite3), which is used by Sunstone (requirements in [2]).
You can install the
Hi Christoph,
We are aware of the top command bug, see [1] if you are interested in the
ticket.
As for the iptables configuration, we are still improving the documentation
and some requirements and configurations are not as detailed as they should.
Some of the networking features have to be
