"
syd,
I don't have additional wan ip hence I can't move my wan from private ip range to true public ip. :(
I don't have additional wan ip hence I can't move my wan from private ip range to true public ip. :(
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#2
16.7 Legacy Series / Re: simple rdp Port Forward - NAT not working
July 27, 2016, 02:27:07 PM
Thank you for looking into. Nic used is e1000.
I have attached the image of firewall log view, rdp connection is initiated from 172.17.1.12 to OPNSense wan ip 172.17.1.25 (port forward is configured as shown in my first post).
I have attached the image of firewall log view, rdp connection is initiated from 172.17.1.12 to OPNSense wan ip 172.17.1.25 (port forward is configured as shown in my first post).
#3
16.7 Legacy Series / simple rdp Port Forward - NAT not working
July 26, 2016, 08:30:55 PM
Just deployed OPNSense 16.7.r2. A simple rdp port forward isn't working. I've attached port forward screenshot.
(OPNSense and my test Windows machines are running on separate VMWare hosts). As this is my test lab, on WAN interface, tick mark removed for "Block private networks" and "Block bogon networks".
Replaced OPNSense with pfsense (same environment) and rdp port forward is working.
(OPNSense and my test Windows machines are running on separate VMWare hosts). As this is my test lab, on WAN interface, tick mark removed for "Block private networks" and "Block bogon networks".
Replaced OPNSense with pfsense (same environment) and rdp port forward is working.
Pages1
