Question

我将Secure Gateway的目标主机设置为主机名ssldemo，而不是IP地址。我使用'--net="host"'选项启动了SG Client以解析主机名。当然，主机操作系统可以解析主机名。请参阅 ping 主机名的日志。但是，当执行trx时，SG客户端无法解析主机名并出现"ENOTFOUND"错误。我尝试添加'--net="host" --add-host "ssldemo:192.168.56.1"'个选项，但是我遇到了同样的错误。

您能告诉我如何解决"ENOTFOUND"错误吗？

linux-h4fn:~ #  docker run -it ibmcom/secure-gateway-client *GATEWAY_ID* --net="host"
IBM Bluemix Secure Gateway Client version 1.1.0
press enter for the command line
[2015-07-06 10:46:50.383] [INFO] The Secure Gateway tunnel is connected
[2015-07-06 10:46:56.824] [INFO] Connection #78 is being established to ssldemo:443
[2015-07-06 10:46:56.845] [INFO] Connection #78 established to ssldemo:443
[2015-07-06 10:46:56.950] [ERROR] Connection #78 to destination ssldemo:443 had error: ENOTFOUND
[2015-07-06 10:46:56.972] [INFO] Connection #78 to ssldemo:443 was closed
[2015-07-06 10:46:58.080] [INFO] Connection #79 is being established to ssldemo:443
[2015-07-06 10:46:58.100] [INFO] Connection #79 established to ssldemo:443
[2015-07-06 10:46:58.296] [ERROR] Connection #79 to destination ssldemo:443 had error: ENOTFOUND

linux-h4fn:~ # ping ssldemo
PING ssldemo (192.168.56.1) 56(84) bytes of data.
64 bytes from ssldemo (192.168.56.1): icmp_seq=1 ttl=128 time=5.01 ms
64 bytes from ssldemo (192.168.56.1): icmp_seq=2 ttl=128 time=11.4 ms

Answer 1

如果在重新启动之前正在运行的Secure Gateway连接时遇到ENOTFOUND错误，则可能是Docker服务本身存在问题，因此可以通过重新启动系统上的Docker服务来解决此问题。

如果SG客户端容器仍在运行，请将其删除：

sudo docker ps
sudo docker kill containerid

重启Docker：

sudo service docker restart

重新启动SG客户端容器：

sudo docker run -it ibmcom / secure-gateway-client clientid

不要更新您的访问控制列表：

acl allow 主机： port

Answer 2

安全网关服务无法识别DNS名称。您可以尝试使用IP地址而不是主机名吗？

如何解决SG客户端的ENOTFOUND错误

2 个答案: