Your first post shows 4 time outs, but not where. When you ping an address, the reply has only a certain amount of time to reply or the intial request dies out there, resulting in the time out. If you feel it is an Internet connection issue, try using tracert (Windows) to charter or google or pelican.
Example:
C:\Documents and Settings\Administrator>c:\windows\system32\tracert google.com
Tracing route to google.com [64.233.167.99]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms 192.168.0.240
2 3 ms 2 ms 2 ms 192.168.0.33
3 2 ms 2 ms 2 ms xxx.xxx.xxx.xxx
4 13 ms 12 ms 12 ms adsl-68-127-45-213.dsl.irvnca.pacbell.net [68.127.45.213]
5 11 ms 12 ms 11 ms dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]
6 10 ms 12 ms 12 ms bb2-g9-0.irvnca.sbcglobal.net [151.164.92.196]
7 13 ms 12 ms 12 ms ex2-p14-0.eqlaca.sbcglobal.net [151.164.243.170]
8 12 ms 12 ms 12 ms asn6327-shaw.eqchil.sbcglobal.net [151.164.249.202]
9 11 ms 19 ms 12 ms 216.239.46.180
10 23 ms 22 ms 22 ms 209.85.253.178
11 21 ms 22 ms 22 ms 209.85.243.123
12 74 ms 84 ms 79 ms 209.85.242.210
13 74 ms 74 ms 74 ms 209.85.243.116
14 77 ms 74 ms 94 ms 209.85.241.20
15 72 ms 72 ms 72 ms 209.85.241.23
16 82 ms 74 ms 72 ms 66.249.94.134
17 75 ms 84 ms 77 ms 72.14.232.74
18 72 ms 72 ms 72 ms py-in-f99.google.com [64.233.167.99]
Trace complete.
If any of the lines came back with *
17 * * * 72.14.232.74
You know that there may be a problem with a router out there...
The second post is normal. Your router ha a built in firewall and logger and is reporting the addresses out there are actively 'probing' your connection. Happens all the time and 'ping' is widely used, as it usually gets ignored by sys admins - unless they notice a huge volume coming from one or more sources.
You can see what your eternal I.P. is, by going to
www.whatismyip.com. If it matches your third post, then it is your I.P., but your service is probably dynamic, so the number will change from time to time.