I believe my question was already in the previous thread, so I started a new thread for follow-up questions.
Link to previous question:
>>You will not need to change anything on his equipment,
That's good to know. I want to keep it as simple as possible.
>>maybe available addresses in their DHCP scope (if you wanted to set up statically)
I guess it will be better to just ask what IP address they would want to assign to the devices?
>>as for on different subnets, that isnt ...
Actually, I once had a project for synchronized digital clock through out the factory. The device each had a LAN module and was assigned a static IP address. Since the clocks are put in different parts of the factory, some are connected to a different subnet. In the same setup, if I am going to use WLAN instead of LAN, what will I need to do? Is it enough to just add a WAP for each subnet/location?
>>By turning DHCP off you are allowing either their server or their router to "dish" out IP addresses.
I don't quite understand this. So will this happen when I turn the DHCP off on the router but ON on my device? And what problems will I face if I did forget to turn the DHCP off?
>>whether you assign static ips with MAC filtering or DHCP with MAC filtering you still get the same effect.
Hmm, so what exactly is the advantage of using DHCP/Static IP over the other and vice versa.
>>Port restriction is the way to go but dont be like every other person out there ...
I have done a little programming with TCP sockets and WCF, but afaik it can't do anything without an endpoint to receive the packets. How will it be possible to do anything from just one open port? I don't doubt that it is indeed possible for a good hacker, but I just want an idea on how it was done and how to prevent it. I don't want the addition of my device to be a possible cause of a breach to their network. Too much responsibility. :-)