From: Robert Penz <robert.penz@outertech.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB or CBQ ?
Date: Tue, 01 Oct 2002 13:11:14 +0000 [thread overview]
Message-ID: <marc-lartc-103347831101977@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103327810612944@msgid-missing>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Anyone else seen this one?
>
> ping -n {remote host}
> { 6 second delay }
> 64 bytes from 216.168.105.33: icmp_seq=0 ttl=255 time=6sec
> 64 bytes from 216.168.105.33: icmp_seq=1 ttl=255 time=5sec
> 64 bytes from 216.168.105.33: icmp_seq=2 ttl=255 time=4sec
> 64 bytes from 216.168.105.33: icmp_seq=3 ttl=255 time=3sec
> 64 bytes from 216.168.105.33: icmp_seq=4 ttl=255 time=2sec
> 64 bytes from 216.168.105.33: icmp_seq=5 ttl=255 time=1sec
> 64 bytes from 216.168.105.33: icmp_seq=6 ttl=255 time=242usec
> 64 bytes from 216.168.105.33: icmp_seq=7 ttl=255 time=250usec
> ...
suse linux? if so, reverse lookup doesn't work, for that ip.
- --
Regards,
Robert
- ----------------
Robert Penz
robert.penz AT outertech.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE9mZ7y8tTsQqJDUBMRAs+5AJ9lWrTDyCN8RA1MWwWXPazCoxkSrACgnrhC
xh2G6e1NzgmDzQlJI2qOfjs=
=ryCz
-----END PGP SIGNATURE-----
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-10-01 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 5:40 [LARTC] HTB or CBQ ? brt_informatics
2002-09-29 9:18 ` Stef Coene
2002-09-30 10:52 ` SERBAN Rares
2002-09-30 15:15 ` Stef Coene
2002-09-30 15:26 ` Michael T. Babcock
2002-09-30 15:37 ` Stef Coene
2002-10-01 12:56 ` Michael T. Babcock
2002-10-01 13:11 ` Robert Penz [this message]
2002-10-01 13:20 ` Michael T. Babcock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-103347831101977@msgid-missing \
--to=robert.penz@outertech.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.