With the iPhone 17 Pro, Apple is sourcing OLED panels from different manufacturers. It’s a bit of a lottery — some phones end up with Samsung panels (considered the best), while others come with LG or BOE panels. The catch? A few non-Samsung screens show a noticeable blue tint.

The easiest way to check? Use 3uTools.

• Runs on both Windows and Mac
• Works perfectly on iOS 26 (as of Sept 25, 2025)
• Doesn’t need a jailbreak
• Spits out your hardware info in seconds, including the display’s serial prefix

Look for G9P, G9N, or G9Q in the serial number — that means you’ve got a Samsung panel.

Apple used to let us pull this info by digging into sysdiagnose logs, but they shut that down in iOS 26. Thankfully, 3uTools makes it super easy. I haven’t had the time to play with all its extra features yet, but for this one purpose alone it’s worth grabbing.

Big shoutout to the developers for keeping it free!

But on macOS, if you have iCloud’s “Private Relay” feature enabled, all of your web browsers may fail to resolve that subdomain to the local LAN address. Instead, they try to go out to the WAN IP, breaking your internal routing.

What makes this tricky is that the behavior doesn’t show up in basic tests. Using tools like nslookup or ping in Terminal still returns the correct local IP. Yet in Safari, Chrome, and Brave, the same domain wouldn’t connect to my internal server. The culprit? iCloud Private Relay.

I had assumed that Private Relay would only affect Safari traffic, but it actually interfered with DNS resolution across the system for all browsers. Once I disabled it, everything immediately started working the way it was supposed to.

So, if you’re running Split DNS at home and notice that your browsers refuse to resolve local resources—even though command‑line tools work fine—check whether iCloud Private Relay is enabled. Turning it off solved the problem for me.

Hopefully this tip saves someone else a few hours of head‑scratching.

What’s the Endorsement Process About?

Basically, ISC2 checks that:

• You actually have at least five years of cybersecurity work experience.
• You played fair on the exam and didn’t cheat.

You’ll need to complete this step, and pay the ISC2 membership fees, before you can really say you’re CISSP certified.

Here’s some personal news—I’m officially CISSP certified as of today, valid for the next three years! To keep it going, you need to earn Continuing Professional Education (CPE) credits. I’ve put together a list of places where you can get free CPE credits to help with that.

Where to Find Free CPE Credits

Here are some solid options to earn free CPE credits:

• ThreatLocker Webinars
• Hack The Box CPE Guide
• ISC2 Official CPE Partners
• SANS Webcasts
• (Might not be free) Antisyphon Training

Bonus tip: Taking other ISC2 certifications can often count toward your CISSP renewal credits too.

A Few Tips for Renewing Your CISSP

• Keep an eye on your CPE credits so you don’t have to scramble last minute.
• Mix it up with webinars, labs, courses, and events to keep learning interesting.
• Check ISC2’s website every now and then to stay on top of any changes.

Good luck if you’re on this journey—and congrats to anyone who’s passed the exam and completed the endorsement! You’ve earned it.

Hardware & software requirements

• TP-Link or Tapo smart plugs.
  • I am using specifically P115 and EP25 models which are working out of the box with the software stack I chose to use.
• Tapo P316M smart power strip is not working out of the box.
  • Although I am not a coder, I am working to figure it out and have a pull request on github where I try to add support for it.
    • https://github.com/python-kasa/python-kasa/pull/1561
    • https://github.com/python-kasa/python-kasa/issues/1558

The software stack is

• InfluxDB v2 for time series database storage.
• Grafana for visualization and charts of the data.
• https://github.com/lux4rd0/kasa-collector for self-hosted local fetching of power usage metrics from the local network devices, then storing the data in influxdb.

So, is it working?… kinda

I won’t go over setup and complexity but will share some insights and lessons learned. This setup is working as expected for the individual smart plugs with energy monitoring, the smart power strip metrics are not working.

There are some caveats and issues that I think everyone trying to replicate this setup should know about TP-Link and Tapo devices. Unplug any existing TP-link/Tapo devices from your network before onboarding a new device.

• The TP-Link Simple Setup (TSS) protocol, which shares credentials from existing devices, can break authentication with the python-kasa library which is a dependency in this stack.

How do you know TSS broke it?

Check it with the kasa discover command and look for “tss”

root@kasapi:~/python-kasa# uv run kasa --debug --username xx --password "xx" --host 192.168.66.240 discover
DEBUG:kasa.transports.klaptransport:Handshake1 posted at 2025-07-23 14:37:43.119547. Host is 192.168.66.240, Response status is 200, Request was 20708b23c4238cf0ce6da978d69f6e6e
DEBUG:kasa.transports.klaptransport:Handshake1 success at 2025-07-23 14:37:43.119597. Host is 192.168.66.240, Server remote_seed is: fff7df5db632df5ff316dd5f5734dd5e, server hash is: 06a480a245ab224d4875bc8fdcd75a68dc0ebf1a61818f5e194bcb5adc5eb3b0
DEBUG:kasa.transports.klaptransport:Device response did not match our challenge on ip 192.168.66.240, check that your e-mail and password (both case-sensitive) are correct. 
DEBUG:kasa.protocols.smartprotocol:Unable to authenticate with 192.168.66.240, not retrying: Device response did not match our challenge on ip 192.168.66.240, check that your e-mail and password (both case-sensitive) are correct. 
== Authentication failed for device ==
	== Discovery Result ==
	Device Type:        SMART.TAPOPLUG
	Device Model:       P316M(US)
	IP:                 192.168.66.240
	MAC:                REDACTED
	Device Id (hash):   REDACTED
	Owner (hash):       xx
	Supports IOT Cloud: True
	OBD Src:            tss
	Encrypt Type:       KLAP
	HTTP Port:          80
	Login version:      2

What it should look like in order for authentication to not be broken you ask?

root@kasapi:~/python-kasa/python-kasa# uv run kasa discover
== Authentication failed for device ==
        == Discovery Result ==
        Device Type:        SMART.TAPOPLUG
        Device Model:       P115(US)
        IP:                 192.168.66.179
        MAC:                REDACTED
        Device Id (hash):   REDACTED
        Owner (hash):       REDACTED
        Supports IOT Cloud: True
        OBD Src:            tplink
        Encrypt Type:       KLAP
        HTTP Port:          80
        Login version:      2


== Authentication failed for device ==
        == Discovery Result ==
        Device Type:        SMART.TAPOPLUG
        Device Model:       P316M(US)
        IP:                 192.168.66.240
        MAC:                REDACTED
        Device Id (hash):   REDACTED
        Owner (hash):       REDACTED
        Supports IOT Cloud: True
        OBD Src:            tplink
        Encrypt Type:       KLAP
        HTTP Port:          80
        Login version:      2

P316M device information when fully authenticated with proper credentials and no ‘tss’

The below is what you should expect to see:

root@kasapi:~/python-kasa/python-kasa# uv run kasa --username xyz --password xyz --host 192.168.66.240 discover
Discovering device 192.168.66.240 for 10 seconds
== None - P316M ==
Host: 192.168.66.240
Port: 80
Device state: False
Time:         2025-07-24 12:45:51-04:00 (tz: America/New_York)
Hardware:     1.6 (US)
Firmware:     1.0.5 Build 250306 Rel.151943
MAC (rssi):   REDACTED (-46)

== Primary features ==

== Information ==
Signal Level (signal_level): 3
Cloud connection (cloud_connection): True
Update available (update_available): None
Check latest firmware (check_latest_firmware): <Action>

== Configuration ==
Auto update enabled (auto_update_enabled): True
LED (led): True

== Debug ==
Device ID (device_id): x
RSSI (rssi): -46 dBm
SSID (ssid): x
Reboot (reboot): <Action>
Device time (device_time): 2025-07-24 12:45:51-04:00
Current firmware version (current_firmware_version): 1.0.5 Build 250306 Rel.151943
Available firmware version (available_firmware_version): None
Matter setup code (matter_setup_code): x
Matter setup payload (matter_setup_payload): MT:x

