Hi all

I have a router with 4 wired ports

Then I have two sixteen port switches connected

From there my house it hardwired like a mad man.

My question: Should I plug 2 ports from the router to each switch, will that free up a bottle neck?

the way I have it now there are 2 unused ports on the router. Seems a waste.

And I got like 10 things on each switch with only 1 Ethernet going to the router, isn’t that a terrible bottle neck ?

Thx

  • b3542@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    Nope. That’s a great way to create a layer 2 loop - it will break everything without LAG capabilities or spanning tree.

  • dshepsman@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    Back in the old days, if you connected 2 ports to 1 switch it would cause routing issues/network storms etc.

    Modern switches should prevent that, but unless you have managed switches, and know how to configure link aggregation, just leave it as 1 per switch

    • Jmkott@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      It still does. Not sure many unmanaged switches support either spanning tree or automatic link aggregation.

      Connecting two ports to the same network without specifically configuring spanning tree or loop detection, or link aggregation will destroy your network.

      Here is why. A broadcast packets coming in one port is sent out all ports. If port A and B are both connected to the router, a broadcast packet received on A will be sent out B. The router will receive it and send it back to port A. Switch will receive it and send it back out B. This will repeat until the network is swamped.

  • bigmike13588@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    Nooooo! Port from router to 1 switch, then line from 1st switch to 2nd switch and on to devices.

  • cyber1kenobi@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    Don’t daisy chain them. One line from the main switch (your router) to each additional switch. If your devices support it and you can figure out how to setup LAG (link aggregation) you can combine two links to each switch for more speed but you probably don’t need that.

    • SP3NGL3R@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      I would 100% Daisy chain for the average home. Okay maybe not 100%, but what it does is frees up full gig speed across the home while protecting a single gig connection to the router for actual Internet traffic. I would put the most ‘internet needed’ critical things on the first switch and the less critical on the second. If there is zero LAN-LAN stuff is happening (cameras to a recording station, home media server, etc.) Then maybe fork it in parallel mixing the most critical across the switches.

  • Downtown-Reindeer-53@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    Yes, each switch has the upstream port connected to your router. Unused ports are not a waste.

    IF you have gigabit ethernet ports on everything, there is no real bottleneck. You won’t saturate - i.e. fill the connection - because you don’t run everything at full blast at the same time. Most home devices take VERY little bandwidth. Even your streaming devices are relatively low. If you have something that is higher bandwidth you could put it directly on a router port, but it’s not likely you will notice much.

  • Inside-Finish-2128@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    I’ll take a different slant than most others here. Daisy chain the switches. I trust a switch’s ability to switch packets closer to line rate more than I’d trust a router’s ability to do so. I’d rather keep the switch to switch traffic on two devices rather than force it through a third. Obviously use the fastest ports on the switches for the switch to switch link.

    But definitely not two cables from switch to router, and unless you can build a LACP LAG between the switches definitely not two cables switch to switch.

    • SP3NGL3R@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      This. I use 1 cable from router into a 16 and then additional switches if the 16 (like a small POE switch). This avoids one extra device for LAN traffic while leaving a full gig just for WAN. Avoiding a bottleneck for actual Internet traffic.

    • Jdornigan@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      Another option would be to get a small switch and use that to connect the two switches together and then connect the small switch to the router. For about $40 they can buy a gigabit switch or about twice that for a managed one.

      • Leading_Study_876@alien.topB
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 months ago

        There is something to be said for this.

        The internal switches on “routers” can be quite poor at port-to-port traffic handling, particularly multicast. Certainly true historically. Say 5 to 10 years ago. Is it still? Don’t know.

        Also, cheap home switches can have their own issues. But at least, if you have your own home network hardware (and possibly your own secondary router) then when it comes time to change your ISP and get a new router or Modem, it does make it a lot easier.

      • Donut-Farts@alien.topB
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 months ago

        TP-Link makes a 5 port gigabit unmanaged switch for less than $20USD. It’s great. You can get it with PoE for $50.

    • alphaxion@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      This is basically just using a core switch and keeping your router as your edge of network.

      I’d go even further and buy a layer 3 lite switch as that core and have your gateway address on endpoints be that switch IP. Have some routing to point 0.0.0.0/0 on your switch to your router IP.

      Move DHCP and DNS roles onto a server and disable them on your router.

      With that set up, it means you can swap out your edge of network without disrupting your internal traffic.

    • gangaskan@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      You could also link back on both switches to the router, long as spanning tree is working as intended, it should not loop, and you have a redundant link in the event you have to cable manage things or a link breaks for whatever reason

  • megared17@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    Unless both the router and rhw switches support link aggregation, and you configure it properly on both, each switch should connect using only one cable.

    You could connect other devices into either of the spare ports on the router, if convenient. Maybe a home server or something?

    Fwiw, the 4 ports on your router are part of a switch too, just one that is built in. And there is at least.one additional logical port, that connects from that built in switch to the router part internally.

    • SirLauncelot@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      It’s actually a physical trace inside. The 4 ports you see will typically be on a 5 or 6 port switch. 1 port will go to the cpu, another is for a second phy for the cpu and is typically the wan port.

  • MrBigOBX@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    That only works on switches and routers that support LAGG/LACP AND you know how to configure it correctly.

  • Oisteink@feddit.nl
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    Right - so Link Aggregation is a thing no matter what the others here say.

    To use more than one port per link you need some kind of support for it. LAPC is quite common (and easy) form of link aggregation but also there are other implementations.

    Speed is one thing I question (or pps as you have 2x amount available) but also failover. If one cable/interface stops working the other(s) keeps things working

  • Northhole@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    What is the bottle neck you are experiencing?

    Is sound like you think there is a bottle neck, but have not experienced poor performance indicating a bottle neck?

  • JoeCensored@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    That’s an easy way to create a network loop. Consumer grade switches usually don’t support protocols like spanning tree.

  • DavidtheCook@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    Either one port from the router to switch one and another cable from switch one to switch two OR one cable from the router to each switch one and another cable to switch two and NO cable between switch one to switch two. Do not create loops!

    Two cables from the router to a single switch creates a loop and all three devices connected in a circle creates another loop. Both of these scenarios will create significant bottlenecks and broadcast storms.

    Now, if you have managed switches, there are other things you can do for fault tolerance, but that’s an entirely different conversation.