Agree, that 3 symptoms describe 3 level of 7-layer OSI model.
no routing to host - Layer 3 (IP layer) connection refused - Layer 4 (transport - TCP/UDP) connection reset - Layer 5 (session layer) or higher > 1. Sounds like a routing issue. Packet flow cant reach the destination. > 2. Sounds like a firewall/no service issue > > -- > æ > > > > > > On 4/25/12 3:05 PM, "Frank Zhang" <frank.zh...@citrix.com> wrote: > >> This is not only for CloudStack, but they are common issues when you are >> playing CloudStack regarding network. >> I often suffer these errors, there are some tips from my practice: >> >> >> 1. "No route to host" >> Most likely iptables rule prevents the port from accessing. First check >> iptables rule in your VM, then check SecurityGroup rules in CloudStack. >> Finally check the rules in host where the VM is running(in this case, >> please file a bug for SecurityGroup) >> >> >> 2. "Connection refused" >> >> The destination port is reachable, however, there is no application >> listens on that port >> >> >> >> 3. "Connection reset" >> >> The established connection has lost. >> >> Please correct me if you see anything wrong. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > cloudstack-users mailing list > cloudstack-us...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/cloudstack-users > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.