== Children ==

        == Smart Plug 1 (P316M) ==

        == Primary features ==
        State (state): True
        Current consumption (current_consumption): 0.0 W
        Voltage (voltage): 120.3 V
        Current (current): 0.0 A

        == Information ==
        Auto off at (auto_off_at): None
        Today's consumption (consumption_today): 0.0 kWh
        This month's consumption (consumption_this_month): 0.0 kWh
        Overloaded (overloaded): False

        == Configuration ==
        Auto off enabled (auto_off_enabled): False
        Auto off in (auto_off_minutes): 120 min (range: 0-65536)
        Unable to read value (power_protection_threshold): 'enabled'

        == Debug ==
        Device ID (device_id): x
        On since (on_since): 2025-07-23 17:42:09-04:00
        Reboot (reboot): <Action>

        == Smart Plug 2 (P316M) ==

        == Primary features ==
        State (state): True
        Current consumption (current_consumption): 0.0 W
        Voltage (voltage): 120.2 V
        Current (current): 0.0 A

        == Information ==
        Auto off at (auto_off_at): None
        Today's consumption (consumption_today): 0.0 kWh
        This month's consumption (consumption_this_month): 0.0 kWh
        Overloaded (overloaded): False

        == Configuration ==
        Auto off enabled (auto_off_enabled): False
        Auto off in (auto_off_minutes): 120 min (range: 0-65536)
        Unable to read value (power_protection_threshold): 'enabled'

        == Debug ==
        Device ID (device_id): x
        On since (on_since): 2025-07-23 17:42:09-04:00
        Reboot (reboot): <Action>

        == Smart Plug 3 (P316M) ==

        == Primary features ==
        State (state): True
        Current consumption (current_consumption): 37.5 W
        Voltage (voltage): 119.4 V
        Current (current): 0.33 A

        == Information ==
        Auto off at (auto_off_at): None
        Today's consumption (consumption_today): 0.49 kWh
        This month's consumption (consumption_this_month): 0.73 kWh
        Overloaded (overloaded): False

        == Configuration ==
        Auto off enabled (auto_off_enabled): False
        Auto off in (auto_off_minutes): 120 min (range: 0-65536)
        Unable to read value (power_protection_threshold): 'enabled'

        == Debug ==
        Device ID (device_id): x
        On since (on_since): 2025-07-23 17:42:09-04:00
        Reboot (reboot): <Action>

        == Smart Plug 4 (P316M) ==

        == Primary features ==
        State (state): True
        Current consumption (current_consumption): 62.0 W
        Voltage (voltage): 119.9 V
        Current (current): 0.54 A

        == Information ==
        Auto off at (auto_off_at): None
        Today's consumption (consumption_today): 0.618 kWh
        This month's consumption (consumption_this_month): 0.787 kWh
        Overloaded (overloaded): False

        == Configuration ==
        Auto off enabled (auto_off_enabled): False
        Auto off in (auto_off_minutes): 120 min (range: 0-65536)
        Unable to read value (power_protection_threshold): 'enabled'

        == Debug ==
        Device ID (device_id): x
        On since (on_since): 2025-07-23 17:42:09-04:00
        Reboot (reboot): <Action>

        == Smart Plug 5 (P316M) ==

        == Primary features ==
        State (state): True
        Current consumption (current_consumption): 0.0 W
        Voltage (voltage): 120.1 V
        Current (current): 0.0 A

        == Information ==
        Auto off at (auto_off_at): None
        Today's consumption (consumption_today): 0.0 kWh
        This month's consumption (consumption_this_month): 0.0 kWh
        Overloaded (overloaded): False

        == Configuration ==
        Auto off enabled (auto_off_enabled): False
        Auto off in (auto_off_minutes): 120 min (range: 0-65536)
        Unable to read value (power_protection_threshold): 'enabled'

        == Debug ==
        Device ID (device_id): x
        On since (on_since): 2025-07-23 17:42:09-04:00
        Reboot (reboot): <Action>

        == Smart Plug 6 (P316M) ==

        == Primary features ==
        State (state): True
        Current consumption (current_consumption): 0.0 W
        Voltage (voltage): 119.9 V
        Current (current): 0.0 A

        == Information ==
        Auto off at (auto_off_at): None
        Today's consumption (consumption_today): 0.0 kWh
        This month's consumption (consumption_this_month): 0.0 kWh
        Overloaded (overloaded): False

        == Configuration ==
        Auto off enabled (auto_off_enabled): False
        Auto off in (auto_off_minutes): 120 min (range: 0-65536)
        Unable to read value (power_protection_threshold): 'enabled'

        == Debug ==
        Device ID (device_id): x
        On since (on_since): 2025-07-23 17:42:09-04:00
        Reboot (reboot): <Action>


