|
True, each packet can take a different route. The point was, it's not just your ISP and yourself that you need to worry about, there's a whole list of computers belonging to different people/agencies. The traceroute was just to give you an idea of what I'm talking about. On Wed, 4 Dec 2002, Hall, Philip wrote: > > And you're right, sort of, too... > > > Do a traceroute from the remote computer to the AS/400. Assuming that > > the ISPs firewalls allow traceroutes, each line of the output will be > > one gateway that the packets travel through. > > My understanding is that it's even worse than what tracert will show > you. As I understand the packet delivery mechanism, each separate packet > in a transmission can take different routes to the same target, and > although tracert is pretty accurate, as gateways come on & offline (or > get busy, or whatever) you can never be 100%[*] sure where your packets > have been or what's happened to them en route. > > --phil > > [*] You can, of course, code something (i.e. implement the guts of > tracert on every packet you send/recv) that will help determine the > hosts that the packets passed through.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.