MikroTik: Simple Guest WiFi Setup on hAP ax³ (WifiWave2)

MikroTik routers with WiFi, like hAP ax³ with wifiwave2 package, can be used to create a “guest WiFi network”.

The guest WiFi gives clients access to the Internet, but isolates them from your main network, so they can’t see and don’t have ability to access any of your devices on it.

For example, to improve the security, you can put all your IoT devices on the guest WiFi network, so if one of them is hacked, the attacker won’t be able to get access to the devices on the main network.

This post shows how to perform a quick setup of the simple guest WiFi network on MikroTik hAP ax³ with wifiwave2 package. (more…)

MikroTik: Block Internet Access by IP/MAC

More and more smart devices with an Internet connectivity are appearing in our homes.

If you don’t want your smart socket, robot vacuum cleaner or IP camera to leak your personal data, you can block these devices from accessing the Internet by their IP/MAC addresses.

In this post I will show you how to block an Internet access by IP/MAC using a MikroTik router. (more…)

Windows: Measure Command Execution Time in PowerShell

The time command in Linux and Unix-like operating systems is used to determine how long a specific command or script will take to run.

In Windows PowerShell there is a built-in Measure-Command, that can be considered as the Linux time command equivalent.

This short post shows how to use the Measure-Command in PowerShell to evaluate the processing time taken by different commands, scripts or programs in their execution. (more…)

Dig Without Cache

dig can return cached responses because it caches the results of previous queries to improve performance.

For the same reason the cache responses can come from the configured name servers.

This is useful when you are querying the same domain multiple times, but it can be problematic when you need to check if a change you made to a DNS record has propagated.

Luckily, the dig command can be forced to resolve without using cache and this post demonstrates how to do this. (more…)

Kubectl: Port-Forward to Service – Kubernetes

kubectl port-forward is a Kubernetes command that allows to access internal cluster resources from outside the cluster.

It tunnels a traffic from a specified port on a localhost to the specified port on the specified Pod.

The kubectl port-forward command is useful for troubleshooting issues, setting up services locally without exposing them, and debugging applications within the cluster.

This post shows the examples of how to use the kubectl port-forward command to access the internal cluster resources from the locathost. (more…)

Install Kubectx & Kubens on Windows

kubectx and kubens are two command-line tools that can help to manage Kubernetes clusters and namespaces more efficiently.

kubectx is used for switching between Kubernetes contexts (clusters) faster, while kubens is used for switching between Kubernetes namespaces more easily.

This post shows how to install kubectx and kubens on Windows so they can be used from PowerShell or Command Prompt (CMD). (more…)

WHOIS Command on Windows – PowerShell & CMD

In Linux, a whois command is used to lookup information about domains or IP addresses.

But if you try to run the whois command on Windows from PowerShell or command prompt (CMD), you will receive one of the errors below:

‘whois’ is not recognized as an internal or external command,
operable program or batch file.
– or –
whois : The term ‘whois’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

This post shows how to install the whois command on Windows and make it available in PowerShell and CMD. (more…)

[SOLVED] PowerShell: Running scripts is disabled on this system

While trying to run a PowerShell script you may get an error message that says “cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.

This error message is due to the default execution policy set by PowerShell, that determines whether PowerShell scripts can be run on a system.

By default, the execution policy is set to Restricted, which means that PowerShell scripts cannot be run.

To fix this error message, it is required to change the execution policy to RemoteSigned and this post shows how to do this. (more…)