> it was temperamental and didn't like any layer 2 "hiccups" The clock was probably doing the "correct" thing when it got a TCP packet for a connection which i

> it was temperamental and didn't like any layer 2 "hiccups" The clock was probably doing the "correct" thing when it got a TCP packet for a connection which it didn't recognize and sent back an RST, which caused the client to abort. > kind of problems that teaches you to question your assumptions Yep. I learned a lot from dealing with large layer-2 networks (commonly running on hardware not suited for the task). Mostly I learned to never run large L2 networks.