Samutz

Those speeds are normal for you? If so, then that ping doesn't sound that odd.

Several questions:
Who exactly is your ISP (comany and type (dailup, dsl, cable, satellite, etc))?
Did you try any other servers on the Speedtest website? Sometimes the nearest isn't always the fastest.
Have you tried another computer on the same network to make sure it's not just yours?
Did you try rebooting everything? Computer, modem, router, any other network devices you might have.

My initial impression is that it is your ISP though. If it's fixed by now, could you post your latest speedtest results? I'd like to see what it says when it's normal.

There's quite a bit of info missing here. Sounds like this person is a relative/sibling, roommate, or coworker and you don't own the router (and thus can't just ban him from using it) and just want to be sneaky and block his access without him and/or the router's owner knowing about it. Am I close?

That said, if you can provide us with the brand and exact model of the router, we might be able to find the documentation on it and figure out how to do what you're asking. Otherwise take it up with the router's owner.

If you're running windows, try netstat -ab > netstat.txt in a command line, then open the text file and look for the ip:port. This should tell you what process is using the port and possibly what it's trying to connect to.

There's a similar command for linux. I don't recall what it is off the top of my head. Just netstat with different options.

Fishaman P, on 10 October 2011 - 01:06 AM, said:

Nah. It's just hasn't been updated since it's initial implementation. I sent Costello an update for it, let's see... (checks PM history)... 3 and a half years ago, but he later said he lost it or never received it or something.
And by that time I had already left and lost the files myself. It really does irritate me to see my work still buggy and broken after all this time.

CoNS, on 13 October 2011 - 09:39 AM, said:

10.0.0.1 is not valid for your network. It needs to be 192.168.1.2 or something else in the 192.168.1.* range that's not being used.
Also check the DHCP range on the first router to make sure 192.168.1.2 (or whatever you use) isn't in the range so that it doesn't try to give that IP to a computer.

For example, on my network my DHCP range is 192.168.1.50 - 255. 2-49 are reserved for static IPs, like switches, servers, etc.

You also shouldn't be using the Internet/WAN port on the 2nd router. Doing so is like creating a second network within your main network. What you really want to do is extend the existing network for things to work smoothly.