iptables + log

[burnme]

Hoi,

ich möchte alles, was ich per iptables
logge, als broadcast message ausgegeben werden
soll. Wenn das schon net geht, sollte es auf tty1 ausgeben.
Wie mache ich das?

thx

[Jasper]

Original geschrieben von burnme

ich möchte alles, was ich per iptables
logge, als broadcast message ausgegeben werden
soll. Wenn das schon net geht, sollte es auf tty1 ausgeben.
Wie mache ich das?


siehe 'man syslog.conf', abschnitt ACTIONS.

-j

[burnme]

also, die man syslog.conf
gibbet bei mir net....
und man syslog
findet der unter
action nur:
LOG_ALERT
action must be taken immediately

das hilft mir imo net viel weiter....

[Jasper]

Original geschrieben von burnme
also, die man syslog.conf
gibbet bei mir net....


was verwendest du denn für ein OS?

hier der abschnitt. kann natürlich bei deiner version von syslog etwas anders funktionieren.

ACTIONS
The action field of a rule describes the abstract term ``logfile''. A
``logfile'' need not to be a real file, btw. The syslogd(8) provides
the following actions.

Regular File
Typically messages are logged to real files. The file has to be speci-
fied with full pathname, beginning with a slash ``/''.

You may prefix each entry with the minus ``-'' sign to omit syncing the
file after every logging. Note that you might lose information if the
system crashes right behind a write attempt. Nevertheless this might
give you back some performance, especially if you run programs that use
logging in a very verbose manner.

Named Pipes
This version of syslogd(8) has support for logging output to named
pipes (fifos). A fifo or named pipe can be used as a destination for
log messages by prepending a pipe symbol (``|'') to the name of the
file. This is handy for debugging. Note that the fifo must be created
with the mkfifo(1) command before syslogd(8) is started.

Terminal and Console
If the file you specified is a tty, special tty-handling is done, same
with /dev/console.

Remote Machine
This syslogd(8) provides full remote logging, i.e. is able to send mes-
sages to a remote host running syslogd(8) and to receive messages from
remote hosts. The remote host won't forward the message again, it will
just log them locally. To forward messages to another host, prepend
the hostname with the at sign (``@'').

Using this feature you're able to control all syslog messages on one
host, if all other machines will log remotely to that. This tears down
administration needs.

List of Users
Usually critical messages are also directed to ``root'' on that
machine. You can specify a list of users that shall get the message by
simply writing the login. You may specify more than one user by sepa-
rating them with commas (``,''). If they're logged in they get the
message. Don't think a mail would be sent, that might be too late.

Everyone logged on
Emergency messages often go to all users currently online to notify
them that something strange is happening with the system. To specify
this wall(1)-feature use an asterisk (``*'').

-j

[burnme]

also,
das hilft mir ehrlich gesagt nicht weiter...
dh, ich muss was an der syslog.conf
ändern? oder bei iptables?
thx

[tomes]

--> http://www.infodrom.org/~joey/Writing/Linux-Magazin/syslogd.html

T;o)Mes

[HangLoose]

@tomes

das ist ja mal wieder klar, kaum benutze ich metalog, haust du hier so'nen klasse link zum syslogd raus. ;)

der link ist echt klasse. :)


Gruß HangLoose