04. How Routers Work - Network+ and CCNA Concepts

[@cj7334]

Your explanation for router config and troubleshooting was clearer than that used by the official cisco netacademy training course I'm taking.

[@eurotechsolutions2539]

Hey Derek, just wanted to say how much I appreciate your videos. You are an amazing teacher and I’ve learned so much through your channel! I just started my career in networking and your content has been invaluable. Just wanted to express my gratitude for you putting your content out there to help people like myself. Look forward to more videos to come!

[@tciproductions]

That's really nice feedback, thank you for that!

[@LupusYonderboy]

Man, I don't consider myself a pro, but I thought I had a good grasp on the topics you addressed. Turns out, I didn't and just learned something I think I should have known for ages. Grasping a concept and grasping how things actually work, that's two different pairs of shoes though. So from my perspective, I think you explained this very well in a way that let me get the sense of what you explained. Thank you for that. I look forward to the next lab!

[@tciproductions]

That's nice of you to say, I appreciate the feedback. I know it can be dry material.

[@wizsc]

Ive watched only 14 seconds so far, but I guarantee you, this is a great video!

[@Shubham-Mishra]

Yeah my man is back ❤

[@guilmm]

Great video, man. Thanks!

[@darrenoleary5952]

I'm looking at setting up something similar whereby router1 manages the vlans for a network while router2 manages the dhcp scopes for those vlans. I've configured the eth interface on router2 to be in the same subnet as router1 and I can ping one from the other without issue. Both routers connect via a managed switch. When I then configure a port on the switch for a desired vlan and connect a computer to that port, it fails to obtain an ip address. Any ideas what I've done, or where I've gone, wrong?

[@tciproductions]

Off the top of my head, I would want to know if the DHCP responsible router is attached to a trunk port on your switch, and the VLANs are sent over tagged to it, and the DHCP router should have matching sub-interfaces. Otherwise, you'd need to use some equivalent of Cisco's IP-helper concept where it forwards DHCP requests deeper into your routing network, but I rarely see things like that on other brands.

[@darrenoleary5952]

@@tciproductions both routers are in the same subnet - 192.168.254.251/24 and 192.168.254.252/24 and connected to the same switch. The ports on the switch that each router is connected to are configured with the same vlan/port profile. I am unable to ping router2 from a PC that successfully gets an IP from router1.

[@tciproductions]

@@darrenoleary5952 I guess I'd have to see a diagram, but here's what I am imagining: ibb.co/qkp95Nh

[@rashadchalabi]

thanks!

[@Jr2728]

Nice

[@tciproductions]

Thank you!

[@joshhaas8121]

Do you think the edge router is a good solution is 2024+ There have not been no patches or updates in years

[@tciproductions]

Exactly, people are tossing them out, they are easily found in lots on ebay, just like old cisco equipment. Grab up anything you can and build a lab from cheap old junk to learn on.

[@darrenoleary5952]

I think the last update was about 12 months ago. Hopefully the v3 firmware (shown on router1 in this video) is released sometime soon.

[@darrenoleary5952]

​@tciproductions the ER4s are still expensive on eBay here in Australia. Some new-in-box are as cheap as $200AUD, while others are upwards of $400AUD.

[@luciano.a]

This is awesome content and I`m learning a lot here! Either way, I cannot let this out of context joke pass by 😂 kzbin.infoUgkxzEcX3AQ3coATYZpVG_PfEAHvR_dfU7Jb?feature=shared

[@tciproductions]

Oh man, phrasing! New fear of public speaking unlocked.

[@luciano.a]

@tciproductions Just messing with you, keep up the amazing videos 👍