One Minute

Sometimes where two or more GP20/30 readers are used
in closed prximity a read on one reader is echoed in a nearby reader.

There are 2 possible cause of this. The most common
is the field in one reader being inductively coupled to
the other because they are close. In this case there
is nothing to do except separate the readers more or
change the rotation of one/both readers.

The second cause of echoing is the two readers operate
on the same local DC supply. If the DC is not sufficiently
smoothed it is possible for any RF field in the lead of one
reader to travel down the cable and appear at the other/s
reader.(Echo)

The effect happens most where the DC wires are connected
in common in the field and not taken back to the low
impedence DC supply on the controller.

The solution is to decouple the DC supply lead to the reader
as below:

2. PostgreSQL Database Setup

Create the a database named syslog. To do this, run this command: createdb syslog

Environment:

• FreeBSD 5.1
  
• Syslog-NG
• PostgreSQL (v 7.3.2 used here; Compiled from source)

Next, create the table in the newly-created datbase. Download the SQL directly: syslog.sql

CREATE TABLE logs (
	host varchar(32) default NULL,
	facility varchar(10) default NULL,
	priority varchar(10) default NULL,
	level varchar(10) default NULL,
	tag varchar(10) default NULL,
	date date default NULL,
	time time default NULL,
	program varchar(15) default NULL,
	msg text,
	seq serial,
	PRIMARY KEY (seq)
); 

3. Syslog-NG Setup

Install Syslog-NG.

Edit your syslog-ng configuration file.

/etc/syslog-ng/syslog-ng.conf.

Here are the relevant parts of syslog-ng.conf:

#
# SQL logging support
#

destination d_pgsql {
pipe("/tmp/pgsql.pipe"
template("INSERT INTO logs (host, facility, priority, level, tag, date, time, program,
msg) VALUES ( '$HOST', '$FACILITY', '$PRIORITY', '$LEVEL', '$TAG,
'$YEAR-$MONTH-$DAY', '$HOUR:$MIN:$SEC', '$PROGRAM', '$MSG' );n
)

template-escape(yes)

);

};

log { source(src); destination(d_pgsql); };

Getting PostgreSQL and Syslog to Work Together

Use this script I've adapted for PostgreSQL, syslog-ng-pgsql-pipe.sh:

#!/bin/sh
#
# File: syslog-ng-pgsql-pipe.sh
#
# Take input from a FIFO and run execute it as a query for
# a PostgreSQL database.
#
# IMPORTANT NOTE:  This could potentially be a huge security hole.
# You should change permissions on the FIFO accordingly.
#
                                                                                                                                               
if [ -e /tmp/pgsql.pipe ]; then
        while [ -e /tmp/pgsql.pipe ]
                do
                        psql -q -U mydbusername syslog < /tmp/pgsql.pipe>        done
else
        mkfifo /tmp/pgsql.pipe
fi

quota from http://www.securityfocus.com/...

> I would like to analyze in real time, the AS400 events. I'm seeking a
> method to forward AS400 logs in syslog, SNMP or SMTP.

I'm not familiar with the AS400 (been over 12 years), so please bare with me.
I assume the problem is there is no stock syslog and/or no way to get syslog
to compile? Is there a copy of logger? If so, you can use that. If not, its messy but:

tail -f /var/log/messages | nc -u 192.168.1.1 514 &

will work in a pinch.
I've used this to Syslog off log entries that I've been either too lazy to
setup correctly, or only needed a short term solution. This of course
means you need a working copy of Netcat, but the code is pretty small
and portable.

Refer to link below for those who want to do a central remote logging.

Winlogd
Ntsyslogd
Evtsys

|start|->|run|->

control userpasswords2 --> edit user
dcomcnfg --> run/stop services
cmd --> launch dos terminal
msconfig --> launch startup/boot time menu
shutdown  -> shutdown  PC

... this is what i usually used. will update if use more

Thanks to George McCashin for providing this information.

Web based configuration:

1). Log on to the web interface as an "admin" user
2). Go to Configuration-Report Settings-Syslog
3). Click on 'Enable Syslog'
4). If you want all traffic logged also click on 'Include Traffic Log' as well
5). Enter the log host address and port (Address of Kiwi Syslog Daemon and UDP port 514)




Additional note provided by Kevin Branch:

This will log all traffic coming through all types of Netscreen policies (permit/deny/tunnel),
as well as log traffic permitted by default (if the Netscreen is set to permit sessions that are not
specifically denied).

The "Log Packets Terminated to Self" option has
nothing to do with sessions across the Netscreen, but
rather logs sessions to the Netscreen itself
(which should only be Netscreen management traffic, but will also show up probes from the Internet)

Alternatively, you can configure the NetScreen from the CLI.

Command Line Interface configuration:

The specific commands required to set up a Syslog server are listed below:

#set syslog config ip_address #security_facility
#local_facility
#set syslog enable
#set syslog traffic
#set log module system level level destination syslog

Note: The set syslog config command requires that you
define the security facility and local facility. See
the syslog command in the NetScreen CLI Reference
Guide for a complete list of options for security_facility and local_facility.

Note: You must enter the set log command once for each message level. The options for level are listed below:

#emergency
#alert
#critical
#error
#warning
#notification
#information

Freebsd syslog
- by default syslog service is enable on freebsd with -ss option.
- to enable remote logging.
= edit /etc/syslog.conf
- add @hostname, where @hostname is the place where the logging server is located.
= make sure in /etc/service
- syslog 514/udp exist

It allows data to be acquired quickly and automatically using radio frequency. Unlike bar-coding, RFID technology enables the reading, writing and recording of data on the applied tag irrespective of location, type of environment, contact or visibility. Thus RFID opens up new opportunities in the areas of identification logistics, material management, production and service.