It looks like a user has already voted, when in fact they haven't

I'm experiencing an issue where it seems like users have already voted on a node, when in fact they haven't. To be more specific, I'm using the rate module to assign numeric 'up/down" votes to certain nodes. However, even when first time visitors access the site, they're presented with a "You voted +1/-1" message.

I took a look in the votingapi_vote table and noticed that the vote_source column is storing private ip's.

Here's my query results:

mysql> select * from votingapi_vote;
+---------+-------------+-----------+-------+------------+------+-----+------------+----------------+
| vote_id | entity_type | entity_id | value | value_type | tag | uid | timestamp | vote_source |
+---------+-------------+-----------+-------+------------+------+-----+------------+----------------+
| 1 | node | 427 | 1 | option | vote | 37 | 1345844392 | 192.168.32.179 |
| 8 | node | 262 | -1 | option | vote | 37 | 1346286817 | 192.168.32.179 |
| 9 | node | 96 | 1 | option | vote | 37 | 1346287547 | 192.168.32.179 |
| 10 | node | 4534 | 1 | option | vote | 1 | 1357841195 | 192.168.33.157 |
| 11 | node | 220 | 1 | option | vote | 1 | 1357841227 | 192.168.33.157 |
| 12 | node | 4593 | 1 | option | vote | 1 | 1357841237 | 192.168.33.157 |
| 16 | node | 21 | 1 | option | vote | 37 | 1357842436 | 192.168.33.157 |
| 17 | node | 219 | 1 | option | vote | 0 | 1357844177 | 192.168.34.88 |
| 18 | node | 36 | 1 | option | vote | 0 | 1358974939 | 192.168.33.214 |
| 19 | node | 4561 | 1 | option | vote | 37 | 1358980162 | 192.168.33.157 |
| 22 | node | 36 | 1 | option | vote | 37 | 1359051297 | 192.168.33.157 |
| 24 | node | 4574 | 1 | option | vote | 37 | 1359054807 | 192.168.33.157 |
| 25 | node | 184 | 1 | option | vote | 96 | 1359056039 | 192.168.33.157 |
| 26 | node | 819 | 1 | option | vote | 37 | 1359061977 | 192.168.33.157 |
| 27 | node | 184 | 1 | option | vote | 0 | 1359075450 | 192.168.33.157 |
| 31 | node | 4540 | 2 | option | vote | 0 | 1359110443 | 192.168.1.67 |
| 33 | node | 4574 | 2 | option | vote | 0 | 1359112902 | 192.168.1.67 |
| 35 | node | 4568 | 2 | option | vote | 0 | 1359112946 | 192.168.1.67 |
| 37 | node | 4569 | 2 | option | vote | 0 | 1359112984 | 192.168.1.67 |
| 39 | node | 4576 | 2 | option | vote | 0 | 1359113027 | 192.168.1.67 |
| 41 | node | 4579 | 2 | option | vote | 0 | 1359113069 | 192.168.1.67 |
| 43 | node | 4577 | 2 | option | vote | 0 | 1359113093 | 192.168.1.67 |
| 45 | node | 4578 | 2 | option | vote | 0 | 1359113121 | 192.168.1.67 |
| 47 | node | 4587 | 2 | option | vote | 0 | 1359113151 | 192.168.1.67 |
| 49 | node | 4566 | 2 | option | vote | 0 | 1359113230 | 192.168.1.67 |
| 51 | node | 4555 | 2 | option | vote | 0 | 1359113396 | 192.168.1.67 |
| 53 | node | 4585 | 2 | option | vote | 0 | 1359113435 | 192.168.1.67 |
| 55 | node | 163 | 2 | option | vote | 0 | 1359113506 | 192.168.1.67 |

Shouldn't the module be storing public ip address instead of private? Has anybody else experienced a similar issue?