| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 828.1 | Nothing eating up log space! | CHEFS::AYLESBURY_L | | Tue Jan 16 1996 08:35 | 8 |
| 828.2 | Same in kern.log, gated.log, wwwproxy.log | SNOFS1::snod17dgp10.gen.sno.dec.com::therkelsenp | ummm, I forget | Thu Jun 13 1996 23:06 | 26 |
| 828.3 | Log everything... | GALVIA::SMITH | | Fri Jun 14 1996 05:23 | 15 |
| 828.4 | cause is most likely DHCP | SNOFS1::do1.sno.dec.com::therkelsenp | ummm, I forget | Mon Jun 17 1996 03:29 | 17 |
| 828.5 | boot DHCP! | GALVIA::SMITH | | Mon Jun 17 1996 07:20 | 6 |
| 828.6 | define 0.0.0.0 as internal network ? | PRMS00::COLE | | Mon May 12 1997 10:46 | 8 |
| so should I define 0.0.0.0 as an internal (BLUE) network to eliminate
these messages or is there a better method to avoid filling up
the log files ?
...larry
|
| 828.7 | | EEMELI::EINAMO | | Tue May 13 1997 04:58 | 12 |
| Hi
My customer is also complaining that 0.0.0.0 fils his kern log and www.log
....
for first aid I did advice him to go nad snif your intranet (blue cable) and try
to find the statinon that is sending those 0.0.0.0 fames
Are we sure that it is not us (altavista firewall) that generated those bootp
packages ?
Marko
|
| 828.8 | | CHEFS::16.37.11.61::PITT | Gone with the winsock ... | Fri May 16 1997 11:19 | 8 |
| It certainly wasn't the firewall if you installed it exactly
as instructed in the manual...
I have noticed WWWproxy stuff as well, but have not had any
chance to investigate - I can't even remember which configuration
it was ...
T
|
| 828.9 | Check /etc/ifaccess.conf | KYOSS1::MONTARE | Alex Montare | Tue May 27 1997 12:19 | 5 |
| I don't know if this is "supported" but I've had luck eliminating these
messages by editing the file /etc/ifaccess.conf. In that file there is
a line for network 0.0.0.0 that ends with the keyword "denylog".
Changing this to "deny" stopped the logging and still blocked the
packets (yes, I did test it!).
|