hi ya clive
On Fri, 7 May 2004, Clive Menzies wrote:
> Tracing the path to www.google.com (216.239.59.99) on TCP port 80 (www),
> 30 hops max
> 1 * * *
> 2 * * *
> 3 * * *
> 4 * * *
> 5 * * *
> 6 * * *
> 7 * * *
> 8 * * *
> 9 * * *
> 10 * * *
> 11 * * *
> 12 216.239.59.9
Clive Menzies wrote:
On (06/05/04 18:17), Alvin Oga wrote:
you're probably trying to go thru a slow firewall or heavily loaded
network
Try tcptraceroute instead.
Regards,
David.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTEC
On Thu, May 06, 2004 at 06:17:35PM -0700, Alvin Oga wrote:
> you're probably trying to go thru a slow firewall or heavily loaded
> network
where simultaneous different browsers work?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTE
On (06/05/04 18:17), Alvin Oga wrote:
> hi ya
>
> On Fri, 7 May 2004, Clive Menzies wrote:
>
> > Nope, sid still gives "Bad Request".
> >
> > However, debian.org works fine .. curious because
> > http://www.google.com definitely won't work on my sid box. One of
> > life's little myst
On Sat, Jan 04, 2003 at 02:49:20AM -0600, John Hansen wrote:
> This is a repost. Please forgive me. I do not subscribe to this e-mail
> list. Please e-mail me back with comments. Thank you so much. It's a
woody
The reason you probably didn't get many responses the first time is
that the open sour
On Friday 20 September 2002 13:46, Andy Saxena wrote:
> On Thu, Sep 19, 2002 at 08:03:56PM +0100, john gennard wrote:
> | I still have problems trying to configure a home network.
> | Thinking traceroute might shed some light on this, I ran the
> | program and got the following error messages:-
>
On Thu, Sep 19, 2002 at 08:03:56PM +0100, john gennard wrote:
| I still have problems trying to configure a home network. Thinking
| traceroute might shed some light on this, I ran the program and got
| the following error messages:-
|
| a. From box 4 to 5 where ping works but not telnet
|
| t
Bud Rogers <[EMAIL PROTECTED]> wrote:
> I started getting these errors yesterday. I can't figure out where
> they're coming from. System is mostly woody with a few packages from
> unstable. Any hints would be most appreciated.
> [EMAIL PROTECTED]:~$ traceroute www.debian.org
> traceroute: War
On Sun, Oct 01, 2000 at 04:04:36PM -0500, William Jensen wrote:
> An update to myself...in case others are having this problem:
>
> I added the following rule to my script:
>
> $IPT -A INPUT -p icmp --icmp-type 0 -j ACCEPT
>
> My understanding is now the box will accpet 'echo replies' that I wou
On Sun, 1 Oct 2000, William Jensen wrote:
> Another update to myself and others that may want this information:
>
> This update concerns traceroute. If I added the following rules I can now
> traceroute to anywhere, but traceroutes to me fail:
>
> $IPT -A INPUT -p icmp --icmp-type time-excee
Another update to myself and others that may want this information:
This update concerns traceroute. If I added the following rules I can now
traceroute to anywhere, but traceroutes to me fail:
$IPT -A INPUT -p icmp --icmp-type time-exceeded -j ACCEPT
$IPT -A INPUT -p icmp --icmp-type port-unrea
An update to myself...in case others are having this problem:
I added the following rule to my script:
$IPT -A INPUT -p icmp --icmp-type 0 -j ACCEPT
My understanding is now the box will accpet 'echo replies' that I would generate
by 'ping debian.org'. I then went to another pc on the net and tr
On Wed, 22 Mar 2000, Pollywog wrote:
> Is it just me or does traceroute need to be suid root?
Traceroute needs to be setuid so it can write IP packets directly rather
than using the socket interface. Without that ability, it could not set
the time-to-live on the packet and thus wouldn't work.
There were problems with a version of the netstd package (3.07-8 I think) which
was
in potato a few days ago. You probably got this version when you upgraded. Try
updating to the newest (3.07-9) version, it fixed this problem on mine.
Chris Schleifer
Phillip Deackes wrote:
> Today I tried to us
[EMAIL PROTECTED] (Miquel van Smoorenburg) wrote:
>
> - Your traceroute binary is setuid, but not to root, or
> - there is some firewall rule blocking ICMP packets installed
Thanks, Mike. I took a look in /usr/sbin and found a few files which are
set as owned by gsmh and as group 1000 - me in oth
In article <[EMAIL PROTECTED]>,
Phillip Deackes <[EMAIL PROTECTED]> wrote:
>Today I tried to use traceroute and got the message:
>
>traceroute: icmp socket: Operation not permitted
>
>This has happened only recently. I tried running the command as root,
>but got the same message.
- Your tracerout
Maybe netstd?
bash-2.01$ dpkg -S tracer*
scotty: /usr/doc/examples/scotty/traceroute.1
netstd: /usr/doc/netstd/examples/traceroute/mean.awk
scotty: /usr/doc/examples/scotty/traceroute
netstd: /usr/sbin/traceroute
netstd: /usr/doc/netstd/examples/traceroute/README.awk
netstd: /usr/doc/netstd/exampl
When Paul Miller wrote, I replied:
When I run "dpkg -S traceroute" is see things from the netstd package.
>
> What package contains the traceroute program (not mtr, something similar
> to microsoft's tracert.exe program).
>
> ---
> Paul Miller <[EMAIL PROTECTED]>, finger for public PGP key
>
>
> traceroute: IP_HDRINCL:Protocol not available
Probably you're still running the 1.2.13 kernel, but the new
traceroute uses some features only in 1.3... at least that's why I see
that message.
19 matches
Mail list logo
