-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tim Wegner wrote:
| Jim Ford asked:
|
|> My Dachstein setup appears to be working fine but Azereus reports a
|> NAT problem. As I'm still struggling up the ipchains learning curve,
|> I don't want to fiddle with anything and unwittingly throw the doo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Ford wrote:
| In less than 24 hours I've had over 600 'deny' entries in my Dachstein
message.log file.
| I don't know wether this amount is normal, large or small - but the bulk
of them relate to
| IPs for private networks. Most of them are 10.35
Am Freitag, 18. November 2005 20:53 schrieb Trev Peterson:
>
> 11. Edit /mnt/cf/syslinux.cfg
> Here is my syslinux.cfg (output of cat /mnt/cf/syslinux.cfg):
> display syslinux.dpy
> timeout 0
> default linux initrd=initrd.lrp init=/linuxrc rw root=/dev/ram0
> LEAFCFG=/dev/hda 1:msdos
Is the space
Jim Ford asked:
> My Dachstein setup appears to be working fine but Azereus reports a
> NAT problem. As I'm still struggling up the ipchains learning curve,
> I don't want to fiddle with anything and unwittingly throw the doors
> open to attackers. I'd welcome suggestions for an ipchains line to
>
In less than 24 hours I've had over 600 'deny' entries in my Dachstein
message.log file.
I don't know wether this amount is normal, large or small - but the bulk of
them relate to
IPs for private networks. Most of them are 10.35.160.1 and several 192.168.*.*
range.
Can anyone explain what's at w
Hi Julie,
Very difficult to say what the cause is, especially because it happens
randomly. Do you see anything strange in the logs?
The first thing that comes to mind is that your log filespace is running
out of memory, you can check with "df". It's that the case you can
increase the log tmpfs in
