How to get 2 separate networks to talk to each other?
-
Well sniff on pfsense server interface when you ping - looks like you have just plain connectivity problem..
-
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)
-
look in pfsense arp table - what does it show for this 70.2 IP
-
@kiokoman
I did make a static entry under DHCP static mapping for SERVER interface as 192.168.70.2. -
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.
-
@johnpoz
Yup, I just checked the MAC address, it matches.
How do I sniff while pinging? Where do I find this in pfsense? -
diag menu, packet capture...
-
@ilovechickennuggets
but you did not answer my question, put a screenshot of that static entry pls -
I just want to let you you I appreciate and thank you for your patience. I am not too good with this area stuff. Here's what I got from the packet capture, hopefully with the right settings.
-
Well there are no pings in there..
So up the level of output so you can see the mac.. I think your mac is wrong to be honest. Since you set a static.
And when you did the sniff you did it at the same time as you were pinging?
Not seeing any response for dns in there either..
-
These are the current static mapping settings of the entry. The first shows pfsense. The second shows the MAC of the nas. So to make sure I was getting the right IP and MAC, I restarted my NAS. Somehow it gave me a new IP from dhcp. I did something wrong.
P.S. kiokoman, thank you for your help too!
-
And can you ping this IP?
-
@johnpoz
Yes the sniff happened at the same time as the ping.After I restarted my NAS just now, it gave me new IP of 192.168.70.10 - which is the start of my DHCP range.
-
and can you ping that?
Can your nas ping pfsense 70.1 address?
-
Packet capture is not picking up anything during the ping
-
Well then no nothing is going to work... Can the server ping pfsense IP? Does internet work? You have it directly plugged into an interface on pfsense - there are no switches.
I am not sure that your doing the sniff correctly to be honest.. do a tcpdump on pfsense while you ping..
Open up 2 ssh windows to pfsense and do it this way... start a tcpdump for icmp on the interface this server network is on..
Then in the other windows ping... Then also ping from the server to 70.1 address while your sniff is running
example
This sever is physical right - its not some VM running on something?
Lets try this - install the package arping... Lets try that..
example
-
now i'm curious to see where the hell we are hitting the head
-
-
see my edit.. about using arping package as well.
Clearly you would use server as the interface and ip of your nas..
-
@johnpoz @kiokoman
Ok I did a complete shut down and reboot. The NAS is now getting the correct static IP. In Pfsense, under Status/ DHCP Leases -showing as online
I installed ARPing and ran it with following settings
As for SSH and tcpdump, I am going to need to educate myself on this because I'm treading onto something completely new to me. I'll be back try your advice after I go through some documentations and tutorials. I don't have SSH set up and it looks like I need to generate a key.
