DHCP, IoT, HDC, eSIM, Phone, GCP, EXIMP, IPv6

Studied in detail how Windows 2016 server Dynamic Host Configuration Protocol (DHCP) client retry / back-off / failure scenarios and logic works. It seems that the batch of 4 queries, with longer timeouts are triggered around every 6 minutes. So in normal situations, there's really no reason to manually intervene. Just wait it out, when the DHCP server is working again.
First their (OVH) DHCP service is broken, then they're claiming it's our fault, because we're using a firewall and do not reply to ICMP echo requests aka PING doesn't work. As well as we're not using any statically configured addresses. Honestly, how do you think that the IPv4 public address PING (echo request / reply) would work, if the server can't get that public IPv4 address over DHCP to begin with? And there's only the non-routable IPv4 address (APIPA) attached to that interface, without gateway.
24 hours later ... OVH and their customer support. Ha, ha, no really not funny at all. Once again, are they really that (absolutely and incredibly) bad support. They confirmed that time their DHCP server was down. I don't know even how long it took to fix it, because after around 24 hours, I got fed up and configured all the hosts manually, disabling DHCP client. But it's just enraging that they provide misinformation, mislead the customer, they don't provide all the required information, trying to make the process as hard and annoying as possible for their clients. - They've clearly read the book of covert sabotage. Just playing and stalling things, and causing everything to fail, even if you're not doing anything directly malicious.
IoT is here, and your whole network is open for hackers. Surprising? Nope... Totally expected outcome.
Had a Telia Helsinki Data Center (HDC) tour today. It's awesome high security production facility, and excellent location for cloud service providers, whom might not be interested building their own infrastructure on green field. Data centers location is also very good from several aspects. Also they didn't fail as some cloud / dc providers have failed, by showing anything too secret to be shown to outsiders. Which I've written earlier about in my blog several times.
Had so much fun with one integration project, where the target is moving faster than you can aim. Isn't this what the agile projects are for? Did I yesterday order blue four wheel drive pickup with diesel engine? Well, today I would like to have red electric cabriolet. Maybe tomorrow I'll ask it to be submersible vehicle or something that's able to fly. But let's not worry about that yet, right? Because you've already started working, I assume the delivery is completed quickly and cheaply, right? - Btw. this randomization project has been running for around three years and not finished yet.
Studied Embedded-SIM (e-SIM / eSIM / eUICC). - Sounds interesting, future will tell if this is the way forward. Yet it probably is. Of course another way would be just entering identity information, or using some other linking method. But these are things just like the payment card industry, where legacy technology and it has been always done this way are really important factor. There's really little space for alternative technologies, even if those would work just as well.
Fine tuned my phone. I really deeply hate useless and slow animations which some UI designers low. First thing to do with every system, is to get rid of that time and resources wasting gunk, they've showed in.
Google Cloud Platform (GCP) poster, shows Google network, POPs and data center locations and interconnections.
Huawei's EXIM platform is annoying, because it doesn't allow you to set offset of the automatic display brightness control. Which leads the display being almost always way too bright. Yet another engineering failure. Also the sensor used for screen brightness is directional. This leads to interesting fluctuations when you're walking under street lights or so.
Microsoft is moving IPv6 only , this is totally expected path. I'm just wondering about the companies and network operators that haven't even heard of IPv6 yet.

2019-01-26