Netgear DG834 v. DG814 Logs

My old DG814 used to log every web site accessed and then email it when
the log was full.

My new DG834 that replaced it does not seem to log web access any more.
Am I missing an option somewhere or is this a fact.
--
Les Desser
(The Reply-to address IS correct - hope Swen ignores it))

Les Desser <leslie@[127.0.0.1]> wrote:
> My old DG814 used to log every web site accessed and then email it when
> the log was full.

> My new DG834 that replaced it does not seem to log web access any more.
> Am I missing an option somewhere or is this a fact.

You have missed something! The DG834 has a proper firewall which you can setup
to block or allow any incoming or outgoing connections as you wish - and to
*OPTIONALLY* log what it is doing. It uses a somewhat different "rule-based"
approach to the DG814.

The default setting is to allow but NOT to log any outgoing connections. While you
cannot alter the default rule you can slot in another rule or rules which will take
precedence.

To do what you want just add a firewall rule to still allow HTTP outgoing but to log
any connections for it. This new rule will be of higher priority than the default.

In article <bsno40$(E-Mail Removed)>, Brian McIlwrath
<(E-Mail Removed)> writes
>Les Desser <leslie@[127.0.0.1]> wrote:
>> My old DG814 used to log every web site accessed and then email it when
>> the log was full.
>
>> My new DG834 that replaced it does not seem to log web access any more.
>> Am I missing an option somewhere or is this a fact.
>
>You have missed something! The DG834 has a proper firewall which you can setup
>to block or allow any incoming or outgoing connections as you wish - and to
>*OPTIONALLY* log what it is doing. It uses a somewhat different "rule-based"
>approach to the DG814.
>
>The default setting is to allow but NOT to log any outgoing
>connections. While you
>cannot alter the default rule you can slot in another rule or rules
>which will take
>precedence.
>
>To do what you want just add a firewall rule to still allow HTTP
>outgoing but to log
>any connections for it. This new rule will be of higher priority than
>the default.

Thanks. Done that and indeed it now logs. Unfortunately, it only logs
the IP addresses after DNS lookup while the 814 used to log the actual
site names. Don't suppose anything can be done about that as it seems
to be logging the firewall rules, which are only applied after the DNS
lookup.

Incidentally, does anyone know the limits to the number of firewall
rules?
--
Les Desser
(The Reply-to address IS correct - hope Swen ignores it))

Les Desser <leslie@[127.0.0.1]> wrote:

> Thanks. Done that and indeed it now logs. Unfortunately, it only logs
> the IP addresses after DNS lookup while the 814 used to log the actual
> site names. Don't suppose anything can be done about that as it seems
> to be logging the firewall rules, which are only applied after the DNS
> lookup.

Yes - I think this is correct. The DG814 didn't have a true firewall or
customisable logging and I guess this is a penalty for improved functionality!

> Incidentally, does anyone know the limits to the number of firewall
> rules?

No - but I have several setup. For imformation it is possible to log
EVERY outgoing connection by setting up a "Custom service" called, for
example, "AllPorts" which includes TCP/UDP ports 1->65535. I have this but
I then had to add several "don't log" rules (at higher priority) to prune
out things like DNS lookups to keep the log from groing too fast!