OpenVPN migration to new Instance from legacy not working in tap mode

[phanos]

I have been running openvpn (legacy now) for the past 2+ years on opnsense with no issues to mention. I have configured it in TAP mode and had two clients connected to my home network remotely. 

After noticing that the openvpn is being migrate to the new openvpn instance version I decided to try and migrate everything to the new version but unfortunately I am unable to make it to work as expected. My clients do get connected to the server but after that I can not ping anything on my home lan network. If I try traceroute on any of my lan ip(s) from a client it shows that it can not find the home lan. It would seem to me that there is not routing info being sent from openvpn server to the clients.

I believe I have copied all the settings, certificates etc correctly to the new openvpn instance and I can see the service is coming up just fine. I have setup the same firewall rules and exported the clients again from the opnsense interface to be sure everything is up to date. I tried numerous different scenarios such as to assign the new ovpns to and interface, enabling that interface and setting firewall rules on that one too, creating a bridge and adding the ovpns interface to it but still nothing.

The only thing I notice that propably is relevant is that under Interface-->Overview the new ovpns is not getting assigned either an "IPv4" address or any "Route" while the old one from the legacy server does. I am guessing here if it does not get assign the proper data then it will not sent them to client later correct?

Does anyone have any clue what it going on here and why the new OpenVPN Instance is working as expected? Did I miss a step somewhere and I should add something to the interface and/or route in order to make it work?

Thanks

[maverickcdn]

The only thing I notice that propably is relevant is that under Interface-->Overview the new ovpns is not getting assigned either an "IPv4" address or any "Route" while the old one from the legacy server does. I am guessing here if it does not get assign the proper data then it will not sent them to client later correct?

This won't show a route/address as the OVPN interface should be a member of your bridge interface along with your LAN interface for a TAP config

Is your bridge correctly setup? https://docs.opnsense.org/manual/how-tos/lan_bridge.html

[phanos]

The only thing I notice that propably is relevant is that under Interface-->Overview the new ovpns is not getting assigned either an "IPv4" address or any "Route" while the old one from the legacy server does. I am guessing here if it does not get assign the proper data then it will not sent them to client later correct?

This won't show a route/address as the OVPN interface should be a member of your bridge interface along with your LAN interface for a TAP config

Is your bridge correctly setup? https://docs.opnsense.org/manual/how-tos/lan_bridge.html

You mean add the openvpn interface as a member of the bridge LAN? No i did not do that. In the old vpn it did not have to and I never notice anywhere that in the new openvpn it needs to do that?

[maverickcdn]

I came from another platform after the now legacy mode was destined to be removed and don't know anything about it so I setup a working config (for me) by bridging (frowned upon it seems) the TAP interface and my LAN interface to a bridge where the bridge is the host network.  Whether this is the correct way or not it works great for my needs, if you want more details of my config let me know.

[phanos]

I came from another platform after the now legacy mode was destined to be removed and don't know anything about it so I setup a working config (for me) by bridging (frowned upon it seems) the TAP interface and my LAN interface to a bridge where the bridge is the host network.  Whether this is the correct way or not it works great for my needs, if you want more details of my config let me know.

thanks I will try it and let you know