2016年2月23日火曜日

SATA Rev.3.3

I just read the news about SATA Rev. 3.3


SATA-IO Expands Supported Features in SATA Revision 3.3 Specification

I don't mention about what's updated here, but I think "power disable" is a good feature.
SATA drive itself supports hot plug, but  without any mechanics, you need to pull the drive with the condition "power is still supplying". This should increase the risk of breakage, since when you pull the drive, drive doesn't have the way to control itself, head and still spinning. And possibility to heads touch to the media.

Of course, you could send command to stop the spinning even under current specification.  But its purpose is just for power saving. So if system need to access to the drive, system will start spinning of the drive. I can't say it's never occurred during you send this command to HDD then walk in to the place which HDD is used.

I think it's nice update.


To be continued,
Spike.

2016年2月19日金曜日

Seems TP-Link started lock down their firmware

I could hear some crying voice in this morning. Mostly that's because of below kind of issue.


http://ml.ninux.org/pipermail/battlemesh/2016-February/004379.html

https://www.reddit.com/r/technology/comments/46c3tx/tplink_begins_router_lockdown_due_to_fcc_proposed/

Some quotes here,

 Camille09:28:15 pm Right, due to FCC

Adam Longwill09:28:50 pm Thank you very much. Can you explain why the
WDR3600 appears to be locked down? Is it possible that your list is not
totally updated?
And do you have a method or avenue that people who wish to use other
firmware have?

Camille09:34:02 pm Yes, wdr3600 as dual band wifi router, is also locked
down. And there is no other way to use other firmware. Sorry for that

Fucking hell. The FCC fucked up big time on this issue and now generations of routers are completely ruined.

So what was happened in router world is here. There is alternate firmware for router. Such as open-wrt,  tomato or dd-wrt. Here, I'll call them as "open source firmware". And some company purchase the router of Asus, TP-Link, netgear, Buffalo, etc. Then flash it to open source firmware and customize it as they want. Then provide customized router to their customer or use for their purpose.

But this time, TP-Link started to prevent to flash to those kind of open source firmware. we call this as "lock down to router". What's this mean? this means, those users can't use open source firmware anymore on the TP-Link router. And it means their business will be stopped in worst case. Because they can't produce their product for their customer.

Why this related to FCC? FCC is now issuing the new rule. And in that rule, FCC is requesting to manufacturer to prevent to emit the illegal RADIO output. This contains power of RADIO and frequency of RADIO. So FCC doesn't ask to manufacturer to prevent to flash to open source firmware directly. But on most of the open source firmware, RADIO power or frequency is customize-able (because, there is a driver source code!). so what manufacturer can do to follow the FCC's request is lock down their router. Just prevent to be flashed to open source firmware.

of course, there is another way to achieve FCC's requirement. If power of RADIO and frequency of RADIO is decided by hardware, such as read the configuration from SPI, or using e-Fuse, maybe possible. But my view, it's difficult to have the restriction by hardware level.

So just my view, but other competitors will follow this decision. Asus, Netgear, Linksys will lock down their firmware on their router in near future.


So far, if you want to customize your router, I have 1 answer.

I've been suspected this situation. So to avoid my business risk, I studied about DD-WRT-NXT product. Seems it's customize-able, but WiFi-driver is provided by binary. I can't modify it. Also it's already have the lock down scheme. When I build a new firmware, I need to signing the firmware before applying. router doesn't allow the firmware before signing.
I'm feeling as long as I use DD-WRT-NXT product for my business, I'll not be affected by this FCC regulation update.


 Hope everybody will find any solution soon.


bad fortune sneaks to you silently, and suddenly appeared.
Spike.

2016年2月13日土曜日

Firmware Update : Motorola Moto 360 2nd



 I've been having a Moto 360 2nd, and using it for daily life. Today, I got below message suddenly.

That message is written in Japanese, but  basically what he is saying is "Ready to go for firmware update. Swipe to left to install new firmware."

It's very rare, I didn't have same experience for last 4 month, this means when I purchase this to until this morning. I decided to record the firmware update sequence. Just because...
 

Part of the movie is forwarded to shorten the time. it's took about 10 minutes to complete the firmware update. And most of the part is lazy, boring, because just waiting for bar reaches to right side. Or watching some moving object.
Anyway firmware update was successfully done.

