F5F Stay Refreshed Power Users Networks Assist with configuring several computers linked via two distinct networks

Assist with configuring several computers linked via two distinct networks

Assist with configuring several computers linked via two distinct networks

A
Atoll396
Member
Find
149
04-30-2016, 06:51 AM
#1
I'll try to clarify my setup in detail. I'm using three devices: a Windows 10 PC, a FreeNAS server, and an Ubuntu machine. Each device connects via its built-in Gigabit RJ45 NIC to a small switch connected to my router. Additionally, each has a 10Gbps SFP+ NIC linked into a MikroTik switch (CRS305-1G-4S+IN) with four SFP+ ports and one gigabit RJ45 port. To illustrate the configuration, I created a diagram showing the current setup. The issue is this: FreeNAS doesn't support registering multiple NICs as distinct IP addresses. A forum post mentioned you can't have several network interfaces on the same subnet or netmask. I've set both the RJ45 and SFP+ NICs to different subnets, but I can't reach the FreeNAS server from either of my other devices. When I ping the FreeNAS machine from any of my PCs, it returns "From XXX.XXX.XXX.XXX Destination Host Unreachable," indicating the router knows the IP exists locally but can't access it. Even after removing the gigabit port and using only the SFP+ connection, other machines still face the same problem. I want to be sure this isn't happening on my desktop or Ubuntu machine—FreeNAS is the only one affected. How should I link these connections properly? For example, when copying files from my desktop to FreeNAS, I need it to use the SFP+ port through the SFP+ switch, but currently it defaults to the gigabit port via the gigabit switch. I've attempted to map SMB network sharing to the SFP+ NIC, but that fails and causes drives to disconnect. I'm hoping a solution to this will also resolve the first problem.
Reply
Reply
A
Atoll396
04-30-2016, 06:51 AM #1

I'll try to clarify my setup in detail. I'm using three devices: a Windows 10 PC, a FreeNAS server, and an Ubuntu machine. Each device connects via its built-in Gigabit RJ45 NIC to a small switch connected to my router. Additionally, each has a 10Gbps SFP+ NIC linked into a MikroTik switch (CRS305-1G-4S+IN) with four SFP+ ports and one gigabit RJ45 port. To illustrate the configuration, I created a diagram showing the current setup. The issue is this: FreeNAS doesn't support registering multiple NICs as distinct IP addresses. A forum post mentioned you can't have several network interfaces on the same subnet or netmask. I've set both the RJ45 and SFP+ NICs to different subnets, but I can't reach the FreeNAS server from either of my other devices. When I ping the FreeNAS machine from any of my PCs, it returns "From XXX.XXX.XXX.XXX Destination Host Unreachable," indicating the router knows the IP exists locally but can't access it. Even after removing the gigabit port and using only the SFP+ connection, other machines still face the same problem. I want to be sure this isn't happening on my desktop or Ubuntu machine—FreeNAS is the only one affected. How should I link these connections properly? For example, when copying files from my desktop to FreeNAS, I need it to use the SFP+ port through the SFP+ switch, but currently it defaults to the gigabit port via the gigabit switch. I've attempted to map SMB network sharing to the SFP+ NIC, but that fails and causes drives to disconnect. I'm hoping a solution to this will also resolve the first problem.

Reply
Reply
X
XaVaTaR
Member
Find
77
04-30-2016, 08:25 AM
#2
It could be a stretch, but... A single RJ-45 switch might let you set up several local networks using just one output port, isolating clients so they don’t appear in the local group like OpenWRT does. Check the forum thread for details.
Reply
Reply
X
XaVaTaR
04-30-2016, 08:25 AM #2

It could be a stretch, but... A single RJ-45 switch might let you set up several local networks using just one output port, isolating clients so they don’t appear in the local group like OpenWRT does. Check the forum thread for details.

Reply
Reply
M
MinerJC_66
Member
Find
106
05-02-2016, 03:15 AM
#3
The reason for using a separate subnet isn't immediately clear. Bridging those interfaces might seem possible, but it could be more effective. Alternatively, placing those three devices on a different network would work if they are the only ones there. Otherwise, you'd need to adjust routing settings on the ISP router as the default gateway.
Reply
Reply
M
MinerJC_66
05-02-2016, 03:15 AM #3

The reason for using a separate subnet isn't immediately clear. Bridging those interfaces might seem possible, but it could be more effective. Alternatively, placing those three devices on a different network would work if they are the only ones there. Otherwise, you'd need to adjust routing settings on the ISP router as the default gateway.

Reply
Reply
S
Suicide_Haru
Junior Member
Find
34
05-09-2016, 03:44 AM
#4
I ended up discovering the answer online. My first searches on Google suggested you couldn't run multiple interfaces on FreeBSD/FreeNAS using the same subnet, but that turned out to be incorrect. By manually adjusting the IP addresses of all my RJ45 connections to 192.168.1.XXX and setting SFP+ connections to 192.168.2.XXX, I’m still struggling to get everything configured properly. Now I just wish the internet made this information more accessible.
Reply
Reply
S
Suicide_Haru
05-09-2016, 03:44 AM #4

I ended up discovering the answer online. My first searches on Google suggested you couldn't run multiple interfaces on FreeBSD/FreeNAS using the same subnet, but that turned out to be incorrect. By manually adjusting the IP addresses of all my RJ45 connections to 192.168.1.XXX and setting SFP+ connections to 192.168.2.XXX, I’m still struggling to get everything configured properly. Now I just wish the internet made this information more accessible.

Reply
Reply