Mailinglist Archive: opensuse-security (465 mails)

< Previous Next >
Re: [suse-security] cable modem router and traceroute
  • From: "Bill Eastman" <beastman@xxxxxxxxxxxxx>
  • Date: Fri, 14 Dec 2001 07:40:21 -0600
  • Message-id: <020a01c184a4$e25663e0$0801a8c0@xxxxxxxxxxxx>
It works with the cable modem, but not if I put the router in. If I take
the router out and replace it with floppyfw, then it works. Anyway, as you
told me, /usr/sbin/mtr which is included wih SuSE 7.3 Pro provides more
information and it uses ICMP and works wih the router.

----- Original Message -----
From: "Roman Drahtmueller" <draht@xxxxxxx>
To: "Bill Eastman" <beastman@xxxxxxxxxxxxx>
Cc: <suse-security@xxxxxxx>
Sent: Friday, December 14, 2001 6:53 AM
Subject: Re: [suse-security] cable modem router and traceroute


>
> The traceroute that ships with SuSE will not work with my cable modem
> router. I contacted the manufacture, and learned that SuSE is using a
> different traceroute than Red Hat and Mandrake. He sent me a link to ftp
a
> traceroute that will work.
> /usr/sbin/mtr does work, as does ping.
>
> The traceroute that Red Had and Mandrake are distributing includes a -I
> option so it can be forced to use ICMP. The traceroute that comes with
SuSE
> does not have a -I option and uses only UDP.
>
> What is the difference between the two traceroute programs? How is one
more
> secure than the other?

Our traceroute had a format string error a while ago, the other's
traceroutes had different problems. We are glad that we ship the one we
have and not the other package. The fact that ICMP pings are not possible
is unfortunate, but (as I wrote to you privately already) the problem here
is not the traceroute but the cable modem.

>
> Bill

Roman.
--
- -
| Roman Drahtm├╝ller <draht@xxxxxxx> // "You don't need eyes to see, |
SuSE GmbH - Security Phone: // you need vision!"
| N├╝rnberg, Germany +49-911-740530 // Maxi Jazz, Faithless |
- -


--
To unsubscribe, e-mail: suse-security-unsubscribe@xxxxxxxx
For additional commands, e-mail: suse-security-help@xxxxxxxx



< Previous Next >
References