So far the issue is only 1, I don't know what's improved by this firmware update. I tried to get that information by google, but couldn't. I hope, it doesn't contain the bug such as consume the battery more than before...



Today I felt a new wind(maybe...)
Spike.

2016年2月11日木曜日

TeraStation TS5000 : Install plex, but failed

I tried to install plex on TS5000. I just enabled root accessibility on this device by below.
http://wind-spike.blogspot.com/2016/02/terastation-ts5000-how-to-obtain-root.html

First, I tried to check what system is it?
     root@TS5200D57A:~# uname -a
     Linux TS5200D57A 2.6.39.4-atom_usi #1 SMP Tue Dec 22 09:25:48 JST 2015 x86_64 unknown
Seems like I should choose anyting 64bit binary.


Next, I moved to plex download page. And choose computer and download the binary for ubuntu 64bit.

     # wget https://downloads.plex.tv/plex-media-server/0.9.15.2.1663-7efd046/plexmediaserver_0.9.15.2.1663-7efd046_amd64.deb

And then just try to install by dpkg command.
    # dpkg -i plexmediaserver_0.9.15.2.1663-7efd046_amd64.deb

I found that when I install this package, adduser, start and stop command is the issue.
So I added below trick on my TS5000.
     # addgroup plex
     # adduser -S -s /bin/bash -h /var/lib/plexmediaserver -G plex plex

     # echo "" > /sbin/apt-key
     # chmod +x /sbin/apt-key

     # echo "" > /sbin/start
     # chmod +x /sbin/start

     # echo "" > /sbin/stop
     # chmod +x /sbin/stop

This trick is basically just ignore the error in the postinstall script. TS5000 uses busybox so doesn't have the expected argument on adduser command.
Doesn't have apt so, ignore apt-key, not the system.d so ignore the start and stop command.

As a result of above, I could successfully install deb package anyway.

But when I execute the binary it says,
     # /usr/sbin/start_pms
     6 3000 /root/Library/Application Support
     8192
     ./Plex Media Server: error while loading shared libraries:
     /usr/lib/plexmediaserver/libboost_system.so.1.59.0: ELF file OS ABI invalid

sounds like plex doesn't like this kernel version.
So far I don't have a solution to fix current situation.


To be continued
Spike.

2016年2月6日土曜日

TeraStation TS5000 : How to obtain the root privilege

Here is the note to how to obtain the root privilege on the TeraStation which is provided by Buffalo.
All procedure is shown in below movie.






Procedure is very easy.
  1. Connect LCD and keyboard to TeraStation. And check that your LCD and keyboard works properly with TeraStation.
  2. Shutdown the system manually.
  3. Connect USB flash to USB port of TeraStation. which is a bootable USB. Here I used Knoppix.
  4. Get into the BIOS menu. And configure to boot from USB device. By this result, your system will boot as normal linux system instead of TeraStation system.
  5. logging into console of linux. If your user is not root when you login to linux system, you need to become root user. Here I used "sudo -s" command.
  6. Confirm that all HDD devices are recognized on your system.
    Note : if linux version is old, possibly neccesarily driver is not exist. Then you couldn't see any HDD device on that system. In that case, I recommend to use another linux distribution.
  7. Assemble RAID which are used as system volume on TeraStation. You can assemble those volume by sdx1 and sdx2 of the HDD which used on TeraStation.
  8. As a result of assemble, you'll be able to see md0 and md1. md1 is the target RAID volume. you need to mount this volume. Here, I mounted as "RAID-array1".
  9. move to /RAID-array1. then modify ./etc/shadow to change password of root user as known password. Here, I just copy the line of "admin" user. And then change its user name to "root". By this result, password for "root" user becomes same password to "admin" user.
  10. sync and unmount the mounted RAID devices. then reboot the system as TeraStation system.
  11. when console will be displayed, now you can login to TeraStation system as root. username and password will be "root" and "password". "password" is a default password of "admin" user.
  12. I recommend to you to change the password of "root" user to different string for your security.


When you get root privilege, you'll be able do various things. For example, TeraStation itself doesn't support plex server functionality. But if I could get proper binary, I could run it on TeraStation.
Modify the system of TeraStation, add owncloud, anything possible.
There seems telnet command is existed. So you can run telnet and access via telnet remotely.


