Uyuni Documentation › Advanced Topics › Ports

A Ports

A.1 Uyuni Server
A.2 Uyuni Proxy Server
A.3 Uyuni Client

A.1 Uyuni Server #

Some ports are only relevant if you actually run the related service on the Uyuni server.

Ports to Open on UyuniServer #

67

Inbound / TCP/UDP / DHCP

Required when Uyuni is configured as a DHCP server for systems requesting IP addresses.

69

Inbound / TCP/UDP / TFTP

Used when Uyuni is configured as a PXE server and allows installation and re-installation of PXE-boot enabled systems.

80

Inbound / TCP / HTTP

Client and proxy server requests travel via HTTP or HTTPS.

80

Outbound / TCP / HTTP

Used to contact SUSE Customer Center/Novell Customer Center.

443

Inbound / TCP / HTTPS

All Web UI, client, and proxy server requests travel via HTTP or HTTPS.

443

Outbound / TCP / HTTPS

Uyuni uses this port to reach SUSE Customer Center (unless running in a disconnected mode with RMT or SMT-as described in Section 2.2, “Disconnected Setup with RMT or SMT (DMZ)”).

5222

Inbound / TCP / osad

When you wish to push actions to clients this port is required by the osad daemon running on your client systems.

5269

Inbound/Outbound / TCP / jabberd

Needed if you push actions to or via a SUSE Manager Proxy.

4505

Inbound / TCP / salt

Required by the Salt-master to accept communication requests via TCP from minions. The connection is initiated by the minion and remains open to allow the master to send commands. This port uses a publish/subscribe topology; the minion subscribes to notifications from the master.

4506

Inbound / TCP / salt

Required by the Salt-master to accept communication requests via TCP from minions. The connection is initiated by the minion and is open only when needed. Usually, minions will open this port when they have to report results to the master, such as when a command received on port 4505 has finished. This port uses a request/response topology; the minion sends requests to the master.

25151

TCP

For cobbler.

Internally Used Ports on Uyuni Server #

2828

Internal /

Satellite-search API, used by the RHN application in Tomcat and Taskomatic.

2829

Internal /

Taskomatic API, used by the RHN application in Tomcat.

6868

Internal

Auditlog-keeper to database.

6888

Internal

Auditlog-keeper API, used by the RHN application in Tomcat.

8005

Internal

Tomcat shutdown port.

8009

Internal

Tomcat to Apache HTTPD (AJP).

8080

Internal

Tomcat to Apache HTTPD (HTTP).

9080

Internal

Salt-API, used by the RHN application in Tomcat and Taskomatic.

32000

Internal / TCP

Port for a TCP connection to the Java Virtual Machine (JVM) that runs Taskomatic and the search (satellite-search).

Note: Ephemeral Ports

Anything from port 32768 on (more exactly, what you can see with cat /proc/sys/net/ipv4/ip_local_port_range) is an ephemeral port, typically used as the receiving end of a TCP connection. So if process A opens a TCP connection to process B (for example, port 22), then A chooses an arbitrary source TCP port to match with destination port 22.

This image is a graphical representation of the ports used in Uyuni:

Port 80 (http) is not used to serve the Web UI, and is closed in most installations. Port 80 is used temporarily for some bootstrap repositories and automated installations.

A.2 Uyuni Proxy Server #

Ports to Open on UyuniProxy Server #

22

Inbound /

Required when using ssh-push or ssh-push-tunnel contact methods. Check-in on clients connected to a Uyuni Proxy will be initiated on the Uyuni Server and “hop through” through to clients.

80

Outbound /

Used to reach Uyuni.

5222

Inbound / TCP

For push actions and connections issued by osad running on the client systems.

5269

Inbound/Outbound / TCP

For push actions with the server.

A.3 Uyuni Client #

Ports to Open on Uyuni Client #

22

Inbound / SSH

Required when using ssh-push or ssh-push-tunnel contact methods.

80

Outbound

To reach the Uyuni server or SUSE Manager Proxy server.

5222

Outbound / TCP

For push actions with the server or proxy server.

Print this page