Skip to main content

Logically Planning a Network ft. Shopify

 "We are designing a new workspace with 3 floors. On average, there will be 100 devices on each floor that require wired and wireless connectivity. Submit a network design including: (1.) A network diagram (2.) Hardware choices (3.) VLAN and subnetting information (4.) Anything else you think is relevant."


 This was a question for a position at Shopify. While it was publicly available, I decided to wait and post this when the position closed.

The Methodology/Framework

Break it into chunks. Separate it by something, in this instance, the floors.

Determine the departments.

Subnets per floor - I'm not using CIDR.

Pick the hardware.

Ask other questions.


This company uses Juniper and Aruba products. As you've seen, Juniper is far easier to get started with. I tried using Cisco DevNet for automation work without using a Linux machine to remote into it - Absolutely arduous.


EX9200 Switches - 120 ports, to account for growth.


 Shopify handles business proceedings and gives online shops a web interface, but what would this department specifically be doing? There's some cloud database somewhere else handling those transactions, not these people.

Without that information, I'm accounting for potential growth and suggesting a MX10.

AP33 Juniper WAP - Remember backwards compatibility. We don't know how old some of these nodes will be that are coming onto the network.

Which medium - Wired or Wireless - Would the devices be using the most? With my laptop, if I connect it via Ethernet cable to my router, it will only use one connection or the other - It won't use Wi-Fi and Cable at the same time.


 This Juniper firewall is an on-prem appliance. You may not want the extra physical appliances and opt for a software firewall package for all of your nearly 300 end points. As this encompasses the entire network - think drawing a circle around a network and calling it a firewall - consider it.


 Since the machines need both wired and wireless, let's make them all laptops. That means they need an Ethernet port - Like this Lenovo Thinkbook

Will they be using IP Phones? Network printers? 


There are no instructions as to how the systems will be organized, so that means I can do as I like! Let's assume that the 'average' of 100 devices means 100 or less.

FLOOR 1: 94 Devices

29 - Sales

25 - Help Desk

5 - Food and Beverage Stations (Think purchasing at a company cafeteria. Imagine they use Square devices.)

20 - Copywriters

20 - Secretaries


Subnet Bits: 3
Max # of Subnets: 8
Hosts per Subnet: Want to minimize the addresses in them to prevent waste, but things don't fit so neatly in the real world.
Mask Bits: 27
Hosts per Subnet: 30. We could possibly make more subnets and dictate them as "Sales1" and "Sales2" for instance, as to not absolutely push the limit, and the amt of hosts in each would be lessened.

FLOOR 2: 90 Devices

30 - Marketing

30 - Meme Makers

30 - TikTokers

This is a little easier, because we can assume that there will be more people added to the Marketing or TikTok VLANs, so I feel better regarding more hosts per subnet here.

Max # of Subs: 4
Subnet Bits: 2
Mask Bits: 26
Hosts Per: 62

FLOOR 3: 99 Devices

40 - Customer Support

55 - HR

4 - Level 3 Techs

I'm okay with breaking departments into multiple subnets here. With 30 hosts per subnet, there's growth allowed for each department. There can be 2 for CS and HR. Level 3 techs wouldn't need 2 subnets of 30 hosts unless they hired some more people.

Max # of Subs: 8
Subnet Bits: 3
Mask Bits: 27
Hosts: 30

You could also account for growth with 4 Subnets of 62 hosts per subnet, but that's too much for L3 techs, even accounting for growth.

Assume that all devices are reaching an internet and an intranet. Do we need other machines to host internal pages and files?

 Do some departments need more of those resources than others? For example, should Sales and Help Desk get more throughput than HR?


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