Port Forwarding stopped working after upgrading to 2.8.0

comet424

and if i just set
outbound on dns resolver to the pia vpn... i set no forwarding.. and i dont have an ip in the general setup... i can get a pia vpn dns i guess but my internet stalls out and stops working and i loose dns resolving all i can do is ip pinging...

so i havent found that sweet spot of i know 100% not leaking internet will always work for wan and vpn clients.

and even if my modem stalls it will bounce back without needing a reboot or so..

stephenw10

Ok so what are clients on the internal network that uses the VPN being passed to use for DNS?

Is all their traffic being routed over the VPN?

comet424

@stephenw10

ya all the traffic i route through the vpn.. except like my Webserver.. some xboxs to try to stop double natting, gaming comp.. my iot devices and cameras that update through the wan but dont use vpn.. all my other devices tablets comps vms all go through the vpn.. except a few VMS that are on WAN but majority everything

so thats where i have Vpn_clients alias all those ips use VPN and ive done No_vpn_clients alias ips or i just did Lan subnet * * * * after the vpn clients..

and i have that bypass policy as i learned if i wanted to have split wan and vpn and over the network i needed to have thr routing bypass policy thats in front of everything

stephenw10

So are you passing specific DNS servers to those VPN clients or are they using the pfSense interface address?

Are you routing even DNS queries from those clients over the VPN or are they bypassing the rules and allowed to the local interface?

If all traffic, including DNS, is routed over the VPN then it cannot leak from some local resolver.

comet424

@stephenw10
im not 100% sure?? not sure what you all mean sorry

so all LAN use 192.168.0.1 as the dns and gateways for VPN and WAN clients

on the other Vlans they just use default so 192.168.10.1 for camera network thats the dns for that
192.168.20.1 dns for the IOT network and so on

for the lancache.. server it is 192.168.0.32 where all the host over rides goto .. and the uplink is 103.86.96.100 dns i just used it as thats what i had.. from nordvpn

now under the VPN PIA as dhcp options i use

persist-key
persist-tun
remote-cert-tls server
reneg-sec 0
auth-retry interact
dhcp-option DNS 10.0.0.243

the 10.0.0.243 is the dns for PIA vpn.. now i seen some use semi colon on the end and some dont.. but neither made a difference..
and for my 2nd pia vpn i use 10.0.0.242 as the dns as i tried using the same 10.0.0.243 but found no difference

as for bypassing the rules i dont think they do????
first line is pfblocker
2nd line is the routing bypass policy
3rd line is the vpn clients out the vpn gateway
4th line is the wan clients out the wan gateway

i also watched another video where in the NAT rules for the VPN he didnt use the PIA interface.. but used the WAN interface NAT part.. i not sure if that makes a difference or not

if u need more screen shots i can post them if u need to see more..

stephenw10

Ok so all clients are using pfSense for DNS. Both VPN and non-VPN clients. So that means to avoid a 'DNS leak' reported on vpn clients that Unbound must send all queries over the VPN. Either by resolving using the VPN interfaces only or by forwarding to the PIA DNS servers only.

That does mean that if the VPN is down no clients will be able to resolve. Both vpn and non-vpn clients.

I'm not sure why you have added the DNS servers to the VPN client config. Those should be passed to you by the server. But Unbound won't use them there either way. It can only forward to servers configured in general setup.

A better setup here would be to put vpn clients on a separate interface. That way you can easily pass them different DNS servers to use etc.

comet424

@stephenw10
hi ok
so the reason i do the dhcp options part wht the dns is thats the PIA VPN instructions they tell you to type it in there.. and then you choose 1 of the 3 dns servers they offer

and then i have the Forwarding unchecked

so that sucks you cant do both without leakage

so for the better setup

so you mean do
LAN IPS would not use VPN
VLAN 5 IPS would use the WAN

like how i have it right now IoT Cameras DMZ Vlan use WAN so its not a split Internet on the same interface

so would i change anything special?

and the reason i left a dns ip address in general setup.. even when i dont check Forwarding in the dns resolver with the dhcp options ip address. is even with that my internet goes down and it doesnt bounce back till i reboot or its given time..

so when i have the current setup with the dns leaking on the vpn side... is it actually leaking?? or is it just falsly reported.. do you happen to know? as i learning on the go and when you try to google you cant find info... so like is the actual cloudflare or isp seeing what your doing out the vpn side?

and do i need that bypass routing policy then as i read i needed that when you do split internet like wan and vpn
and over multi interfaces

stephenw10

Yes, like that. Use a separate VLAN for clints you want to use the VPN.

Pass clients on the subnet the VPN DNS servers to use dircetly.

Route all traffic from those clients over the VPN and block traffic not routed.

That will prevent leaks and should also no longer drop the VPNs etc. But it will mean VPN clients can;t use the lancache or any other local resource.

