Jump to content

uTorrent trying to communicate with itself?


Recommended Posts


I'm not sure how to categorize this, since ultimately uTorrent is running well, but I am experiencing wierld FW messages which I would be happy to get rid of..

I'm running uTorrent behind a linux firewall (iptables).

The fw's ifconfig command returnes:

eth-net Link encap:Ethernet HWaddr 00:40:63:D9:1B:9A

inet addr: Bcast: Mask:

inet6 addr: fe80::240:63ff:fed9:1b9a/64 Scope:Link


RX packets:68388 errors:0 dropped:0 overruns:0 frame:0

TX packets:52851 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:11889966 (11.3 MiB) TX bytes:31266309 (29.8 MiB)

Interrupt:5 Base address:0x8000

Which means in plain English that my public IP is

uTurrent is configured to use incoming port 8798 and source port 9999 through the UI...

My problem is that the FW is reporting that uTorrent (running on an internal host of is trying to communicate with itself:

Mar 12 02:47:59 gw kernel: [ 1359.212000] Shorewall:all2all:REJECT:IN=eth-local OUT= MAC=00:0e:0c:34:be:04:00:d0:b7:3e:34:84:08:00

SRC= DST= LEN=48 TOS=0x00 PREC=0x00 TTL=128

ID=6656 DF PROTO=TCP SPT=9999 DPT=8798

WINDOW=65535 RES=0x00 SYN URGP=0

Shouldn't uTorrent be aware of it's own public IP / port and avoid from connecting to itself?

I would be happy to get rid of these messages since FW messages are something I tend to go through and I'd rather have them filled with actualy hack attempts on my machine rather that useless uTorrent messages...

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...