133 reputation
5
bio website
location
age
visits member for 1 year, 7 months
seen 2 days ago

Oct
8
awarded  Popular Question
Jul
4
awarded  Tumbleweed
Dec
7
awarded  Scholar
Dec
7
comment “No route to host” with ssl but not with telnet
the problem was indeed the IPv4 routing. There the firewall on the VM-Host blocked the communication between VMs on different VM-Hosts. I found this out using traceroute.
Dec
7
accepted “No route to host” with ssl but not with telnet
Nov
30
revised “No route to host” with ssl but not with telnet
added 593 characters in body
Nov
30
awarded  Editor
Nov
30
comment “No route to host” with ssl but not with telnet
updated the description with details
Nov
30
revised “No route to host” with ssl but not with telnet
added 399 characters in body
Nov
30
comment “No route to host” with ssl but not with telnet
that does not help either: openssl s_client -connect puppet.master.ip.address:8140 connect: No route to host connect:errno=113
Nov
30
awarded  Student
Nov
30
asked “No route to host” with ssl but not with telnet