2 LAN configuration and intermittent traffic.

[vincent_y79]

Below is a simplified diagram of my network. It might even be what I'm going to describe is expected and I should stop pursuing this. I'm client 1A and when I try to communicate with freenas (FN) on 30.7, I get intermittent connection. I can ping it all day, I can ssh (but get disconnected in few minutes), get on shares, but anything sustained stops or intermittent.

ping all around works and responses are fast.
testing with iperf:
1A <-> 1B works as expected
1A <-> FN1.7 also works as expected
1A <-> 30B works across the network so I'm assuming pfSense config is fine and transfers over 900Mb/s
FN:30.7 <-> 30B works

But:
1A --> FN30.7 connects, but only transfers 256KB and every tick below is 0.00 Bytes
oddly enough when going the other way, it works
FN30.7 --> 1A works and transfers fast just the like rest

Without other changes to the network, when I remove bce0:1.7 from freenas and change the default gateway to 30.1 from 1.1, the transfer 1A --> FN30.7 works. (Actually I haven't tried not changing gateways to see if that makes a difference)

Is there a config on freenas that I'm missing or is is this just not going to work due to some internal system? Is freenas getting my traffic from 1.100 to 30.7 and routing its response to its 1.7 because of the originating address?

 

[Allan Jude]

Yes, most likely your issue is that the FreeNAS is receiving the the connection on the vlan30 (bce3, 30.7) but replies on vlan1 (bce0, 1.7) because it decides based on the source address (1.100) and subnet mask.

Why not just connect over the local network (vlan1) instead of going via the pfsense to vlan30?

The other solution is to offer vlan30 tagged on the switch port for client 1A, and give it an IP in that subnet, and then the reply will stay in vlan30.

 

[vincent_y79]

Thanks so much for the reply, I wanted to have smb on the 1.0/24 and plex/mineos on the 30.0/24. I couldn't think of another solution. I was hoping that there would be a mac based forwarding like citrix's netscaler where it would forward the traffic back where it came from and not by the route lookup.