envio land » openbsd

Cache HIT with No Limits on Mikrotik 4.x

envio — Mon, 03 Jan 2011 07:33:48 +0000

Recently I have successfully setup my proxy (CentOS 5.5) and mikrotik 2.9.X with cache HIT no limits. When my RB 1100 came, I move my mikrotik 2.9.x to this new RB 1100.

These day I just realized that my cache HIT is limited so my Mikrotik count the cache HIT. On Mikrotik 2.9 we use TOS for packet mangle and it’s value is 0×30 (Hexadeciamal) or 48 in decimal. I watched the data packet for cache hit mangle and the value to small rather when I saw on squid log HIT.

After googling , I found that on Mikrotik 4.x, the TOS value is not same as Mikrotik 2.9 even on Mikrotik 4.x also written as DSCP (TOS). So I start search the algorithm converting TOS on Mikrotik 2.9 to DSCP (TOS) on Mikrotik 4.x. So here’s the table :

DSCP TOS

0        0
1         4
2        8
3        12
4        16
5       20

Source : http://forum.mikrotik.com/viewtopic.php?f=1&t=19826

Just divide the TOS from Mikrotik 2.9 by 4 and insert the value on DSCP (TOS) on Mikrotik 4.x , you mangle rule will work like a charm

clamav update on OpenBSD 4.4 to latest version using Ports & CVS

envio — Mon, 13 Apr 2009 04:47:05 +0000

This step how to update you clamav to the latest version using OpenBSD Ports :

Extract OpenBSD 4.4 ports packages, should be ports.tar.tgz , extract it to /usr/ports
use this command

#tar zxf ports.tar.gz -C /usr

Delete the clamav ports tree , we should do this because some patch from original OpenBSD 4.4 ports will make conflict with the newest clamav version (0.94.2)

#rm -rf /usr/ports/security/clamav

Now , get some OpenBSD CVS to get the news clamav ports source

#export CVSROOT=anoncvs@anoncvs.ca.openbsd.org:/cvs

Get the clamav ports source

#cd /usr
#cvs -q get -P ports/infrastructure/db/user.list
#cvs -q get -P ports/security/clamav

Then Compile it :

#cd ports/security/clamav
#make install

The news clamav now in your OpenBSD box

ClamAV update to 0.94.1 on OpenBSD 3.9

envio — Wed, 19 Nov 2008 10:50:27 +0000

Recently I have successfully update ClamAV on OpenBSD 3.9 server. Yeah, it’s old OpenBSD version, I read there a security problem on ClamAV version 0.94 and below. I update this ClamAV to version 0.94.1 using OpenBSD ports, need some modification here to make this 3.9 work well.

On “Makefile”, remove “>” on LIB_DEPENDS section, so it will be like this

LIB_DEPENDS= gmp.6::devel/gmp \
bz2.10::archivers/bzip2 \
iconv.4::converters/libiconv

On “pkg/PLIST”, remove “@bin” and also “@sbin”, and then add “share” to “manual” path, the “manual” path will be like this

share/man/man1/clamconf.1
share/man/man1/clamdscan.1
share/man/man1/clamscan.1
share/man/man1/freshclam.1
share/man/man1/sigtool.1
share/man/man5/clamd.conf.5
share/man/man5/freshclam.conf.5
share/man/man8/clamav-milter.8
share/man/man8/clamd.8

If you finish with “make”, use “make update” on ClamAV ports to update your installed ClamAV

New version of ClamAV need “/dev/null”, so if you run ClamAV in chroot like I did, you need make /dev/null in our chroot path. For example, my chroot path for CLamAV is /var/clamav. Usually /var mounted with “nodev” so we must remove “nodev” mount option.

#mount -o dev -u /dev/wd0e
#mount
/dev/wd0a on / type ffs (local)
/dev/wd0d on /home type ffs (local, nodev, nosuid)
/dev/wd0e on /var type ffs (local, nosuid)

#mkdir /var/clamav/dev
#mknod /var/clamav/dev/null c 2 2

Make new “dev/null” belong to user that run ClamAV chroot, I use “_clamav” as my chroot user.

#chown _clamav:_clamav /var/clamav/dev/null

Just Like That … and don’t forget to update the virus database

ClamAV Ports on OpenBSD 4.3

envio — Sat, 11 Oct 2008 04:56:13 +0000

It’s long time for me not deal with OpenBSD ports, few days ago I must install mail server, so I prefer to use OpenBSD . One component of this mail server is antivirus then I use ClamAV, I prefer to use ports system to install ClamAV to get newest version. So I need ‘porting’

Using this CSV to update my port source of ClamAV

# cd /usr
# export CVSROOT=anoncvs@anoncvs.ca.openbsd.org:/cvs
# cvs -q get -P ports/security/clamav/

After update my ClamAV source was updated from version 0.92.1 to 0.94, then ready to ‘make’ and ‘make install’

# cd /usr/ports/security/clamav
# make
# make install

Some thing wrong when on “make install”, this error nearly same as I found when I porting postfix, but when in postfix I prefer to use old version rather using new one because It was late and I was so tired :p It say “unknown element @bin/” when I do make install.

So what kind of this error, I have no clue about this, googling didn’t give good result because you know it’s OpenBSD . Then I try to compile older ClamAV that came from ports, the version is 0.92.1. The result is, everything was smooth, normal porting process, so I guest the problem was in port update.

I decide to review the ports code, compare the updated version and the original version of clamav ports, Comparing this file /usr/ports/security/clamav/pkg/PLIST and I found this :

clamav-0.92.1

@comment $OpenBSD: PLIST,v 1.9 2008/01/02 18:10:51 bernd Exp $
@newgroup _clamav:539
@newuser _clamav:539:539:daemon:Clam AntiVirus:/nonexistent:/sbin/nologin
bin/clamav-config
bin/clamconf
bin/clamdscan
bin/clamscan
bin/freshclam
bin/sigtool

clamav-0.94

@comment $OpenBSD: PLIST,v 1.11 2008/07/08 22:38:12 sthen Exp $
@newgroup _clamav:539
@newuser _clamav:539:539:daemon:Clam AntiVirus:/nonexistent:/sbin/nologin
bin/clamav-config
@bin bin/clamconf
@bin bin/clamdscan
@bin bin/clamscan
@bin bin/freshclam
@bin bin/sigtool

Why there exist “@bin” ? so I remove all @bin, save this file, and doing ‘make’ and ‘make install’ again. The result : ClamAV 0.94 successfully installed What a weird

Making OpenBSD 4.3 Bootable CD using Nero

envio — Wed, 17 Sep 2008 10:33:05 +0000

In previous version OpenBSD included the CDROOMXX.FS on their release (XX is the version of OpenBSD), we need CDROOMXX.FS to make bootabe CD. When we using nero to make bootable CD, it need BootImage, and than we can use CDXX.FS as boot image, so the disk we will make will bootable.

So whereis the CDROOM43.FS ? we can find it on file cdemu43.iso, you can extract it and you can use CDROOM43.FS as boot image.

Open BSD Rescue

admin — Mon, 21 Jul 2008 04:36:33 +0000

When facing unwanted situation like very bad disk situation or some thing else,we may use this command to enter single mode of OpenBSD,

boot> boot -s

Enter that command after boot prompt appear on the first time.