监控互联网连接稳定性的软件

Question

由于世界上最好的 ISP之一提供了出色的互联网连接服务，我所在地区的互联网连接非常非常不稳定。我有时可以连接，但大多数时候连接会断开（带有错误消息），几分钟后，它会恢复。如果我直接ping域名（即在cmd命令中），我会收到一条消息。unable to resolve hostping www.google.com -tcannot ping

由于连接的闪烁特性，很难向支持人员证明互联网连接不稳定。所以我正在考虑使用一个软件来记录连接情况，以便我可以呈现给技术人员并确保他们没有任何借口不解决我的问题。

有这样的软件吗？

编辑：当然，这样的软件不应该记录我的浏览习惯，并且必须能够在我不在线的情况下监控和记录互联网连接情况。

Answer 1

为了快速、短期监控，Ping Plotter 之类的工具可以为您提供连接图，其中不仅包括 ping 时间图，还包括显示没有连接时的红条。

对于更持久、长期的监控，像Cacti或Smoke Ping这样的专用工具是不二之选。

Answer 2

请原谅我有点跑题了，但几年前我感受到了你的痛苦，我开发了一个你可能会觉得有用的工作流程。

在调试连接问题时，我将其分为三个部分：

• 我与 ISP 的连接（在我和 ISP 的网关之间）
• ISP 的基础设施（您必须进行一些调查才能找到这一点，因为有些 ISP 不会公开他们的网络范围。查看 traceroute 的输出并针对从您的网关开始的每个 IP 执行“whois”。Up在某种程度上，它们将分配给您的 ISP，这是您 ISP 的内部基础设施）
• 互联网的其余部分

我最喜欢的调试网络问题的工具是mtr。至少有 Linux 和 Windows 版本。它的工作原理类似于 ping 和 traceroute 的组合 - 它就像一个交互式 traceroute。

由于 IP 数据包丢失，会发生多种连接问题。我将按相反的顺序详细说明它们：

• ISP 之外的问题。这不是您的 ISP 支持扭转愤怒客户的借口。他们应该与上游提供商合作并解决这个问题。此类问题并不经常发生，因为骨干网 ISP 的质量更好。如果某些链接出现故障并且流量临时重新路由到带宽较低的备份链接，则可能会发生这种情况。
• ISP 基础设施内部的问题。这是你可以更加严厉的情况。致电支持人员并告诉他们“您使用此 IP 的路由器（您将看到 mtr 中的哪一个，那里会出现数据包丢失）有问题。修复它们并告诉我您需要多长时间来修复它。” 有时他们会说十分钟或三十分钟，只是为了躲你的电话，因为大多数人打电话一次就放弃了。如果他们说 10 分钟后问题仍未解决，请在 10 分钟后再次致电。永远不要说“互联网不工作”或类似的话。确切地告诉他们问题是什么，如果你能弄清楚，这会让他们明白你知道技术部分，他们不会通过提供一些愚蠢的技术借口来让你闭嘴。
• 您和网关之间的问题。这些可能更难调试，因为涉及许多因素。它们的发生可能是因为您的网卡出现故障。但它们也可能发生，因为您通过旧电话线获得 ADSL 并且信号很差。这已经是你的 ISP 头疼的问题了，它应该取代你的电话线来达到标准。

Missing internet stresses people a lot, so never be rude when talking with support guys. Remember that they are just earning some money this way and generally they are not your ennemies :-) So be nice to them. But also always ask for their name and ID. It is important because this way you already know the name you shall complain about later, if the support guy provides inaccurate information or is just telling plain lies to you (yes, that happens too). If you feel that you are wasting your time, politely request to be hooked up with an upper-level sysadmin and talk to him.

Set up a locally hosted forum and spread the word among the clients of a certain ISP. If something gets bad, the forum will instantly fill up with complaints and logs which prove that the ISP indeed has issues and that your case is not a single one. Such an argument is very valuable if the situation evolves and you have to talk with a senior manager. They are very sensitive about such matters and this is one of the reasons why a lot of ISPs don't have their own tech support forums for customers, because every reported issue is bad PR for them :-)

As correctly pointed, monopolies, especially government-linked ones, are another pain. But this is a double edge sword. If the monopoly gains bad reputation against its clients as "crappy ISP", as soon as there will appear a second player on the market (and this will eventually happen, sooner or later) - a lot of clients will cancel their contracts. Not for switching to a better ISP, just for getting rid of a crappy one.

Regarding your ping problem: yes, it can be a DNS issue. Sometimes ISP startups (especially in developing countries) get a pair of DNS servers configured when launching their services. At some point the client base grows enough that the DNS servers can't handle the load anymore "just because sometimes it still works, so no need to fix anything". There are a couple of workarounds here that can help mitigate the problem:

• use alternate DNS servers: the ones from google or from opendns. Use them if you can, it is not always possible, because some ISPs go as far as blocking DNS requests to third-party DNS servers (guess what happens when their own DNS servers die for some reason)
• use a local DNS caching proxy. I've used pdnsd and it did the job very well for me