Netgear WGT624v2 POS

I just returned a Netgear WGT624v2 because, despite their claims, it does
NOT "notify you of hack attempts, attacks and unauthorized access to your
network or Internet sites." Not only that, but the "reboot" problem persists
with firmware version 4.1.8. Tech support was non-responsive except for the
automated e-mail response, and it was for the wrong model!

I give up on Netgear. They used to be good, but now I'm looking elsewhere.
Does anybody make reasonably priced, full function gear for the home user
anymore??? Seems that Linksys and Dlink have just as many troubles. Would
somebody with a Belkin F5D7230-4 care to report on its logging functions,
maybe even supply a sample?

Thanks

"Steve" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I just returned a Netgear WGT624v2 because, despite their claims, it does
> NOT "notify you of hack attempts, attacks and unauthorized access to your
> network or Internet sites." Not only that, but the "reboot" problem
persists
> with firmware version 4.1.8. Tech support was non-responsive except for
the
> automated e-mail response, and it was for the wrong model!
>
> I give up on Netgear. They used to be good, but now I'm looking elsewhere.
> Does anybody make reasonably priced, full function gear for the home user
> anymore??? Seems that Linksys and Dlink have just as many troubles. Would
> somebody with a Belkin F5D7230-4 care to report on its logging functions,
> maybe even supply a sample?
>
> Thanks

Here's a Belkin log:

System log:
Wed May 26 19:49:39 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Thu May 27 07:50:18 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Thu May 27 19:50:57 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Fri May 28 07:52:03 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Fri May 28 19:52:49 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sat May 29 07:53:34 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sat May 29 19:54:10 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sun May 30 07:54:53 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sun May 30 19:55:41 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Mon May 31 07:56:18 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Mon May 31 19:57:06 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Tue Jun 1 07:57:59 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Tue Jun 1 19:58:47 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Wed Jun 2 07:59:33 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Wed Jun 2 20:00:11 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Thu Jun 3 08:00:52 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Thu Jun 3 20:01:42 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Fri Jun 4 08:02:23 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Fri Jun 4 20:03:04 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sat Jun 5 08:03:52 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sat Jun 5 20:04:30 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sun Jun 6 08:05:20 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sun Jun 6 20:06:01 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Mon Jun 7 08:06:48 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Mon Jun 7 20:07:34 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Tue Jun 8 08:08:17 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Tue Jun 8 20:08:58 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Wed Jun 9 08:09:35 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Wed Jun 9 20:10:16 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Thu Jun 10 08:11:04 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Thu Jun 10 20:11:47 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Fri Jun 11 08:12:29 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Fri Jun 11 20:13:09 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sat Jun 12 08:13:51 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sat Jun 12 20:14:32 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sun Jun 13 08:15:21 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sun Jun 13 20:16:03 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Mon Jun 14 08:16:55 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Mon Jun 14 20:17:37 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Tue Jun 15 08:18:26 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Tue Jun 15 20:19:08 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Wed Jun 16 08:19:57 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Wed Jun 16 20:20:41 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Thu Jun 17 08:21:26 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Thu Jun 17 20:22:12 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Fri Jun 18 08:22:58 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Fri Jun 18 20:23:36 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sat Jun 19 08:24:18 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sat Jun 19 20:25:01 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
Sat Jun 19 21:39:11 2004 -67.86.17.18 logout
Sat Jun 19 21:39:31 2004 -67.86.17.18 login

Firewall log:
Sat Jun 19 21:22:37 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:22:56 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:22:56 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:24:09 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:24:09 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:24:09 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:25:09 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:25:09 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:25:59 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:25:59 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:26:15 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:26:15 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:26:55 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:26:55 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:26:55 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:26:55 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:28:10 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:28:10 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:28:53 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:28:53 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:29:31 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:29:31 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:29:31 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:30:42 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:30:42 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:31:16 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:31:16 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:31:26 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:31:26 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:34:26 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:37:44 2004 1 Blocked by DoS protection 10.39.32.1
Sat Jun 19 21:37:44 2004 1 Blocked by DoS protection 10.39.32.1

Ron Bandes, CCNP, CTT+, etc.

Ron,

Thanks for the log. My old Netgear FR314 provides, IMHO, a more useful log:

06/19/2004 00:09:37.208 - TCP connection dropped - Source:221.125.35.230,
2178, WAN - Destination:xxx.xxx.xxx.xxx, 5554, WAN
06/19/2004 00:11:04.640 - ICMP packet dropped - Source:24.83.108.237, 8,
WAN - Destination:xxx.xxx.xxx.xxx, 8, WAN
06/19/2004 00:18:22.784 - TCP connection dropped - Source:82.64.188.224,
1869, WAN - Destination:xxx.xxx.xxx.xxx, 21, WAN
06/19/2004 00:27:04.672 - ICMP packet dropped - Source:24.86.143.114, 8,
WAN - Destination:xxx.xxx.xxx.xxx, 8, WAN
06/19/2004 00:34:18.432 - TCP connection dropped - Source:80.100.125.179,
14702, WAN - Destination:xxx.xxx.xxx.xxx, 4899, WAN
06/19/2004 00:40:04.112 - ICMP packet dropped - Source:24.65.197.192, 8,
WAN - Destination:xxx.xxx.xxx.xxx, 8, WAN
06/19/2004 00:46:45.416 - TCP connection dropped - Source:218.93.90.21,
4746, WAN - Destination:xxx.xxx.xxx.xxx, 1025, WAN

