paging Motorola - please evacuate your ninja bots from route-views.oregon-ix.net

Paging Motorola. Please leave some system resources for the rest of
us and LOG OFF when you're done. Thank you.

bye,Kai

sonet:~$ date
Mon Nov 10 13:56:46 EST 2003

sonet:~$ telnet route-views.oregon-ix.net
[....]
route-views.oregon-ix.net>who
    Line User Host(s) Idle Location
   2 vty 0 idle 1w3d gate01.mot.com
   3 vty 1 idle 1w3d gate02.mot.com
   4 vty 2 idle 1w3d 203.135.29.11
   5 vty 3 idle 1w2d www.sohoskyway.net
   6 vty 4 idle 1w3d mippet.ci.com.au
   7 vty 5 idle 1w2d a65-124-16-8.svc.towardex.com
   8 vty 6 idle 1w2d gate01.mot.com
   9 vty 7 idle 1w2d gate02.mot.com
  10 vty 8 idle 1w3d 216.140.58.174
  11 vty 9 idle 1w3d host1.tla.com
  12 vty 10 idle 1w3d gate01.mot.com
  13 vty 11 idle 1w2d gate02.mot.com
  14 vty 12 idle 1w3d gate01.mot.com
  15 vty 13 idle 1w2d gate01.mot.com
  16 vty 14 idle 2d19h gate02.mot.com
  17 vty 15 idle 1w1d gate02.mot.com
  18 vty 16 idle 1w1d gate01.mot.com
  19 vty 17 idle 1w1d gate02.mot.com
  20 vty 18 idle 1w1d gate01.mot.com
  21 vty 19 idle 1w0d gate02.mot.com
  22 vty 20 idle 1w0d gate02.mot.com
  23 vty 21 idle 4d10h 203.130.226.203
  24 vty 22 idle 5d23h gate02.mot.com
  25 vty 23 idle 1w0d Blackberry.rt.ru
  26 vty 24 idle 1w0d gate01.mot.com
  27 vty 25 idle 1w0d gate02.mot.com
  28 vty 26 idle 1w0d gate02.mot.com
  29 vty 27 idle 1w0d gate01.mot.com
  30 vty 28 idle 6d12h gate01.mot.com
  31 vty 29 idle 3d18h gate02.mot.com
  32 vty 30 idle 3d20h office.gill.force.vcn.com
  33 vty 31 idle 4d16h gate02.mot.com
  34 vty 32 idle 6d17h gate02.mot.com
  35 vty 33 idle 2d13h gate02.mot.com
  36 vty 34 idle 5d13h 203.130.226.203
  37 vty 35 idle 4d22h gate01.mot.com
  38 vty 36 idle 2d03h phlox.cs.wisc.edu
  39 vty 37 idle 4d23h a207-99-126-144.svc.towardex.com
  40 vty 38 idle 3d15h gate01.mot.com
  41 vty 39 idle 3d14h gate02.mot.com
  42 vty 40 idle 3d06h gate02.mot.com
  43 vty 41 idle 4d05h gate02.mot.com
  44 vty 42 idle 3d17h mail-out.hk.reach.com
  45 vty 43 idle 3d12h gate02.mot.com
  46 vty 44 idle 2d15h gate02.mot.com
* 47 vty 45 idle 00:00:00 sonet.conti.nu
  48 vty 46 idle 2d14h gate02.mot.com
  49 vty 47 idle 2d22h gate02.mot.com
  50 vty 48 idle 1d07h gate02.mot.com
  51 vty 49 idle 2d01h gate02.mot.com
  52 vty 50 idle 2d09h gate02.mot.com
  53 vty 51 idle 00:00:14 ip-157-14.newcomamericas.net
  54 vty 52 idle 00:04:10 office.gill.force.vcn.com
  55 vty 53 idle 11:10:41 gate02.mot.com
  56 vty 54 idle 00:00:34 gateway.panamsat.com
  57 vty 55 idle 16:11:06 gate01.mot.com
  58 vty 56 idle 01:40:51 johnnypc.csu.net
  61 vty 59 idle 16:17:18 hq1.colosseum.com
  62 vty 60 idle 2d00h gate02.mot.com
  65 vty 63 idle 09:30:35 CPE-144-136-76-220.nsw.bigpond.net.au
  69 vty 67 idle 00:04:49 turing.servers.luna.net
  70 vty 68 idle 00:04:52 turing.servers.luna.net
  71 vty 69 idle 00:04:47 turing.servers.luna.net
  72 vty 70 idle 00:04:42 turing.servers.luna.net
  73 vty 71 idle 00:04:45 turing.servers.luna.net
  74 vty 72 idle 00:04:43 turing.servers.luna.net
  76 vty 74 idle 00:04:41 turing.servers.luna.net

  Interface User Mode Idle Peer Address

Uhm... I think those "ninja" bots are in frozen-state. They probably logged off
but their session may have been locked up in router vty. May be its time for
route-views to go another reboot?

-hc

Or someone with enable to "clear line vty <n>" and if necessary apply
an access-class. Shouldn't have to reboot.

Maybe TCP keepalives would help.

John