cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Aspiring Expert
2,146 Views
Message 1 of 3

Port Forwarding Rule Added Via UPnP

14:24:13, 27 May.(2110048.260000) Port forwarding rule added via UPnP. protocol: UDP, external ports: any->57902, internal ports: 57902, internal client: 192.168.1.65
14:23:34, 27 May.(2110008.940000) Port forwarding rule added via UPnP. protocol: UDP, external ports: any->57902, internal ports: 57902, internal client: 192.168.1.65
14:22:53, 27 May.(2109967.800000) Port forwarding rule added via UPnP. protocol: UDP, external ports: any->57902, internal ports: 57902, internal client: 192.168.1.65
14:22:10, 27 May.(2109925.160000) Port forwarding rule added via UPnP. protocol: UDP, external ports: any->57902, internal ports: 57902, internal client: 192.168.1.65
14:21:37, 27 May.(2109892.130000) Port forwarding rule added via UPnP. protocol: UDP, external ports: any->57902, internal ports: 57902, internal client: 192.168.1.65
14:21:06, 27 May.(2109861.170000) Port forwarding rule added via UPnP. protocol: UDP, external ports: any->57902, internal ports: 57902, internal client: 192.168.1.65
14:20:26, 27 May.(2109820.740000) Port forwarding rule added via UPnP. protocol: UDP, external ports: any->57902, internal ports: 57902, internal client: 192.168.1.65

Hi guys, would anyone be able to tell me what the above messages in my HH3's log mean?  My connection has been fine but I would like to know why this is happening every few seconds. 

 

At first I thought it was because of a certain program I was using but it happens even when this program isn't running so I just don't know!!  Any help is appreciated.

 

EDIT:  So I'm guessing it's something to do with having UPnP turned on.  The reason I'm asking is because I've seen other people's logs and they aren't filled with this message.

0 Ratings
2 REPLIES 2
2,130 Views
Message 2 of 3

Re: Port Forwarding Rule Added Via UPnP

Hello,

 

If I were you I would switch of UPnP for a bit and see what application breaks! 57902 is a Dynamic port so it's tricky to know what is opening it.

 

Identify what device it is by navigating to

http://192.168.1.254

Click on A-Z in the top right

Home Network

Go through each device in turn and identify which one has claimed a lease of 192.168.1.65

 

You can switch on/off UPnP by

http://192.168.1.254

Click on A-Z in the top right

UPnP

 

Let us know how you get on. It could really be anything - if 192.168.1.65 turns out to be on a Windows PC, I would make sure my AV was up to date and a full scan comes back clean 😮

 

 

Hope this helps,

0 Ratings
Aspiring Expert
2,123 Views
Message 3 of 3

Re: Port Forwarding Rule Added Via UPnP

Thanks, TommyBobbins.

I will turn off UPnP and see what happens.

I checked the logs again my computer has a lease of 192.168.1.64 - this IP address is also showing the same error in the logs. I suspect the other IP address, ending in 65 is my Dad's computer. He uses Windows and I use Mac.

I'll keep you posted.

 

EDIT:  Just turned off UPnP and that was OK.  I checked a program called uTorrent and it says the incoming TCP port (54488) is working.....I find this strange as I have portforwarding turned off... :s

 

Any ideas?

 

 

EDIT AGAIN:

 

Just wanted to add this in:

 

  
  
  
  

 

18:54:38, 27 May.(2126273.250000) Port forwarding rule added via UPnP. protocol: UDP, external ports: any->52503, internal ports: 52503, internal client: 192.168.1.65
18:53:53, 27 May.(2126228.130000) Port forwarding rule added via UPnP. protocol: UDP, external ports: any->52503, internal ports: 52503, internal client: 192.168.1.65
18:53:20, 27 May.(2126194.690000) Port forwarding rule added via UPnP. protocol: UDP, external ports: any->52503, internal ports: 52503, internal client: 192.168.1.65

20:34:34, 27 May.(2132268.320000) Port forwarding rule added via UPnP. protocol: UDP, external ports: any->54488, internal ports: 54488, internal client: 192.168.1.64
20:34:31, 27 May.(2132266.240000) Port forwarding rule deleted via UPnP. protocol: UDP, external ports: any->54488, internal ports: 54488, internal client: 192.168.1.64
20:34:29, 27 May.(2132264.190000) Port forwarding rule added via UPnP. protocol: TCP, external ports: any->54488, internal ports: 54488, internal client: 192.168.1.64
20:34:27, 27 May.(2132262.050000) Port forwarding rule deleted via UPnP. protocol: TCP, external ports: any->54488, internal ports: 54488, internal client: 192.168.1.64

As you can see it happens on different ports and UDP and TCP ports....

 

Hasn't happened in the 20mins or so I've had UPnP turned off.  Still, I am curious as to what causes this.

0 Ratings