email sent.
For the record, the only differences from the default config for d-link are (that I could locate):
the router is set up for the 192.168.2.XXX subnet, netmask 255.255.255.0
The brick is pre-configured for 192.168.2.2, and ports 444 and 80 are forwarded to it on the "virtual server" page for both UDP and TCP packets.
They have also renamed the wireless network to "PENTAIR8" with no security (why I moved it to my subnet, I have a hacker kid next door, and who knows what tricks he would pull on my pool. He has already noticed the new open wireless network and connected to it and sniffed around several times... We have a friendly relationship so when he asked I explained what it was and that it would go away very quickly.)
And last but not least they have enabled the PING response on the WAN side of the router.
Thats it as far as I could tell.
I have backed up the config file should anyone else need it, but it should also be available from pentair.
To make the brick work on my network, all I did was in the screenlogic connect initial screen, reconfigure the ip from static to dynamic and saved it, then moved it to my router. No port forwarding set up needed on my router for it to work from anywhere in the world.
Essentially from what traffic I can see on my network, the brick is constantly in contact with pentairs (actually their vendor) server to act as a proxy for contacting your home system. Pretty standard stuff. The brick does generate broadcast traffic on the network, but its not alot and not having any impact whatsoever on my internal network.
Leaving it on the pentair supplied router is entirely acceptable and would work fine for most consumers, just plug the internet supply cable from their router to the internal side of your home router and it just works. Good config as shipped, because it protects you security wise from any risks associated with having a vendors piece of equipment on your internal network (not completely, but you are assuming a level of trust plugging anything into your network).