• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: October 30th, 2023

help-circle




  • Unless you’re doing something very unusual (multiple ISP’s or a home lab), a home only needs one router – this is where you went wrong. You add WiFi with AP’s – not routers. A normal router should be able to handle as many networks/VLANs/DHCP scopes as necessary and will have a single default route out to the Internet.

    You’ve made your network needlessly complicated. In order to fix things, you should setup all but one router in AP bridge mode. This does not completely fix things because wireless routers aren’t going to act as a single controller for your wireless devices. If you can return all of these routers, I’d recommend it because AP’s would provide a better solution. Do you even have a need for more than one network? Do you even have a managed switch? Does everything go back to a central switch?





  • Your house is too large for adequate coverage by a single device unless it has no interior walls and you don’t care about the speeds as you get further from the wireless router.

    You should be looking for a router without WiFi but with proper QoS. Your WiFi can then be done with multiple AP’s to provide better coverage throughout the house. You just need cables from your switch to the locations where you’d want to put the AP’s. The solution to bad WiFi is not a more powerful transmitter. You need to reduce the distance to each WiFi source which you do by adding more AP’s. In a case where you can absolute not run cables and nothing currently exists for MoCA then you would use mesh but it’ll never be as good as a cabled solution.

    If you want coverage to the detached workshop, run a cable there and add an AP. If you can’t run the cable then use a wireless bridge designed for point to point and then add an AP to that.



  • Link speed is your hard limit – you can’t go faster than that. Nothing gets divided up just because a device is on. The concept of bottlenecks is what’s important. If you had a 100Mbs switch (with 1Gbs uplink) and a 1Gbs router with a 500Mbs ISP speed, a PC on the switch will be bottlenecked at your 100mbs switch port – it won’t be able to go beyond 100mbs. If you have 5 PC’s on that 100Mbs switch all trying to do 100Mbs each (since that’s the bottleneck of the switch), each PC will be able to do 100Mbs and since you have a 500Mbs speed connection – each PC should get 100Mbs. The switch uplink will pass 500Mbs/1000Mbs and the router will pass 500Mbs to the ISP. If you add a 6th PC trying to do 100Mbs then it gets bottlenecked at the ISP link since it can only do 500Mbs even though the router can do 1Gbs.

    If your 100Mbs switch had no 1Gbs uplink then the fastest switchport to the router would be 100Mbs. In the first scenario of 5 PC’s trying to do 100Mbs each, they would all be throttled to roughly 20Mbs since the total connection out of the switch would be 100Mbs. If only 1 device tried downloading, the limit would be 100Mbs for that device since the limit would be the link speed of the switch to the router.

    If you had a PC directly connected to your router at 1Gbs bypassing any 100Mbs switch limits, the bottleneck would be at the ISP of 500Mbs. If you had devices on the 100Mbs switch (with 100Mbs uplink) trying to download at max capacity while your PC was directly connected, your expected speed would be 400Mbs since 100Mbs would be going to the switch.

    The concept of a 24-port Gigabit switch with only 1Gbs uplink works because no device is expected to be constantly utilizing 1Gbs for a sustained period of time. They also supply full bandwidth to ports across the switch that don’t have to go across a common uplink. PC A and PC B can talk to each other at 1Gbs if on the same switch while PC C is talking to the Internet at 1Gbs. As long as the devices aren’t utilizing a common port at the same time, there’s no bottleneck.



  • The connection from SW-A to SW-B should be a VLAN trunk – ie tagged (all vlans assigned assigned would normally be the default). VLANs have to be defined on both switches.

    The connection from SW-A to the router would also be configured as a VLAN trunk - ie tagged.

    The only difference is how the router would be configured. From a Juniper/Cisco perspective, you would create subinterfaces for each tagged VLAN and assigned them the VLAN Id’s of the tagged ports. Each subinterface would have an IP address corresponding to the network’s default gateway. I’m not sure if the PFSense is different – I never use this software for a router.

    VLAN 1 is normally considered special because it would be the native VLAN on most switches so would be an untagged VLAN. If this is unintended, the easiest thing would be to change the VLAN number and tag it. Alternatively if the switch and router allow it, simply change the native VLAN to something besides 1. It it’s intentional then do nothing.




  • I’m a networking engineer with 20+ yrs experience. I don’t reference my background unless challenged. I give the best advice that I can in these forums since I see them as a sea of ignorance. Most people aren’t network professionals and make very poor choices because of marketing and consumer availability. They then come back on the forums and complain about issues that exist because of their poor choices in gear.

    Examples:

    Why is my latency so high? Because you didn’t get a router capable of QoS and are suffering from network congestion.

    I need a new router because my WiFi doesn’t reach the other end of my large house. That’s because you should have purchased AP’s and not relied on a single wireless source built into a router.

    Why is my $80 all in one device locking up every day? Because it’s a poorly manufactured all in one device.

    The list goes on.