[OT] Red Code Cisco 675 madness

Aaron aaron at darklands.org
Sun Aug 5 17:10:45 PDT 2001


Try assigning a port other than 80 to the web service (even though
it's disabled).

Aaron

On 01.08.05 at 19:04, Dan Sanderson wrote:

#
# Another off-topic Cisco 675 question for everyone.  If you don't like
# Cisco questions, rest assured that an answer to this one will make me very
# happy.
#
# As most Cisco 675 owners know by now, the "Red Code" ("Code Red"?) virus
# has a payload that attacks Cisco 675's using an old DoS exploit, crashing
# the router and necessitating power cycling to restore service.  The
# prevelance of the virus causes this to happen every couple of hours now,
# and it's driving me insane.
#
# Qwest claims it only affects routers set up to have web-based
# configuration enabled, and shutting off this feature fixes the problem.
# This isn't true; I've "set web disable" a dozen times now, writing and
# rebooting as per instructions.  "show web" properly lists the feature as
# disabled.  Other security web sites claim that upgrading the firmware
# includes patches that will solve this.  I believe I properly followed
# instructions to upgrade to v2.4.1, and "show version" properly lists the
# new version number.  However, I'm still having this problem.
#
# I'd bet money that Qwest won't be able to help me with this, and I'm not
# waiting the 113 minutes on hold to be told everything I already
# know.  However, this has got to be a very widespread problem, so I'm
# hoping someone else has suggestions.  Has anyone had success in fixing
# this problem?
#
# If it comes down to it, is it possible to get another brand of external
# DSL modem/router to use with Qwest.net?  Anyone have any to
# recommend?  What are the disadvantages to doing this, if it's possible?
#
# Many thanks for any assistance you can provide.  I'd suggest taking this
# discussion off the list, but I'm betting I'm not the only one here having
# problems.  :)
#
# -- Dan
#
#
#
#



More information about the Linux mailing list