I also remember that the two switches at the four post rack, one is in the Public VLAN, and the other is in the Private one.
So, your thought of static vs dynamic makes sense as a posible cause of the issue.
And thanks, I learned two new words from your previous email. :)
Deriving from cyberpunk novels, meatspace is the world outside of the 'net-- that is to say, the real world, where you do things with your body rather than with your keyboard. William
Gibson's novels (
Neuromancer,
Mona LisaOverdrive, and Count Zero in particular) note the difference between the 'Net of the console cowboys and the world of the meat outside.”
A
tounge in cheek explanation from programmers as to why an old program no longer works, even if it hasn't been touched in years.
Also applys to the
decay of physical
storagemediums.
(Urban Dictionary)
On Friday, September 11, 2020, Yardena Cohen <
yardenack@gmail.com> wrote:
Thanks so much Daniel, I know you worked hard on this, I'm sure the
problem isn't your setup, just the meatspace equivalent of bitrot. I
will try logging into the switches next time I'm there!
After giving this some thought, and a couple nights sleep, I suspect
the problem is only affecting machines that assign themselves a static
IP in 192.168.42.1/16 or 2001:470:488f:c0de::1/64. If they try
something in 100.64.64.1/22 or 2001:470:488f:f00d::1/64 instead, it
will probably just work.