Event log entries

Sister boyfriend came over xmas day and noticed soon as his laptop connected to my router, my speeds were very erratic. He said he had torrents running which i said was fine and least that explains it. Confirmed this in the router logs as was getting lots of these entries:

[LAN access from remote] from xxx.xxx.xxx.xxx to 192.168.0.20:20330

192.168.0.20 was the IP the laptop was using

Soon as the laptop was switched off the speeds became consistent again, however despite him going home and the laptop not being on the network for 3 days now, im still getting the above in the event log every few minutes. Speeds/pings are all normal but why is there attentps to send data to a computer that is no longer on that IP address?

Also confirmed that no other device is using 192.168.0.20

Edited by bobble_bob (Sun 28-Dec-25 10:03:28)

I wonder if UPnP has created some NAT entries which haven't cleared up - would be worth checking the port forwarding sections on the router and see if anything is there.

Or maybe the router software is misbehaving and it has left open some translations which it shouldn't have.

Suppose the obvious one is - have you restarted the router?

Not restarted the router as there isnt an issue as such, just more curiosity.

I did check upnp and the port that bittorrent seems to use (20330) is open on IP 192.168.0.20 only which would make sense

I would assume as that internal IP is not currently in use, the requests are just going nowhere?

Edited by bobble_bob (Sun 28-Dec-25 12:34:15)

A second vote for power cycling the router.

Thanks will do.

I think Netgear routers have issues with upnp. Ive had multiple and all had similar issues, where as they open a port but never close it until power cycing the router

For example they open the ports for my PS5 to play online, but even after days of the PS5 being turned off, the ports remain open

In reply to a post by bobble_bob:

Not restarted the router as there isnt an issue as such, just more curiosity.

I did check upnp and the port that bittorrent seems to use (20330) is open on IP 192.168.0.20 only which would make sense

I would assume as that internal IP is not currently in use, the requests are just going nowhere?

Yes - any unsolicited inbound traffic on destination port 20330 will be getting sent to 192.168.0.20 which isn't being recieved.
I would remove the port forwarding rule manually if that is indeed allowed.

As upnp allowed it, it wont let me remove it manually

I will power cycle when home as i assume this will close the port

Edited by bobble_bob (Sun 28-Dec-25 13:27:45)