Um, fucked up google translate anyone?
You clicked with the mouse fisical, that sounds, um...
About the packet traser, never herd of it, but maybe the reason it does nothing is because the site and or packets are encrypted, or there’s just no packets to get. Both are likely.

No, this should not be in the developer room. Cisco Packet Tracer is not a tool for software development; it is a router/switch/VLAN simulation tool written by Cisco for their CCNA/CCNP/CCIE courses. I've never gotten Cisco Packet Tracer to work at all; it uses QT and the way they use QT makes it rather difficult to use. I've found Cisco's VIRL (virtual internet routing lab) to be a much better alternative, though it can be kinda confusing to get used to.

@quanin, oh, it crashed a lot for me too. Never figured out why, though! VIRL is basically this full-on virtual server that allows you to set up virtual routers and switches in pretty much any configuration you like. I have no idea why Cisco doesn't recommend it in their courses; I've found that it can pretty much do most, if not all, of what packet tracer can do, plus more. I shutdown my instance though -- its $200.00 for the initial license, then I set up my instance on Packet, which was an additional $37.00 or so.

@Ethin: Hey neat. I hadn't even heard of Packet until I saw this. Crazy. Also, isn't VIRL essentially like its own OS? So how would that be accessible to a Blindy McBlinderson? I mean you either need to shove it in a VMware or blow away your current OS to install it, so that can potentially be problematic, no? Also there's a very good reason Cisco doesn't recommend this for actual, honest to god production labs or student environments. The thing's a beast just to run 15 nnodes, and with the specs on most students' laptops these days they'd hit the floor. I recall somewhere reading for best results, at least 16 GB RAM on a core i7. You're not getting that with your student loan money.

@Diego: Don't count on it.