jcagle Posted April 9, 2015 Report Share Posted April 9, 2015 Have you guys ever thought about using a conventional server-client model? The model that you guys use is backwards. By starting a service (client) on a port the product opens up a vector of attack. It also requires the server to know where all the clients are, which can change IPs at anytime when you have a DHCP environment. A traditional client uses ephemeral ports on the client to communicate to standard port on the server. The least your team could do would be to make sure the "client" relays information about its current IP address to the server. This is not hard to do with broadcast or multicast on a network. It is when you get on different networks that this becomes troublesome. Also, can you guys build some *nix CLI tools that we can use that would help us find clients, monitor server/client metrics. That would really help me. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.