Show Posts

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.

Messages - WJScott

Pages: [1]

19.1 Legacy Series / Re: NAT - Port Forward not working from Windows PC's

« on: September 13, 2019, 05:18:55 pm »

It does not have a public IP, only an internal, that the xFinity router forwards (DMZ Port) all traffic to 192.168.0.250/24.

19.1 Legacy Series / Re: NAT - Port Forward not working from Windows PC's

« on: September 10, 2019, 04:50:44 pm »

Changing the Destination to "This Firewall" made no change.
Diagram Below:
http://www.greenscott.com:8383/LABNet.png

19.1 Legacy Series / Re: NAT - Port Forward not working from Windows PC's

« on: September 05, 2019, 04:51:38 pm »

All,

I appreciate the reply, but there are no 4433 and 433 in any of the data I provided.
This was a simple Port Forward, not even a redirect so the inbound port is looking to be redirected from my external router VIA the DMZ redirect (Any/Any) to the OPNSense appliance and it is failing.

Being that I could not wait any longer I have established the rule on the external router and it is working fine, and to be able to support multiple I have refocused on port redirection 8080 --> 3389 (Yes, MS RDP).
I have monitored all the logs and see the traffic being passed to the target but no session is established but a direct rdp session works fine bypassing the OPNSense Appliance.

Using 8080 as I know it is an open port at my location.

Below is my configuration of the NAT:

Disabled: Unchecked
No RDR: Unchecked
Interface: WAN
TCP/IP Version: IPV4
Protocol: TCP
Source: Any/Any/Any
Dest/Invert: Unchecked
Destination: WAN Address
Destination Port: From: 8080 - To: 8080
Redirect Target IP: RDP (Alias)
Redirect Port: MS RDP [3389]
Pool Options: Default
Log: Checked
Description: Port Redirect 33389 --> 3389
NAT Reflection: Enabled
Filter Rule assoc: None (Manually Created)

Firewall Rule 01:
Action: Allow
Disabled: Unchecked
Quick: Checked
Interface: WAN
Direction: IN
TCP/IP Ver: IPv4
Protocol: TCP
Source/Invert: Unchecked
Source: Any/Any/Any
Destination: RDP (Alias)
Dest Port Range: From: MS RDP [3389] to: MS RDP [3389]
Log: Checked

Firewall Rule 02:
Action: Allow
Disabled: Unchecked
Quick: Checked
Interface: WAN
Direction: IN
TCP/IP Ver: IPv4
Protocol: TCP
Source/Invert: Unchecked
Source: Any/Any/Any
Destination: WAN Address
Dest Port Range: From: 8080 to: 8080
Log: Checked

I see the traffic being allowed in the F/W log but no session is established with the redirect.
OPNSense just does not seem to work any longer for this function. Or I am doing some really wrong and I am blind.

19.1 Legacy Series / Re: NAT - Port Forward not working from Windows PC's

« on: September 05, 2019, 01:44:27 am »

WOW!

Not sure what else to say!
Its been multiple months and over 100 have read the thread but not one contributor to help me resolve the issue.

19.1 Legacy Series / Re: NAT - Port Forward not working from Windows PC's

« on: July 03, 2019, 05:34:16 pm »

This is baffling!

I've inserted a NAT to redirect 3389:

-Interface:     WAN
-TCP/IP Version: IPv4
-Protocol: TCP
-Source: Any
-Source port range
from:     MS RDP
to:     MS RDP
-Destination: WAN Address
-Destination port range
from:     MS RDP
to:     MS RDP
-Redirect target IP: 192.168.0.240
-Redirect target port: MS RDP
-NAT Reflection: Enabled (Have tried disabled also)
-Filter rule association: Yes

Automatic Rule Created:
-Proto: IPv4 TCP
-Source: *(Any)
-Port: 3389(MS RDP)
-Destination: 192.168.0.240
-Port: 3389(MS RDP)
-Gateway: *(Any)
-Schedule:
-Description: NAT

With the above F/W rule the attempt is denied:

__timestamp__   Jul 3 15:30:53
ack
action    [block]
anchorname
datalen   0
dir    [in]
dst   192.168.0.250
dstport   3389
ecn
id   53827
interface   em0
ipflags   DF
label   Default deny rule
length   52
offset   0
proto   6
protoname   tcp
reason   match
ridentifier   0
rulenr   3
seq   2596550757
src   174.228.133.87
srcport   1240
subrulenr
tcpflags   S
tcpopts
tos   0x20
ttl   110
urp   64240
version   4

Create a manual rule:
-Proto: IPv4 TCP/UDP
-Source: *(Any)
-Port: *(Any)
-Destination: 192.168.0.250
-Port: 3389(MS RDP)
-Gateway: *(Any)
-Schedule:
-Description:

Nothing gets entered into the log with the manual rule enabled, disable it and the deny continues?
I dont see how this could be expected behavior, help?

19.1 Legacy Series / Re: NAT - Port Forward not working from Windows PC's

« on: July 03, 2019, 04:11:13 pm »

and for clarity, I have also tried to the do this for RDP using an alternate port inbound and redirect it to 3389 to no avail.

19.1 Legacy Series / NAT - Port Forward not working from Windows PC's

« on: July 03, 2019, 03:34:29 pm »

Odd situation...

I have setup a NAT/PF that redirects port 4433 to 443 for the dashboard UI so that I can access it externally (This is a personal setup). The odd thing is that from my phone Android/Chrome I can access it.
Trying from 2 different laptops (One Corporate controlled and the other personal) I am not. I have tried IE, Chrome, Opera and Firefox browsers to no avail.

What is going on?
Any help would be appreciated!

General Discussion / How-To: HAProxy - TCP Forward/Redirect

« on: May 13, 2018, 12:02:12 am »

So, I have used HAProxy for a long time, but it was always by modifying the haproxy.cfg file. with OPNSense you have a UI in front of it and I am unable to find where the cfg file is stored to manually make the changes. That said, Can someone please describe how-to redirect a URI rdp.mydns.com to an internal ip address say: 192.168.1.13 (Port being redirected is 3389/RDP).

I tried to setup a condition and then use HTTP Redirect, but that is not working...

Pages: [1]