really so it would be that hard to do a c:/> Netstat -n -p tcp -b | more to get the server addresses and ports, than see your PUBLIC IP address that your traceRT puts out, (even with NAT overload, you can't hide that you're connecting to SWTOR, you only change ports with new connections, not IPs.) Than wait for your connection attempt to SWTOR. And just FYI fomr what I can tell SWTOR does not offer an encrypted service, maybe for login, but even that would not be a hard nut to crack if you have enough logins recorded. The only people really safe are the ones with security-key-gens. Your connection, your chat, it's all plain text, and anyone looking for your IP can see your connection to the server, they don't have to hijack a site in your building, just one of the routs on the way, it only takes 1 lazy admin and a brute force cracker. than from there you better hope the ASA. IPS/IDS are configured correctly and maybe toss in some ACL's to make it interesting, because jacking into your office/computer from that point is easier to do than it is to prevent.
It doesn't matter how many years IT you have, if someone wants to get into your system they will find a way, firewall, or millions $$ in security hardware. It takes 1 mess up, or sometimes you don't have to do anything wrong and you'll still be vulnerable.
Wow - throwing some technical terms makes your post all that more impressive?
I think I'll leave this thread now, I've said my piece.
The OP posted an apocalyptic idea that by revealing an internal IP address I'd somehow committed a major breach of security protocol.
I addressed this post by explaining that no, I hadn't. That the revelation of my own internal IP address, the internal IP address of my router and gateways was not going to compromise my/our network.
I am extremely confident in my own knowledge and that of my security team - to the point where I know my network is extremely safe.