Members Area
BlueSky
Members Area
Search
Latest Posts
@Ko-Fi
Buy us a Ko-Fi
@PayPal
Or support us via PayPal
@Amazon
Or buy from Amazon to help keep this site ad free
@Thank you
to our site members
How to setup Google Nest WiFi | Part 20 | Port forwarding
What Are You Looking For?
Recommended for you

How to setup Google Nest WiFi | Part 20 | Port forwarding

0
google next wifi port forwarding

In this video we take a look at how you setup port forwarding, on a Google Nest WiFi router. So we will be referring to a process that allows a device on our home network, to be accessible from the Internet.

A Port forward is simply a way to detect incoming requests, and redirect specific traffic to a device on our network. This can be useful in many scenarios; such as accessing a security camera remotely. Hosting a website or game server, or running a remote desktop connection.

Note: In this example we will be creating a port forward to a Synology NAS. For more information on how to configure a Synology NAS please see our how to guides.

Quick reference notes

  • Open the Google Home app.
  • From the Home page select Settings
  • Within Settings locate and choose Nest WiFi – Advanced Networking – Port Management
  • Select the New (+) icon to add a port forward
  • A list of the devices connected to your router are displayed.
  • Select the device that you wish to create a port forward for
  • Now in the add rule panel, enter the port number and data protocol you wish to use

Note: When port forwarding you have two different data protocols to choose from. Transmission Control Protocol or TCP, provides the guaranteed delivery of data, error checking, and sequencing of data packets. This makes TCP very useful for applications that require reliable and error-free transmission. So we would use TCP with services relating to web browsing, email, file transfers and online gaming. User Datagram Protocol or UDP, is used for faster communications, but does not guarantee delivery. So UDP tends to be used with applications or services that require speed. This would include video streaming, DNS and online gaming.

  • Select the Save button
  • Test that the port forward is now working. We find Shields Up! to be very useful when testing a new port forward

Firewall port being Open Closed or Stealth

When discussing firewall ports you will see reference to ports being open, closed and stealth. While open and closed ports are fairly self explanatory, stealth is a bit different. While a firewall port when probed will respond as being either open or closed. A stealth-ed port will remain silent.

The aim of this behaviour is to provide another layer of security, as the person doing the probing will presume there is no device behind the probed port and move on to their next target. However, as not all services will work if a port is stealth-ed and certain services will have to use default ports. An attacker does not always need to know if a port is open or closed. You might find that ‘stealthing’ a port to be of only limited value. 

Reference materials

Add a comment

Leave a Reply

Your email address will not be published. Required fields are marked *

You might also be interested in these: