Re: Adding "mail" function?

scp is included, the recommended way to handle logs is to use syslog to a
remote box on the lan and save them there or forward them to a remote host
(list you would with a commercial router)

If you do not have another unix box that you can log to, there are a few
free syslog receivers for windows out there. there are even windows event
loggers that will convert your standard "event viewer" type logs to syslog
and send them to a remote host or log them locally as plain text files.

Continuous writes to the flash will damage it.

I have been running the same flash card in my emBSD router/firewall since
the inception of the project with no issues, i do however log to full obsd
box.

Also as far as compiling binaries for use on emBSD, straight compiles from
OpenBSD of the correct version will work on emBSD. The libraries and paths
have not been tinkered with in order to maintain 100% binary
compatibility. Note: if you have a package from the ports that depends on
libs from the ports you will need to install those dependancies also.

just for Reference, 1.0 is based on obsd 2.8, 1.1 is based on obsd 2.9,
2.0 is based on 3.0 and the work in progress which has not been released
as of yet, 2.1 is based on 3.1 stable code.  The 2.1 version should be
available shortly from the FTP site.

2.0 works just fine, however, there can be issues with the version of PF
included there as is will not forward things like GRE and IPSec. This is a
limitation of the code that was used there.

Ken

On Wed, 3 Jul 2002, Eric Ziegast wrote:

> > About the only function I am missing is the "mail" command
>
> Consider also:
> 	- Using ftp, scp or rsync to just copy logs off of the EMBSD box
> 	  without mail.  (again, like mail, you might have to compile and
> 	  install a program from OpenBSD source)
> 	- Using network-based syslog to an internal server.  You can log
> 	  data automatically in real time at a relatively even data rate
> 	  without load or bandwidht spikes when it's time to transfer
> 	  logs.  Writing logs to local "disk" isn't good for the longevity
> 	  of the flash card, or writing to a memory-based filesystem can
> 	  have the logs disappear when the power drops off.
>
> I don't know how much of a difference it makes (haven't compiled programs
> for my Net4501 yet), but considering the Net45xx uses a 486, you might want
> to make sure you're compiling for a 486 or 386 processor.  If you have
> trouble getting your Pentium-compiled code to work, look at the "-m" options
> of gcc and see if you want to add any of them to CFLAGS.
>
> Just a thought.
> --
> Eric Ziegast
>

-Ken

---
"Lies, Damned Lies, And Micro$oft Press Releases" - Tilda, From TechTV