Yes, that's exactly what I did. ebtables -F on the instance's inbound
chain. It was the 'DefaultSharedNetworkOffering'. I assumed there were
at least ebtables rules to keep the VM from using IP addresses it
didn't own, but this was like I had security groups turned on, without
the ability to edit t
If ebtables -F restores vm service(s)... it sounds like a bug.
On Wed, Mar 13, 2013 at 8:42 PM, Marcus Sorensen wrote:
> Quick question, I deployed a basic zone today on 4.1 for testing, and
> I chose the default network provider WITHOUT security groups. The
> result was that all of the instance
Quick question, I deployed a basic zone today on 4.1 for testing, and
I chose the default network provider WITHOUT security groups. The
result was that all of the instances deployed could not host services.
They could get out, but nothing could reach their IPs. I ran an
'ebtables -t nat -L' and saw
