There's a lot we don't know about your config including what VPN protocol you are using. However, it does sound like you might be trying to achieve a split tunnel config. That is to say that some of the traffic should go through the VPN tunnel and the rest through the regular wan. Is that your goal?
If you want a split tunnel, the easiest way to do this is via Policy Based Routing. This will allow you to setup specific policies with respect to what traffic should use each upstream connection (tunnel vs wan).
If you need additional help, please start by posting your config.
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button (red circle; this works best in the 'Markdown' composer view in the blue oval):
Remember to redact passwords, VPN keys, MAC addresses and any public IP addresses you may have:
ubus call system board
cat /etc/config/network
cat /etc/config/firewall
.sneppah tahw tsuj si taht ,noitarugifnoc krowten eht rettam t'nseod ,eussi eht si ereht woN
.ti trats dna elbanE :2
.NPVnepO eht pu tes :1
...od uoy tahw si ereH
Here is the details WITHOUT an active VPN...
I'll upload the config when the VPN is active later tonight when I don't need the internet for a few minutes.
BusyBox v1.36.1 (2025-12-17 21:08:22 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 24.10.5, r29087-d9c5716d1d
-----------------------------------------------------
Eveything is almost the same with the VPN active. The only difference is...
config forwarding
option src 'zone_lan4'
option dest 'zone_wan'
becomes
config forwarding
option src 'zone_lan4'
option dest 'zone_vpn_external'
I don't know why that happenned...
I did a reply to the message, and deleted the text that was in there, and then I typed and sent.
I think some char went through maybe corrupted at the start and reversed everything...
With the VPN active at the moment, the communication gets to the external servers and does HTTP access using domain names when the domain name is set locally on my internal server.
The real problem is that when I have the VPN active, I can't use the internet from any of the other parts of the network either.. not from LAN1 or LAN2 or LAN3.
I did not write it in Hebrew.
The message is right to left and bottom to top... What character causes that to happen when submitting? I actually don't know, so that's why I ask.
It is literally my text COMPLETELY reversed...
No, I asked about routing configurations, you showed the firewall (i.e., forwarding rules).
Yes, I understand the issue, and you've only showed us firewall rules.
So are you saying that you've made no routing configurations to have the the network you desire use VPN, while the remaining networks use the connection you desire (I assume WAN as you stated in the first post)?
They are not over redacted actually.
They are still giving the required information without giving all the information away.
The settings are how the network needs to be set up for separation and segregation.
The forwarding on the firewall settings allow for the required locations to talk to each other in the correct way.
There is only one thing that I haven't managed to get fixed up that will take a while due to the way things work, and that is the HTTPS DNS requests, there is no easy way in the system to filter those for redirection to the DNS server.
Information that is redacted:
hostname: [REDACTED],
system: [REDACTED],
model: [REDACTED],
board_name: [REDACTED],
The username and hostname
the ipv6 prefix that shouldn't be there since ipv6 is disabled.
No other information is redacted... So it isn't over redacted.... No important information has been redacted...
Edit: Oh, forgot that the 2 blacklisted IPs have been redacted as well. As they are of no consequence either to this whole issue.
RFC1918 addresses ( option ipaddr '[LAN1.1]') do not reveal anything private or sensitive about your network. However, without seeing them, we don't know if you've got any errors/overlaps.
Likewise, why have you redacted the system/model/board name information? Sure, I understand redacting the hostname... but the other things just tell us about the hardware so there's nothing revealing there, either.
Meanwhile, the key question I was asking was this:
It looks as if you basically ripped everything out of the default config and re-wrote everything yourself. For example, in the firewall, there are a whole bunch of rules that would normally be there and are missing.
The device definitions are also rather unusual...
What were the goals in adding all of these options? It's quite unusual and it would be good to know why you've included all those things that are not in a default config.
This also looks very strange... what VPN protocol are you using that would have a DHCP server on the tunnel? For example, openvpn tunnels, when defined in the network config file, would be a simple unmanaged interface like this:
config interface 'VPN'
option proto 'none'
option device 'tun0'
Anything more than that would be invalid for OpenVPN.
LAN1 is LAN1. There are no overlaps or errors as the networks internally work perfectly.
LAN2 is LAN2...
They could be referred to as 192.168.1.* and 192.168.2.*
Whatever you want to referr to them as like that is up to you..
What rules are missing that you would believe should be there?
What is wrong with the eth0 WAN port?
tun0 VPN interface is like that because that's the way it needs to be..
protocol needs to be DHCP to get the IP from the VPN service for reference. I don't have it manually set.
the HOSTNAME is there to send that as the hostname instead of sending the internal machine identifier.
I use internal DNS, not the peer DNS, so it is set to inactive.
force link means it's always there in the options so it doesn't destroy the configuration and can be activated and deactivated whenever I want.
the list dns is telling anything that tries to ues the VPN connection that the DNS server to use is the internal DNS server dedicated to the VPN, for protection.
I dont' know what delegate is in the options there.
But then again this is all very obvious if you know the system and actually know the options and read them.