One NIC handles caching while the other manages internet traffic.
One NIC handles caching while the other manages internet traffic.
Hello friend, I improved my PC (Windows 10) and added another network card. Most tasks are working now, but internet speed isn't ideal. It seems like every time I open a browser window, the request heads straight to my stuck point. My second NIC is 1 gigabit while the first is 10 gigabits. On my PC I arranged the cards as follows: NIC A takes priority, NIC B connects to the router at 192.168.2.60, and NIC B links to 192.168.1.1 via the router. What I observe with each request is that when I load a site, the browser sends the request through NIC A to the website's IP address. But NIC A can't reach the internet since FreeNAS isn't linked to my router. Then the data travels over NIC B and connects properly. This process takes time for every query. I set this up to cache downloads on FreeNAS (which is running a Docker VM, that part worked before but with the slower B card). So when downloading, the request should first go to FreeNAS via A, using its cache if available. If not, it should use NIC B to reach external servers. The caching setup isn't complete yet, so I'm unsure if this configuration will improve performance. Any suggestions would be great! Thanks, Manu
Verify your routing table (`route`). The default route (0.0.0.0/0) should list your router (192.168.1.1) as the gateway. You can also execute traceroute (for instance to Google DNS at 8.8.8.8 or CloudFlare at 1.1.1.1) to observe the path and hops packets follow.
It's nice to hear! I wasn't aware there was such a straightforward method for finding the path. I'll look into it right after finishing work. Thanks a lot!
Here’s a revised version of your update:
Well, here’s the latest: I managed to run tracert 8.8.8.8, but the route went directly through my network. It took about 1 minute and 18 seconds to reach Google after 11 hops. I’m not sure if this is typical, and I can’t tell if it checks my NAS first. I’ll keep testing and checking.
I believe the goal is to enable FreeNAS to use the regular LAN while letting the cache display the IP of the second NIC on FreeNAS. This way, when your PC needs data, it connects via the quicker path and bypasses the default route. I’m not sure if this configuration is possible with the current cache setup. Ideally, you’d just connect the PC and FreeNAS over a 10Gb switch for simplicity.