• Destination sign - klop.solutions - because tech matters, wherever on earth you are

    Klop.solutions

    Because tech matters. Wherever on earth you are.

Latest posts

USB audio is complicated, and we humans don’t like that. So we start simplifying things, even vendors do that. Unfortunately, simplification can lead to wrong information. Like as with USB async audio, the DAC “asks” for data (some vendor’s flyer, long time ago). With USB, there is one master, the host. Only firewire was able to reverse the roles. Or what about digital is digital, so cables don’t matter. The data packets send with USB audio are fire-and-forget. Bad cable means packet loss. But since it’s digital, a good cable is good enough. Better “copper” does not improve things. Since USB audio is fire-and-forget (USBRead More →

Some years ago I played with Home Assistant. I really like the concept of their “bullet proof” design. Since that is what you need for home automation. But it’s still a geeky system, compared to Philips Hue or Apple Home. And that’s fine, but do I want my lights controlled, during 3 weeks holiday abroad, by such a system? My setup uses mostly Hue lights, switches and a sensor. This is controlled by the Philips Hue bridge, which connects to Apple Home through Homekit. I think this is a setup used by many, and the configuration is very simple with the Home app. With thisRead More →

Modern cryptography is key to modern on line communications. This area of IT looks very complex and daunting to many, so it’s always a good start to get the basics right. I’m not gonna use much words for explaining, others have done that much better. Communicate secretly requires encryption so others cannot read it. Encryption uses some secret or key. Both sides need to have this key. So far, nothing new here. Has been done like that for thousands of years. But wait, what is missing here… Right, knowing who is who or trust. Without trust, I might send a secret message to the wrongRead More →

The IPv6 prefix I got from my ISP in Denmark did not stick, as explained here. Well, Google revealed that my ISP expects IAID to be 1 (one), when requesting a prefix using DHCPv6. The mechanism around IAID is explained in RFC3633. And guess what, the DHCPv6 client in my Mikrotik router requests a prefix with IAID 2 (two), not 1. This IAID is a number associated with the interface, and in my case WAN interface “ether1” has IAID: 2. You can find your IAID as follows: “:put [/interface find where name=“ether1”]”. I have not found a way to change this mapping in RouterOS. RouterOSRead More →