Registered a URL and setup a forum as the IPCam stuff really needed its own site vs my irregular blog posts about IPCam hacking at

Author Topic: 2 Problems with Wanscam AJ-C2WA-C118 and AJ-C0WA-C116: Wifi and Scheduler  (Read 16680 times)

May 28, 2012, 05:40:55 am

I bought these 2 cams Wanscam on lightinthebox website on may 2012.

I have the same problem on the both and I'm asking to me if the problem is in the firmware or Web ui:

The versions out of the box are:
Device Firmware Version
Device Embeded Web UI Version

- First: webcam can't connect on my wifi network. I've  verified more times all parameters, reboot many times. After a lot of searchs, I think that webcan can't support Wifi WPA TKIP. ?
My wifi network is secured by WPA - TKIP. In scanning wireless network I can't see my network.. And When I set manually parameters, no connection too. Also I've remarked that some caracters are not correctly displayed after setting on the web interface; exemple: the beginning of my keycode WPA is:
8X>|q%WP+LOQm++u  and after 'submit' it's display:  8X>|q} LOQm  u

Very strange isn't it?
So if you have an idea you are welcome ...
I've already submit the case on the Wanscam support but any response (2 weeks )
And I try to find a new firmware and Web ui version on the web. but I'am not sure that the file lr_cmos_0_41_2_46 found on (madmox)  is for my webacm's models. Also in Foscam website I've found some news versions of firmware and web ui, but also I don't sure that the model is the same..
And on these webcam we can't backup the origianl firmware, isn't it?

- Second:
In Alarme Service Settings, I want tu use the scheduler to activate / unactivate the motion detection.
But whatever the time slot selected or unselected, the motion detect is already activate...
I think also that an upgrade of the web ui version should resolve the problem.
What do you think?

Thanks for your help

  • No avatar
  • *****
May 29, 2012, 04:28:42 am
for the wifi problem:

most ip-cams can only use US channels 1-11 not european 12 & 13

wpa tkip is ok but don't use special characters since webui, wpa-supplicant and router might use different code table.

a quick board search would have pointed you to this post regarding fostar utility.
« Last Edit: May 29, 2012, 04:33:33 am by schufti »

May 31, 2012, 04:42:53 am
Hello schufti

thank you for your help

My Wifi's channnel is 11, so no problem with this.

And if I change the keycode of the secure wifi to unuse special characters , I should change keycode on all my devices (about 12) and security network should be less. I don't like it...
Is there another solution to set the keycode in webcam?

I don't understand what is fostar utility.. What about it?

  • No avatar
  • *****
May 31, 2012, 06:04:35 am
sorry, the comment about fostar slipped into the wrong answer ... this is what happens if you spend too much time in these forums.

no, security will not be less if you use special characters that are common in both code-sets, but this is trial and error. I would avoid all of the quote / tick characters, ampersand, pound (UK, not #) and paragraph. And if you haven't changed the code for a long time, it would be a good oportunity now.

I wouldn't try fostar fw on WanScam product. But yes, you are able to backup your original fw. see the thread about firmware recovery method 2

user madmox updated his WanScam with "other" firmware that seems to work fine. look in thread "submitting new firmware"
« Last Edit: May 31, 2012, 06:30:54 am by schufti »

June 06, 2012, 05:11:02 am
Hi everybody

Just to tell that problems are resolved . It can be useful for someone:

- Wifi: indeed some caracters are not interpreted by the web ui: the '%' and the '+' present in the secure keycode are modified when saving. So I have to replace them by '!' and '_' and then the secure keycode is well saved and the webcam could connect to wifi network..

- Scheduler: in fact there is a difference of one hour between the real time and the time of the detection and then the time of picture sent by mail. Even if parameters you set in the time fieds. I set GMT +1 Paris and for the serveur NTP. the date and time is good on OSD and on the web interface but, the detection begin one hour earlier than set in schedule...
So now i known it and I do with this...

Thanks to Schufti to find the track for the Wifi ..  ;)