alobi
Cadet
- Joined
- Dec 1, 2013
- Messages
- 6
Hi guys . I'm having issues with pfSense, FreeNAS, and two NICs - I'm hoping someone has some sage advice for me.
I have a network setup that looks like this:
My iMac is part of LAN subnet 192.168.2.x, and FreeNAS (with two separate NICs) is a member of both subnets 192.168.1.x and 192.168.2.x. I have two rules at the top of my pfSense firewall, one to allow all traffic from LAN A to LAN B and the other to allow all traffic from LAN B to LAN A. This all works fine, and I can SSH, ping, access shares, etc. across subnets. The reason FreeNAS has two NICs is to assign certain jails to LAN A (a VPN connection) and others to LAN B (clear net).
My problem is subtle but frustrating. As I said, my devices can talk to FreeNAS across subnets, but the connections are fragile. My SSH connection will drop with a broken pipe after ~70 seconds, even if the connection isn't idle. My AFP shares disconnect frequently, causing lots of BBoDs (beach balls of death) on the Mac accessing the shares while it tries to restore the connection. Even accessing FreeNAS from the web GUI has issues - my Mac on LAN B attempts to connect to FreeNAS on LAN A via web GUI but the browser can never load the entire page. It ends up looking like the attached image.
Accessing FreeNAS from the same subnet works fine though. SSH connections don't drop, the web GUI loads, etc.
I've isolated this to FreeNAS to the best of my knowledge - my reasoning being I can SSH to another Mac on a different subnet (the same subnet that FreeNAS lives on), without any broken pipes.
I've been racking my brain on this for a while and I'm stuck. Any ideas?
I have a network setup that looks like this:
Code:
NIC A --> switch --> FreeNAS | | internet -> pfSense -- | --> FreeNAS | | --> switch -- NIC B | --> iMac
My iMac is part of LAN subnet 192.168.2.x, and FreeNAS (with two separate NICs) is a member of both subnets 192.168.1.x and 192.168.2.x. I have two rules at the top of my pfSense firewall, one to allow all traffic from LAN A to LAN B and the other to allow all traffic from LAN B to LAN A. This all works fine, and I can SSH, ping, access shares, etc. across subnets. The reason FreeNAS has two NICs is to assign certain jails to LAN A (a VPN connection) and others to LAN B (clear net).
My problem is subtle but frustrating. As I said, my devices can talk to FreeNAS across subnets, but the connections are fragile. My SSH connection will drop with a broken pipe after ~70 seconds, even if the connection isn't idle. My AFP shares disconnect frequently, causing lots of BBoDs (beach balls of death) on the Mac accessing the shares while it tries to restore the connection. Even accessing FreeNAS from the web GUI has issues - my Mac on LAN B attempts to connect to FreeNAS on LAN A via web GUI but the browser can never load the entire page. It ends up looking like the attached image.
Accessing FreeNAS from the same subnet works fine though. SSH connections don't drop, the web GUI loads, etc.
I've isolated this to FreeNAS to the best of my knowledge - my reasoning being I can SSH to another Mac on a different subnet (the same subnet that FreeNAS lives on), without any broken pipes.
I've been racking my brain on this for a while and I'm stuck. Any ideas?