[DEBUG] Packet is not forwarded to controller

Even if the transport is destroyed and the connection does not
exist in uid_map_, the packet is not forwarded to controller.
This error occurs when destination address exists in peerlist in tap
module and forwarded to tincan manager with non-zero destination uid.
In detail, after connection is destroyed, we still keep the ipv4-uid
mapping in tap peerlist and forward to tincan manager with its
previous uid. So I add logic in tincan manager to forward packet with
non-zero uid that does not exist in uid_map_.
Merge pull request #12 from kyuhojeong/forward

[DEBUG] Packet is not forwarded to controller
sdf
Log file detailing

Timestamp is added at the head of each log line.
I abandoned the previous apprach which replacing the talk_base
logging class.
This time, I used macro to replace LOG_TS with LOG with timestap.
To the best of my knowledge, libjingle does not provide wall time
clock utils, but only process or O/S clock tick. So CurrentTime class is
added in new file tincan_utils.
Forgot to add files

All LOG_F is changed to LOG_TS
remove unnecessary log message
if defined(LINUX) is added at timestamp logging
Merge pull request #14 from kyuhojeong/timestamp

Timestamp Log Detailing