Technical Anshu
Tutorials Blog
🌐 Synology Networking

Multiple LAN Ports on a Synology What the Extra Cards Really Do

In the video, the Synology runs as a virtual machine on VMware. Two extra network cards go in, each gets its own MAC address and static IP, and the ports take separate jobs — LAN on one side, WAN on the other. This page follows that same build and adds the part nobody says out loud: what extra ports honestly change, and what they never will.

✍️ Technical Anshu🖥️ Synology DSM on VMware⏱️ 12 minute read
🎥 The full build in the video — extra LAN cards added in VMware, MAC addresses assigned, static IPs set in DSM

Most NAS boxes ship with one or two LAN ports, and most owners never touch the second one. The video shows a fuller build: the Synology is a VMware virtual machine, so "adding a LAN card" means adding virtual adapters — VMXNET3 cards with manually assigned MAC addresses — then giving each interface its own static IP and its own job inside DSM. Below is that same route, in order, with the honest expectations filled in: extra ports buy you separate duties, more simultaneous users and a spare path when something fails. They do not buy one user double speed, and pretending otherwise is how people end up disappointed.

DSM — Control Panel › Network › Network Interface
LAN 1 — office network (static)192.168.1.10
LAN 2 — WAN side (static)192.168.2.10
LAN 3 — spare / failoverNot configured
Bond 1 (optional) — LAN 1 + LAN 2One IP for both
The Network Interface list from the video's build, with example addresses. Your own IPs will follow your own network plan.
1

Step 1 — Add the Cards While the VM Is Off

In the video, the Synology is a VMware virtual machine, so the hardware step happens inside the VM settings, not with a screwdriver. On a physical Synology this same step is simply plugging the switch cables into ports you already have.

  1. Power the VM completely off — not suspended
  2. Open Edit Settings and add a Network Adapter for each extra LAN card you want (the video adds two)
  3. Keep the adapter type as VMXNET3
  4. Expand each new adapter, switch its MAC address from Automatic to Manual, and type in a unique MAC for that card
  5. Power the VM on and log in to DSM

Why the manual MAC matters: an automatic virtual MAC can change when VM settings are edited, and DSM ties each interface to its card. A changing MAC makes ports shuffle places, so your carefully set static IPs land on the wrong interface and the NAS seems to "randomly" vanish. One card, one permanent MAC, written down — that is the discipline the whole build rests on.

2

Step 2 — Give Every Card One Job and One Static IP

In DSM, open Control Panel > Network > Network Interface. The new adapters appear as extra LAN entries. Before changing anything, decide each card's single job: this one serves the office LAN, that one faces the WAN side, the third is a spare.

  1. Select an interface and click Edit
  2. Under IPv4, choose Use manual configuration
  3. Give the card an address from the network it serves — the LAN card from the office subnet, the WAN-facing card from the router-side subnet — and pick addresses outside the DHCP pool so nothing else is ever handed the same number
  4. Only the interface that reaches the internet needs the default gateway; the others keep a plain address
  5. Apply, then reconnect to DSM at the new address to confirm it stuck

DHCP is fine for a printer. It is wrong for a server: the NAS is the box every PC and backup job points at, so its addresses must never move.

3

Step 3 — Option A: Keep the Ports Separate, Like the Video

The video's layout keeps the cards independent. The LAN card serves the office PCs — file shares, backups, everyday access. The second card faces the WAN side — that is where remote access and outside-facing services arrive, while sharing stays on the internal port.

Then harden the split exactly as shown in the video: open Control Panel > Security > Protection and enable Auto Block and DoS protection. Add firewall rules to match the design — full access from the LAN subnet, and on the WAN-facing interface only the ports of services you deliberately publish. A port with no job stays shut.

4

Step 4 — Option B: Bond Two Ports Into One Interface

If separate duties are not the goal, DSM can join two ports into a single logical interface called a bond. One IP address, two cables behind it.

  1. Go to Control Panel > Network > Network Interface > Create > Create Bond
  2. Choose a mode — Adaptive Load Balancing needs nothing from the switch, while IEEE 802.3ad needs link aggregation switched on at the switch too
  3. Select the two LAN ports and give the bond one static IP

A bond pays off when many users hit the NAS at the same time, or when one port is kept as insurance for the other. What it does not do is the subject of the next honesty check — and of a full page in this series.

5

The Honest Bit — What Extra Ports Really Buy

Here is the part the product boxes skip. Extra ports genuinely buy three things: separate duties (the LAN/WAN split in this video), more people at full speed simultaneously, and a spare path so a dead cable or port does not take the NAS offline.

They do not buy one user double speed. A single file copy is a single connection, and a connection lives on a single link — two gigabit ports still give one copy roughly one gigabit, about 110 MB/s. If one PC truly needs more, the honest answers are a single faster port (2.5 or 10 GbE), or SMB Multichannel on models that support it — not a bond.

One more honesty note for this exact build: these cards are virtual. The real ceiling is the host machine's physical network port and the switch behind it, shared with everything else on that host. And DSM is Synology's software for Synology hardware — a VM build like this is a lab setup, fine for learning and testing, not a licenced production NAS.

🔴 One rule from the video worth copying exactly: no two cards share a MAC address, and no card keeps a changing one. Duplicate or shifting MAC addresses make interfaces swap identities, static IPs land on the wrong port, and the NAS "randomly" disappears — the most confusing fault in this whole setup, and the easiest one to prevent.

🎥 See It Done Live in the Video

Adding the cards in VMware, assigning the MAC addresses and setting the static IPs in DSM — the complete build, shown live in the video.

▶️ Watch Full Video
❓ Common Questions (FAQ)

Will two LAN ports make my file copies twice as fast?

No. One copy travels as one connection, and both separate-port and bonded setups keep that connection on a single link, so one user still tops out near one port's speed — about 110 MB/s on gigabit. The gain is for several users at the same time, a separate WAN and LAN split, or failover. A single faster port (2.5 or 10 GbE) is the fix for one user.

Do I need a special switch to use two ports?

Not for the setup in the video. Separate interfaces, Adaptive Load Balancing and Active/Standby all work with an ordinary switch. Only the IEEE 802.3ad and Balance XOR bond modes need a managed switch with link aggregation configured on its side.

Why does the video set MAC addresses by hand?

Because the Synology is a virtual machine. VMware can hand a virtual adapter a new automatic MAC address when settings change, which makes DSM see a new card and shuffle the ports. A fixed manual MAC keeps LAN 1 as LAN 1 forever.

This guide is based on the Technical Anshu video on adding multiple LAN cards to a Synology NAS • Stuck on a step? Ask in the video comments — answers happen there 🙏