So yesterday morning I was sitting on my bed with a mug of tea reading The Register when there was a loud click and everything went an eerie sort of silent.
Riiiick! came a call from the living room.
Not me! I replied.
The click was our "disjoncteur", the main electricity trip switch. Built in 1968, if there is any sort of disturbance (within a tolerance of 650mA) that it doesn't like, nasty transients on the line (read: lightning strikes), or if we exceed the 12kW allocation that we are paying for (out in the countryside, one pays for a certain number of kilowatts, we were originally 6kW but this meant you couldn't have the water pump kick in when the kettle and fridge were on!)... anything that upsets it - CLICK!
Sometimes it happens for no discernible reason. I consider this a "mouse peed on the wiring" event. The usual "fix" is to push the button and turn everything back on again.
I noticed my lamp was dim. I also noticed the Pi and printer had started up. I went through - noting the Livebox was booting - and told her to turn it off.
After unplugging most things, I turned on the power long enough to probe the phase that the bedrooms were on. I wasn't going to waste time probing all of the phases, this was enough to indicate a serious problem:
I called the EDF fault line. There was no reported fault in our area. So I spoke to an engineer who patiently explained that I must check the disjoncteur to ensure that the thing hadn't tripped out. In return, I patiently explained that it was off, however when I turn on I'm only seeing 130V.
A few hours later two jolly guys arrived in a big blue truck.
They probed where I had probed and confirmed things were screwy. Never mind, these old disjoncteurs, you know... So he undid the EDF-only part and probed there. Oh... hang on...
So he undid the EDF-only (secured with a plastic crimp) holding the main supply fuses. He popped them all out and probed the incoming source. Two of the three phases were dead. Just as the house wiring would likely rise to ~380V if the neutral failed and the single phase would fail to tie relative to ground, if a phase fails the alternative is to try to spread the available power throughout the wiring. That's why I was only seeing ~130V. That's roughly 380V divided by three.
Well, at least this clears anything in our property, plus removes the excuse for anybody to arbitrarily try to pass off a Linky (so-called smartmeter) onto us.
One of the men suited up and took the cherry-picker up to the incoming lines, so see if the supply was okay (thus indicating a fault between the pole and the distribution box). The lines were not okay. Two phases down.
I took the other EDF man across the garden and said - your problem is probably over there - indicating the step-down transformer at a neighbouring farm. Or perhaps I should say the step-down transformer at a neighbouring farm that has a propensity for blowing up.
The men drove off and mom wondered why no other reports of power failures had been received. I told her about the Livebox, printer, Pi... Have you worked it out yet?
Okay, here's the thing. A filament lamp (regardless of technology) requires a certain amount of juice to make it work. If you wire a British (or French) light bulb into the American mains, it will glow dimly. If you do the reverse, it'll glow like burning magnesium until it fails. So if you turn your lights on, you might notice them being really dim. But look around the house, you'll probably see most modern gadgets working correctly. Do you have an iPad charger? Look at the bottom and you'll see it'll work on anything from 100-240V. My printer, likewise. These devices can be made for mass export with no difference whatsoever other than a country-specific power lead. The monitor that my Pi plugs into, says on the back,
100-240V ~0.9A / 50/60Hz. So all this tech stuff will still be working. With that in mind, would a person whose kettle or microwave is acting weird not look at the TV and TV decoder still functioning and not think that the kettle or microwave is at fault? It was half eleven on a weekday. August, fair enough, but I wonder how many French housewives would pop off the power distribution cover and prod around with a multimeter? That could explain why nobody else reported a fault in the time it took for the engineers to arrive.
The power failed just before eleven thirty. They finally had it all sorted by eight o'clock in the evening, including switching off the main high voltage line through dinner time. With that off, the entire town and all of the farms and everything connected would have been disconnected. Oh, wait, that went off at about half five. Whoo, right in the middle of milking time. Hope they had a genny to kick in and take over.
Turns out that an extremely unfortunate and largish bird either landed or took off and passed current through its body, creating an arc powerful enough to cook the bird and bring down one of the high voltage wires (either 11kV or 20kV, I forget). As a side effect, our wonky step-down transformer suffered. The low voltage was the transformer trying to cope with one of its inputs missing, I suppose we should be glad it didn't just take its default panic reaction - but then the bird had already blown itself up (poor men had to remove what was left of it from the line).
As a side effect, I'm quite pleased that the men repaired the transformer well. I'm seeing a good strong 230V on the mains. Normally it's closer to 218V. I wonder how long that'll last in the summer heat until it'll be time to invite the Photonic Induction man to say "aww, it's popped".
Cheap little webcam
The other day, a nearby supermarket was selling a motorised webcam for a "we want to shift this old stock" kind of price. It was a low-res VGA (640x480) model. I thought it might be interesting to hook this up so I could talk to mom one the phone at work while watching her do stuff. You know, like might be possible with Skype if you were able to call yourself (on different devices). Plus the motorised functions, I might hook it up in the eaves over the front door or something. Or otherwise, it might be nice to have it at the corner of the house to look across the front and down the side. I can't though, it struggles to maintain a WiFi connection in my room, never mind a solid stone wall further.
There was an HD model. It cost several times more. So I left it on the shelf.
It is essentially a cheap Chinese FOSCAM rip-off.
For the initial setup, I plugged the device directly into the Livebox. WiFi wouldn't work until the necessary stuff had been configured. The camera was rather tedious to set up because it insisted upon rebooting itself for Every. Single. Modification. It was worse than Windows 95.
Eventually I got there, and as expected with "Internet of Things", there are some issues to be aware of:
- The default username is "admin". The default password is "123456" (some other models have "admin" as the password). BE SURE TO CHANGE THIS.
- You can set up users who can view but not modify the settings. Be careful who you give access too, they can choose to hear the recorded audio.
- The device contacts the mothership. The MyMCL app can 'find' the camera by looking up its ID - so quite clearly the camera must send its ID (and its IP addresses) off to the mothership for storage.
You can disable this (look in settings under Manufacturer's DDNS), but you may find the app won't work if you do this.
- By default, the camera will attempt to punch a hole in your router's firewalling using UPnP. This means it will make itself accessible to the outside world. If you are a user that has no idea about NAT and address routing, then this may be useful. Just be aware that from the moment you turn it on, it may well be world-visible. You DID change the password, right?
You can disable the UPnP client (in settings under UPnP), but by the time you get there, it's likely already done it. I don't know if unticking this option undoes any association (because my Livebox has UPnP disabled).
- Absolutely DO NOT give the admin access password to people that do not need it. The camera divulges loads of information if you have the right password.
- Excuse the Germanic/Old English, but security in general is shit. Pretty much like most Internet of Things devices.
Review, sort of
There is an app. It is small. It asks for permissions that probably aren't necessary, but at least it doesn't go as far as wanting to read sensitive log data or contacts information. There is also a web interface built into the camera itself. As my Pi has laid claim to port 80, I have set the camera to respond to port 8080. Upon entry, you'll first be asked to enter the login name and password. Once you have done so, you'll see this:
The smartphone mode just gives a really simple streaming picture (MJPEG) with controls for up, left, down, and right.
The IE mode isn't worth mentioning. OCX control? Seriously?
The Firefox mode (which also works with phones and tablets), is the better option. Here, the controls look like this:
The controls at the top move the camera. The rest of the left are for configuring the video options. You can choose VGA (640×480) or QVGA (320×240) image sizes. The IR button is for turning the IR lights on and off. The arrows are for sweeping left and right, or up and down (continuously). The other buttons that look like a book and a pair of trousers (!) are for flipping the image horizontally or vertically (or both). This may be useful if the camera is mounted upside down in a dome.
For what it is worth, here is the image in its native size (the trees and fencing showing up the compression artefacts):
The camera supports having up to 16 preset locations defined. You can set one of these presets to be the 'home' position once the camera boots or reboots (settings, under PTZ).
The camera can transmit audio, but it is utterly horrible. I'm not sure whether it is over-amplified and over-compressed or what, but the best option is to simply not rely upon the microphone.
There is no option to disable the microphone. If you don't want anything to be heard, you'll need to void your guarantee and disconnect the thing the hardware way.
There is a speaker port, so you can apparently talk to your computer and the data will be sent back to the camera. I have not tried this.
In the settings, there is apparently the option to enable some sort of motion detection, and if there is an alarm event, to email you (a picture?) and/or upload picture(s) to an FTP server. I have not experimented with either of these.
The IR light is quite powerful. This is our loft. The beam of light is because there is a place where the sun can shine in between the roof and the wall. It shows up at sunset. I think it's a hole from where a roof beam used to be, but when the roof was redone in 18-something, the beams were put in different places. Anyway, that explains the odd light. The top picture, sunset in the loft with natural light, and then again with the IR light switched on. While IR makes the image black and white (obviously!), it is actually surprisingly powerful for a few little LEDs around the camera lens.
Playing with the API
Looking at the interface, once you have logged into the device (standard browser auth), you can call "login.cgi" to read who you are, because even though auth is used, pretty much every request to "do stuff" requires the username and password to be suffixed to the URL. So "login.cgi" returns the following:
"pri" is 255 for the administrator and 1 for a viewer. There's a third option (operator), but I don't know how that differs from one or the other of the previous choices.
Now, let's pull apart some of the controls. Essentially the camera provides a video stream that is a never-ending JPEG. You can get at it with the following:
Of course, amend the IP address, username, and password as applicable. And note passing the information in CLEAR TEXT. A clever idea over the public internet, no?
Switch to QVGA size:
The camera should reply with
To switch back to VGA, param=0 and value=0. If you are playing the video, the size will change automatically. At least, it does with Firefox.
Param=14, value=1 will turn the IR light off, while value=1 will turn it on. Yes, it seems back to front.
There are plenty of other options, but none that I have the time to pull apart tonight.
Yet another IoT security warning
get_status.cgi will return some fairly innocuous things that can identify the camera:
get_params.cgi script will drop the following juicy information:
Thankfully it is clever enough to stop at dev9_port for non-admin users. However admin level users can extract all of the information. And note that this includes the passwords in plain text, the WiFi security key, all of your email/ftp credentials (if you have them)...
It gets better. Keep reading.
If it is not bad enough that the session management is the absolutely genious idea of sending the user name and password with every GET request, in clear text no less, we can actually fail even harder than that.
Jeezuzz Christ. You're gonna want to sit down.
Trust me. Sit down.
Doing a port scan of the camera, three ports were open and listening. 8600, 8080, and 23. I don't know what 8600 is, probably some video interface for the naffness that is the OCX (I could WireShark it, but that means running IE, so I won't). 8080 is our webserver portal. That leaves 23.
It starts with a dead boring login prompt that says "(none)" because the machine has no identity.
So I try my name and password. No good.
Then I try admin and 123456. No good.
So, okay, let's try root and admin. Nope, not that either.
Wait, don't tell me... root and 123456.
Yup. That was it.
The username is root and the password is 123456.
No, wait, don't stand up. We fail harder than that. Because passwd is an unknown command. So the user data file that holds the login password is not only hardcoded to root/123456, there is no way (short of hacking the firmware directly) to be able to change this password.
So now that anybody can log into the machine, it's a bit of a doddle to get important information:
# cat /system/www/system.ini
Now I know you're extracting the urine. So there's this device, that has a bloody great backdoor (if it looks like a duck...), and a conveniently readable file from which can easily be read your device's MAC addresses (yellow), IP addresses (but that's no big deal, you already know that), the view-only user name and password (magenta), the freakin' admin name and password (red), plus the router's SSID and WiFi password (brown).
Holy hell, that's a whole heap of fail for a device so small.
Looking elsewhere with telnet, I can...
# cat /proc/cpuinfo
system type : Ralink SoC
processor : 0
cpu model : MIPS 24K V4.12
BogoMIPS : 239.10
wait instruction : yes
microsecond timers : yes
tlb_entries : 32
extra interrupt vector : yes
hardware watchpoint : yes
ASEs implemented : mips16 dsp
VCED exceptions : not available
VCEI exceptions : not available
So this would appear to be based upon the Ralink RT5350F; a 360MHz MIPS processor with 8MiB storage and 32MiB RAM.
The storage is laid out as:
Filesystem 1k-blocks Used Available Use% Mounted on
rootfs 3008 3008 0 100% /
/dev/root 3008 3008 0 100% /
/dev/mtdblock6 3072 2512 560 82% /system
/dev/mtdblock7 512 248 264 48% /param
The memory is:
# cat proc/meminfo
MemTotal: 29344 kB
MemFree: 10308 kB
Buffers: 1032 kB
Cached: 4472 kB
SwapCached: 0 kB
Active: 5672 kB
Inactive: 4084 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 4280 kB
Mapped: 1504 kB
Slab: 5316 kB
SReclaimable: 636 kB
SUnreclaim: 4680 kB
PageTables: 304 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
CommitLimit: 14672 kB
Committed_AS: 9504 kB
VmallocTotal: 1048404 kB
VmallocUsed: 2720 kB
VmallocChunk: 1044644 kB
And it can be a quick way to check WiFi network status:
# iwlist ra0 scanning
ra0 Scan completed :
Cell 01 - Address: 00:00:00:00:00:00
Frequency:2.437 GHz (Channel 6)
Quality=100/100 Signal level=-25 dBm Noise level=-92 dBm
Bit Rates:54 Mb/s
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
Cell 02 - Address: 00:00:00:00:00:00
Frequency:2.437 GHz (Channel 6)
Quality=76/100 Signal level=-60 dBm Noise level=-92 dBm
Bit Rates:54 Mb/s
And, finally, it is nice to see they are using an up to date Linux kernel that won't be susceptible to vulnerabilities. Haha, you think?
# cat /proc/version
Linux version 2.6.21 (root@mailzxh-desktop) (gcc version 3.4.2) #636 Fri Nov 16
10:03:21 CST 2012
It is a shame that the PTZ control does not offer any way to restrict its movement, because the camera head can rotate nearly 360°, you might prefer to allow certain areas to be seen but lock out others.
From the outside world, its security depends upon where you are. You can close the device off from prying eyes if you change the passwords and use a viewer-only level login. Unfortunately the passing of login information with every GET request means that you simply cannot access this device on a public AP. I have set up a VPN for situations like this, and places that don't allow VPNs, I switch to phone tethering. This still has problems because many western countries have politicians that are in favour of wholesale recording of web "metadata", and GET requests (the stuff you fetch) is metadata. Problem is, when the URL contains the login credentials, it then becomes sensitive metadata. So if you access your device remotely, don't use the admin login, use the visitor one.
From the inside (intranet), all bets are off. It is shamefully wide-bloody-open.
So, as is depressingly usual on Rick's b.log, it's an okay bit of low-budget hardware let down by abysmal software. Or rather, the software functions but it seems as if security (I feel sick writing that word) was sort of bolted on as an afterthought.
Some more time and attention to detail could have made a pretty nice little clone of the FOSCAM. Instead, it is about what you'd expect. On the other hand, it does actually work (and the IR range is impressive), so that's a step up from some cheap devices.
Please note that while I check this page every so often, I am not able to control what users write; therefore I disclaim all liability for unpleasant and/or infringing and/or defamatory material. Undesired content will be removed as soon as it is noticed. By leaving a comment, you agree not to post material that is illegal or in bad taste, and you should be aware that the time and your IP address are both recorded, should it be necessary to find out who you are. Oh, and don't bother trying to inline HTML. I'm not that stupid! ☺
You can now follow comment additions with the comment RSS feed. This is distinct from the b.log RSS feed, so you can subscribe to one or both as you wish.
|David Pilling, 12th August 2016, 01:34|
Interesting insight into how electricity works in rural France. Here of course it is common for each third house to run from one phase, occasionally if one phase goes down you can play at spotting who is on which phase.
Smart meters are on the way here - interesting that they work off the mobile phone network - what you have no signal where the meter is - yup they don't necessarily work for everyone.
|David Pilling, 26th August 2016, 18:14|
This and the later blog about the camera are enlightening. You've got a couple of missing photos of the loft on this page.
|Rick, 27th August 2016, 10:42|
Thanks for the report. Was working...um.... I'll look this evening.
|Rick, 27th August 2016, 18:36|
Weird. Firefox didn't want to show the images. Neither did Safari. So I downloaded them, opened them in my photo editor, resaved them, uploaded them, and now they work. <scratches head>
Thanks for reporting this.
|David Pilling, 31st August 2016, 18:33|
"resaved them, uploaded them, and now they work."
I use Chrome. I could easily have got an error message for you from the programmers console ctrl+shift J (similar in other browsers). But I just assumed they were missing.
|Steve Graham, 20th January 2017, 15:37|
I found your blog because I have an identical camera (except it's black) and did a port scan, and thus found out that it offers telnet.
I tried the user/pass combinations I'd created in the web UI but they weren't accepted, so I did an internet search to find the right ones.
"root/123456". Good grief.
|Steve Graham, 20th January 2017, 18:39|
Well, one good thing came out of it. I'd previously tried to use the FTP upload and found that it didn't work.
When I logged in to the camera, I found it's creating a temporary FTP script which tries to "cd /" before uploading the image.
My FTP daemon, pure-ftp, includes a chroot option to keep access within the user's home directory, so "cd /" now works.
|Rick, 27th February 2018, 19:41|
Thanks for the info about the cd / thing. I was wondering why trying to upload to my Orange website (uses FTP) kept failing.
That said - please read my blog entry of 2017/06/17, you might want to chuck the camera in the bin if it has the same horribly serious flaw...
List all b.log entries
Return to the site index
PS: Don't try to be clever.
It's a simple substring match.
Last read at 01:55 on 2020/07/06.
© 2016 Rick Murray
This web page is licenced for your personal, private, non-commercial use only. No automated processing by advertising systems is permitted.
RIPA notice: No consent is given for interception of page transmission.