Nas4Free behind pfsense

irs

C:>ping 192.168.0.250

Pinging 192.168.0.250 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:>ping 192.168.0.137

Pinging 192.168.0.137 with 32 bytes of data:
Reply from 192.168.0.137: bytes=32 time=41ms TTL=63
Reply from 192.168.0.137: bytes=32 time=42ms TTL=63
Reply from 192.168.0.137: bytes=32 time=43ms TTL=63
Reply from 192.168.0.137: bytes=32 time=55ms TTL=63

Ping statistics for 192.168.0.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 55ms, Average = 45ms

C:>tracert -d 192.168.0.1

Tracing route to 192.168.0.1 over a maximum of 30 hops

1 151 ms 204 ms 222 ms 192.168.0.1

Trace complete.

C:>tracert -d 10.0.7.254

Tracing route to 10.0.7.254 over a maximum of 30 hops

1 45 ms 70 ms 46 ms 10.0.7.1
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * ^C

C:>tracert -d 10.0.7.1

Tracing route to 10.0.7.1 over a maximum of 30 hops

1 526 ms 632 ms 191 ms 10.0.7.1

Trace complete.

C:>tracert -d 192.168.0.1

Tracing route to 192.168.0.1 over a maximum of 30 hops

1 351 ms 700 ms 437 ms 192.168.0.1

Trace complete.

C:>tracert -d 192.168.0.250

Tracing route to 192.168.0.250 over a maximum of 30 hops

1 773 ms 736 ms 970 ms 10.0.7.1
2 * * * Request timed out.
3 * ^C
C:>tracert -d 192.168.0.137

Tracing route to 192.168.0.137 over a maximum of 30 hops

1 197 ms 263 ms 365 ms 10.0.7.1
2 257 ms 203 ms 105 ms 192.168.0.137

Trace complete.

irs

My settings are as follows:
OpenVPN on pfsense router
access nework 192.168.0.0/24
NAS4FREE 192.168.0.250 port 12000
Tunnel Network: 10.0.7.0/24
client network 192.168.10.0/24

I can connect my DVR but can not connect owncloud and nas4free

C:>route print | find "10.0.7.1"
0.0.0.0 128.0.0.0 10.0.7.1 10.0.7.2 276
128.0.0.0 128.0.0.0 10.0.7.1 10.0.7.2 276
192.168.0.0 255.255.255.0 10.0.7.1 10.0.7.2 276

johnpoz

Well this says vpn is working

C:>tracert -d 192.168.0.137

Tracing route to 192.168.0.137 over a maximum of 30 hops

1 197 ms 263 ms 365 ms 10.0.7.1
2 257 ms 203 ms 105 ms 192.168.0.137

So your issue is on your nas box – most likely the firewall as already pointed out multiple times!

irs

thanks for your help.

Firewall?
inside my Nas4free firewall is not checked it is not configured.

P3R

@irs:

NAS4FREE 192.168.0.250 port 12000

In the very first post of the thread you say that the NAS4Free is on the OPT1 interface.

Now you're saying NAS4Free have the address 192.168.0.250.

Have you moved the NAS4Free to the LAN interface now?

irs

Actually it was beginning as i am new i wast knew many things than suggested in this post to protect well must do that on openvpn.

so now I am on openvpn but still am unable to access my nas4free from remote on openvpn.?

I hope explain it well?

P3R

Is NAS4Free connected to the LAN network 192.168.0.0/24?

Does it have the address 192.168.0.250/24?

irs

yes my nas4free is connected to my pfsense network address 192.168.0.0/24
and my NAS4FREE ip is 192.168.0.250
my DVR is also connected on the same network 192.168.0.137
and I am able to use it with that local network

my openvpn is connected on tunnel 10.0.7.0/24

my remote ip 192.168.10.0/24 windows machine

I can connect owncloud locally but can not connect through vpn.

![openVPN diag.png](/public/imported_attachments/1/openVPN diag.png)
![openVPN diag.png_thumb](/public/imported_attachments/1/openVPN diag.png_thumb)

P3R

Go to System, General, WebGUI, Hosts allow in NAS4Free admin GUI.

If you have only 192.168.0.0/24 configured there, change it to 192.168.0.0/24 192.168.10.0/24

Also in NAS4Free admin GUI:

Check that on Network, LAN Management, IP address you have the network set to /24

Check that you have Network, LAN Management, Gateway set to whatever address your pfsense have on it's LAN interface (in your first post it was 192.168.0.1).

irs

thx for the suggestions I will try and let you know the results.

Onece again Thank you for the help you and all other extended to me.

biggsy

@P3R:

Go to System, General, WebGUI, Hosts allow in NAS4Free admin GUI.

If you have only 192.168.0.0/24 configured there, change it to 192.168.0.0/24 192.168.10.0/24

Also in NAS4Free admin GUI:

Check that on Network, LAN Management, IP address you have the network set to /24

Check that you have Network, LAN Management, Gateway set to whatever address your pfsense have on it's LAN interface (in your first post it was 192.168.0.1).

You will also have to add 10.0.7.0/24 (your VPN network) to the NAS4Free hosts allow.

P3R

@biggsy:

You will also have to add 10.0.7.0/24 (your VPN network) to the NAS4Free hosts allow.

Will that be the source address of the traffic from the VPN?

If so, no reason to allow 192.168.10.0/24 then?

I don't know OpenVPN as you can see, I use IPSec.

Anyway, there must be something else that's very wrong since not even ping works…

biggsy

Yes, the OpenVPN tunnel IP will be needed.

In fact, I tried to access the Web UI of my own NAS4Free over OpenVPN (for the first time, I guess). It didn't work until I added the tunnel network to System, General, WebGUI, Hosts allow.

I agree that there is something more serious going on if PING doesn't work. Hard to tell what the OP has done though.

irs

"I agree that there is something more serious going on if PING doesn't work. Hard to tell what the OP has done though."

so you need my config file?

irs

I tried with the suggested webgui ip address but no luck.

Hosts Allow
192.168.10.0/24 10.0.7.0/24 192.168.0.0/24
Space delimited set of IP or CIDR notation that permitted to access the WebGUI. (empty is the same network of LAN interface)

Network, LAN Managment
IP Address 192.168.0.250/24
Gateway 192.168.0.1