News: This forum is now permanently frozen.
linktree m0n0wall Forum  >  m0n0wall Support (English)  >  Services  >  Captive Portal
linktree Topic: Captive portal doesn't work very well
Pages: [1]
Topic: Captive portal doesn't work very well  (Read 3561 times)
« on: April 10, 2011, 22:55:48 »
lalo *
Posts: 24
I have mounted a captive portal system on a Hotel for internet surfing by every room.
But i have a problem.
The system runs on a pentium 2 , 450Mhz with 64mb of ram i have 3 nic wan, lan, and lan2 for captive portal, the problem is that people start to surf and it works fine after half an hour everything stops work i dont now if its a problem on the configuration. If someone of you can idicate me the steps to check for finding the problem...

here are some logs


Last 50 captive portal log entries
Mar 22 21:33:23
LOCKWARNING: waited for lock for 3 minute(s)
Mar 22 21:33:23
message repeated 2 times
Mar 22 21:34:23
LOCKWARNING: waited for lock for 4 minute(s)
Mar 22 21:34:23
LOCKWARNING: waited for lock for 4 minute(s) - breaking lock!
Mar 22 21:35:27
LOGIN: accenture, 5c:ac:4c:53:f0:d7, 192.168.2.236
Mar 22 21:40:40
LOGIN: accenture, 5c:ac:4c:53:f0:d7, 192.168.2.236
Mar 22 21:40:40
CONCURRENT LOGIN - REUSING OLD SESSION: accenture, 5c:ac:4c:53:f0:d7, 192.168.2.236
Mar 22 21:54:32
TIMEOUT: zibi, 00:16:ea:72:22:6c, 192.168.2.201
Mar 22 22:05:37
TIMEOUT: accenture, 00:26:c6:78:0c:d6, 192.168.2.234
Mar 22 22:35:50
TIMEOUT: accenture, 5c:ac:4c:53:f0:d7, 192.168.2.236
Mar 22 23:05:07
LOGIN: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 22 23:05:20
LOGIN: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 22 23:05:20
CONCURRENT LOGIN - REUSING OLD SESSION: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 22 23:16:06
TIMEOUT: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 23 06:27:59
LOGIN: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 23 06:40:04
TIMEOUT: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 23 06:48:26
LOGIN: zibi, 00:16:ea:72:22:6c, 192.168.2.201
Mar 23 07:06:15
TIMEOUT: zibi, 00:16:ea:72:22:6c, 192.168.2.201
Mar 23 17:03:16
LOGIN: zibi, 00:16:ea:72:22:6c, 192.168.2.201
Mar 23 17:55:34
TIMEOUT: zibi, 00:16:ea:72:22:6c, 192.168.2.201
Mar 23 22:00:48
LOGIN: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 23 22:08:15
TIMEOUT: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 23 22:58:55
LOGIN: accenture, 5c:ac:4c:53:f0:d7, 192.168.2.236
Mar 23 23:17:45
LOGIN: accenture, 00:1f:3b:76:fd:0f, 192.168.2.247
Mar 23 23:18:03
LOGIN: accenture, 00:1f:3b:76:fd:0f, 192.168.2.247
Mar 23 23:18:03
CONCURRENT LOGIN - REUSING OLD SESSION: accenture, 00:1f:3b:76:fd:0f, 192.168.2.247
Mar 23 23:36:52
TIMEOUT: accenture, 5c:ac:4c:53:f0:d7, 192.168.2.236
Mar 23 23:44:22
LOGIN: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 23 23:45:55
TIMEOUT: accenture, 00:1f:3b:76:fd:0f, 192.168.2.247
Mar 23 23:49:57
TIMEOUT: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 24 06:38:00
LOGIN: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 24 06:52:47
TIMEOUT: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 24 18:15:26
LOGIN: zibi, 00:16:ea:72:22:6c, 192.168.2.201
Mar 24 18:41:30
TIMEOUT: zibi, 00:16:ea:72:22:6c, 192.168.2.201
Mar 24 20:40:00
LOGIN: zibi, 00:16:ea:72:22:6c, 192.168.2.201
Mar 24 21:40:43
TIMEOUT: zibi, 00:16:ea:72:22:6c, 192.168.2.201
Mar 24 22:13:58
LOGIN: zibi, 00:16:ea:72:22:6c, 192.168.2.201
Mar 24 22:23:00
TIMEOUT: zibi, 00:16:ea:72:22:6c, 192.168.2.201
Mar 24 23:06:09
LOGIN: accenture, 00:1f:3b:76:fd:0f, 192.168.2.247
Mar 25 00:06:43
TIMEOUT: accenture, 00:1f:3b:76:fd:0f, 192.168.2.247
Mar 25 06:40:19
LOGIN: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 25 06:48:23
TIMEOUT: accenture, c0:38:f9:bf:56:b7, 192.168.2.252
Mar 25 20:25:14
LOGIN: zibi, 00:16:ea:72:22:6c, 192.168.2.201
Mar 25 21:19:11
TIMEOUT: zibi, 00:16:ea:72:22:6c, 192.168.2.201
Mar 27 09:35:24
LOGIN: bruno, 00:26:4a:cf:4b:0f, 192.168.2.246
Mar 27 09:41:43
TIMEOUT: bruno, 00:26:4a:cf:4b:0f, 192.168.2.246
Mar 27 19:53:14
FAILURE: Super, 7c:c5:37:9a:9a:65, 192.168.2.195
Mar 27 19:54:07
FAILURE: admin, 7c:c5:37:9a:9a:65, 192.168.2.195
Mar 31 14:58:06
FAILURE: , 00:23:6c:8a:5d:02, 192.168.2.253
Mar 31 15:08:25
LOGIN: accenture, 00:23:6c:8a:5d:02, 192.168.2.253
« Reply #1 on: April 10, 2011, 23:14:29 »
lalo *
Posts: 24
What is that LOCKWARNING: waited for lock for..... message??
« Reply #2 on: April 11, 2011, 23:34:57 »
lalo *
Posts: 24
Please can someone help me??


Thank You All
« Reply #3 on: December 08, 2011, 21:32:53 »
knightmb ****
Posts: 341
It means the server has more users than it can process, hence the LOCK warning. You would need to move the authentication/management to a dedicated server I believe, check out these services which might be able to remedy your issue.  http://amaranthinetech.com/index.php?option=com_content&view=article&id=4&Itemid=8
Radius Service for m0n0wall Captive Portal - http://amaranthinetech.com
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines