the first part of a connection. If you're not sure, the best thing to do
is telnet to your ircd from your shell, e.g.:
- [andy@fullers hopm]$ telnet porkscratchings.someserver.org 6667
- Trying 207.8.219.202...
- Connected to porkscratchings.someserver.org.
+ [miwob@svn ~]$ telnet irc.ircd-hybrid.org 6667
+ Trying 74.208.44.181...
+ Connected to irc.ircd-hybrid.org (74.208.44.181).
Escape character is '^]'.
- :porkscratchings.pa.us.someserver.org NOTICE AUTH :*** Looking up your hostname
- :porkscratchings.pa.us.someserver.org NOTICE AUTH :*** Checking Ident
- :porkscratchings.pa.us.someserver.org NOTICE AUTH :*** Got Ident response
- :porkscratchings.pa.us.someserver.org NOTICE AUTH :*** Found your hostname
+ :irc.ircd-hybrid.org NOTICE * :*** Looking up your hostname
+ :irc.ircd-hybrid.org NOTICE * :*** Checking Ident
+ :irc.ircd-hybrid.org NOTICE * :*** No Ident response
+ :irc.ircd-hybrid.org NOTICE * :*** Found your hostname
Just try to pick something in the first line of IRC output (for efficiency
reasons).
HOPM (Hybrid Open Proxy Monitor) is an open proxy monitoring bot designed for
Hybrid based ircds. The bot is designed to monitor an individual server (all
servers on the network have to run their own bot) with a local operator {}
-block and monitor connections. When a client connects to the server, HOPM will
-scan the connection for insecure proxies. Insecure proxies are determined by
-attempting to connect the proxy back to another host (usually the IRC server in
+block and monitor connections. When a client connects to the server, HOPM will
+scan the connection for insecure proxies. Insecure proxies are determined by
+attempting to connect the proxy back to another host (usually the IRC server in
question).
HOPM is written ground-up in C language, concept derived from wgmon. It
botnick fdstat -- Output some into about file descriptors in use.
Also if several HOPMs are present in one channel they will all respond to !all,
-for example !all stats (fixed in BOPM 3.1.0).
+for example !all stats.
-Rehashing HOPM
+Rehashing HOPM
--------------
A /kill to hopm will cause the process to restart, rehashing the configuration file
- bugs@ircd-hybrid.org
* IRC contact:
- #ircd-coders on irc.ircd-hybrid.org
-
-Credits
--------
-
-Please see the CREDITS file.
/*
+ * Hybrid Open Proxy Monitor - HOPM sample configuration
+ */
-HOPM sample configuration
-
-*/
+/*
+ * Shell style (#), C++ style (//) and C style comments are supported.
+ *
+ * Times/durations are written as:
+ * 12 hours 30 minutes 1 second
+ *
+ * Valid units of time:
+ * year, month, week, day, hour, minute, second
+ *
+ * Valid units of size:
+ * megabyte/mbyte/mb, kilobyte/kbyte/kb, byte
+ *
+ * Sizes and times may be singular or plural.
+ */
options {
/*
};
-IRC {
+irc {
/*
* IP to bind to for the IRC connection. You only need to use this if
* you wish HOPM to use a particular interface (virtual host, IP
* The username and password needed for HOPM to oper up.
*/
oper = "hopm operpass";
-
+
/*
* Mode string that HOPM needs to set on itself as soon as it opers
* up. This needs to include the mode for seeing connection notices,
* commands. HOPM will also print messages in these channels every
* time it detects a proxy. Only IRC operators can command HOPM to do
* anything, but some of the things HOPM reports to these channels
- * could be soncidered sensitive, so it's best not to put HOPM into
+ * could be considered sensitive, so it's best not to put HOPM into
* public channels.
*/
channel {
* proxies or other forms of IRC abuse. By checking against these blacklists,
* HOPMs are able to ban known sources of abuse without completely scanning them.
*/
-
-OPM {
+opm {
/*
* Blacklist zones to check IPs against. If you would rather not
* trust a remotely managed blacklist, you could set up your own, or
* target_string is matched, or if at least max_read bytes are read from the
* connection, the negotiation is considered failed.
*/
-
scanner {
/*
* user {} blocks to decide which users get affected by which
* scanners.
*/
- name="default";
+ name = "default";
/*
* HTTP CONNECT - very common proxy protocol supported by widely known
*/
timeout = 30 seconds;
- /*
+ /*
* Target IP to tell the proxy to connect to
- *
+ *
* !!! THIS MUST BE CHANGED !!!
*
* You cannot instruct the proxy to connect to itself! The easiest
*/
target_port = 6667;
- /*
+ /*
* Target string we check for in the data read back by the scanner.
* This should be some string out of the data that your ircd usually
* sends on connect. The example below will work on most
*/
/*
- * Usually first line sent to client on connection to ircd.
+ * Usually first line sent to client on connection to ircd.
* If your ircd supports a more specific line (see below),
* using it will reduce false positives.
*/