TeraStation is a compact storage platform. So it'll be better to use PC server type computer, if you could do the things you want to do on this hardware. Now you have a freedom.




Swimming bird, now you have a freedom.
Spike.

Review - dashboard cam : DP VIDEO DVR135W

I've been interested in the dashboard cam. And I found good price one at Fry's. So purchased and tried.


Here is the box. As you can see, price is downed at the store. (^^

Here is the spec of camera. HD, night vision, micros SD. Seems very normal specification.

Here main unit. You can put it on the front window. and ...

You could see what's recorded now by this small monitor.

From this side, you could see USB connector. This connector is used for power supplying and take the movie out from camera.

Here is the sample movie which I took by this camera. it's not bad. if you want to use this as a dashboard cam, it's enough.



As a conclusion, I returned this camera to Fry's. Why? it doesn't support over write recording. When it fill up the capacity of SD card, it's stopped to record. What I expected is over write recording. From this point, this doesn't match to my expectation. So returned.
If you want to have anyhow dashbard cam, I think this camera is good. cheap, easy to use.
Oh, but I need to mention about the price, when I check the amazon, amazon sells this camera cheaper than Fry's. This is another reason I return this unit to Fry's. Please be carefull when you purchase this kind of dash cam.

If I put the score to this product, I put 60 out of 100. I recommend, but you should know there is a better camera than this. You can't expect to this product much, because of its cheap price.

Here is the link to product page on Amazon.




Recording the contents what you're seeing is interest idea.
Spike.


DD-WRT-NXT : How to configure web filtering

I just updated the movie on YouTube. it describes about how to configure web filtering on DD-WRT-NXT.




On this movie, describing about DNS based web filtering. So if you want to block the access to something bad for your family, you could block the access by this method.
It's described in movie, but this method doesn't cover the accessing method such as input IP address directly on browser.

Only below command you need to execute on the console of DD-WRT-NXT to block the access.
     uci add_list dhcp.@dnsmasq[0].address=/yahoo.com/0.0.0.0
     uci commit dhcp
     /etc/init.d/dnsmasq restart

This is basically when client try to ask the IP address of yahoo.com, router answers "hey, it's 0.0.0.0". So client can't get the IP address, then can't access to specified URL.

But as you can see, if client uses external DNS server such as google DNS (8.8.8.8), client still can get IP address of blocked url. To prevent this hole, you need little more configuration.

Below is the command to prevent the access to external DNS server.
     uci add firewall redirect
     uci set firewall.@redirect[0].src=lan
     uci set firewall.@redirect[0].proto=tcpudp
     uci set firewall.@redirect[0].src_dport=53
     uci commit
     /etc/init.d/firewall restart

This command add the rule for firewall (on linux, iptables), to redirect to router itself if he get the packet which destination port is 53 (DNS). So after this configuration, client can't send the DNS resolve request over the router.

It would be great if this contents helps you to have a healthy life.



Tomorrow is another day!
Spike.

Notes :
referred page : http://dd-wrt.com/nxt/wiki/doku.php?id=howto:use_cases:dns_blocking

2016年2月3日水曜日

DD-WRT-NXT : How to configure WAN failover


I just updated the movie on YouTube. it describes about how to configure WAN failover on DD-WRT-NXT.





On this movie, just describes about how to switch WAN interface to other port. But this is necessarily knowledge to realize WAN failover.

As described in movie, it uses same logical interface for WAN connection, eth0.2. But depends on your network design, you could use another logical interface such as eth0.5.
And you need to implement the logic how fail over the interface. Maybe you need to send keep alive, or pinging to internet server. But again, completely depends on your design.

And here is the command which I'm using in the movie.
To use original WAN port and disable one of LAN port.
     uci set network.vlan_lan.ports='0 1 2 6t'
     uci set network.vlan_wan.ports='4 6t'
     uci commit
     /etc/init.d/network restart

To use alternate WAN port and disable original WAN port.
     uci set network.vlan_lan.ports='0 1 2 6t'
     uci set network.vlan_wan.ports=‘3 6t'
     uci commit
     /etc/init.d/network restart


If you need my advice or comment, please contact me.

追伸:
キャラを間違えて、英語で投稿してしまいました。。。
日本語にて情報が必要な方いらっしゃいましたら、お気軽にコンタクトしてください。


To be continued.
Spike.