- 1 Hyper-V 2012 R2: Pros and Cons of Generation 1 vs. Generation 2 VMs
- 2 Harnessing the Power of Hyper-V Network Virtual Switches
- 3 Working with SSH and Secure FTP Servers in Windows
- 4 Discover Windows 8's Hidden Server Features
- 5 Server Virtualization Customer Reviews: VMware, Hyper-V, XenServer and More
Enterprise Unix Roundup: Jabbering Openly Page 2
|Main||In Other News||Recent Updates||Tips of the Trade|
MIT announced that the version of the telnet client it ships with kerberos has buffer overflows that could allow a malicious user to run arbitrary code with the privileges of the telnet client user. There are updates for Fedora Core 3, Fedora Core 2, Ubuntu, and FreeBSD. According to the MIT advisory, any telnet client derived from the BSD telnet implementation may share this vulnerability.
Tips of the Trade
Network administrators have long relied on the traceroute program (tracert on Windows) for debugging network connection problems. Typical output looks something like, this:
$ traceroute serverwatch.com traceroute to serverwatch.com (22.214.171.124), 30 hops max, 40 byte packets 1 border1.secureip.net.au (126.96.36.199) 1.18 ms 0.722 ms 0.658 ms 2 188.8.131.52 (184.108.40.206) 2.913 ms 2.207 ms 2.449 ms 3 330.ge-5-0-0.GW5.SYD2.alter.net (220.127.116.11) 3.865 ms 3.894 ms 2.910 ms 4 0.so-4-3-0.XR2.SYD2.Alter.Net (18.104.22.168) 4.960 ms 3.622 ms 2.270 ms 5 so-6-0-0.TR2.SYD2.ALTER.NET (22.214.171.124) 1.947 ms 2.750 ms 3.674 ms ... 13 svl-core-03.inet.qwest.net (126.96.36.199) 214.925 ms 214.722 ms 216.181 ms 14 ewr-core-01.inet.qwest.net (188.8.131.52) 283.658 ms 282.766 ms 283.231 ms 15 ewr-cntr-01.inet.qwest.net (184.108.40.206) 282.792 ms 283.923 ms 283.764 ms 16 msfc-22.ewr.qwest.net (220.127.116.11) 286.986 ms 287.703 ms 426.549 ms 17 * 18.104.22.168 (22.214.171.124) 286.967 ms !X *
Which is fine for seasoned network admins, but what if you need to use traceroute output to demonstrate a problem to a not-so tech-savvy boss or co-worker? Or, perhaps you, yourself, prefer a visual representation. In that case try Xtraceroute. Xtraceroute displays both a visual and text representation of the route your packets travel over the planet. The graphical image can be rotated and resized. Simply run:
$ xtraceroute [hostname]
Xtraceroute looks for LOC DNS records and then top-level domain names. You may add static mappings, using the Database menu, to /usr/share/xtraceroute/site_hosts.cache and /usr/share/xtraceroute/site_networks.cache (on Debian it's /etc/site_hosts.cache and /etc/site_networks.cache) to speed up lookups of known hosts. See man xtraceroute to learn more Xtraceroute commands.