I'm not extremely comfortable with doing firewall testing remotely on
production systems, but I need to set up some incoming IP blocks.
I've got a FreeBSD RELENG_5_4 system with public interface rl0.
I want all traffic allowed unfettered, except traffic from particular
IPs to be completely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've got a system that's sending a ton of referral spam to websites on
my RELENG_4_9 system. I'd like to block them from accessing my system
at the TCP level. What's the best and easiest way to do this?
I assume I'll need to recompile the kernel wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been able to get Postfix and SASL1 to authenticate to system accounts
under FreeBSD with no problem, but now I'm trying to use SASL2. I'm
running into problems.
I built postfix and sasl2 from ports with no problems. I created
/usr/local/lib/sas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 2, 2003, at 12:01 PM, Lowell Gilbert wrote:
H.Wade Minter <[EMAIL PROTECTED]> writes:
I'd like to update my ports-installed version of Perl from 5.8.0 to
5.8.1. On my test system, I did a "portupgrade -rR perl", but it
didn't update any of my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd like to update my ports-installed version of Perl from 5.8.0 to
5.8.1. On my test system, I did a "portupgrade -rR perl", but it
didn't update any of my installed p5- modules, which caused breakage
until I reinstalled all of them by hand.
Is th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I installed the vsftpd port on my RELENG_4_8 system as a replacement
for the standard ftpd. However, it doesn't appear to be honoring
/etc/shells - a user listed in the passwd file with a shell
(/sbin/nologin) that does not appear in /etc/shells is
One of my RELENG_4_8 servers is crashing regularly. I think it's
hardware, but I'm not sure which part is the culprit. The crash messages
are below - any suggestions?
My googling is pointing to disk, but I'd like a second opinion.
#
Jun 16 19:50:56 carlton /kernel: panic: pmap_enter: attem
On 5 Nov 2002, Simon J Mudd wrote:
> In your case it may also be useful to enable debugging in smtpd by
> modifying master.cf and adding a -v line, and then restarting postfix
> with postfix reload.
Turns out the problem was that postfix didn't have access to the
/var/pwcheck directory. Putting
This is a tale of two postfix installs.
Install one was on a clean 4.7 system, and works like a charm. Using
pwcheck_pam, everything's peachy.
On the other system, also a 4.7 install, currently running sendmail, I'm
attempting to migrate to postfix. Everything seems to be working fine,
except I
