►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Welcome
everyone
to
two
enemy
labs
episode,
11
I,
believe
it's
episode,
11
I'm,
Claude,
toad
aka,
Derek,
winkworth
I
am
I,
am
the
host
today
and
we
are
going
to
be
talking
with
a
community
member
named
Brian
Linkletter
who's
written
some
very
interesting
blog
post
for
us
and
he's
he's
definitely
gone
in
headfirst
into
entery
labs.
So
we
thought
it'd
be
pretty
cool
to
have
him.
They
have
him
on
the
show.
B
B
A
Yeah,
especially
open-source
ones
right
I
mean
there
are
some
Network
emulators
out
there
that
are
quite
expensive
if
you
want
to
pay
the
money
for
them,
but
there's
there's
a
handful
of
different
things
that
simulate
different
kinds
of
network,
not
just
networks
but,
like
you
know,
simulated
congested
links
and
stuff
like
that
to
you
know
to
you
know:
to
create
realistic,
I,
guess:
scenarios
with
bandwidth
constraints
and
stuff
like
that
and
there's
all
kinds
of
free
ones
all
out
there.
But
it's
it's
not
like.
There's
a
guide
that
says:
here's
all
your
options
right.
B
That's
right
and
and
they're
all
based
on
different
technology,
which
is
interesting.
So
if
you're,
exploring
Network
emulators
I
through
that
I
started
learning
about
software-defined,
networking,
virtualization,
etc
long
before
I
had
to
use
any
of
that
technology
at
work.
Now
we
use
it
of
course,
every
day,
but
back
then
in
2012
to
2014
when
I
was
exploring.
B
All
of
this
particularly
software-defined
networking
was
just
getting
off
the
ground,
wasn't
something
everybody
had
heard
of
yet
yet
you
would
see
it
being
used
to
build
some
of
these
network
emulators
because,
of
course,
the
scripting,
the
orchestration.
That's
what
they're
all
about
they're
about
putting
different
elements
together
to
create
something
that
other
people
can
use
yeah
exactly.
B
Like
every
other
network
emulator
that
I've
written
about
it
was
I
came
to
it
from
something
else.
So
I
was
working
on
a
couple
of
other
tools
that
you're
probably
familiar
with
fEARnet
lab
and
Wistar,
trying
to
understand
them,
because
I
was
noticing
that
there
were
these.
This
new
family
of
network
emulators
was
being
created.
B
That
was
using
docker
and
containers,
and
that
was
really
interesting
to
me
and
just
by
working
on
those
tools,
of
course,
and
every
lab
started
showing
up
in
my
searches
and
then
there
were
a
couple
of
podcasts:
I
listened
to
packet,
pushers,
being
one
of
them.
That
mentioned
it
that
brought
on
I,
think
Matt
to
discuss
it,
and
and
so
from
there
I
decided
to
check
it
out
and
take
deep
dive
into
it
and
see
how
it
worked.
B
B
A
A
Can
you
give
us
so
yeah
and
it
sounds
like
you
got
into
it:
I
mean
you've.
You've
written
I
think
two
different
blog
posts
so
far,
one
of
them
is
actually
a
pretty
pretty
straightforward
guide
and
how
to
set
up
the
development
environment,
and
then
there's
a
second
one,
where
it's
it's
more
of
like
how
to
build
a
lesson
once
you
have
that
environment
in
place.
So
can
you
walk
through
those
a
little
bit
yeah.
B
The
in
the
first
one,
what
I
did
I
put
a
little
bit
of
a
different
twist
on
it,
because
I
wanted
to
use
KBM
instead
of
VirtualBox,
so
I
just
added
the
the
extra
steps
that
are
required
to
setup
KVM.
There's
really
only
one
thing:
you
need
to
install
the
KTM
driver
for
kubernetes
or
for
mini
cube,
and
then
you
just
have
to
change
that
that
file.
B
I
was
able
to
to
raise
some
issues,
and-
and
you
know,
you
and
Matt
responded
quite
quickly
and
I
think
some
of
them
are
lined
up
to
be
fixed
in
the
next
release
of
energy
labs,
and
we
also
talked
a
little
bit
about
how
the
energy
labs
handles
certain
types
of
lab.
Endpoints
I
wouldn't
call
them,
they
weren't,
really
defects.
They
were
just
the
way
any
labs
worked
and
you
guys
I
found
it.
You
guys
were
already
thinking
about
how
you
were
going
to
change
that.
B
So
I
feel
that,
just
as
just
by
getting
involved
in
the
community
just
by
trying
to
learn
about
this
and
then
and
then
you
know
raising
the
issues
on
github
and
communicating
in
the
in
the
forums,
I
think
that
was
just
in
itself
a
contribution
because
I
was
able
to.
You
know,
put
some
things
on
the
table
and,
and
we
had
a
good
discussion
about
it
and
I
think
some
things
might
change
because
of
some
of
those
points.
B
So
I
feel
really
good
about
you
know
getting
in
there
and
trying
things
out
and
then,
as
a
result
of
all
that,
I
wrote
this
this
post,
which
goes
through
you
know.
How
do
you
set
up
a
lesson
and
I?
Would
you
know
people
that
are
trying
to
use
energy
labs
if
you're
looking
at
the
documentation,
if
you're
wondering
how
do
I
get
started
and
things
like
that,
it's
it's
actually
really
simple,
like
you
are
trying
to
make
energy
labs
simple
to
use
for
for
courseware
or
for
lesson
developers
to
develop.
B
I
should
say:
there's
only
a
few
text
files
that
you
need
to
create
in
order
to
get
a
lab
working.
If
you're
not
trying
to
create
a
new
image,
because
that's
something
I
haven't
done
yet-
is
to
create
a
new
type
of
image
for
energy
labs.
If
you're
going
to
use
the
images
that
you
and
Matt
have
already
put
on
energy
labs,
then
creating
a
new
lab
is
really
really
simple:
you're,
just
manipulating
some,
you
know
typing
out
some
text
files
putting
in
the
commands.
B
You
want
to
be
running
in
the
nodes
that
you've
defined
in
the
lab
definition
file
and
and
off
you
go
and
you
can
iterate.
You
can
build
them
one
stage
at
a
time
and
test
to
make
sure
everything
works.
The
way
you
want
and
when
you're
done
you've
got
all
that
working
on
your
own
laptop
and
then
you
can
contribute
back
to
the
project
if
you,
if
you're
ready
at
that
point
to
contribute
and
so
I
found
it
to
be
really
really
easy
to
well.
B
I
shouldn't,
say
easy,
because
I
don't
want
people
to
think
that
if
they
can't
get
this
on
the
first
try
that
there's
something
wrong
with
them.
It
does
take
a
little
bit
of
you
have
to
read
the
instructions.
A
little
bit
and
you'll
you'll
probably
find
a
few
things
that
don't
work
the
way
you
want
them
to
just
when
you're
getting
started,
but
I
mean,
from
the
point
of
view
of
you
know,
you'll
have
to
just
basically
learn
how
the
tool
works,
but
it's
yeah.
It's
relatively
easy
to
get
this
going.
B
I
was
very
satisfied
with
with
the
lessons
and
I
kind
of
started
a
lesson
on
just
kind
of
like
how
to
create
lessons,
which
is
what
I
was
the
example
I
made
in
the
blog
and
I.
Don't
know
if
that
would
be
something
that
is
contributed
to
the
to
the
main
block
to
the
main
system.
But
it's
a
it's
something.
I
could
start
and
do
quickly
and
yeah,
so
I,
that's
more
or
less
what
the
blog
post
was
about.
B
That's
how
we
went
through
the
whole
process
of
or
how
I
went
through
the
process
of
trying
to
learn
about
energy
labs
and
creating
lessons
and
yeah.
So
there's
just
the
the
lab
definition
file
and
then
once
you've
got
that
done.
You
just
have
to
create
the
directory
in
which
the
lesson
file
will
be
placed.
That's
the
stage
you
just
have
a
markdown
file.
That
is
all
the
information
about
the
stage
that
you're
creating
or
the
the
lesson.
B
And
then,
if
you
want
to
create
another
part
of
the
lesson
you
just
create
another
stage
directory
with
another
guide,
markdown
file
in
it,
and
if
you
are
using
the
Juniper
images,
you
would
have
to
have
a
configuration
file
in
there
for
the
devices
and
what
I
found
right
now
is
you
know,
particularly
the
the
lessons
in
there
right
now
are
all
fairly
basic
lessons.
So
the
same
basic
configuration
will
work
for
every
node.
B
You
know
we
just
just
copy
their
config
files
that
are
there
right
now,
that's
what
I
did
I'm
not
familiar
with
juniper
I'm,
not
familiar
with
napalm,
so
I
just
copied
the
image
file.
That
was
there
changed
the
IP
addresses
and
I
had
a
lab,
so
it
was
really
and
because
the
focus
of
this
tool
is
on
the
the
orchestration
and
the
management
and
automation
tools
that
kind
of
go
around
these
products.
B
A
Yeah
I-
and
you
know
what
you
said,
something
in
there
that
was
really
important.
People
often
think
I,
don't
know,
I,
don't
know
how
to
code.
I
know
I'm
not
familiar
enough
with
how
you
know
this
project
is
built
and
to
make
meaningful
contribution.
But
the
thing
is:
it's:
that's,
there's
actually
no
relationship
between
those
things
and
making
meaningful
contributions.
I
mean
you
blogging.
A
Instructional
blogging
like
like
you've
done
is
in
our
minds,
is
a
meaningful
contribution
and
then
raising
issues.
You
know
just
if
you're
having,
if
you
run
into
a
problem,
you
know
you,
don't
you
don't
have
to
be
the
one
that
fixes
it,
but
if
you're
the
one
that
points
it
out
I
mean
then
it
gets
fixed
and
that's
just
that's
a
that's,
a
very
meaningful
contribution.
So
you
know
the
thank
you
for
doing
that
and
I
hope
everyone.
A
B
I
like
to
get
started
well
learning
about
the
project
and
there's
no
I
think
when
you're
new
to
a
project
you're
bringing
something
really
special
to
a
project,
you're,
bringing
the
beginners
experience
and
and
that's
something
that
the
people
who've
been
working
on
the
project
for
a
long
time.
Don't
have
anymore.
So
that's
really
valuable
to
bring
to
a
project.
B
I
like
to
get
started
helping
out
with
documentation
in
a
project
I
mean
my
blog
posts
are
effectively
trying
to
expand
the
documentation
a
bit
and
I
may
get
into
trying
to
figure
out
how
to
contribute
back
to
the
project
by
putting
some
of
that
into
your
documentation
by
a
github
and
that'll,
be
something
else.
I
have
to
learn
how
to
actually
contribute
to
the
project
via
github,
but
I
like
to
start
with
the
documentation.
Every
project
needs
help
with
the
doc.
They
need
a
review
they
need.
Maybe
they
need
new
documentation
created.
B
They
definitely
would
probably
benefit
from
again
the
beginner
experience
of
going
through
the
documentation
and
sitting
well.
It
would
have
been
better
this
way
for
me
as
a
beginner.
Maybe
a
beginner's
guide
could
come
out
of
that,
and
things
like
that,
so
the
documentation
is
a
great
way
to
to
get
started,
contributing
to
a
project,
yeah
and
and
and
like
I
said
earlier.
My
experience
has
always
been
the
best
way
to
learn
about.
B
Something
is
to
think
about
how
you're
going
to
explain
to
somebody
else
so
as
you're
making
your
notes,
while
you're
working
through
this.
A
lot
of
that
can
be
contributed
back
to
the
project,
I'm
sure
and
then,
of
course,
as
you
as
you
get
more
comfortable
with
what
you're
doing,
for
example,
a
project
like
a
nuri
laughs.
You
could
contribute
a
lesson
and,
and
there
it
doesn't
in
my
opinion,
it
doesn't
have
to
be
something
you
already
know
about.
Like
I
am
in
your
target
audience
I
am
someone
who
you
know.
B
I
still
consider
myself
to
be
a
network
engineer,
even
though
I've
been
a
manager
for
ten
years
and
I
want
to
keep
my
skills
up
to
date,
and
so
I'm
learning
about
network
automation
and
things
like
that,
I'm
not
very
familiar
with
it.
I've
got
a
basic
ideas
of
it.
A
few
tools
and
I
want
to
learn
more
and
when
I
come
into
a
project
like
this
I'm,
not
sitting
here.
Thinking
well,
I,
don't
know
enough
to
contribute
I'm
thinking.
B
You
know,
because
if
you
shouldn't
always
think
that
you
have
to
do
your
own
thing,
you
can
get
in
and
just
help
what
are
whatever
is
going
on
already
so
I
like
this
have
been
a
few
project.
I've
contributed
so
far,
and
my
investigations
to
know
open
source
and
and
every
one
of
them
it's
usually
been
documentation
where
I've
been
able
to
to
help
out
and
I
think
that's
been
I.
Think
that's
important.
That's
an
important
contribution
as
well.
A
You
know,
and
that's
that's
not
a
good
substitute
and
so
documentation
is
super
important.
It's
how
people
hack
the
way
around
you
know
without
having
you
know
if
they
don't
already
know
how
to
read
code.
They're,
not
gonna,
do
that
to
learn
how
to
use
the
product
or
the
you
know
the
thing
whatever
it
is.
They're
there
you
know
whatever
project
it
is
they're
messing
around
with
yeah.
So
that's
that's
absolutely
true.
B
Yeah,
it's
true,
there's
so
many
great
projects
that
that
the
documentation
could
be
improved
and
in
my
experience
when
I've
been
looking
at
tools,
I
tried
to
learn.
There
are
some
that,
because
a
lot
of
what
I
do
is
I'm
looking
at
a
lot
of
this
stuff
comes
out
of
universities,
Network
emulators
and
things
like
that.
So
I'll
look
at
a
academic
paper
where
they
describe
it
and
I'll
go
okay.
Great
I
want
to
check
out
that
tool
and
I'll
go
to
the
github
repository
where
the
tool
is
and
there's
not
a
scrap
of
documentation.
B
There's
just
absolutely
no
way
to
consume
this
tool
or
even
get
started
because
whoever
created
it
really
just
put
something
on
github,
more
probably
to
store
it
for
themselves
and
not
really
to
make
it
available
to
people.
But
documentation
is
so
important.
You
can't
ever
get
involved
in
something
unless
there's
at
least
something
to
get
you
started.
So
when
you're,
you
know
it
doesn't
matter
how
great
the
code
is.
B
If
people
don't
know
where
to
start
or
how
to
get
at
least
something
going,
they'll
never
be
able
to
get
involved
in
your
project
or
community,
or
you
know,
contribute
to
your
community,
so
I'm
a
yeah,
a
big
believer
that
documentation
is
important.
You
know,
training
is
important,
helping
people,
you
know
every
product
that
gets
sold
today
has
to
if
its
commercial
comes
along
with
training,
because
you
need
to
people
need
to
have
a
good
experience
using
the
product
and
if
they
don't
then
they'll
just
not
use
it
anymore
or
not
get
involved.
B
A
So
so
how
would
you
what
kind
of
what
would
you
say
to
a
network
engineer
that
wants
to
get
involved
with,
with
with
sharing
like
as
they're
learning,
automation
or
anything,
even
network
engineering?
Stuff?
That's
not
specifically
about
automation
right,
but
you
know
they're.
They
learn
something
new
right
and
they
want
to
share
it
or
they.
You
know
they
they
have
some
neat
design
or
or
something
they
did.
You
know
what
is
your
recommendation
for?
How
do
they?
You
know
how
do
they
get
started
in
the
practice
of
sharing
that
knowledge
all.
B
Right
well,
I'm,
a
big
fan
of
I
would
call
it
creating
your
own
platform.
That's
a
term
other
people
have
used,
and
you
know
just
start
start
a
simple
little
blog
there's,
so
many
I
won't
get
into
the
tools
or
how
to
do
it,
because
there's
so
much
good
information
out
there
about
how
to
do
it,
but
just
get
started
doing
something
like
that.
When
I'm
good
looking
for
information
I
go
to
Google
I
often
find
blogs
by
engineers
who
you
know
in
their
About
section.
They
say
this
blog
is
just
for
me.
A
B
They
they
put
that
in
there
and
then
it's
useful
to
the
next
person
who
comes
along
and
finds,
and
there
are
a
lot
of
topics
where
you
know
the
the
number
one
hit
is
just
some
individual
engineers,
blog
and
so
they're
really
helping
the
community
that
way
and
it
you
know
it
could
be
blogs.
You
could
be
doing
YouTube
videos
YouTube
is
full
of
videos
of
Engineers
explaining
you
know
what
what
they've
learned
or
what
they're
working
on.
B
No,
I
hope
I'm
pronouncing
that
right
and
I
was
just
checking
it
before
this
call
here
to
see
if
it
was
still
available-
and
I
noticed
he's-
got
a
second
edition
coming
out
at
the
end
of
june.
So,
even
though
I
consider
his
first
edition
to
still
be
100%
relevant,
it
was
very
practical.
It's
a
how-to,
it's
all
the
tools,
you
know
just
do
this.
Do
this
this,
and
and
that's
how
you
do
it
a
technical
blog?
So
it's
it's
not
a
lot
of
fluff.
It
gets
you
right
into
it.
B
That
wants
to
do
something
like
this
and,
of
course,
there's
a
million
blogs
on
how
to
but
I
would
say,
don't
worry
about
when
you're
getting
started,
don't
worry
about
how
it
looks
or
what
technologies
you're
using
just
start
writing
just
start
putting
stuff
out
there.
You
can
always
go
back
and
reformat
it
or
put
it
on
a
new
tool
or
a
new
platform.
B
A
I
would
make
the
I
would
say:
I've
written
a
few
blogs
and
I
I
would
yeah
that's
a
hunt.
That's
totally
accurate.
You
the
best
way
to
get
started.
This
just
is
just
to
do
it
and
not
every
blog
is
gonna,
be
you
know
the
best
blog
you've
ever
written
and
it
Vince.
That's
fine
me,
you
know
it's
not
it's
not
a
big
deal.
Just
keep
doing
it.
You
know
it'll
start
coming
together.
More
and
more
often
where
you
put
something
out.
That's
that's
a
pleasure
to
read
and
it's
informative
right.
B
B
I
think
that
well,
there's
there's
the
two
I
think
the
two
big
ones
G
and
s
3
and
even
G-
that
don't
need
any
love
for
me.
They've
they've
got
huge
communities,
there's
a
lot
going
on
with
those
tools.
I
think
they're
generally
used
by
a
lot
of
people
for
labbing
exam
preparation
and
things
like
that.
There's
a
lot
of
really
cool
smaller
projects
that
are
interesting
just
because
of
the
technology
they're
using
they're
all
implemented
in
different
ways.
So
you
can
learn
a
lot
about
the
building
blocks
of
virtualization
and
and
network
automation.
B
By
looking
at
how
these,
which
tools
these
people
use
to
build
these
network
emulators
one
that
comes
to
mind
an
early
one,
I
started
working
with,
and
it's
still
going
strong
is
called
clue,
Nicks
and
it's
a
it's
just
a
bunch
of
KVM
virtual
machines,
and
it's
got
a
nice
graphical
user
interface
I,
really
like
the
core
network
emulator,
because
it's
all
based
on
containers.
So
you
on
a
small
laptop
like
mine.
B
I've
got
a
8
year
old
laptop
here,
and
you
know
if
everything's,
just
based
on
containers
and
and
I
know,
energy
labs
is
based
on
containers.
You
could
potentially
have
a
lot
of
nodes
in
a
network,
emulation
scenario
on
a
modestly
powered
system,
so
I
really
like,
and
it's
got
a
nice
graphical
user
interface
as
well.
B
Some
of
the
more
interesting
you
know,
modern
I'm
called
a
modern,
because
they're
now
getting
based
on
modern
technology
are,
are
the
tools
I've
started
to
see
now,
like
VR
net
lab
I
took
a
good
look
at
that
one
and
and
Wistar
is
interesting.
It's
another
Juniper.
Your
project
looks
like
it's
a
little
bit.
It
got
started
now.
B
It
seems
to
be
just
kind
of
in
maintenance
mode,
but
it's
and
that's
what
happens
to
a
lot
of
projects
they
get
going
and
then
they
kind
of
go
on
maintenance
mode,
but
I'm
talking
the
ones
I'm
mentioning
right
now
we're
the
ones
that
I
think
are
a
lot
more.
You
know,
they're
active
they've
got
people
working
on
them.
If
you
raise
an
issue,
it's
likely
that
someone's
going
to
get
back
to
you.
B
There's
plenty
of
projects
I
could
list
where
I
think
that
I
yeah
I
don't
know
what's
going
on
there
anymore,
there's
some
projects,
but
it's
been
four
years
since
they've
been
updated.
There's
a
couple
of
projects
that
I
haven't
looked
at
yet
like
there's
one
called
the
shadow
network
emulator,
which
is
still
an
active
project.
I
can
see,
updates
there,
I
haven't
looked
at
it,
yet
that's
that
one
is
emulating
to
peer
networks
like
like
tour,
The,
Onion,
Router
and
and
also
can
do
Bitcoin
peer.
You
know
the
Bitcoin
networks
and
things
like
that.
B
So
that's
interesting
like
because
of
Technology,
it's
emulating,
meaning
that
is
cool
because
it
does
software-defined
network
emulation
and
mini
net
has
many
variations.
The
interesting
thing
about
many
net
is,
of
course,
there's
many
net,
but
there's
also
many
net
Wi-Fi
maxie
net
and
these
other
things
that
we're
all
based
on
meaning
that,
where
different
people
have
sort
of
forked
it
and
taking
it
in
some
special
direction,
so
there's
a
lot
you
can
look
at
and
and
I
listed
them
all
on
my
blog.