It is a real shame that the newer, more capable models don't provide this
information. Personally, I value the logging more than the later bells and
whistles.


"Ron Bandes" <RunderscoreBandes @yah00.com> wrote in message
news:K_5Bc.28515$(E-Mail Removed) et...
> "Steve" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > I just returned a Netgear WGT624v2 because, despite their claims, it
does
> > NOT "notify you of hack attempts, attacks and unauthorized access to
your
> > network or Internet sites." Not only that, but the "reboot" problem
> persists
> > with firmware version 4.1.8. Tech support was non-responsive except for
> the
> > automated e-mail response, and it was for the wrong model!
> >
> > I give up on Netgear. They used to be good, but now I'm looking
elsewhere.
> > Does anybody make reasonably priced, full function gear for the home
user
> > anymore??? Seems that Linksys and Dlink have just as many troubles.
Would
> > somebody with a Belkin F5D7230-4 care to report on its logging
functions,
> > maybe even supply a sample?
> >
> > Thanks
>
> Here's a Belkin log:
>
> System log:
> Wed May 26 19:49:39 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Thu May 27 07:50:18 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Thu May 27 19:50:57 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Fri May 28 07:52:03 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Fri May 28 19:52:49 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sat May 29 07:53:34 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sat May 29 19:54:10 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sun May 30 07:54:53 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sun May 30 19:55:41 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Mon May 31 07:56:18 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Mon May 31 19:57:06 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Tue Jun 1 07:57:59 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Tue Jun 1 19:58:47 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Wed Jun 2 07:59:33 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Wed Jun 2 20:00:11 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Thu Jun 3 08:00:52 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Thu Jun 3 20:01:42 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Fri Jun 4 08:02:23 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Fri Jun 4 20:03:04 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sat Jun 5 08:03:52 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sat Jun 5 20:04:30 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sun Jun 6 08:05:20 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sun Jun 6 20:06:01 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Mon Jun 7 08:06:48 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Mon Jun 7 20:07:34 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Tue Jun 8 08:08:17 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Tue Jun 8 20:08:58 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Wed Jun 9 08:09:35 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Wed Jun 9 20:10:16 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Thu Jun 10 08:11:04 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Thu Jun 10 20:11:47 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Fri Jun 11 08:12:29 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Fri Jun 11 20:13:09 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sat Jun 12 08:13:51 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sat Jun 12 20:14:32 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sun Jun 13 08:15:21 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sun Jun 13 20:16:03 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Mon Jun 14 08:16:55 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Mon Jun 14 20:17:37 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Tue Jun 15 08:18:26 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Tue Jun 15 20:19:08 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Wed Jun 16 08:19:57 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Wed Jun 16 20:20:41 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Thu Jun 17 08:21:26 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Thu Jun 17 20:22:12 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Fri Jun 18 08:22:58 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Fri Jun 18 20:23:36 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sat Jun 19 08:24:18 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sat Jun 19 20:25:01 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> Sat Jun 19 21:39:11 2004 -67.86.17.18 logout
> Sat Jun 19 21:39:31 2004 -67.86.17.18 login
>
> Firewall log:
> Sat Jun 19 21:22:37 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:22:56 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:22:56 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:24:09 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:24:09 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:24:09 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:25:09 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:25:09 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:25:59 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:25:59 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:26:15 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:26:15 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:26:55 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:26:55 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:26:55 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:26:55 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:28:10 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:28:10 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:28:53 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:28:53 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:29:31 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:29:31 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:29:31 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:30:42 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:30:42 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:31:16 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:31:16 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:31:26 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:31:26 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:34:26 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:37:44 2004 1 Blocked by DoS protection 10.39.32.1
> Sat Jun 19 21:37:44 2004 1 Blocked by DoS protection 10.39.32.1
>
> Ron Bandes, CCNP, CTT+, etc.
>
>

"Steve" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Ron,
>
> Thanks for the log. My old Netgear FR314 provides, IMHO, a more useful
log:
>
> 06/19/2004 00:09:37.208 - TCP connection dropped - Source:221.125.35.230,
> 2178, WAN - Destination:xxx.xxx.xxx.xxx, 5554, WAN
> ...
> It is a real shame that the newer, more capable models don't provide this
> information. Personally, I value the logging more than the later bells and
> whistles.
>
>
> "Ron Bandes" <RunderscoreBandes @yah00.com> wrote in message
> news:K_5Bc.28515$(E-Mail Removed) et...
> > "Steve" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> Would
> > > somebody with a Belkin F5D7230-4 care to report on its logging
> functions,
> > > maybe even supply a sample?
> >
> > Here's a Belkin log:
> >
> > System log:
> > Sat Jun 19 20:25:01 2004 -WAN DHCP Client Connected IP xxx.xxx.xxx.xxx
> > Sat Jun 19 21:39:11 2004 -67.86.17.18 logout
> > Sat Jun 19 21:39:31 2004 -67.86.17.18 login
> >
> > Firewall log:
> > Sat Jun 19 21:37:44 2004 1 Blocked by DoS protection 10.39.32.1
> >
> > Ron Bandes, CCNP, CTT+, etc.

Here is a log from my old SMC Barricade 7004BR:

Sunday, June 20, 2004 10:22:07 PM Unrecognized access from
202.103.45.229:2823 to TCP port 9898
Sunday, June 20, 2004 10:38:08 PM Unrecognized access from
63.127.192.137:6587 to UDP port 1026
Sunday, June 20, 2004 10:42:15 PM 192.168.123.109 login successful


Here is a log from my newer SMC 2804WBR:

Security Log
06/20/2004 22:23:11 192.168.117.105 login success
06/20/2004 21:13:30 NTP Date/Time updated
06/20/2004 15:14:24 NTP Date/Time updated
06/20/2004 09:15:18 NTP Date/Time updated
06/20/2004 03:16:12 NTP Date/Time updated
06/19/2004 21:17:06 NTP Date/Time updated
06/19/2004 15:17:59 NTP Date/Time updated
06/19/2004 09:18:53 NTP Date/Time updated
06/19/2004 03:19:47 NTP Date/Time updated
06/07/2004 21:57:40 192.168.117.104 logout
06/07/2004 21:54:05 192.168.117.104 login success

DHCP Client Log
01/01/2002 00:00:01 DHCP Client: Receive Ack from 192.168.123.254,Lease
time=3600000
01/01/2002 00:00:01 DHCP Client: Domain name =
01/01/2002 00:00:01 DHCP Client: Send Request,Request IP=192.168.123.108
01/01/2002 00:00:01 DHCP Client: Receive Offer from 192.168.123.254
01/01/2002 00:00:01 DHCP Client: Domain name =
01/01/2002 00:00:00 DHCP Client: Send Discover

The 2804WBR never sees attacks because it's behind the 7004BR. Some emails
sent by the 2804WBR firewall because it thought it detected an outbound
attack:

--- begin firewall email
Dear User
Your router has detected and protected you against an attempt to gain access
to your network. This may have been an attempted hacker intrusion, or
perhaps just your Internet Service Provider doing routine network
maintenance.
Most of these network probes are nothing to be worried about - these types
of random probes should NOT be reported, but you may want to report repeated
intrusions attempts. Save this email for comparison with future alert
messages.
Your router Alert Information

Time: 05/20/2004, 17:41:10
Message: IP Spoofing
Source: 192.168.117.104, 138
Destination:192.168.117.255, 138 (from WAN Inbound)


Visit the UXN Combat Spam web site to get more detailed information about
the intruder - http://combat.uxn.com/
1. Type the intruder's IP address into the IP WHOIS search engine
2. Click the Query Button
3. Detailed network and administration information will be displayed
--- end firewall email

--- begin firewall email
Dear User
Your router has detected and protected you against an attempt to gain access
to your network. This may have been an attempted hacker intrusion, or
perhaps just your Internet Service Provider doing routine network
maintenance.
Most of these network probes are nothing to be worried about - these types
of random probes should NOT be reported, but you may want to report repeated
intrusions attempts. Save this email for comparison with future alert
messages.
Your router Alert Information

Time: 05/16/2004, 01:55:35
Message: Smurf
Source: 192.168.117.104
Destination:66.218.66.255, Type:8, Code:0 (from LAN Inbound)


Visit the UXN Combat Spam web site to get more detailed information about
the intruder - http://combat.uxn.com/
1. Type the intruder's IP address into the IP WHOIS search engine
2. Click the Query Button
3. Detailed network and administration information will be displayed
--- end firewall email

--- begin firewall email
Dear User
Your router has detected and protected you against an attempt to gain access
to your network. This may have been an attempted hacker intrusion, or
perhaps just your Internet Service Provider doing routine network
maintenance.
Most of these network probes are nothing to be worried about - these types
of random probes should NOT be reported, but you may want to report repeated
intrusions attempts. Save this email for comparison with future alert
messages.
Your router Alert Information

Time: 03/31/2004, 21:26:05
Message: SYN Flood to Host
Source: 192.168.117.103, 1390
Destination:198.62.124.7, 80 (from WAN Outbound)


Visit the UXN Combat Spam web site to get more detailed information about
the intruder - http://combat.uxn.com/
1. Type the intruder's IP address into the IP WHOIS search engine
2. Click the Query Button
3. Detailed network and administration information will be displayed
--- end firewall email

Ron Bandes, CCNP, CTT+, etc.