Critique my networking workshop outline?

I've been asked to conduct a networking workshop to teach basic networking to some members of our IT department. They also wanted some hands on stuff, so I dug out an old 8-port Cisco switch and a smaller router (1900 series) from storage.

I've been thinking of how to structure the class, and I think I've come up with a rough lesson outline, but I wanted to bounce some ideas off all of you.

Anyway, here goes...

• First part of the class starts with some slides, before we jump right into labbing.

• Start by showing the OSI Model and confirming that everyone's seen this and knows what it is.

• Tell them to forget that and then bring in the TCP/IP model (which I feel better represents what you actually see in real life.)

• Work up from the bottom of the stack

• Physical layer stuff explaining basic concepts like sending pulses on the line in a specific timing window to create "symbols". (Make obvious reference to telegraphs, and explain how it's like that only faster and machines read the symbols instead of humans.) (Spend no more than 5 minutes on this part, this isn't electrical engineering it's basic networking)

• Explain concepts like half vs full duplex, Auto-Negotiate and a few standards like 100base-T, 1000base-T, 1000base-sx, etc. (Again spend no more than 3-5 minutes on this part maybe just 1 slide to show a few basic pinouts and connectors.)

• Delve into layer 2 and give an explanation on the Ethernet standard and the structure of a frame. Explain about MAC Addresses, and broadcast vs unicast.

• Explain about how switches build a layer 2 forwarding table, explain mac learning, and Broadcast & Unknown Unicast flooding.

• First lab, everyone plugs a laptop into the switch and I have them all IP their machines based on seat number, and ping each other with no default gateway configured. I run wireshark on my machine, and show off all the ARP broadcasts as their machines seek out which layer 2 address they should send these packets to. (I'm hoping this part blows them away.)

• Taking a short break, we'll be moving on to layer 3 when return.

• More slides when they come back. I'll explain about layer 3 and how the layer 2 frames carry layer 3 packets in them when it needs to be written on the wire. I'll show them the IPv4 Packet Header and explain some of the basic concepts.

• I'll load a new configuration on the switch that puts every 2 ports in a separate VLAN. I'll have the class re-IP their laptop based on flipping their index card over and seeing their new address, subnet mask, and gateway.

• Confirm that they can still ping eachother in the same VLAN but they can't ping the laptops in the other VLAN's any more.

• Ill introduce the concept of routing and how it's used to get between different networks. At this point I'll hook up the 1900 to the switch and make them watch while I configure a basic Router on a Stick configuration. I'll then make them watch while I put together a quick trunk port on the switch.

• Everyone will set their default gateway based on the previous configuration.

• Everyone will confirm they can now ping each other. The Router is routing their packets between the different VLAN's.

• Now at this point I'll ask various people around the room questions and toss them a piece of candy if they get it right. Review questions like "what does a switch do if you send it a frame to a destination MAC Address that isn't in its forwarding table?" and "how do hosts determine where they should send their layer 2 frames when they want to talk to a specific IP Address?)

• After the section we finish up with Transport Layer and Application layer. Briefly explain about source port, destination port, show a TCP header and a UDP headers.

• Obligatory explanation of "TCP vs UDP" lol (every networking class should always mention this, right?)

• Show a wireshark capture of me SSH'ing to the switch from my laptop or something so we can see the ports in the packets, and sequence numbers and ACK's etc, also they can see the crypto handshake

• By then it will probably be around lunch time, so class dismissed.

What do you all think? I know it sounds kinda lame right now, I've been thinking of ways to make it more interactive like making them "be a switch" and write out "frames" on index cards and build a mac table, but some of that could possibly take up too much time or be a little difficult to orchestrate.

Also I'm kinda not happy with not having at least a 2-hop routing scenario. I was originally wanting to make a 3-router network and have everyone taking via static routes, and show how many static routes they need, and then configure like a super basic "router ospf 1, network 10.0.0.0" configuration to show how easy that made it, or heck even just "router rip" and done... but I think it would take too much time and the fan noise from the 3 routers would make it difficult for people to stay focused.

EDIT: Another big concern is that it doesn't touch subnetting or binary, which seem staples in all beginner level courses. Do I dare skip this?

Any thoughts?