<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hello,<br>
<br>
taken from <a
href="https://fedorahosted.org/spacewalk/wiki/HowToInstallProxy"><a class="moz-txt-link-freetext" href="https://fedorahosted.org/spacewalk/wiki/HowToInstallProxy">https://fedorahosted.org/spacewalk/wiki/HowToInstallProxy</a></a><br>
<ul>
<li>Outbound open ports 80, 443, 4545 (only if you want to enable
monitoring) and 5269
</li>
<li>Inbound open ports 80, 443 and 5222
</li>
</ul>
Best regards,<br>
Tomas Kasparek<br>
<br>
<div class="moz-cite-prefix">On 06/15/2016 04:52 AM, Sam Sen wrote:<br>
</div>
<blockquote
cite="mid:0737E45B-2EB3-4A1F-9B50-3E08B717FC23@ariasystems.com"
type="cite">
<pre wrap="">I’m interested in moving our master Spacewalk server to AWS. In each DC, I want to have a proxy server that will handle registration for its respective hosts. In terms of the proxy server, we allow all outgoing connection but we do restrict incoming connections. Do I need to allow certain ports for the proxy to communicate with the Spacewalk server in AWS?
As a test, I blocked all traffic from my Spacewalk server in my local DC to a local proxy server. I ran “yum repolist” from a host that is registered to the proxy server. The command hung. Looking at tcpdump, I noticed the server was attempting to communicate with the proxy server over https. Once i removed the iptables rule, I was able to run “yum repolist."
_______________________________________________
Spacewalk-list mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Spacewalk-list@redhat.com">Spacewalk-list@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/spacewalk-list">https://www.redhat.com/mailman/listinfo/spacewalk-list</a></pre>
</blockquote>
<br>
</body>
</html>