Al,
I suppose the only news is that the angry scan is still in process. I
started it at 1124 on the 5th. It has been running 24/7 since. The ip slice
I created seems to have some ~16M addy's to ping, I may be at it several
more days.......As I watch the scanner work, it seems to grab a block of
20-30 ip addys and then pause for ~4sec (?process/ping?), grab the next
block of addy's.
or,
if I told the router to /ignore all pings/, I may just wasting time burning
trons! I mention this because IIRC, way back when this router was used
(1998-2001), I believe making the router un-ping-able was considered an
additional strong security feature (besides the rule-set of the router). I
am still digging thru my old docs for the router to see what my settings
were. LOL! I know I have my current router also set this way. I can ping
all my pcs and they all answer the ping. If I ping the router, it just do
not answer! I am re-thinking this. Can I get more bozo? I might be trying!
I am running this in a static mode - just the pc, the router, and a single
cat5e cable. I am off my LAN for this, so now the pc is beginning to bitch
about not being able to talk to the server for nod32 updates! Last night,
for grins, I cranked up WireShark to see what the angry scan looked like.
All I got for a 45sec peek was constant calls by the pc for the gateway and
server. LOL!
I may stop the scan soon and just try to kill/reset the router's f/w to
default. I know this will wipe out all the neat custom rules from years
ago, but maybe all those old rules don't matter anymore in today's
cesspool.......... :)
Thanks for asking.
Best,
Duncan
At 07:21 01/07/2008 -0500, you wrote:
> >>Or, do I just toss it in the big red plastic box?
Any news?
al
