The Mikrotik does. The Wireguard stack running on that Mikrotik doesn't. Why is it important for you that the Wireguard stack knew the actual address of the peer?The only real solution working is from @lurker888 with srcnat. But in this case mikrotik does not see the real IP of connected client.
(that is, if the actual intention was to make ether1 an access port to VLAN 999, despite having no IP configuration attached to VLAN 999).all should start working the intended way.
I guess you have updated a wrong topic?Ok, quick update: after changing the PFS group to "none"...
If you use the trick with public address on the Mikrotik itself, it must be set as a local-address on the peer. The dst-nat rules are OK.I guess something is wrong there.
Can you follow the instructions in viewtopic.php?p=902082#p902082 ?please let me know when you have free time that i provide you anydesk access and you can check the config.
(unless you pay a beefy surcharge to get a public one).with IPv4, only CGNAT
Learning by doing is the most efficient way, but when it comes to internet security, it has its drawbacks, so I repeat my offer for remote assistance: viewtopic.php?p=1123221#p1123221I'm still watching some videos but so far I have this
/interface/lte/monitor lte1Where do I check for this info?
If you feel like that, you can follow the instruction in this post.I have no idea how to properly configure the firewall rules honestly. I'm very new to this
Go ahead and try importing that to a cloud providerI know, I know ...
Yes, I am.Are you telling me that this is not possible?