comet424

@stephenw10 ah ok... and well that sucks
so there really isnt any good ways to get both worlds and use a lancache..

if i put the lancache server as one of the vpn clients.. can then the WAN clients use the lancache?

and how come dns leaks when i split vpn and wan on the same ips like the lawerance systems videos dont even say when you follow his instructions that dns leaks .. and i still dont know why the one video shows using WAN interface of NAT for the PIA VPN

guess stuff just isnt as simple... i guess i wouldnt have the problem if my internet was fast and you just run it all out the vpn lol

but ya ill try to transisiton my VPN or WAN clients to a seperate Vlan then.. do i still need that routing bypass policy?

comet424

@stephenw10

so i toggled teh routing policy off for now
i set that LAN only uses VPN

i find my desktop pc still getting ISP dns but if i run a firefox Docker i will get it to goto teksavy

i left the dns resolver to all/all for inbount and outbound.. and unchecked dnseq and unchecked the forwarding.. and removed the ip address's in the general setup

i did run
ipconfig /release
ipconfig /flushdns
ipconfig /renew

but it still retains isp as a dns
i made sure in the dhcp settings that gateway and dns are 192.168.0.1

but still pointing wrong dns is there other spots it saves dns
i not getting good tests at this rate

comet424

can you do VPN on LAN and WAN on the VLAN

or do you need to start things

LAN = WAN
Vlan = VPN

as i seem to having dns issues if i leave it as VPN = LAN and WAN= VLAN5
as i get isp dns on my gaming desktop when behing the VPN etc

going to play around but also trying to understand more

Gertjan

@comet424 said in Port Forwarding stopped working after upgrading to 2.8.0:

i find my desktop pc still getting ISP dns but if i run a firefox Docker i will get it to goto teksav
....
ipconfig /release
ipconfig /flushdns
ipconfig /renew

Your PC uses DHCP, right ? By default, it does.
Double check that you didn't set a DNS (statically) yourself on this PC.

If DHCP : The DNS the PC got was given by the DHCP server - which is (should be !) pfSense.

Check that :

-> Use another PC to access the pfSense GUI !.

and hit Start.
Now, on the PC :

ipconfig /release
ipconfig /renew

and get back to pfSense.

You should seee the DHCP request from the PC, and the pfSEnse DHCP answer - with the gateway, DNS, etc etc.
What DNS was given by pfSense , By default it is the LAN I of pfSEnse.
If it isn't, that could be explained because you've selected :

Or you've set (DHCP > LAN server) :

to something else ?

comet424

@Gertjan
ok so i tried that.. i also had googled about pia and pfsense and tried to go several google searches in.. as what i find is like the lawerance systems and couple others they dont touch that dns resolver.. they did what i did ips on the same lan so novpn and vpn clients and do the no wan egress.. but none of them ever talk about dns leakage,, but i find it leaks.. and i not 100% is it ok for the dns to leak on the vpn side if no traffic goes out the wan

so here is the tests and i commented a bit too
i also followed a couple other articles where they tell you to add custom options code in the dns resolver.. since i have it set All Inbound just 2 PIA VPns as outbound
i in the dhcp settings for the desktop pc i had left the dns and gateway blank.. this time i entered in 192.168.0.1 but it didnt help i still got a dhcp for 192.168.0.1

packet capture
issue 1.png

windows dhcp ipconfig /all
issue 2.png

rules I set everything on the LAN to just go out the one VPN and not the 2 vpns or the WAN for now

issue 3.png

DNS Resolver.. Inbound All, Outbound to the 2 PIA VPNS. and i followed couple sites they add the server: forwarding for custom options.. i guessing this is for the when the vpn goes down wan cant be resolved anymore and it fails to reconnect..
issue 4.png

Fire Fox Docker Browser #1
fire fox docker 2.png

Fire Fox Docker Browser #2
firefox docker 1.png

Windows Desktop IE Browswer
windows desktop.png

yet all are behind the same firewall.. this is probably why i cant seem to figure out why am i truly leaking or what not but seems the windows desktop says i am

here is the github dnsleaktest you download and run on windows or linux here is the same desktop
windows dns leaktest.png

so i been confused for months and thats probably why this question form i posted has gone on forever cuz i truly never figured whats going on or how to make wan lan ips and vpn lan ips seperated and secure.. and the videos and articles never address this..

and i confused why my desktop pc is always pulling dns even when it should be pulling vpn

and when you run the dnsleak.com website for PIA leak test.. on the 2 Firefox docker.. they tell you its leaking.. so its not even working like they supposed to be.. cuz it throws a whole bunch of ips of the cloudflare

so dnsleak.com sees the cloudflare ips the dnsleaktest.com doesnt see that but sees the cira one but should be i guess teksavy

