diff --git a/_posts/2009-02-02-asus-wl300g.md b/_posts/2009-02-02-asus-wl300g.md
index 7552f53..8ceb201 100644
--- a/_posts/2009-02-02-asus-wl300g.md
+++ b/_posts/2009-02-02-asus-wl300g.md
@@ -36,8 +36,8 @@ So there has to be some sort of checksum which tells the router whether the firm
 
 Therefore I compared the two files `dd-wrt.v23_asus.trx` and `dd-wrt.v23_generic.bin` and voilà: Besides the few bytes at the end of the file, there were 4 additional bytes different at position `0x08`. This HAD to be the checksum. The remaining question was, from which bytes it was calculated. Since the seemingly compressed data began at `0x28`, I tried from there to the end and used [Hex-Workshop](http://www.hexworkshop.com/) to calculate different checksums, but nothing matched what was in these 4 bytes. The next try was from `0x10` but also no match. Then I tried starting directly after the checksum in the header, from `0x0c` and bang: The CRC32 checksum matched that in the header.
 
-![Hex Workshop Screenshot](hexworks.png)
+![Hex Workshop Screenshot]({{ site.url }}/assets/hexworks.png)
 
 So I calculated the CRC32 of my modified file and changed the header - and now I could upload the DD-WRT file using the normal firmware upgrade of the original firmware. After installing v23, you can easily update to v24 using the DD-WRT web interface.
 
-![DD-WRT Version Info](ddwrt.png)
+![DD-WRT Version Info]({{ site.url }}/assets/ddwrt.png)
diff --git a/assets/ddwrt.png b/assets/ddwrt.png
new file mode 100644
index 0000000..d7a9649
Binary files /dev/null and b/assets/ddwrt.png differ
diff --git a/assets/hexworks.png b/assets/hexworks.png
new file mode 100644
index 0000000..a7a0290
Binary files /dev/null and b/assets/hexworks.png differ