diff --git a/content/u/ipv4doublenat.png b/assets/u/image/ipv4doublenat.png
similarity index 100%
rename from content/u/ipv4doublenat.png
rename to assets/u/image/ipv4doublenat.png
diff --git a/content/u/ipv4nat.png b/assets/u/image/ipv4nat.png
similarity index 100%
rename from content/u/ipv4nat.png
rename to assets/u/image/ipv4nat.png
diff --git a/content/u/ipv6direct.png b/assets/u/image/ipv6direct.png
similarity index 100%
rename from content/u/ipv6direct.png
rename to assets/u/image/ipv6direct.png
diff --git a/content/u/blog/how-ipv6-can-help-protesters-in-honk-kong/contents.lr b/content/u/blog/how-ipv6-can-help-protesters-in-honk-kong/contents.lr
index 6292ac1..b0bb663 100644
--- a/content/u/blog/how-ipv6-can-help-protesters-in-honk-kong/contents.lr
+++ b/content/u/blog/how-ipv6-can-help-protesters-in-honk-kong/contents.lr
@@ -45,14 +45,14 @@ have a public IPv4 address. However when the number of devices began
 to exceed amount of officially available IPv4 addresses, NAT was
 introduced and it works as follows:
 
-![IPv4 NAT](/u/ipv4nat.png)
+![IPv4 NAT](/u/image/ipv4nat.png)
 
 Many devices are hidden behind one Public IP address. So for a phone
 to communicate with another phone, it needs to connect via a
 central, publicly available IPv4 server. So in the end, the complete
 picture looks as follows:
 
-![IPv4 Double NAT](/u/ipv4doublenat.png)
+![IPv4 Double NAT](/u/image/ipv4doublenat.png)
 
 
 ## How IPv6 solves the problem
@@ -62,7 +62,7 @@ So every device, every smart phone, every alarm clock, every computer
 can have a public IP address. Because every device can have a public
 IPv6 address, they can communicate directly with each other:
 
-![IPv6 direct connections](/u/ipv6direct.png)
+![IPv6 direct connections](/u/image/ipv6direct.png)
 
 ## How to communicate with IPv6?