Traceroute from Starhub 3G

Traceroute from my laptop using my phone as a 3G router on the Starhub mobile network. A few too many hops, don’t you think?
$ traceroute kef
traceroute to kef (106.187.43.133), 64 hops max, 40 byte packets
1 192.168.43.1 (192.168.43.1) 3.896 ms 2.715 ms 2.036 ms
2 10.208.2.84 (10.208.2.84) 49.258 ms 65.181 ms 82.768 ms
3 10.208.8.2 (10.208.8.2) 59.948 ms 53.263 ms 59.700 ms
4 10.208.8.90 (10.208.8.90) 60.001 ms 52.663 ms 61.582 ms
5 10.208.8.104 (10.208.8.104) 59.451 ms 56.034 ms 59.654 ms
6 10.208.8.138 (10.208.8.138) 59.887 ms 64.902 ms 114.044 ms
7 10.219.3.120 (10.219.3.120) 98.258 ms 51.076 ms 59.962 ms
8 * * *
9 203.116.251.226 (203.116.251.226) 126.892 ms 93.875 ms 99.586 ms
10 61.8.235.41 (61.8.235.41) 71.043 ms 76.005 ms 81.270 ms
11 203.117.190.85 (203.117.190.85) 91.075 ms 91.325 ms 57.604 ms
12 anutsi10.starhub.net.sg (203.118.3.162) 109.199 ms 90.446 ms 137.621 ms
13 203.181.102.193 (203.181.102.193) 141.191 ms 157.753 ms 149.250 ms
14 otejbb204.kddnet.ad.jp (118.155.197.130) 145.116 ms 145.219 ms 135.581 ms
15 cm-fcu203.kddnet.ad.jp (124.215.194.180) 144.386 ms 145.880 ms 145.979 ms
16 124.215.199.122 (124.215.199.122) 234.994 ms 143.375 ms 157.861 ms
17 kef (106.187.43.133) 163.984 ms 155.401 ms 151.273 ms

HTTP Probes

I recently decided to take a look at the HTTP requests I was getting. Well, at least those that returned a 404. You can take a look at it here. Not surprisingly, the most common attacks were at the most commonly used web applications such as phpMyAdmin, along with random stabs in the dark at specific certain URLs, e.g. /manager, /admin. I’ll probably step up my log monitoring from now on.

The file was generated by the following command in my lighttpd log file directory:
zgrep " 404 " * | grep -v robots.txt | cut -d" " -f7 | sort | uniq -c | sort -r > /root/404.txt