acutally, ive found 1 problem....
the target string is enabled, however the second target string (the NOTICE AUTH " one isnt.
in my file i was sent to me that they use for the linux bopms, the second target string specifys a server name, well if the bopm is scanning all connections, wouldnt that fail to work properly as we have 11 servers, 9 open to public...
Code: Select all
/* 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.
*/
# target_string = "*** Looking up your hostname...";
/* Some ircds give a source for the NOTICE AUTH (bahamut for example).
* It is recommended you use the following instead of the generic
* "*** Looking up your hostname..." if your ircd supports it.
* This will reduce the chances of false positives.
*/
target_string = ":Server.ChatUniverse.net NOTICE AUTH :*** Looking up your hostname...";
thats the linux, heres the win32
Code: Select all
/* 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.
*/
target_string = "*** Looking up your hostname...";
/* Some ircds give a source for the NOTICE AUTH (bahamut for example).
* It is recommended you use the following instead of the generic
* "*** Looking up your hostname..." if your ircd supports it.
* This will reduce the chances of false positives.
*/
# target_string = ":server2.ChatUniverse.net NOTICE AUTH :*** Looking up your hostname...";
i commented out the second one on purpose when i configured it becuz it failed to work, now i think its becuz the servers doesnt match the server name present.
also on a side note, it seems the first notice of all our servers are
<- :ChatUniverse.net NOTICE ^White_MAgic6 :*** If you are having problems connecting due to ping timeouts, please type etc etc
can i use a regex for that? like .+ to fill in the rest since it always changes or?
)
