Unable to block access by enabling Username & Password requirement | Search |
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ |
◄ ► |
Author | Message | |||
Paul Benson New member Username: Pbenson Post Number: 1 Registered: 10-2011 |
About 3 weeks after providing other users our NowWAP server information for testing (around 6 devices), someone else began hammering our NowWAP instance which brings it to a constant 200 to 250 concurrent sessions. I decided to enable the username and password settings without any users as shown here to stop the unknown user(s): http://img401.imageshack.us/img401/4152/creds.png After applying this setting, stopping the NowWAP service, and starting it again, we continue to receive heavy traffic. Here is a screenshot after turning our WAP server on for only 60 seconds: http://img84.imageshack.us/img84/4622/traffica.png How can our NowWAP instance possibly be letting through this amount of inbound and outbound traffic within 60 seconds when a username and password are required and there are no users setup? | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3547 Registered: 08-2008 |
Hi Paul, When you're dealing with a test environment, it's hard to say. My guess is that it is a WSP connection-oriented client that is doing something odd. WSP connection-oriented sessions are allocated to a specific IP address and port. So even in a small limited environment, an errant client could create a lot of sessions. That is the only scenario that I can think of, but maybe there is something else I'm missing. I'd suggest enabling the WAPDEBUG.LOG, and sending that log to us so that we can troubleshoot further. To enable this log, manually edit the WAPGW.INI file, and under the [WAPGW] header, add Debug=Yes You can either post the log in reply here, or send it to nowsms@nowsms.com with Attention: Des on the subject line of your message. -- Des NowSMS Support |