@@El_Narix yes, I have an entirely different video talking about the preamble if anyone wants to know more about it.

@emilybaxterthecartoonywitc1805 On the surface based on your description...Yes, you should be able to do that. Each switch interface will have it's own MAC address and the 3 interfaces on the router should each have their own MAC address, so in theory that setup should work.

@@AceNetworker thanks for the info. I just ordered the switches and cables

Everything is put together and is working awesome. 860 mbps speed in both rooms. 👍

Thank You! Appreciate that! Thanks for watching!

You are most welcome. If there's anything specific you want to know more about, do let me know!

@@AceNetworker Im sure this is a supa simple answer for you. I have 3 routers, im trying to ping from 1 rtr to the 3rd rtr but cant. Able to ping to the interface(on the 2nd rtr) closest to the 1st rtr but then it drops at that point. Do i need to configure a static route in the middle (2nd) router so Im able ping across it so I can reach the 3rd router?

@elamaroon8316 without knowing all the details (and that's difficult on yt comments), I would say Yes on the surface. Routers have to pass Layer 3 traffic, and they have to know where other routes and IP addresses are located for pings and traffic to get through. Can you login to the 2nd router and ping directly from it to the 3rd router?

@@AceNetworker yes i can ping from the 2nd rtr to the 3rd rtr. I now am able to ping from the 1st rtr to the 2nd rtrs interface that facing the 3rd rtr. (ip route(command) IP addr/subnet mask and the outgoing interface G0/0) but Im still not able to ping all the way to the 3rd rtr. Your right YT is definitely not the place to try and explain plus im sure im not using the right terminology. Thank you anyway.

@elamaroon8316 you may want to check on "IP Relay" or make sure there are no Access Lists set up on the router that may prevent pings from getting through. If all other traffic works correctly (depending on the brand of the router) IP Relay or sometimes it's called "IP L2 Relay" may need to be setup to allow pings through

@bard2227 It does indeed. The source IP address remains the same, but the source and destination MAC can (and often does) change between segments or from LAN to LAN

@@AceNetworker thank you sir

@bard2227 and (actually) I should have clarified that better: You'll usually keep the same Source MAC address within that LAN. Once you cross a Router (or other Layer 3 device) the Source MAC will change.

@Bozzigmupp Frames are the structure for 1's and 0's sent at Layer 2 on a computer network. They are how ethernet networks communicate data across the network. Think of a frame like a conversation between 2 humans: One says "Hi, how are you today?" and the other person responds with "Great! How are you?" Those intro phrases are like a frame for a conversation to begin

Probably means the port is operating at full capacity/bandwidth. Again, I would check the documentation on that model of switch/device to confirm what that means specifically

Without actually seeing the devices and setup you've got there, I would say check the wireless APs themselves, as they should have their own ground under the UL rating without something having to be improvised. You may also set up surge protectors on the switches the APs are connected to to prevent surges from lightning or other from damaging the devices.

​@@AceNetworker Thank you dear technician for your quick response, Actually,Our APs do not have have grounding cable in AC. I am wondering if using inactive pins as an earthing system! I can connect these 4 inactive pins to switches box... ! Thank you Technician.

You can use either of those types of connections, but here's what you will encounter: You are creating a loop with 2 cables between the same 2 switches. So you'll want to change the Spanning Tree configuration settings on at least 1 of those cable connections to have a higher Spanning Tree "Cost" - This will force the 2 switches to utilize only 1 cable until that connection is not available, then it will start using the 2nd cable only if the first cable (the one with the lower "cost") is not working or connecting. Another option is to NOT use the uplink port and use only 2 normal network interface ports, but configure both of those physical interfaces into a Link Aggregation to function as a single LOGICAL interface. Do that on both switches to have them match each other.

@@AceNetworker Thank you so much Ace for your fast response! I really appreciate your help! Do you have a video that explain Spanning Tree configuration settings or can you suggest me one? You are the best!

I don't have a video explaining the actual settings yet (working on it). But I can list an example here: Setting the cost to 2000 on interface 1/1/1 (or the interface on the cable connection you wanted to be stand-by): switch(config)# interface 1/1/1 switch(config-if)# spanning-tree cost 2000 Setting the cost to the default on interface 1/1/2 (or the interface(s) on the cable you want the switches to utilize primarily): switch(config)# interface 1/1/2 switch(config-if)# no spanning-tree cost You may have different interface numbers and you may have different command parameters, but these are some of the basic commands for Cisco switches.

@@AceNetworker Thanks a lot Ace! .. this is very helpful! ... i assume these commands will work only on managed switches right?

@@mihaitodea8510 Correct. These types of commands will work only on managed switches. Now, if you DON'T add a higher cost to one of those connections, Spanning Tree (assuming these are managed switches, or at least 1 of them is a managed switch) will automatically detect a loop created there and should technically block one of those connections until the 1 working connection doesn't work/connect - at which time it will "unblock" the blocked cable connection/interface and allow it to function. Again, preferable that BOTH switches are managed switches, but if they're not, at least 1 of them needs to be using Spanning Tree for this to work.

You're welcome. Thanks for watching! 😊

You are welcome! Thanks for watching

You are welcome!

Thanks for watching! I'm just (personally) elated this still has validity in today's newer technology, and that Ethernet still uses these basics at its core that I can leave this video up and it still has significant relevance in networking. But again Thank you for watching! And if you'd like anything specific in the realm of networking, let me know on here 😎

You're welcome! Thank you for watching!

Awesome! Glad to hear it! Thanks for watching!

1 - All switches start out defaulted to VLAN 1, so they are all in the same subnet until you configure different VLANs on the interfaces 2 - Depending on the brand of switch, you can usually set up a management IP address in each VLAN. If only one management IP is allowed, then it's usually only allowed in VLAN 1 or you have to create the Management IP address within the subnet of the VLAN you wish to access management of the switch within. For Example: If you wanted to manage/access the switch in VLAN 3, you would create a Management IP address on that switch that is in the same subnet as what the devices on VLAN 3 are using. 3 - Multiple VLANs are usually recommended, especially if you have more than one subnet going across a switch. The Uplink port can also be configured into a different VLAN (other than the default of VLAN 1) and/or be trunked with multiple VLANs Hope that mostly answers your questions. But let me know if I need to clarify anything there. Thanks for watching!

Thanks a lot', your are a geniuos!

You're welcome! Thanks for watching!

Thanks for the sub! And thank you for watching! That is EXACTLY why I create these videos, to simplify it as much as possible for anyone that may be just getting into the field/industry

Thank you! I appreciate that. Thanks for watching!

Working on it. Thanks for watching! I didn't have good sound equipment or software in the beginning, so working with better stuff now 😎

That's good news,@@AceNetworker! I've subscribed!

You're welcome! Thanks for watching!

Great suggestion!

Thank you, and thanks for watching!

Any time! Hope you were able to successfully get them connected. Let me know if you have any issues and I may be able to help further.

You are so welcome! Thanks for watching!

Yep. Exactly the way it was meant to be

Glad it helped!