1

I would like to route all traffic to 192.168.1.10 to hardware port 1 on my router and all traffic to 192.168.1.11 to hardware port 2 on my router. The issue here is that I have a network attached device (192.168.1.10) that claims to have the fastest route to the other device (192.168.1.11). However, the link between devices is broken, and the packets to 192.168.1.11 are lost.

I'd like to explicitly associate IP addresses with the hardware port (1-4) on my router. Is this possible? If so, what feature should I look for in the settings page or in the specification for a new router?

2 Answers2

1

With a router you can give each port an IP. However, it doesn't matter what the router thinks, because if a device feels it should send packet somewhere on the LAN, it going to do that, and it will never arrive at the router. If both the NAS device and the device with the other IP have the same subnet, and you are using a strandard L2 switch, it will use that (which is probably what you want).

So somehow you need to tell the device not to use that route instead of trying to tell the router. A work around might be to change the the subnet on the device to something that does not include the other IP, this will force it to use the router (the device's default gateway) for ip traffic. Here is a nice post about subnetting from Evan.

I also think you need to explain this a bit more, I am not sure I have an accurate picture. But I would focus on fixing the NAS device, pushing all your storage traffic through a router is probably not the best idea.

Kyle Brandt
  • 85,693
0

I would like to route all traffic to 192.168.1.10 to hardware port 1 on my router and all traffic to 192.168.1.11 to hardware port 2 on my router.

That would be possible on a managed switch/hub, but not on an unmanaged hub/switch. Routing network traffic is done to the IP, not the hardware. The benefit being that you could move the cable from your switch/hub's port from 2 to 3 to 8/etc and traffic will always get to the correct host on the network.

If traffic is not moving between the hosts at IPs 192.168.1.10 and 192.168.1.11, it's possible you have a bad port and/or cable(s) but you really need to diagnose the issue to know the true reason before I'd suggest looking at new hardware.