- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
Networking guys (kork?) critique my whole house infrastructure
Posted on 6/1/26 at 8:19 am
Posted on 6/1/26 at 8:19 am
Friend building 6k sf house on 3 floors.
L1 - garage, server room, home theater..semi-underground/finished basement because it's cut into the side of a hill
L2 - kitchen dining room kids rooms den etc
L3 - Master bedroom, home office, main living area because of the views
Ok so we have
- reolink NVR+Poe cameras and doorbell
- tp-link omada switches, in-ceiling APs, controller and router (att fiber passthrough)
- local control HA..zwave+ etc
Right now he's got Ethernet wall plates in multiple rooms across all 3 levels and cat 6a UTP runs to each.
Also ethernet/poe runs to his eaves on the top level for cameras
He has a maintenance closet on all 3 levels PLUS the main server room which is where the cables are pulled to at the moment.
EDIT: There are 4 cable runs going from each of the 3 closets and terminating in the server room.
I had him purchase 4x 48 port patch panels and 4x 24 Port GB switches and 3x 6U server racks. One for each closet.
My plan is to connect the 4 runs to the top floor switch then to the middle floor switch, then the basement switch then the server room where the final patch panel is grounded.
That's the backbone and should future proof his data pipe for some time.
NVR, patch panel and switch #1 in top floor maintenance closet since that's where the camera wire runs now. Might as well not waste switch ports on the 8-10 cameras. Poe ceiling AP and wall outlets also connected to this switch in a 6U mounted in the closet.
Identical setup as above with switch #2 in the middle floor closet and switch #3 in the first floor closet, ceiling AP and patch panels..just no NVR.
Finally the fiber connection to the house, att router, tp-link router, tp-link controller, 4th switch, servers, UPS, etc will live in a larger main server rack (which I haven't decided on size yet)
That's the gist of it. I'm buying premium keystones (color coded!) for the patch panels because I want that part to be rock solid.
I went with tp-link/omada because that controller unifies the router, all 4 switches and all the APs into a single UX which I love and helps hide the ugliness of all this crap.
What do you think? Grade me A to F on this setup. It's ok to laugh at me and tell me this sucks because the walls are still open and we can still change things.
ETA amazingly all of that equipment above came up to roughly $1k! Can't believe how much shite we got for that price. Also good keystones are ridiculously expensive. That alone was almost $200
L1 - garage, server room, home theater..semi-underground/finished basement because it's cut into the side of a hill
L2 - kitchen dining room kids rooms den etc
L3 - Master bedroom, home office, main living area because of the views
Ok so we have
- reolink NVR+Poe cameras and doorbell
- tp-link omada switches, in-ceiling APs, controller and router (att fiber passthrough)
- local control HA..zwave+ etc
Right now he's got Ethernet wall plates in multiple rooms across all 3 levels and cat 6a UTP runs to each.
Also ethernet/poe runs to his eaves on the top level for cameras
He has a maintenance closet on all 3 levels PLUS the main server room which is where the cables are pulled to at the moment.
EDIT: There are 4 cable runs going from each of the 3 closets and terminating in the server room.
I had him purchase 4x 48 port patch panels and 4x 24 Port GB switches and 3x 6U server racks. One for each closet.
My plan is to connect the 4 runs to the top floor switch then to the middle floor switch, then the basement switch then the server room where the final patch panel is grounded.
That's the backbone and should future proof his data pipe for some time.
NVR, patch panel and switch #1 in top floor maintenance closet since that's where the camera wire runs now. Might as well not waste switch ports on the 8-10 cameras. Poe ceiling AP and wall outlets also connected to this switch in a 6U mounted in the closet.
Identical setup as above with switch #2 in the middle floor closet and switch #3 in the first floor closet, ceiling AP and patch panels..just no NVR.
Finally the fiber connection to the house, att router, tp-link router, tp-link controller, 4th switch, servers, UPS, etc will live in a larger main server rack (which I haven't decided on size yet)
That's the gist of it. I'm buying premium keystones (color coded!) for the patch panels because I want that part to be rock solid.
I went with tp-link/omada because that controller unifies the router, all 4 switches and all the APs into a single UX which I love and helps hide the ugliness of all this crap.
What do you think? Grade me A to F on this setup. It's ok to laugh at me and tell me this sucks because the walls are still open and we can still change things.
ETA amazingly all of that equipment above came up to roughly $1k! Can't believe how much shite we got for that price. Also good keystones are ridiculously expensive. That alone was almost $200
This post was edited on 6/1/26 at 2:00 pm
5
Posted on 6/1/26 at 9:31 am to CAD703X
Not network engineer, just EE, but do network some things professionally.
1. CAT6a UTP is what I would pick but I don't know the future. Conduit may take the guess work out of the medium but not the architecture.
2. Can't future proof without knowing future. My house is 25 years old and is a disaster of obsolete tech. 50+ obsolete holes, a couple huge renovation candidates. Whatever tech you build in, you must plan on ripping out down the road.
3. 6000sqft is huge. Not sure 4x AP is enough. We use 4x AP on just over 3000 sqft but it's all stretched out on one level and we also try to cover a lot of outdoor area.
4. 4x 24 port switches? How many things are expected to be wired? This number goes down over time historically. 2.5g is the 2026 residential/SMB standard. All your Minis, business laptops, etc. already ship with this.
5. I keep hearing great stuff about Omada. I just use residential stuff that is actually getting really good now but I also have docker networks and other blast radius controls. Omada can help to solve isolation issues as they come up instead of getting crazy. Good stuff.
6. I don't understand Reolink. You spec nice business grade stuff and then toys for PoE cameras. If running server, you should use a nice software NVR and pretty much anything not from an actual camera manufacturer is either going to give major headaches or at least not give you the configurability and stream implementation to make them shine.
1. CAT6a UTP is what I would pick but I don't know the future. Conduit may take the guess work out of the medium but not the architecture.
2. Can't future proof without knowing future. My house is 25 years old and is a disaster of obsolete tech. 50+ obsolete holes, a couple huge renovation candidates. Whatever tech you build in, you must plan on ripping out down the road.
3. 6000sqft is huge. Not sure 4x AP is enough. We use 4x AP on just over 3000 sqft but it's all stretched out on one level and we also try to cover a lot of outdoor area.
4. 4x 24 port switches? How many things are expected to be wired? This number goes down over time historically. 2.5g is the 2026 residential/SMB standard. All your Minis, business laptops, etc. already ship with this.
5. I keep hearing great stuff about Omada. I just use residential stuff that is actually getting really good now but I also have docker networks and other blast radius controls. Omada can help to solve isolation issues as they come up instead of getting crazy. Good stuff.
6. I don't understand Reolink. You spec nice business grade stuff and then toys for PoE cameras. If running server, you should use a nice software NVR and pretty much anything not from an actual camera manufacturer is either going to give major headaches or at least not give you the configurability and stream implementation to make them shine.
Posted on 6/1/26 at 9:41 am to CAD703X
quote:
I had him purchase 4x 48 port patch panels and 4x 24 Port GB switches and 3x 6U server racks. One for each closet
Wtf is this monstrosity.
Absolutely zero need to have this much hardware and 3 different locations. How many of the runs will be over 100m?
Edit: Read the 4x 48 port patch panels as switches
This post was edited on 6/1/26 at 9:47 am
Posted on 6/1/26 at 9:44 am to CAD703X
For a 6,000 sq. ft. house, you guys are absolutely doing the right thing by running Cat6A while the walls are wide open.
But if we are grading this strictly on network architecture, reliability, and future-proofing, I have to give the current plan a C+.
The physical infrastructure the wires in the wall is an A+. But the topology, hardware choices, and bottleneck risks are where things get messy. Since the drywall isn't up yet, you can easily turn this into a flawless, enterprise-grade system.
You mentioned connecting L3 to L2, L2 to L1, and L1 to the server room. This is called a daisy-chain topology.
If someone accidentally unplugs the switch in the L2 closet, or if that switch dies, the entire L3 floor, master bedroom, home office, main living area, and top-floor cameras, completely loses connection to the router and NVR.
This creates a bottleneck. You are shoving all data from three floors down a single 1Gbps pipe between switches. If the server room is doing a backup, the NVR is recording 10 cameras, and someone is streaming 4K on L3, you will bottleneck that 1Gbps link instantly.
Putting the NVR on the top floor away from the main server room defeats the purpose of having a dedicated server room. If a thief breaks in, a maintenance closet is much easier to kick open than a secured server room. Furthermore, security cameras generate constant, 24/7 network traffic. You want that traffic hitting the NVR as directly as possible, not bouncing through a daisy-chained switch network.
Moreover, you bought 48-port patch panels but only 24-port switches for the satellite closets, and you only have 4 runs connecting the closets. If a closet has 30 drops, a 24-port switch won't cover them. If it only has 15 drops, a 48-port patch panel is overkill.
Since the walls are open, you have the golden opportunity to pivot to a Star Topology with a Fiber Backbone. Do not daisy-chain the closets to each other. Every single maintenance closet should connect directly back to the Main Server Room.
Run OM3 or OM4 Multi-mode Fiber or at least 4x Cat6A lines from the L3 closet directly to the Server Room. Run Fiber/Cat6A from the L2 closet directly to the Server Room. Run Fiber/Cat6A from the L1 closet directly to the Server Room. Furthermore, this ensures that if the L2 switch dies, L3 and L1 keep working perfectly. Move the NVR to the server room Leave the camera wires terminated in the L3 closet's patch panel, patch them into the L3 switch, and let the data flow down the backbone to the NVR, which should sit safely in the main server rack alongside the UPS and main storage.
Upgrade to 10Gbps Interconnects SFP+. Since you are using TP-Link Omada, ensure your switches have SFP+ 10Gbps ports. Instead of using standard RJ45 ethernet ports to connect the switches together, which wastes your 1Gbps ports and bottlenecks the system. Use DAC (Direct Attach Copper) cables or Fiber Transceivers to link the satellite switches back to a central core switch in the server room at 10Gbps.
I'm a software engineer but I know networking from on-premise migration to the cloud. Fix the routing layout before the drywallers show up, and this house will be a networking fortress for the next 20 years!
But if we are grading this strictly on network architecture, reliability, and future-proofing, I have to give the current plan a C+.
The physical infrastructure the wires in the wall is an A+. But the topology, hardware choices, and bottleneck risks are where things get messy. Since the drywall isn't up yet, you can easily turn this into a flawless, enterprise-grade system.
You mentioned connecting L3 to L2, L2 to L1, and L1 to the server room. This is called a daisy-chain topology.
If someone accidentally unplugs the switch in the L2 closet, or if that switch dies, the entire L3 floor, master bedroom, home office, main living area, and top-floor cameras, completely loses connection to the router and NVR.
This creates a bottleneck. You are shoving all data from three floors down a single 1Gbps pipe between switches. If the server room is doing a backup, the NVR is recording 10 cameras, and someone is streaming 4K on L3, you will bottleneck that 1Gbps link instantly.
Putting the NVR on the top floor away from the main server room defeats the purpose of having a dedicated server room. If a thief breaks in, a maintenance closet is much easier to kick open than a secured server room. Furthermore, security cameras generate constant, 24/7 network traffic. You want that traffic hitting the NVR as directly as possible, not bouncing through a daisy-chained switch network.
Moreover, you bought 48-port patch panels but only 24-port switches for the satellite closets, and you only have 4 runs connecting the closets. If a closet has 30 drops, a 24-port switch won't cover them. If it only has 15 drops, a 48-port patch panel is overkill.
Since the walls are open, you have the golden opportunity to pivot to a Star Topology with a Fiber Backbone. Do not daisy-chain the closets to each other. Every single maintenance closet should connect directly back to the Main Server Room.
Run OM3 or OM4 Multi-mode Fiber or at least 4x Cat6A lines from the L3 closet directly to the Server Room. Run Fiber/Cat6A from the L2 closet directly to the Server Room. Run Fiber/Cat6A from the L1 closet directly to the Server Room. Furthermore, this ensures that if the L2 switch dies, L3 and L1 keep working perfectly. Move the NVR to the server room Leave the camera wires terminated in the L3 closet's patch panel, patch them into the L3 switch, and let the data flow down the backbone to the NVR, which should sit safely in the main server rack alongside the UPS and main storage.
Upgrade to 10Gbps Interconnects SFP+. Since you are using TP-Link Omada, ensure your switches have SFP+ 10Gbps ports. Instead of using standard RJ45 ethernet ports to connect the switches together, which wastes your 1Gbps ports and bottlenecks the system. Use DAC (Direct Attach Copper) cables or Fiber Transceivers to link the satellite switches back to a central core switch in the server room at 10Gbps.
I'm a software engineer but I know networking from on-premise migration to the cloud. Fix the routing layout before the drywallers show up, and this house will be a networking fortress for the next 20 years!
Posted on 6/1/26 at 9:51 am to Breauxsif
quote:
You mentioned connecting L3 to L2, L2 to L1, and L1 to the server room. This is called a daisy-chain topology.
If someone accidentally unplugs the switch in the L2 closet, or if that switch dies, the entire L3 floor, master bedroom, home office, main living area, and top-floor cameras, completely loses connection to the router and NVR.
This creates a bottleneck. You are shoving all data from three floors down a single 1Gbps pipe between switches. If the server room is doing a backup, the NVR is recording 10 cameras, and someone is streaming 4K on L3, you will bottleneck that 1Gbps link instantly.
Spot on with this. To take it a step further for maximum redundancy, running two fiber drops from the core switch to each access switch would all for port channeling. Could also do the same with copper, but fiber gives you more "future proofing" since you would only have to swap optics instead of cabling for higher bandwidth (if the switchport allows, obviously)
quote:
Use DAC (Direct Attach Copper) cables or Fiber Transceivers to link the satellite switches back to a central core switch in the server room at 10Gbps.
I wouldn't use DAC cables for switch uplink runs. Stick with regular cat6a if you cant go fiber
This post was edited on 6/1/26 at 9:54 am
Posted on 6/1/26 at 10:12 am to CAD703X
Personally, I'd run all the copper back to the main data closet. There is no way you have a run of over 300 feet.
If you want to keep a data closet on each floor then you'll want a distribution layer switch in your L1 data closet that each Access layer switch will connect to. You'll want two Single mode fiber connections from your first floor closet out to each other closet. You'll want redundancy with this large of setup.
I'd go with Ubiquity for this over TP-link. You would have a Dream machine router, LINK
Then you'll have a distribution layer - Ubiquiti calls their distribution layer an agg switch. LINK
Att Fiber -> Dream machine router -> Agg switch -> Access Switches -> AP's, Camera's and end points.
I can help set this up for you. I've been doing it 30 years.
If you want to keep a data closet on each floor then you'll want a distribution layer switch in your L1 data closet that each Access layer switch will connect to. You'll want two Single mode fiber connections from your first floor closet out to each other closet. You'll want redundancy with this large of setup.
I'd go with Ubiquity for this over TP-link. You would have a Dream machine router, LINK
Then you'll have a distribution layer - Ubiquiti calls their distribution layer an agg switch. LINK
Att Fiber -> Dream machine router -> Agg switch -> Access Switches -> AP's, Camera's and end points.
I can help set this up for you. I've been doing it 30 years.
Posted on 6/1/26 at 10:15 am to Dallaswho
quote:Home Assistant will be the UX for reolink and they have HA's highest integration standard -- PLATINUM so i was going by how well that integrates so we can do fun stuff like play with the reolink AI and person/animal detection, object tracking, etc. to do things with.
6. I don't understand Reolink. You spec nice business grade stuff and then toys for PoE cameras. If running server, you should use a nice software NVR and pretty much anything not from an actual camera manufacturer is either going to give major headaches or at least not give you the configurability and stream implementation to make them shine.
are you saying there are other systems that can also do those types of parlor tricks? i've been very happy with my HA/reolink integration. its been a rock star for me and he's getting several PZT cameras as well.
Posted on 6/1/26 at 10:15 am to CAD703X
I'm buying premium keystones (color coded!) for the patch panels because I want that part to be rock solid.
Yeah don't do that. At Amazon data centers we color code with the patch cable and not the keystone. if you change a port or vlan just change the cable color.
Yeah don't do that. At Amazon data centers we color code with the patch cable and not the keystone. if you change a port or vlan just change the cable color.
Posted on 6/1/26 at 10:22 am to Breauxsif
quote:thats what the 4 cables are for. they are all part of the backbone. not just a single run between switches. i may not have made that clear. those 4 cables to each closet and utlimately to the server room are DEDICATED to managing the backbone.
This creates a bottleneck. You are shoving all data from three floors down a single 1Gbps pipe between switches. If the server room is doing a backup, the NVR is recording 10 cameras, and someone is streaming 4K on L3, you will bottleneck that 1Gbps link instantly.
quote:
Putting the NVR on the top floor away from the main server room defeats the purpose of having a dedicated server room. If a thief breaks in, a maintenance closet is much easier to kick open than a secured server room. Furthermore, security cameras generate constant, 24/7 network traffic. You want that traffic hitting the NVR as directly as possible, not bouncing through a daisy-chained switch network.
fair point. so pull the cable for the cameras all the way to the basement or are you saying its ok to plug the cameras into the switch in the top floor closet but just keep the NVR in the secure area?
quote:
Upgrade to 10Gbps Interconnects SFP+. Since you are using TP-Link Omada, ensure your switches have SFP+ 10Gbps ports. Instead of using standard RJ45 ethernet ports to connect the switches together, which wastes your 1Gbps ports and bottlenecks the system. Use DAC (Direct Attach Copper) cables or Fiber Transceivers to link the satellite switches back to a central core switch in the server room at 10Gbps.
I'm a software engineer but I know networking from on-premise migration to the cloud. Fix the routing layout before the drywallers show up, and this house will be a networking fortress for the next 20 years!
there is definitely a cost factor associated here but that sounds intriguing. it makes sense there should be a better way to link all the switches together.
i'm afraid of how much those switches will cost
scurries off to learn more about DAC and fiber trancievers...
Posted on 6/1/26 at 10:23 am to broadhead
quote:
I can help set this up for you. I've been doing it 30 years.
Posted on 6/1/26 at 10:25 am to broadhead
quote:i'm doing that too
Yeah don't do that. At Amazon data centers we color code with the patch cable and not the keystone. if you change a port or vlan just change the cable color.
the keystones come in 12 packs and 8 colors so i figured why not color code them as well. white - wall outlets
orange - PoE cameras
purple - PoE APs
green - backbone cables
Posted on 6/1/26 at 10:29 am to bluebarracuda
quote:see? i told you i was dumb.
Spot on with this. To take it a step further for maximum redundancy, running two fiber drops from the core switch to each access switch would all for port channeling. Could also do the same with copper, but fiber gives you more "future proofing" since you would only have to swap optics instead of cabling for higher bandwidth (if the switchport allows, obviously)
tell me more about this..would we need an installer who can 'crimp' fiber connections (for lack of a better term) to terminate it at each level? i take it there's a switch with a bulit-in 'fiber' connector we would purchase?
Posted on 6/1/26 at 10:40 am to CAD703X
It is completely normal to look at the phrase "10Gbps Enterprise Topology" and assume your budget is about to be violently murdered. Fortunately, you have a massive advantage here, you chose TP-Link Omada. Omada is popular because it delivers 90% of the features of enterprise brands like Cisco or Aruba, but at a tiny fraction of the cost. You can implement this entire 10G star topology without having to sell a kidney.
If you upgrade the whole system to a 10Gbps Star Topology, it will likely add roughly $900 to $1,100 to the total hardware budget from a quick hardware lookup.
In a standard 2,000 sq ft house, that would be absolute overkill and a waste of money. But in a 6,000 sq ft, 3-story house cut into a hillside with 10 continuous security cameras, server rooms, and an open layout will feel more enterprise like, as opposed to a laggy residential setup.
If you upgrade the whole system to a 10Gbps Star Topology, it will likely add roughly $900 to $1,100 to the total hardware budget from a quick hardware lookup.
In a standard 2,000 sq ft house, that would be absolute overkill and a waste of money. But in a 6,000 sq ft, 3-story house cut into a hillside with 10 continuous security cameras, server rooms, and an open layout will feel more enterprise like, as opposed to a laggy residential setup.
Posted on 6/1/26 at 10:46 am to CAD703X
quote:
tell me more about this..would we need an installer who can 'crimp' fiber connections (for lack of a better term) to terminate it at each level? i take it there's a switch with a bulit-in 'fiber' connector we would purchase?
Should have told your buddy to buy some of these Best switch on the market for the price
Can even swap the 2x10gb module for 8x 10gb one to use solely for switch uplinks
Edit: you also get 48 poe+ ports, with 12 of them being mgig (1/2.5/5/10gb) copper ports
This post was edited on 6/1/26 at 10:48 am
Posted on 6/1/26 at 11:12 am to bluebarracuda
quote:
Should have told your buddy to buy some of these Best switch on the market for the price
Can even swap the 2x10gb module for 8x 10gb one to use solely for switch uplinks
Edit: you also get 48 poe+ ports, with 12 of them being mgig (1/2.5/5/10gb) copper ports
killer price...but that also destroys the nice single-ux i get with omada right?
i'm going to look at some tplink switch options before going too far down this road...
Posted on 6/1/26 at 11:12 am to CAD703X
Reolink uses proprietary streams. They claim RTSP and ONVIF but those have bad session descriptions and change without warning, breaking most third party video handling software. Not sure how HA core handles Reolink but for most cameras they use built in go2rtc who has been fighting with Reolink for a long time to no avail. Their GitHub README explains some, discussions more. go2rtc
Pretty much all FOSS use Dahua as reference implementation because the streams and API are the most predictable. Anything made by an actual camera manufacturer(except maybe Motorola) is made to be universal.
Frigate NVR gives object detection with almost any model available, object classification(which dog), state classification (tell if door is open or closed as a sensor, etc.), LPR, bird classification, LLM tie ins, faces, object tracking, event summaries, counting, presence, image embeddings, text embeddings, semantic search, etc, etc. global, for each camera, for each zone. I think I have over 500 Frigate entities just from default integration. Most are disabled. Also fully customizable notifications. Don’t worry about the guy who came from the left, only the right. If I’m home and garage is open and gates open within ten seconds, don’t notify. Send notification as a gif. Send as critical, include these three actions as options, send “person in front” or as a whole AI review summary, etc, etc. all templated for you.
Pretty much all FOSS use Dahua as reference implementation because the streams and API are the most predictable. Anything made by an actual camera manufacturer(except maybe Motorola) is made to be universal.
Frigate NVR gives object detection with almost any model available, object classification(which dog), state classification (tell if door is open or closed as a sensor, etc.), LPR, bird classification, LLM tie ins, faces, object tracking, event summaries, counting, presence, image embeddings, text embeddings, semantic search, etc, etc. global, for each camera, for each zone. I think I have over 500 Frigate entities just from default integration. Most are disabled. Also fully customizable notifications. Don’t worry about the guy who came from the left, only the right. If I’m home and garage is open and gates open within ten seconds, don’t notify. Send notification as a gif. Send as critical, include these three actions as options, send “person in front” or as a whole AI review summary, etc, etc. all templated for you.
This post was edited on 6/1/26 at 1:54 pm
Posted on 6/1/26 at 11:25 am to CAD703X
quote:
tell me more about this..would we need an installer who can 'crimp' fiber connections (for lack of a better term) to terminate it at each level? i take it there's a switch with a bulit-in 'fiber' connector we would purchase?
LINK
Amazon has fiber cables ready to go.
Posted on 6/1/26 at 11:27 am to CAD703X
quote:
killer price...but that also destroys the nice single-ux i get with omada right?
And you'll need to know how to configure it with command line. I have Cisco at my house but I know how to set it up. I don't recommend this for you.
Posted on 6/1/26 at 11:57 am to Breauxsif
quote:
This creates a bottleneck. You are shoving all data from three floors down a single 1Gbps pipe between switches. If the server room is doing a backup, the NVR is recording 10 cameras, and someone is streaming 4K on L3, you will bottleneck that 1Gbps link instantly.
i screwed up my explanation and confused myself in the process
so to clarify; i have TWELVE cables coming into the main server closet.
4 from top floor
4 from main floor
4 from basement main. closet
those are not daisy-chained; they are coming directly from those levels into the main patch panel
sorry for the screwed up explanation earlier. just wanted to clarify a little on the current setup.
Posted on 6/1/26 at 12:01 pm to broadhead
quote:
And you'll need to know how to configure it with command line. I have Cisco at my house but I know how to set it up. I don't recommend this for you.
CAD is a smart cookie though, seems like he knows how to use AI pretty well too. Configuring the switch for home use is stupid simple even with no background in the Cisco CLI world.
Could also get it to run through Home Assistant, creating a shitty Catalyst Control Center/DNAC (And DNAC/CCC is already shitty
)
Page 1 of 2
Back to top
Follow TigerDroppings for LSU Football News