Is it possible to change FTP port for nodes?

[cornycopia]

I have a primary server setup on Subnet A, and am trying to setup a node on Subnet B on a different campus. Both are on Ubuntu 22.04.
Our IT dept has a hard block on port 21 communication between subnets. I’ve been able to confirm every other port FOG needs is open though.

I’m able to setup a storage node on subnet A alongside the primary FOG instance, but on any other subnet the node will not show up.
I see that the FTP port can be changed in the settings, but changing it doesn’t seem to affect the node issue. Is there a way to point the node to the new FTP port assignment?

Does anyone have any best known methods for getting around this issue?

My next step I’m looking at trying to set up an SSH tunnel between the primary FOG server and the node server.

[youzersef]

This post is deleted!

[Tom Elliott]

@cornycopia I could be wrong, but if I recall correctly, the “FTP” trigger isn’t from the client machine (persay) but rather from the fog server itself.

So NFS is the file mechanism that is used during the upload/deploy process.

The FTP part comes after an Upload completes to move it from the /images/dev/<mac_address> to /images/<image_name> on the FOG Server itself.

So effectively it’s doing a direct mapping. Now to be fair it is using the machines own IP address, instead of 127.0.0.1, so maybe that plays into it. Right now, that’s not something in the code.

[Tom Elliott]

@cornycopia After thinking about it, there’s a “general” port that’s used.

FOG Settings -> FOG_FTP_PORT

Granted this isn’t per server, but it is a choosable thing.