My ethernet runs directly to my iMac and Speedtest shows 930mbps down. Can I split that signal to my Dish network receiver and maintain download speed? If so, what equipment would I need?
I have a 2 node mesh router. I have ethernet from the main node to my iMac. I want to split that off and send one ethernet leg to another room without losing any download performance. No firewall.Umm...yeah a switch is definitely what you want, but please tell me a bit more about your setup. When you say your ethernet runs directly to your iMac, I assume that you mean your iMac is connected to a LAN port on your router (i.e., behind a firewall); is this correct? Most ISP routers incorporate a small (5 ports or so) switch, so could you not connect your Dish receiver to that?
Those ARE cool! And quite affordable, too. Amazing that they provide QoS and other advanced features in an unmanaged switch at a sub-$50 price point. OTOH, a <$20 Netgear switch would be sufficient for the OP's use case.There are some really awesome small port count switches. Cisco sells some good ones, some provide POE, for the future.
Those ARE cool! And quite affordable, too. Amazing that they provide QoS and other advanced features in an unmanaged switch at a sub-$50 price point. OTOH, a <$20 Netgear switch would be sufficient for the OP's use case.
How many Ethernet ports are on your router? If two, just connect the iMac to one and the Dish Receiver to the other.I have a 2 node mesh router. I have ethernet from the main node to my iMac. I want to split that off and send one ethernet leg to another room without losing any download performance. No firewall.
How many Ethernet ports are on your router? If two, just connect the iMac to one and the Dish Receiver to the other.
Adding hardware will not be effective. The capacity of your internet connection is ultimately shared by all devices in your network. Neither the iMac nor the receiver will saturate your connection.
Absolutely. This is why I was asking the OP about his/her setup...it wasn't clear whether a firewall was in the mix. I'm still not 100% sure, but I assume their mesh router must have some sort of firewall.People not using a good firewall, or a firewall at all are standing in the public square with their pants down. Hackers will spend days picking over the data they liberate from unprotected local nodes. *shrug*
Practice safe computing...
Absolutely. This is why I was asking the OP about his/her setup...it wasn't clear whether a firewall was in the mix. I'm still not 100% sure, but I assume their mesh router must have some sort of firewall.
I remember in the early days of broadband, before I knew any better, I used to connect my PC directly to the cable modem. Imagine sitting on the internet with a public IP address and no firewall whatsoever! I used to watch the WAN activity light blinking away and think "I wonder what's going on?" LOL. Of course, this was in the mid-late '90s, so I don't think the threat level was as high as it is today. Luckily, I was never hacked (at least that I know of).
Mmmm...not sure I follow your concern about "cheap" firewalls. As long as the thing blocks unsolicited inbound traffic on the WAN, that's most of the battle. I suppose a really screwed design might do NAT poorly and leave arbitrary ports open for too long, which would open up possible attack vectors. I think a much greater concern is certain insecure router "features" that are enabled by default. One of the chief culprits is UPnP, which is almost always enabled on consumer routers. The idea that any random application on my network can set up port forwards just freaks me out--one of the first things I do when setting up a router is to make sure it's turned off. Another bad idea is enabling WAN administration, which I've seen on some ISP routers. I suppose they do it for remote support, but if you leave this on and leave the default router password unchanged, you've just bought a one-way ticket to Misery City!!... some cheap firewalls are almost worse than no protection at all. Watching my firewall being attacked in real time was weird...
Mmmm...not sure I follow your concern about "cheap" firewalls. As long as the thing blocks unsolicited inbound traffic on the WAN, that's most of the battle. I suppose a really screwed design might do NAT poorly and leave arbitrary ports open for too long, which would open up possible attack vectors. I think a much greater concern is certain insecure router "features" that are enabled by default. One of the chief culprits is UPnP, which is almost always enabled on consumer routers. The idea that any random application on my network can set up port forwards just freaks me out--one of the first things I do when setting up a router is to make sure it's turned off. Another bad idea is enabling WAN administration, which I've seen on some ISP routers. I suppose they do it for remote support, but if you leave this on and leave the default router password unchanged, you've just bought a one-way ticket to Misery City!!
But we digress....