On 09/20/2018 10:16 AM, Niklas Karlsson wrote:
> A while back I had an interviewer praise me because I was able to
> describe in broad strokes how IP over Ethernet works (the usual litany
> about NECvat sbe gur qrfgvangvba be tngrjnl, etc). "Very few people are
> able to describe it on that level, I was told.
"NECvat sbe gur qrfgvangvba be tngrjnl"?
> The supply of sysadmin candidates really must be teeming with lusers.
I've had some really sad applicants in my career. Some of whom have
said that
192.0.2.1/24 and
198.51.100.1/24 are in the same subnet and
can communicate with each other "because the netmask is the same".
> Routing protocols and advanced switching, you only need to know if you're
> actually a networking BOFH, but how IP works from the perspective of the
> source and destination nodes is really something any sysadmin worth his
> salt should be able to recite in hisher sleep.
I agree that any decent system administrator needs to have a basic
understanding of how networking works.
My main desires in candidates is:
· Properly identify if a system is in the local subnet or not.
· Understand what a route is for.
· Understand what a router / (default) gateway is for.
I would also like to see some basic understanding of things like
HTTP(S), SMTP, and DNS. Particularly the application layer protocol(s)
that run on the systems that they administer.
> Worrying, even if it does mean I'm able to look superior.
I've been worrying too. I've had 30 year seasoned unix administrators
think that they can access more of the Internet by arbitrarily changing
the netmask from /24 to /16 or even /8 and then wonder why they could no
longer get to things outside of the original /24.
--
Grant. . . .
unix || die
--
Grant. . . .
unix || die