root@kasapi:~/python-kasa/python-kasa# 

Preamble: I have 5 years professional experience working in Cybersecurity from Google, where I originally started as an IT Support lead before moving internally to become a Security Engineer.

Time commitment: I spent between 8 to 12 hours a day studying for this test over a period of 2 weeks (July 1 to July 14). I took 2 days off in between for a break on weekend days.

• Every day I completed between 50-110 questions, either via chapter domain quizzes or by using the free DestCert App on the iOS store.

Important items to consider

• Actual work experience in the field I felt to be invaluable for this exam. Many questions were related to items I had come across before in my Cybersecurity role.
• The breadth of the CISSP exam is huge and the official study guide I used to study is ~1900 pages long.
• CISSP exam is not only a technical domain test but heavily focuses on scenario based “think like a manager” style questions. Keywords like “BEST”, “LEAST”, “MOST” and “GOAL” often are indicators that your multi choice options are all likely valid answers but paying extra attention to what the question is really asking is critical for success.

My study resources and my personal rating on them:

• BOOK (9/10): ISC2 CISSP Certified Information Systems Security Professional Official Study Guide (Sybex Study Guide) 10th Edition
  • 1900 pages long, pretty dense.
  • My focus was reading each chapter summaries, at the end of each chapter there are between 100 to 150 questions specific to the security domain/chapter covered.
  • Each quiz I took I tracked on a spreadsheet with the answer I selected after skimming through chapters or watching video training content.
    • Any quiz question that I failed or got wrong, I took time to understand why I chose the wrong option on my first attempt and then I focused on understanding the correct answer from the answer key at the end of the book.
• FREE Youtube (10/10): Peter Zerger 8 hour CRAM of all CISSP domains and topics.
  • My first day studying I chose to watch close to 12 hours of video training to “set the stage” before taking the quiz questions from the study guide.
  • He focuses on the vast majority of things you need to know, but because of how condensed each domain is, some minor concepts and things I felt were missing from this… lucky for me another training course I took filled in some gaps (more below).
• FREE Youtube (10/10): 50 CISSP Practice Questions. Master the CISSP Mindset.
  • Watch this video the day before the exam to make sure your headspace on how to evaluate questions is in the right place. Remember, think like a manager based on how the question is propositioned.
• LinkedIn Learning video training and practice exams:
  • Mike Chapple (same guy who authored the study guide!) https://www.linkedin.com/learning/topics/certified-information-systems-security-professional-cissp
  • He covers some stuff I felt was missing from the CRAM videos; Chapple speaks slowly so I often played his videos at 1.25x or 1.50x speeds.
• FREE Crytography DestCert mini masterclass
  • This video does a great job at explaining crypto for the exam.
• FREE Youtube (10/10): Peter Zerger Cyber Attacks & countermeasures
  • Perfect dedicated video that covers all of the common attacks and the available countermeasures.
• (5/10) Cybrary CISSP Training by Kelly Handerhan 2024
  • I tried to use Cybrary as a complement resource prior to finding out my library gave me free access to LinkedIn learning courses, I did the first 2 domains videos and wasn’t personally impressed.

How I hacked my study plan?

1. I used AI / ChatGPT / Perplexity to help me understand certain topics or when I needed concepts explained to me in a different way or tone than the book or videos.
2. I practiced every day. Domain quizzes using DestCert app while on the treadmill or when sitting down at the computer I would do more questions from the study guide book which are different questions than the DestCert app btw.
3. I put a deadline to it and chose to go all-in (vs. studying for months). Pay the extra $200 to get “peace of mind” protection in case you may fail your first attempt, I passed on my first try but this exam is tough and things could have easily gone the other way had I not been studying this much.
4. The most important thing during the test: TAKE YOUR TIME, READ THE QUESTION AND ITS OPTIONS MULTIPLE TIMES before committing to any answer.

Good luck!

As I write this I realize the last post I made here was on April 30, 2023 which is over 2 years ago and being honest with myself I haven’t been the most active at keeping this site updated due to being busy with career/life and posting content elsewhere like Github.

As of July 2025 I now have some time to work on hobby things like this blog and self-improvement goals like obtaining the CISSP certification (Certified Information Systems Security Professional). Taking a break after 10 years at Google and looking forward to see what’s next on my career journey.

• https://www.domnest.com/
• https://www.domcomp.com/
• https://tld-list.com/

• https://www.serverhunter.com/
• https://oneprovider.com/promotion

Backstory: I used FriendlyElec eFlasher tool to flash a raw .img file to the onboard eMMC 8GB storage of my NanoPi. This led to an onbootable system. I had to use UART serial to view the errors and debug.

You will need a UART serial connection and putty installed. This quick how-to guide is intended to be ‘cliff notes’ on what I did to get my device back in working order; you will have to teach yourself or search how to use some of these processes.

Steps

1. Connect UART debug serial to the board.
2. Use putty or terminal to verify that device is unable to boot due to onboard eMMC image.
3. Prepare a microSD card for recovery (it will wipe all your data). Download rk3328-sd-friendlywrt-5.15-20220125.img and use balenaEtcher to prep the MicroSD.
4. Make sure the board is disconnected from power but you have the UART connected and putty running. Now short the “MASK” positive and negative connectors in the board with some cables; I used the GPIO connector nearby as short-circuit source since simply joining both MASK connectors together wasn’t doing anything.
5. While you are shorting the MASK and the board is powered off, then turn on board. It should short-circuit at boot and skip using eMMC for boot and use the SD card instead.
6. Once the image is booted, use SSH to connect to the OS and wipe out the

/dev/mmcblk2

Note: this guide is for Windows, you may use it for getting an idea of what the requirements are for a successful firmware but don’t expect a guide for any other OS to be made. If you find this guide saving you time and hassle you can thank me here.

Prepare your USB stick

You will need to property format and partition your USB in order for the monitor to detect the files. Let’s wipe all the data in a USB stick below.

• Open a Command Window (cmd)
• Enter diskpart
• Enter list disk (it is important you KNOW which disk is the USB key you are formatting)
• Enter select disk x where x is your USB key
• Enter clean
• Enter convert MBR
• Enter create part primary
• Enter select part 1
• Enter active
• Enter format fs=fat32 label=”firmware” (Label is optional – ensures USB key is labelled as ”firmware” in Explorer etc)

Download firmware and copy to USB

Visit samsung.com support page for the G9 monitor, grab the .zip file containing the update. It should look like something like “M-T9549GGAA-1016.0[1109]” (1016.0 is the current version as of this posting).

1. Download .zip file from samsung.
2. Unpack .zip
3. Grab the single file “M-T9549GGAA-1016.0[1109]” and put it on the USB stick on the parent (never put inside a folder inside usb stick).
4. Connect USB to back of monitor; ensure all other USB plugs are unplugged and only the USB stick is connected.
5. Turn on monitor (if not already on), go to MENU > Support > Software Update and hit enter.
6. Monitor should detect the update file/usb stick and apply the newest firmware.

Validate a successful update

Before and after a firmware update do these steps to check your firmware version on the monitor.

1. Turn on monitor (if not already on).
2. Go to MENU > Support > Information
3. Your Model, Serial Number, Software version is displayed. Take note of it.

If samsung.com says your current version is equal or higher than their download then your firmware does not need to be updated.

Important notes (read this!)

• DO NOT RENAME the .img files after unzipping. Just copy them to USB as it is named.
• SAMSUNG ARE IDIOTS. Upgrading a very old firmware to latest version may not be detected as an update; regardless of the proper naming and format in the USB stick. If you face errors of ‘no update files detected’ then find the next firmware release after your current running firmware. I was forced to upgrade from 1008 firmware to M-T9549GGAA-1012.1[984C].img before I was able to flash the latest version downloaded from samsung’s website.

If this guide / tips / how-to saved you time consider thanking me here.