The openssh 3.7.1p2 suite is available in my LEAF packages directory.
Check:
http://leaf.sourceforge.net/devel/jnilo
It is compiled statically against openssl 0.9.7b
It fixes some more security bugs and the stty pb that was occuring since
3.6.1 when compiled against libc5
Jacques
I have searched the documentation and fought with how to properly set up
net-snmp on the latest Uclibc Bering image.
FIRST. MY SETUP.
NameVersionDescription
===-==-=
=
initrd V2.0 uClibc-0. LEAF
Hi all the list.
I have added IPSec restart in the script, because it seems not to work well without it
at each time.
Sorry !
Now, it seems to be ok.
#!/bin/sh
#
# Check a regular interval defined in /etc/crontab that IP exists for IFACE
# and that IP has not changed
# this is obtained by
Troy,
I'm not really a snmp expert, but you can try a few things to
pinpoint the exact problem.
In the netsnmpd config you can set the following options in the
default file for logging to /var/log/daemon.log (restart snmpd after
setting these options).
# snmpd options (use syslog, close
Hi all.
I'm using Bering uClibc-2.0 b3, and I've tried to configure my box to take on print
server duties. I've followed the (excellent) instructions in this thread:
http://sourceforge.net/mailarchive/message.php?msg_id=3595773
...but I've hit a wall, it would seem, with the p910nd daemon.
I have a quick shorewall question.
I am receiving around 500 hits a day from bit torrent ports. (6881 - 6889).
These are flooding my firewall logs and I would like to stop logging hits on
these ports.
I would like to continue with logging the hits on any other ports however.
Is there a way to tell
On Sun, 28 Sep 2003, Troy Aden wrote:
I have a quick shorewall question.
I am receiving around 500 hits a day from bit torrent ports. (6881 - 6889).
These are flooding my firewall logs and I would like to stop logging hits on
these ports.
I would like to continue with logging the hits on any
Sorry about that.
It took me all of 20 seconds to find the answer in the FAQ.
6b. DROP messages on port 10619 are flooding the logs with their connect
requests. Can i exclude these error messages for this port temporarily from
logging in Shorewall?
Temporarily add the following rule:
DROP
Followed this message thread - I have the same issue with Bering v1.2.
Can't drop the PPP [analog modem] link due to UDP and ICMP packets inbound
from the net.
I pulled down the pppd-filter.gz file. However - the web site shows that
its approx 100k - but the file size is 212k. When I scp the
