What Is a Firewall and How to Configure Basic Rules
Most Australian homes have a small box between the street and the laptop, usually supplied with the NBN modem, and plenty of people treat it as plumbing. A firewall is plumbing with judgement: it reads each packet travelling in or out, decides whether to pass it, drop it, or write a line in a log so you can see what happened at two in the morning.
Formally, a firewall is a set of rules applied to traffic at the boundary between a private network and the wider internet. Because most households here connect over the National Broadband Network — fibre to the node, fibre to the premises or hybrid coax — that boundary is sharp, and it becomes worth understanding the moment you add a NAS or a security switch.
The guide covers what filtering does, which hardware suits homes and small offices, and a baseline set of rules you can type in without a networking degree. No prior knowledge is assumed beyond knowing your router's IP address.
How Filtering Actually Works
At the simplest level, a firewall matches packets against rules. Each rule looks at the header of a packet — source and destination address, protocol, port number — and takes an action. A match means allow or deny; no match means the next rule applies, and if nothing matches, the default rule decides.
Modern firewalls add stateful inspection: the box keeps a table of connections it has seen, so a reply packet returning to the laptop you just browsed with is accepted, while a stranger on your port from an address you never contacted is not.
NAT is regularly confused with security. Network address translation rewrites your laptop's private address into the public one so the return path works; that is address plumbing, not protection, and a router doing NAT with no filtering is an open door with a number plate.
Choosing Hardware for Homes and Small Offices
Start with what the provider gave you. Telstra, Optus, iiNet, TPG and Aussie Broadband all ship a modem or router with basic filtering enabled, and on a straightforward NBN plan that may be plenty. The catch is what you cannot change: thin logging, no rule ordering, firmware you cannot update.
A middle option is hardware you control, such as a managed network security switch or a dedicated firewall appliance. The site's product reviews cover switches with VLAN support, while appliances built on pfSense, OPNsense or FortiGate give you a real rule list and changeable defaults. Synology NAS boxes also carry a simple firewall of their own, worth configuring first.
Working Out What You Actually Need
Rules should follow real traffic rather than imagined threats. Start outbound: browsing on 80 and 443, DNS on 53 to your own resolver, NTP on 123, mail on 587. If the business runs VoIP handsets, allow SIP signalling and the RTP media ports, and check how each handset handles NAT, since models are compared in this site's video phone guide.
Inbound is where home setups usually go wrong. The default should deny everything arriving from the WAN, and each exception should be deliberate: a forwarded port for a game server, a camera, or a NAS you want reachable. Streaming services such as iview or Stan need no inbound rules at all.
Configuring a Working Baseline
Log into the admin interface at the gateway address printed on your router's label and work top down, because rule order matters: the first match wins, and a catch-all placed above your allowances overrides them.
A practical baseline runs like this. Allow established and related traffic so replies to your own connections flow. Allow outbound traffic from the LAN subnet, usually 192.168.1.0/24. Deny unsolicited inbound traffic on the WAN interface. Disable remote administration on that interface, usually a single checkbox. Permit DHCP on the LAN side.
Add logging on denied inbound packets at a modest level rather than full debug, or the log fills with noise before you read it. A port forward for a game server or a Synology box serving photos only works if your provider hands you a public address, and several Australian NBN plans use carrier-grade NAT.
Locking Down the Box and the Business
The firewall you are configuring is itself a computer on the internet. Change the default password, turn off UPnP, keep the firmware current, and switch on two-factor authentication for the admin portal where the vendor supports it.
The Australian Cyber Security Centre reports that small businesses lose money to compromised email more often than to clever intrusions, so pair these rules with multi-factor authentication on mail and cloud accounts. Vendor advisories are worth scanning through the site's network security news feed.
Checking the Work and Keeping Watch
Check the work rather than assuming it. Confirm browsing, mail and streaming from a laptop on the LAN, then use a port-checking service to see what your public address exposes. Denied log entries name the source address and port, which usually identifies the misconfigured device.
If the rules look right but traffic crawls, look at the hardware underneath, because a storage bottleneck can masquerade as a network fault; this SATA-to-PCIe adapter guide shows how much the physical path matters on an older machine.
Aussie fatalism helps here: 'she'll be right' fits a faulty kettle, not a firewall. The baseline worth keeping is default deny inbound, allow established traffic first, permit only the outbound destinations you actually use, disable remote administration on the WAN interface, change the admin password, and log denied packets so you have evidence next time things go quiet.