EC2实例没有响应内部平 [英] EC2 instances not responding to internal ping

查看:130
本文介绍了EC2实例没有响应内部平的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我这样做,推出几款亚马逊实例具有相同的安全组是默认之一,ICMP脚本,并允许所有的TCP / UDP连接...所以没有防火墙问题。 我运行一个Ubuntu 11.4 64位AMI工作的罚款。

I did a script that launch several amazon instances with the same security group which is the default one, with ICMP and all the TCP/UDP connection allowed... so no firewall problem. I am running an ubuntu 11.4 64 bits ami working fine.

通常在一堆机器我推出一些不以任何ping或telnet连接做出回应。他们可以ping其他的机器,但不能ping通。其他机器可以ping对方在两个方向上没有任何问题,但通常是一个或两个就是不给任何响应ping。有一个在我启动它们的方式没有什么区别,所以我不明白的地方这个错误来自...

Usually in the bunch of machine I launch some do not respond to any ping or telnet connection. They can ping other machines but cannot be pinged. The other machines can ping each other in two directions without any problem, but usually one or two just don't respond to any ping. There is no difference in the way I launch them, so I don't understand where this bug comes from...

如何避免这个问题,并从中恢复,无需重新启动EC2实例?

How to avoid this problem and recover from it without restarting the EC2 instance?

多谢招标developpers。:D

Thanks a lot tender developpers :D.

推荐答案

试试这个

  1. 请进入 AWS 帐户。
  2. 点击安全组。选择所需的安全组
  3. 点击内向标签上。
  1. Log into AWS account.
  2. Click on Security Groups. Choose the required security group.
  3. Click on the Inbound tab.

创建一个新的规则:

Custom ICMP rule
Type: Echo request
Source: 0.0.0.0/0
0.0.0.0 will allow everyone to ping your server. You can specify your own addresses if you want.

这篇关于EC2实例没有响应内部平的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