[DEBUG] In switchmode, migration debug
If migration occurs and associated ip address does not respond in
local, the ip packet is forwarded to controller. IPOP controller
used to try to forward it and made an exception error. Now if
ip packet that used to be local instance is simply discarded and
let local arp request message is produced. Then finally, arp local
 is invalidated through remote arp reply message.
Merge pull request #16 from kyuhojeong/debug

[DEBUG] In switchmode, migration debug
remove pyc file
Merge pull request #17 from kyuhojeong/rm_pyc

remove pyc file
When ipop run in switchmode standalone, it does not flood arp_request

Add logic on flood remote arp_request message, when it is standalone
switchmode.
Merge pull request #18 from kyuhojeong/standaloneswitch

When ipop run in switchmode standalone, it does not flood arp_request.
[DEBUG] Unknown destination packet try to access arp_table
When unknown destination packet is forwarded to controller. It
tries to access ARP table even though non-switchmode.
Merge pull request #19 from kyuhojeong/debug_arp_table_access

[DEBUG] Unknown destination packet try to access arp_table
Merge pull request #20 from ipop-project/devel

v14.07.0 Release
[DEBUG?] add configurable bridge-ip field in switchmode

The bridge itself does not reply on ARP request that the host
machine of IPOP running cannot receive packet even though it can
send packet to any IPOP and IPOP associated instance. This solution
or work around is IPOP controller provides ARP reply message to
remote peers.
Merge pull request #21 from kyuhojeong/bridge-ip-hardcode

Linux bridge not respond to ARP request
a bug fix