Why is the world scanning me on port 61948?

[edit]***PROBLEM RESOLVED. SEE SECOND POST***[/EDIT]

Hey AO.

I was doing my regular surfing earlier, and the connection seemed a little lagged. As I sometimes do, I pulled up the router admin page and just scoped it out. In checking my incoming log, which is empty 90% of the time, I saw several IP addresses attempting to connect on port 61948 (and a few others). :eek:

I traced the IPs to California, Saudi Arabia and China. World-wide bot-net? Or proxies?

This has been going on an hour or so now. I could just release my IP on my router and wait for ten minutes and grab a new one, and that would (maybe) get rid of the incoming traffic. It's not really bothering me, as these ports aren't listening on any of my computers. But I am curious as to why I'm being targeted, and particularly, why on that particular port? :confused:

Any ideas?

Here's a screenshot: http://www.jeremydeanonline.com/temp...Nov12_2010.jpg
And some of the offending Source IPs:
76.175.253.19
119.6.59.170
92.96.114.9
116.47.88.76
222.186.24.192

I mean, I know that people perform scans all the time - is that what I'm seeing? Maybe I've just never caught one in progress on the router before. It seems to generate the log in "real-time" - meaning, when I click on "incoming log" it shows me only what's incoming for that instant, or maybe that 1 min interval/5 min interval/whatever.

Also, does anyone know how to "beef-up" the logging capability of a Linksys router... seems like you used to be able to log in to them in a UNIX environment. I'd like to record all incoming activity with a time and date stamp in a text file and have it stored to a hard drive on my network once daily. I guess I need to RTFM... :(

Anyway, thoughts, suggestions or criticisms are appreciated. Thanks!

Or how about I'm a jackass.

I have uTorrent configured for port 61948 on my Slack Server. Even though it's not running, I guess the tracker for files I've seeded still has me listed as a seed? So leeches are still trying to connect to me. That makes sense, right? *facepalm*

I'm still interested to know if anyone has ideas for better logging on the router though. Thanks!