View Full Version : 2 NICS different MTUs

01-27-20, 07:08 PM
Is it possible to have 2 NICs, one for internet use with 1500 MTU and the other one for NAS with 9000 MTU?

Both will be using same router and PC

Is there a special guide for this?

01-28-20, 09:29 AM
You can set different MTU size for different NICs. There are some requirements for larger MTUs - the adapter properties should support jumbo frames, you should be using a gigabit switch that supports jumbo frames as well.

To make one NIC route to a specific IP, and another to the gateway/internet/other clients is not very difficult if the two NICs are on separate subnets. What makes it a bit harder is you probably want to keep the NAS in the same subnet as all other local network devices, so that it is accessible to everyone on the LAN. This then requires setting a static route.

Let's say, your router/gateway/DHCP server is at, net mask (you can check this in command prompt with: ipconfig /all). Your first adapter, NIC1 is for all traffic, set with DHCP and normal 1500 MTU, second adapter NIC2 is set with 9000 MTU and a static IP. You are using gigabit switch, etc.
Let's assume your DHCP range is
Let's assume your NAS is set to a static IP:

Setup your two NICs.

First NIC: Let's say it gets some 192.168.0.x IP address via DHCP, netmask, default gateway
Your first NIC for all/default traffic should also be set to higher priority, so that default traffic uses it. You can check each NIC priority / metric in the adapter settings, or using this in command prompt: route print (lower metric means higher priority). See: https://www.speedguide.net/faq/how-to-tell-windows-to-use-a-different-default-350

Second NIC: You will want to use a static IP outside of DHCP range (so that you can set a static route). Let's say it is set to, netmask

Now, you have to specify a static route, so that your NIC2 is used ( ) to connect to the NAS ( directly. This can be accomplished with the "route" command in command prompt.

Before we set the route, you need to note each "interface" and their "metric" again, using command prompt "route print". Let's assume NIC1 is interface "if" 11, and NIC2 is interface 12.
Then, still in command prompt with the route command, add a new static route to your NIC2 (intrrface 12), something like that:

route -p ADD destination MASK subnet_mask gateway_ip metric_cost interface

route -p ADD mask IF 11

In this example, " -p " specifies the route should be persistent (survive reboots), the number " 11 " at the end specifies the interface number of your NIC2. The subnet_mask is because we only want to set a very specific route that affects only this one interface.

Alternate static route (not using the NIC2 specific interface): route -p add mask

You may have to redo this after Windows updates, etc. even though it has the persistent flag set. Alternatively, you can set a batch file to be executed at Windows start to add the route. I hope this helps.

01-29-20, 07:55 PM
OMG! Its so confusing.

Is there a software that could do this? Maybe an app in Synology NAS?

Can you recommend a good switch?

I still do need to connect the switch to my router right?

01-30-20, 12:40 AM
Can you guide on how I connect my devices?

ONU(bridge) - Router(1500) - Switch(9000) - NIC1(1500) - NIC2(9000) - NAS(9000)

01-30-20, 04:22 AM
ONU(bridge) - Router(1500) - Switch(9000) - NICS/NAS

The gigabit switch is just like an extension to the router's LAN ports, so you can connect NIC1 to either the switch or the router's ports, doesn't matter. NIC2 and NAS need to be connected to a gigabit switch that supports jumbo frames, like Netgear GS108 or GS105, for example. Some routers may have gigabit LAN ports too.

It sounds more confusing than it is. You just have to add a static route, so your machine knows which NIC to use for the NAS. Alternatively, you can just enable jumbo frames on your NIC1, and don't worry about NIC2 at all. In this case, your router will automatically scale down to 1500 MTU for internet traffic, and you will still have the benefit of higher throughput to your NAS without adding a second NIC and defining static routes. That's what I do, actually, for simplicity and because I only have one NIC on my main PC.

01-30-20, 04:57 AM
Oh I see. My concern right now is packet fragmentation as you have discussed in optimizing internet connection

01-30-20, 05:28 AM
NAT routers have to change packet headers (source/destination IP, etc.) anyway. Adding the extra task of fragmenting outgoing packets from jumbo frames to fit 1500-byte MTU may add another millisecond of processing I suppose, but it is almost negligible, it only affects outgoing packets. Of course it is a trade-off, for simplicity's sake.

01-30-20, 08:23 PM
Thanks Philip