Case Study: The Offline/Online Laptop

alt: Three panels of a dog with a toy. Panel 1: 'Pls release IP address'. Panel 2: 'No release', Panel 3: 'Only hold onto expired IP'

It's not practical for home internet services to let end users distribute their own IP addresses to their devices.

The option is there, but it's far easier to let people use DHCP - You get a pool of addresses for your devices, and the router does the work in distributing them.

That way, your devices can talk to each other (Somewhat - in a L2 network, they don’t need IP addresses) and reach the internet!

But what happens when one Windows 10 device is unused for months?

The device is totally off. It holds onto an expired IP address - and then it can't get back on. That's what happened this week.

After scanning with Wireshark, no DHCP packets were being sent at all. The laptop didn't want to connect to any home internet router, of which there were two - The main one and the extender.

Flushing DHCP didn't work. Nor did resetting Winsock and the TCP/IP stack, which were new to me. Restarting didn't work either.

When you connect to a new network, it asks for the password, with the text "Or, you can hit the button on the router".

On the top of at least this Xfinity router, there is a button you can press. When a device is looking to connect, the router does all the work in sending the DHCP initiation sequence. No password required.

That forced the computer to release its expired IP address and accept a new one, saving, at the very least, about 50$ for a new extender.

The extender I use is still old and failing, but it can hold on for a moment longer.

Comments

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return. In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now OpenTofu Sometimes, I write articles even when things don't work. It's about showing a learning process. Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach. That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init. As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory

RUN TCP/IP | Morgan Lucas is Tech Blogging

Search This Blog