Stéphane Thirion
  • Home
  • Consulting – Raidho
  • homelab
3K
0
0
0
Stéphane Thirion
Stéphane Thirion
  • Home
  • Consulting – Raidho
  • homelab
  • Ubiquiti

Creating isolated / dedicated networks with Ubiquiti UniFi

  • December 27, 2021
  • Stephane Thirion
Total
1
Shares
0
0
1
0
0
0
0

When you have a rather large network at home, you want and need to secure things a little bit. Family network usage / business network usage / IoT network usage all of these needs to work without impacting each other.

This is my first blog about Ubiquiti UniFi, I’m using this hardware for a year now and I’m very satisfy by the quality and the possibilities of all their products. On top of that my learning curve on the network knowledge has grown a lot, that’s a win !

For this blog I want to share how I created an isolated / dedicated network for all my IoT devices (cameras, car, doorbell, alarm etc etc)

Let’s do it !

Creation of a new network

The first step is to create a new network, to do so click on the advanced option on the left vertical pane and on Networks

Then click on Add a New Network

To create this new network we will need to provide

  • A name : IoT
  • a Gateway IP and a subnet : 192.168.110.1/24
  • a vLan ID : 110
  • Few other specifications such as DHCP

We can now proceed to the new network creation by clicking on Add Network

Creation of a new Wireless Network

Click now on wifi above the networks menu we just used. We can now create a new wifi network

To create a new wifi network we need

  • a name
  • a password
  • to chose the network we previously created
  • choosing the access point to broadcast this new wifi
  • few other options such as wifi band, protocol to use, hiding or not the wifi network.

Click on  Add Wifi Network to create it.

It means that all the devices connecting through this new wifi network will be on the vLan 110.

Assigning vLan 110 on UniFi switches

Now we will configure switch ports to use the configuration we build above.

Of course I know which port are used by what so I can assign vLan to the proper devices. I kow on this USW-Lite-16 PoE switch two cameras are connected on the first two ports.

Let’s click on the first one (orange one)

We can enter a name for this port (mandatory but it’s easier to find out what port is used by which device) and then select the IoT vLan then click on Apply. I had to reboot my cameras so they will have a new IP Address in 192.168.110.0/24 subnet.

Also by default, all the traffic is allowed between the different networks.

Blocking network traffic form / to the new IoT vLan

We need to navigate to the Settings menu and then select Firewall & Security

I already have few rules here in Lan IN so we need to create new ones. To do so we will click on Create new rule

In our case we want to isolate the IoT vLan / Network to communicate with other network (the default one for example)

Give the rule a name, make sure that Before predefined rules is selected, the same with Enabled.

Select Source and change the Source Type to Network. Once that is done, use the dropdown menu to find the network you want to isolate (IoT) and select it. Under Destination, change the Destination Type to Network and in the dropdown, select the network you don’t want device in your source network to access. In my case that’s the default network.

Click on save,  the rule should now show up under your LAN IN rules. The way it’s set up now, all traffic from all other networks to the new network is allowed, but no traffic is allowed to be initiated from this new network to the network selected in destination above.

We have now wifi + wired network isolated on the IoT vLan. This was fairly easy on the firewall side because I don’t need to access with devices from the lan to these cameras. The next step will be to add / move in this vLan all the Raspberry Pis / Virtual Machines that manage IoT, and there will be then some firewall tweaking to do in order to allow access from the main LAN network

You can repeat this as many time as you want to create isolated network.

Total
1
Shares
Tweet 0
Share 0
Share 1
Share 0
Share 0
Share 0
Share 0
Related Topics
  • IoT
  • network
  • ubiquiti
  • unifi
  • vlan
Stephane Thirion

Previous Article
  • ADC
  • Experience
  • Linux

Cloud yes but no, thanks (there is some Citrix)

  • December 7, 2021
  • Stephane Thirion
View Post
Next Article
  • Cloud
  • Docker
  • Kubernetes
  • Raspberry

Kubernetes cluster with Raspberry Pi(s)

  • December 28, 2021
  • Stephane Thirion
View Post
You May Also Like
vmware
Binance – Affiliated link
Coinbase – Affiliated link
Blog Stats
  • 1,239,162 hits
Categories
  • Amazon (1)
  • Apple (20)
    • iOS (5)
    • Mac OSx (11)
  • ArchY.net Site (30)
  • Azure (8)
  • Certifications (3)
  • Citrix (211)
    • ADC (4)
    • Citrix Virtual Apps and Desktops (5)
    • DaaS (2)
    • NetScaler (15)
    • Password Manager (3)
    • Personal vDisk (5)
    • Power and Capacity Management (3)
    • Provisioning Services (22)
    • Receiver (29)
    • SDX (2)
    • ShareFile (8)
    • Single Sign On (3)
    • SmartAuditor (2)
    • Storefront (12)
    • Synergy (25)
    • User Profile Management (2)
    • VDI (7)
    • WebInterface (21)
    • XenApp (84)
    • XenApp Plugin (3)
    • XenClient (10)
    • XenDesktop (55)
    • XenServer (42)
  • Cloud (13)
  • Crystal Ball (2)
  • CTP (13)
  • Docker (2)
  • Events (35)
    • E2E – PubForum (9)
    • Geek Speak (3)
  • Experience (53)
  • Kubernetes (2)
  • Licensing (3)
  • Linux (12)
  • Microsoft (147)
    • Active Directory (1)
    • Azure (8)
    • Office365 (4)
    • PowerShell (19)
    • RDS (5)
    • Windows 10 (6)
    • Windows 2003 (21)
    • Windows 2008 (20)
    • Windows 2008 R2 (54)
    • Windows 2012 (13)
    • Windows 2012R2 (13)
    • Windows 2016 (18)
    • Windows 2019 (4)
    • Windows 2022 (1)
    • Windows 7 (27)
    • Windows 8 (19)
    • Windows Virtual Desktop (1)
    • Windows XP (11)
  • News (5)
  • Raidho (2)
  • Raspberry (3)
  • Scripting (13)
  • Security (5)
  • Slide Deck (1)
  • Thin Clients (3)
  • Twitter (1)
  • Ubiquiti (1)
  • Uncategorized (13)
  • VMware (28)
    • VMWare WorkStation (2)
    • vSphere (16)
Stéphane Thirion
Don't Follow the Trend

Input your search keywords and press Enter.

 

Loading Comments...