Skip to main content

How it Works: Ralph Breaks the Internet

Disney's Ralph Breaks The Internet, the 57th entry into the Disney Animated Canon, was released on Wednesday, November 21st, 2018.

I saw it - Loved it more than the original, wanted to watch it with the mind of a Network Admin  instead of turning my brain off all the way.

While more technically sound than I expected, there are a few picks here and there.



First of all, Mr. Litwak plugs the WiFi router into the same power extension board as he does at least some of his other arcade machines.

I'd say "Good on not plugging them all into the wall!" but it would be impossible anyway. So at least 6 games would go down if that particular power supply went off, and this doesn't look like an establishment that would have a generator.

Redundancy? Not quite, but could be worse.

Now, when the router is plugged in, it's just the router. It's not hinted to be a router/switch combo like one from a ISP. There is an Ethernet cable plugged in, so let's just assume it's off screen.

When Vanellope and Ralph go into the router via it's plug, it's not working or buzzing. It should be! It's plugged into power and connected to the internet, but it's only seen as "on" when Litwak ... presses an icon on his old Macbook that has a PC Wireless Adapter that's connecting to the signal.

The sequence hints that the router is only working when someone is actively using the connection, but it doesn't work that way.

It could be something like the really old dial-up methods or establishing a connection for the first time through a ISP's splash page.

He sets up a password, so...okay on security there, even if it is a very weak password. Should be something like

01-n3-4GxM

How Ralph and Vanellope actually get around said internet - Nearly every layer in the OSI model was relatively represented from Session (Some users get disconnected) to Presentation (The eBay pages), to Physical (going to the internet via the Ethernet cable), Network (Because Instagram, Pintrest, and Amazon aren't all hosted on the same network!), Transport (actually travelling within the internet).

There's no Data Link stuff, and we'll touch upon Presentation later.

The little avatars - Cookies. One approaches Knowsmore and he says "Oh, little Isabel is going the ballet route. Let's hope it goes better than the soccer craze." Why would he say that if she didn't have a past search history?

Spoiler territory;

There is a virus that's a worm, though they never say the word worm, but it acts like one, relying on "insecurities in the code" of games.

To keep it still not-too-spoilery, this shows a case of fairly bad programming for a particular game more than anything else. I was tempted to call this particular instance part of the Presentation layer representation, but I'm not too sure.

It's well worth the time to check it out, at least.



EMPLOYERS: This is me putting knowledge to use while talking about the product of a Target Company.

Comments

Popular posts from this blog

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

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 intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

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

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl