Port restriction rule!

johnpoz

@stephenw10 I am still wondering how your quote ended up in Russian ;)

Antibiotic

@johnpoz Sorry not understand completely what you mean, but its OK because Russia come back to the global honest WORLD))) not a rules-based order

johnpoz

@Antibiotic Steve's post was clearly in english, but then when you quoted it Russian ;) I was not aware that the forum software translated quotes to the posters language or whatever.. So clearly there was some copy paste on your part?

edit:
Your dot rule to lan subnets makes no sense.. Because you have a rule above it that allows any from lan to assume any local used network. So 853 would be allowed by that rule, there is no reason to allow 853 specifically. to lan subnets.

On a bit of side note, what is the point of * as source... How would there be any source ingress into this interface unless it was the subnet this interface is attached too?

The only time any for source makes any sense is if the interface is a transit network. The source IP should either be specific for IPs on this network that you want to have different rules for, or it should be set to the subnet the interface is attached to.

stephenw10

A browser plugin would do that. Or just Chrome with translate turned on.

Antibiotic

@stephenw10 I tried but do something incorrectly

Wireless router IP 192.168.20.11 and set

do \192.168.20.11\HOME but error connection

stephenw10

The file server may not allow connections from outside it's own subnet by default.

Antibiotic

@johnpoz Re design))))

yes do copy past , Do not make copy past of translated world, write by English in forum

Antibiotic

@stephenw10 Yea but in AP mode i don't have any settings to allow this.

stephenw10

If it blocks connections from outside it's own subnet and there's no way to add rules to allow it then you would have to add NAT rules in pfSense. But things start to get ugly when you do that! So I would want to confirm that's really happening.

Antibiotic

@stephenw If i set back to Wireless router mode than make to allow from outside it's own subnet. Set back to AP mode, will this work?

stephenw10

First confirm what is not working.

Can you ping that AP/server from the other subnet? Can you SSH to it? Access it's webgui?

Antibiotic

@stephenw10 Yes i can ping and access web gui and SSH from other subnet. May be its possible to add some rule from SSH but what the rule? Router firmware based on linux.

johnpoz

@Antibiotic So your using some wifi router as just an AP.. Yeah if your just using the makers firmware many of them do not allow setting a gateway on the lan interface.

Can you put 3rd party firmware on it - ddwrt, openwrt, etc. All of these allow for setting a gateway on the lan interface.

If not - sure you could either nat and and allow remote access to its web gui. Or as mentioned you can do a source nat, ie outbound nat so traffic to the AP IP looks like it came from pfsense IP on the same network.

If me I would look to 3rd party firmware. Or better yet get an actual AP vs using some wifi router you had laying about.

Advantages to 3rd party or actual AP is you would also then get vlan support, not just gateway on lan interface.

If stuck with this wifi router as your AP, I would use the outbound/source nat vs double nat and remote access to the devices webgui from remote.

Antibiotic

@johnpoz Alreaddy use asus merlin. its a 3rd party firmware

Antibiotic

@johnpoz said in Port restriction rule!:

Can you put 3rd party firmware on it - ddwrt, openwrt, etc. All of these allow for setting a gateway on the lan interface.

You mean to put 192.168.10.1 in LAN gateway settings?But in this case would 192.168.20.0 subnet to see hard disk? And me use VPN on this gateway 192.168.20.1 for wireless network

johnpoz

@Antibiotic huh??

No you wouldn't put some other network as your gateway.. That setting looks correct.. If you can access its web gui and ssh via that 20.11 IP from your other network.. Then you fine - your problem with share access is most likely has mentioned by Steve - discovery doesn't work across subnets.. Just access the share via the IP 20.11 or use the fqdn you have setup that resolves to that 20.11 IP.

Antibiotic

@johnpoz said in Port restriction rule!:

fqdn

What it mean?

Antibiotic

@johnpoz Do you mean connect by manually: \RTAX86UPro.home.arpa\HOME

stephenw10

Yes. Though entering the IP there should also work.

Check the firewall states when you try that. Is the client even trying to connect?

johnpoz

@Antibiotic fully qualified domain name.. ie what you posted from your AP its fqdn would be rtax86upro.home.arpa.. Be it that resolves on your network? You most likely would of had to have setup the record as a host override in unbound on pfsense or if your using some other dns for your network, etc.

edit
Try IP.. unless you had set it up in your dns, its possible that fqdn does not resolve.. If you ping it does it resolve to that 20.11 address?