Home
ejabberd
ejabberd@conference.jabber.ru
Воскресенье, 20 марта 2011< ^ >
badlop установил(а) тему: www.ejabberd.im english room | March releases: exmpp 0.9.6, ejabberd 3.0.0-alpha-2, and Erlang/OTP R14B02
Конфигурация комнаты
Участники комнаты

GMT+3
[01:09:12] scippio вышел(а) из комнаты
[01:21:51] poopsack вошёл(а) в комнату
[01:22:03] <poopsack> hi
[01:22:25] <poopsack> can someone tell me how to query the ejabberd_service module for a particular user's origin IP address?
[01:26:10] poopsack вышел(а) из комнаты
[01:26:55] poopsack вошёл(а) в комнату
[01:27:13] <poopsack> I'm back
[01:27:15] <poopsack> psi crashed
[01:50:45] <poopsack> :(
[02:04:12] Christian вышел(а) из комнаты
[03:09:44] MBR вошёл(а) в комнату
[03:10:37] <MBR> poopsack - are you there?
[03:12:38] <MBR> [12:22:25 AM] poopsack: can someone tell me how to query the ejabberd_service module for a particular user's origin IP address?
the simplest way to this is to enable the admin web-interface in your ejabberd and then in the web interface
node -> the relevant ejabberd node -> online users -> at the top you will see the information you seek
[03:19:52] <poopsack> okay but I want to do automated proxy scanning
[03:20:06] <poopsack> so I have to be able to get that information out of the server
[03:20:22] <MBR> what is your goal - what are you trying to do?
[03:20:49] <poopsack> well I have lots of abusive clients connecting from proxies
[03:21:11] <poopsack> I want to be able to detect those proxies inbound when they connect to the server and ban them
[03:21:21] <poopsack> me sitting here for hours on end manually doing IP bans is a pain in the ass
[03:21:30] <poopsack> I have a proxy scanner ready to go
[03:21:39] <poopsack> I just need to know how to get IP info out of ejabberd
[03:21:58] <MBR> do you have access to the ejabberd.log file?
[03:22:07] <MBR> grep for the following line
[03:23:08] <MBR> grep "Accepted connection" ejabberd.log > iplist
[03:23:28] <MBR> thats the line thats has ip address when a user connects
[03:25:25] <poopsack> well that's a lousy way to do things but it at least solves my immediate problem
[03:25:27] <poopsack> thanks
[03:25:42] <MBR> though the ip addresses will be in a format
127,0,0,1    instead of   127.0.0.1
[03:25:47] <poopsack> I'm going to get this going then investigate writing a module that returns the info I need in a stanza
[03:26:27] <MBR> a global replace can fix that real quick though
[03:32:24] <poopsack> ugh
[03:32:41] <poopsack> it doesn't tell me which account was authenticated from that IP
[03:33:58] <MBR> yeah - well on that front lets have a look at ejabberdctl
[03:37:09] <MBR> ejabberdctl connected-users-info
[03:37:19] <MBR> run that command on the cmd line
[03:37:26] <MBR> in fact run this instead
[03:40:59] <MBR> ejabberdctl connected-users-info | awk '{print$1,$3}' > users-and-ips
[03:42:04] <poopsack> # ejabberdctl connected-users-info
Error: command "connected-users-info" not known.
[03:42:48] <MBR> you probabaly have to install a module that will allow you to have the command
[03:43:11] <poopsack> any idea what module that might be?
[03:43:16] <MBR> do you have this module installed
mod_admin_extra
[03:45:06] <MBR> install that module and you should be fine -
[03:46:12] <poopsack> cool
[03:46:14] <poopsack> installing now
[03:46:46] <MBR> Nice
[03:50:06] poopsack вышел(а) из комнаты
[03:51:58] MBR вышел(а) из комнаты
[03:54:30] poopsack вошёл(а) в комнату
[03:54:44] MBR вошёл(а) в комнату
[03:58:10] <poopsack> that's more workable than grepping logs.  thanks
[03:58:43] <MBR> youre welcome
[04:14:31] jameschurchman вошёл(а) в комнату
[04:53:47] jameschurchman вышел(а) из комнаты
[05:53:25] MBR вышел(а) из комнаты
[12:19:40] MBR вошёл(а) в комнату
[12:31:08] <MBR> how do i restrict a service in the service discovery to selected users?
[12:47:48] MBR вышел(а) из комнаты
[12:49:17] MBR вошёл(а) в комнату
[14:03:58] MBR вышел(а) из комнаты
[14:07:40] MBR вошёл(а) в комнату
[17:47:41] skinkie вошёл(а) в комнату
[17:48:14] <skinkie> I'm currently seeing that a lot of tree_calls are generated 'out of the blue'
[17:48:33] MBR вышел(а) из комнаты
[17:48:45] <skinkie> I'm currently seeing that a lot of tree_calls are generated 'out of the blue'
[17:49:13] <skinkie> i'm running in debugging mode
[17:49:39] <skinkie> and i don't see any other reference to this node
[17:49:44] <skinkie> other than a tree_call
[20:14:26] poopsack вышел(а) из комнаты
[20:15:11] poopsack вошёл(а) в комнату
[20:22:22] poopsack вышел(а) из комнаты
[21:39:08] skinkie вышел(а) из комнаты
[23:50:29] MBR вошёл(а) в комнату
Powered by ejabberd Powered by Erlang Valid XHTML 1.0 Transitional Valid CSS!