sara fink wrote:
I would say, give them with כפית בפה what to do. Put a capture filter
with source && dest, run ping and wireshark. Either they are dumb or
don't want to do anything.
Or, and that is even more likely, they are talking about areas where
machines running standard operating systems are scarce, if not
non-existing. Most of the internet infrastructure is running operating
systems that do not have a port of wireshark, and in fact has no way of
loading new programs at all save by upgrading the entire firmware (which
requires a reboot, which requires downtime). When such is the case, I
think you can see why giving them a wireshark script and treating them
as if they are dumb is not the way to get results. They will not produce
a minute and a half downtime for thousands of customers merely because
you complain, and frankly, neither would I.
On the other hand, telling them "this router is responsible for the
packet loss" is helpful, because then they can use whatever procedure
they have in place (and they best make #@)[EMAIL PROTECTED] sure they do have such a
procedure) for finding up why that is the case and fixing it.
Shachar
================================================================To unsubscribe,
send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
