Subnet Access - What to do and how to do?

[Padua]

Dear Friends,

I'm having a terrible doubt. Actually I do not know how to do this in pfSense.

I have the following networks:

Rl0 - WAN - Internet
IP: 192.168.5.3/24
GW: 192.168.5.1 -> Note: Here I set the Gateway menu (Interfaces: WAN) interface is an Internet connection

RL1 - LAN_WiFi (Wireless)
IP: 192.168.15.1/24

RL2 (OPT1)
IP: 192.168.1.1/24

RL3 (OPT2)
IP: 192.168.0.1/24

RL4 (OPT3)
IP: 10.0.0.253/24
GW: 10.0.0.4 -> Note: Here I need this to be the gateway. Where should I set? On the menu (Interfaces: OPT3)?

Need by any of these networks to access a file server that is in another place
with IP: 192.168.4.20

Should I create a route here? What would be the same if this is the case?

So for all to understand this file server is in the building number 01
while I'm in the building number 02.

The connection between the buildings 01 and 02 is made by the wireless network. In this case the RL4 (OPT3)

pfSense
2.0-RC1 (i386)
built on Mon May 2 21:11:55 EDT 2011

Since already thank anyone who can help.

Thanks,

Padua

[wallabybob]

Sound like you need a static route saying 10.0.0.4 is used to access 192.168.4.20 (web GUI: System -> Routing click on Routes tab

And you will then need to configure suitable firewall rules to allow access from OPTx networks (by default that is blocked).

[Padua]

Ok I'll try.
Give me a hint how to set up this rule, please.

[clarknova]

Go to System: Routing: Gateways and add an entry for the IP address of the remote router that your are connected to via OPT3. Do not check the default gateway box. Save.

Now go to System: Routing: Static Routes and add a route. Destination network is 192.168.4.0/24 (or whatever mask the fileserver uses) and the gateway is that you just created. Save.

If you did it right then pfsense now knows that any packet destined for the 192.168.4.0/24 subnet needs to be routed through the 10.0.0.x router at the other end of your wireless link.

Note that the router on the other end of the wireless link must also similarly have a route back to the networks connected to pfsense, using 10.0.0.253 as the gateway, unless you're using advanced outbound NAT to NAT everything out of OPT3, in which case the fileserver just thinks it's talking to 10.0.0.253, which the remote router already know how to find.

If the remote network (192.168.4.0/24)'s router (10.0.0.x) is using pfsense as it's default gateway then you can disregard the last paragraph, as it will route all non-local traffic to pfsense anyway.