so ive never figured out this rolling headache lol

stephenw10

There are many ways you could set this up. The way I outlined above is simplest for avoiding 'dns leaks' but you can do it other ways. Including some that include using the lancache.

Does the Lancache have it's own DNS server?

When you see a DNS leak reported it's because the client is using a DNS server that's resolving from an IP address local to the WAN and not the VPN. So that means either Unbound sending queries out of the WAN or forwarding to local servers like the ISP. So if you are going to have VPN client devices use Unbound in pfSense it must send queries over the VPN only. So either set Unbound to use the VPN interfaces for outbound queries or forwarding to the VPN DNS servers only.

By default pfSense will be passed DNS servers to use by the ISP and adds them to the list in General Setup. You can disable that though by unsetting DNS Server Override.

comet424

@stephenw10 ok i understand i not sure how to do all that but i am learning things as i go too. learning experience and the simplets way is still getting cloudflare on a desktop pc even though its all going out the vpn and i guess that options i have is to keep the wan alive.. least that what i figured it does

so for lancache ya it has an upstream ip address i used 10.0.0.241 as the upstream
and the lancache is 192.168.0.32

i had to re read what you wrote to try to understand things.. stupid dislexia and learning disabilities.. but also here is the NAT i did it in hybrid mode.. i also used to have nat to only go out vpn clients.. but disabled and did entire networks so all the interfaces get WAN and VPN as i saw another video doing that too.. not sure what one is the right way.. and seemed when i was with NordVPN how ever it worked.. it worked better then PIA.. i only went PIA cuz it was cheaper.. but it seems to been more issues as i didnt have these leak issues with the nordvpn that i do with the pia... as i even set it to all all inbound and outbound

so basiclly your saying when you want to use VPN and No VPN Clients... you gotta set All Inbound and just the 2 VPN for outbound..

and as for the Dns Server Override.. ya thats been unchecked for a long time.. havent checked that button

and i guess i confused cuz the videos of these people that setup the vpn and no vpn for pia.. dont touch the dns resolver.. so they leave it at default all/all inbound and outbound..

so thats where i getting also confused they dont talk about it ever.. or ever talk about dns leakage
only about the no wan egress kill switch.

but currently my setup above is it only sends out the VPN and i get the cloudflare on my desktop pc but not the others... but i going to try a reboot of windows see if that does anything..

and this is my nat and general settings

comet424

if you happen to have any screen shots how to configure it to be secure even if i have split network
and better routing as these videos arent showing how to stop leaking or touch the dns resolver

comet424

@stephenw10 and i know your too busy to watch or skim videos
but these were the videos i followed where i did like that but they dont talk about leakage or dns resolver.. and i never get there results

syncbricks 1
Lawerence Systems

and i commented on there youtube videos about the setups not talking about dns leakage or dns resolver.. but they too busy to reply either

Gertjan

@comet424 said in Port Forwarding stopped working after upgrading to 2.8.0:

and i confused why my desktop pc is always pulling dns even when it should be pulling vpn

Normally, your PC, the OS, pulls the DNS from the gateway, which is pfSense.
pfSense centralized all local network ( your LAN devices ) DNS requests, and resolves from there.
Resolving means : it uses root DNS server, a TLD DNS server and a domain name server to obtain a DNS answer.
Or : Plan B : you forward to for example 1.1.1.1 : now the resolver send all traffic to this DNS resolver (= 1.1.1.1).
The resolver uses the outgoing connection, also called WAN.
Or, you could have two WAN's : the one going to your ISP, and a VPN-WAN connection. You could inform the resolver to forward to 1.1.1.1 over the VPN connection.

If you use this last solution, you still leak DNS info to .... 1.1.1.1 ^^

When I see the result of dos command "dnsleaktest" shown above it says your DNS leaks to ...
the 7 DNS Cloudflare servers you have specified yourself (?).
So, is it really leaking ? It does what you asked it to do.

I know, more questions then answer.

MoonKnight

@comet424

Maybe you are using DOH on your windows IE browser? Change it to static IP and add your DNS server IP.

Gertjan

@MoonKnight said in Port Forwarding stopped working after upgrading to 2.8.0:

Maybe you are using DOH on your windows IE browser?

True. Forgot about that one.
On any device, locally installed software can use the 'system DNS' (the one you see when typing ipconfig /all)
or
it can use any DNS other DNS is choses to use.

These days, afaik, most application (browers and others) use their 'own' DNS, totally bypassing the pfSense Resolver/DNS.
They (the browser's author) say : for your own security, and that(s not false, but mostly because they want your DNS traffic as it has a value (for them).
This traffic will flows encrypt through pfSense to whatever destination it chose to use and you can't do anything about it.
Remember : this is TLS traffic so you can't route it to somewhere else.
I would consider this also as DNS leaking ....