Recent content by humangod

Ignore everything Shaun o stated. It's all 100% incorrect. You need to provide more information. Post a screenshot of your ping results and a screenshot of your local IP configuration.

I wouldn't say that's the most you can expect. I would say that if you're getting +/- 10% of the top speed that you're paying for, you're wasting your time to try to squeeze out anymore. It's not your modem or your computer or the coax. You're right where you should be. Don't look at this as a...

Well you won't like the answer. You're getting what you're paying for. Comcast is doing some sort of traffic shaping on their network to limit customer speeds to what they're paying for. Traffic shaping is a sort of QoS that can limit traffic based on any number of variables, including a...

Trust me, you want security from the rest of the tenant network. I'd recommend putting in a small SOHO firewall and using that as your layer 3 routing device. Something that does stateful inspection. Perhaps an ASA 5506-X or an older ASA 5505. You can find 5505's online pretty cheap. A new one...

Let me try to understand your post. You're paying for 150Mbps but you're achieving 141Mbps? You want to achieve 150Mbps? Or you want to achieve more than 150Mbps?

I'd suspect some sort of traffic inspection software on your workstation; perhaps security software like an anti-virus or HIPS. Try disabling any security software that you have installed.

Assuming that ESP is selected instead of AH, NocturnalPing has it correct. It should be noted that interesting traffic (traffic that is encrypted within the VPN tunnel) or the clients sending the interesting traffic will not know about any part of the network that is routing the encrypted...

looks right. are you able to access your router's config with this change? and what about your internet connection?

I agree with the others. This is a case of using the wrong tool for the job. You're asking a router to act as a switch. If I were you, I would make that router be an actual router since that is what you're working with. I checked out the manual for the TP-Link router and found out it supports...

additionally, to make sure you've correctly configured your router, after performing all of the above steps, run ipconfig to make sure you have the addresses stated above. then try to ping your gateway of 10.0.0.1. if you get timeouts, something is wrong. if you get replies, your config is good...

so use the 10.0.0.0/24 network. this means this: router's LAN IP: 10.0.0.1 subnet mask: 255.255.255.0 default gateway 10.0.0.1 DHCP range handed out by the router: 10.0.0.10 - 10.0.0.254 (i always like to reserve the first several IP's for static use later on. you don't need to do that and could...

what ip are you pulling from your router via dhcp? 192.168.x.x? or 10.x.x.x?