How to get 2 separate networks to talk to each other?

[johnpoz]

Does your nas have a gateway set? That points back to pfsense 70.1 address?

Can you ping the NAS from pfsense server interface, ie 70.1 ?

Either the nas has firewall, or has no gateway. I would sniff on the server interface while you ping - do you see the pings going out to the nas IP? Is it the correct mac? If so then its an issue with the traffic not actually getting to the nas, or the nas not answering, or the nas not having a way to answer because wrong gateway or no gateway.

[kiokoman]

yeah the problem is the freenas, maybe try to restart it / check its network interface / check its firewall

[johnpoz]

I think he has floating rules as well, since looks like he is blocking outbound traffic on his lan with those arrows before the interface name.

BTW - you might want to edit your firewall log pic, your showing your wan IP there in those blocks to 1433 and 2236, oh your first pic of firewall rules is showing it as well.

[kiokoman]

that ipv6 blocking rule is due to the fact that he disabled ipv6 from here
login-to-view

i think that removing that create a hidden floating rule

[ilovechickennuggets]

@johnpoz @kiokoman

I have my NAS set up in the above picture after a new start over on the NAS. NAS gateway is pointing to 70.1
In addition, I have set pfsense DHCP server to identify the NAS by MAC address linking to 192.168.70.2 as static. I double checked and made sure the MAC of the NAS is matching correctly.

I am not able to log in or ping my NAS at 192.168.70.2 from my LAN network. Traffic graph on my pfsense dashboard now shows activity on 192.168.70.1, previously nothing.

[johnpoz]

@ilovechickennuggets said in How to get 2 separate networks to talk to each other?:

I am not able to log in or ping my NAS at 192.168.70.2 from my LAN network

But can you ping it from the server IP on your pfsense?

[ilovechickennuggets]

@johnpoz Did you mean in pfsense - Diagnostics -> Ping 192.168.70.2? I'm not quite understanding this.

[johnpoz]

yes - exactly how your pinging from the lan interface.. Just pick the server interface... example

login-to-view

[ilovechickennuggets]

@johnpoz
login-to-view

No, 100% packet loss

[kiokoman]

eh now i remember an old 3d where someone enabled static arp and was unable to ping
did you perhaps enabled static arp somewhere?

[ilovechickennuggets]

@kiokoman I have new information to present. I was doing my ping wrong using default as source. I was curious and tried again with LAN and also resulted in packet loss.
login-to-view

login-to-view
login-to-view

Static ARP is not enabled.

[johnpoz]

PING it from the SERVER IP of pfsense - change your source to server!!

[ilovechickennuggets]

@johnpoz login-to-view

[johnpoz]

Well sniff on pfsense server interface when you ping - looks like you have just plain connectivity problem..

[kiokoman]

the nas is out of the dhcp range, it must have a static entry, please check if you inadvertently enabled

ARP Table Static Entry Create an ARP Table Static Entry for this MAC & IP Address pair.

if so disable / untick it

or if you have set a wrong gateway (should be empty)

[johnpoz]

look in pfsense arp table - what does it show for this 70.2 IP

[ilovechickennuggets]

@johnpoz

@kiokoman
I did make a static entry under DHCP static mapping for SERVER interface as 192.168.70.2.

[johnpoz]

And your sure that is correct? there for your 70.2 address.

Sniff when your pinging from pfsense server interface... Do you see the traffic go out to the correct mac, if so if no answer its on the client or the connection to the client..

If pfsense can not talk to it from its own interface in the network, then its never going to work from a different network.

[ilovechickennuggets]

@johnpoz
Yup, I just checked the MAC address, it matches.
How do I sniff while pinging? Where do I find this in pfsense?

[johnpoz]

diag menu, packet capture...