Hmm, not sure where part of this thread has disappeared to but in answer to your last question about using public addressing meaning it is on the internet side -
I would assume by giving it a routeable IP it is now ON the Internet side
No, not at all. Whether it is on the internet side or not depends on your network topology and not the IP addressing you use. So if you wanted you could address your entire LAN with public addressing and connect it to the internet with a firewall/router. It would still be your LAN and not WAN.
However, couple of things to note -
1) if you use public addressing internally on your LAN and it is not yours ie. you haven't been assigned it then you need to ensure it does not "leak" out onto the internet ie. you should not allow traffic with those source IPs onto the internet because the return traffic will actually go to the real owner of the public IPs.
2) if you do own the public addressing then it will be routable from the internet so you need to make sure you only allow access to what you want with a firewall preferably. That is one of the advantages of using private addressing on your LAN ie. it is not reachable from the internet.
Generally speaking you tend not to use public addressing internally. What you tend to do is use private addressing on your internal/DMZ devices and then if they need to be accessed from the internet you NAT the private IPs to public IPs which can be done on a router/firewall.
But as i say, there is nothing to stop you using public addressing on our LAN.
Jon
