[ripe-list] RIPEng

Sorry for top-posting. . .

A few years ago I was frustrated at some knowledge gaps on my team, so I put together a training workshop that took 3 1/2 days (the first time I did it).

I gave them each a Raspberry Pi. I walked them through boot-up, CLI, files, and using iptables to block all IPv4 and using ip6tables to block normal stuff. IPv6 addressing and SLAAC, of course.
Bought them each a domain name ($2).
Installed and configured bind as an auth server.
Installed and configured apache and showed them certbot/LetsEncrypt, and hand-mangling HTML.
Installed and configured postfix with DKIM and DMARC.
Security throughout, opening up firewall rules for the new services, so we learned about UDP and TCP. Along the way, I gradually gave them less detailed instructions, so they had to learn how to learn from an online tutorial.
At the end of the training, I had them take HE's IPv6 certification, and of course, they'd already completed all the requirements, and got the IPv6 Sage T-shirt.

I've been thinking about how I might do something similar to teach routing. . .  Have 15 people at three round tables. Each with a few "households" and a router. Discuss subnetting, give them subnets. Configure static routes. Then connect to others at the table, see why dynamic routing is easier, learn OSPF. Day 2, start connecting with other tables: BGP. Security along the way, of course. The "households" might be minihardware designed to accept DHCPv6 and ping from a specific address to a specific address and turn green when ping succeeds. Routers might be Bird on something with a handful of ports. I haven't spent much time on it--suggestions welcome.

Taking a setup like this and doing some basic monitoring, then device provisioning, with Python or Go, would seem to me the logical next step.

Maybe there's a version of data center management, layering cloud/virtualization services over it.

Each of these could be done in less than a week, with breaks and meals. Building the classes could take a couple of months each.

I'd love to build and do this, but I still have a day job.

Lee


-----Original Message-----
From: ripe-list <ripe-list-bounces at ripe.net> On Behalf Of Randy Bush
Sent: Sunday, February 4, 2024 5:45 PM
To: Q Misell <q at as207960.net>
Cc: RIPE List <ripe-list at ripe.net>
Subject: Re: [ripe-list] RIPEng

This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.



> I think a workshop based format would be best, it's just a matter of
> finding someone willing to teach.

perhaps WHAT to teach will help guide who might teach it.  and that will depend a lot on the intended audience.

i am told the fosdem track was geared toward a youngish set, and used, among other things, micro:bits using microblocks.  but i am hoping someone who was there could speak with more authority.

i am more used to teaching workshops to older entry-level engineers
  - linux/unix boot-camp, how to live on the command line,
    install, configure, maintain, ...
  - ip addressing, forwarding, and building a LAN,
  - basic routing, way more basic than philip, like rip and maybe
    simple use of is-is,
  - how to install and configure a few services (e.g. mail
    and/or dns)
each being a separate full week hands on

but this is far too ambitious to start.  i suggest choosing a well-defined audience and one subject, teach it once or twice, and learn from that experience.

randy

--

To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/