On 7/6/12 2:10 AM, "Randy" <randy_94...@yahoo.com> wrote:
>--- On Thu, 7/5/12, William Herrin <b...@herrin.us> wrote: > >> From: William Herrin <b...@herrin.us> >> Subject: Re: job screening question >> To: "Jon Lewis" <jle...@lewis.org> >> Cc: "nanog@nanog.org" <nanog@nanog.org> >> Date: Thursday, July 5, 2012, 6:43 PM >> On Thu, Jul 5, 2012 at 9:28 PM, Jon >> Lewis <jle...@lewis.org> >> wrote: >> > You've never (much less recently) seen a customer >> misconfigure their end of >> > an ethernet handoff such that you end up with duplex >> mismatch? Granted, in >> > that case, distance is irrelevant...but it is half >> half-duplex ethernet :) >> >> If I was asking an ethernet question, I'd rather ask: >> >> 1. How do you make a crossover ethernet cable to connect two >> switches? >> (cross the green and orange pairs) >> >> 2. What happens if you plug that cable into a pair of >> gigabit ethernet >> switches? (mdix malfunctions, ports negotiate to 100 full, >> on some >> poorly implemented switches the mix of straight and crossed >> wires >> eventually damage the ports so they can no longer do gige) >> >> Regards, >> Bill Herrin > > >Or for that matter, in the absence of auto-MDI/MDIX: > >1) when is a straight-through cable *required*? >2) when is a cross-over cable *required*? > >How about another HR-Question: > >what do 0.0.0.0/1 and 128.0.0.0.0/1 as static-routes accomplish? > >./Randy > My favorite screening question at the moment is: What does a NULL-Route for 169.254.0.0/16 not fix on a Cisco router? Answer - Compliance with RFC 3927 because it doesn't fix the problem of a link-local source address. Answers that also mention proxy-ARP result in immediate interviews. --Dave
