My institution’s firewall is blocking my remote connection to the 34.56.65.180 server to pull PUD and TUD data from the recreation and tourism model. My department IT asked if anyone would know if the return traffic will be on a specific port range. The numbers are being scattered back to my server so it’s hard for the IT to write a new rule to bypass the firewall.
What do you expect to happen?
If I can pinpoint a return port range, I can bypass the firewall stopping the connection currently.
What have you tried so far?
It is always 54322 on their end, but it has been scattered around 529** on our end. If there’s a limit to the scatter, we can write a rule around that.
Hi @Kylork , that’s an interesting question. This model uses the Python library Pyro5 to communicate between client and server. Pyro5 appears to use the standard library socket to create a client-side socket and bind it to an unused port. I have not been able to figure out a way to configure the port on the client. If there was a way, it would require setting up your own socket and using the Pyro5 api directly to connect to our server.