Menu

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.

Show posts Menu

Messages - cryotize

#1
Thanks - This seems to make sense.

If i check on which ports and interfaces the server is listening on, this doesn't seem to make much sense anymore :/
See the output of command "sudo ss -ltn" (obviously, i removed all other, unnecessary ports which are open too):

State             Recv-Q            Send-Q                        Local Address:Port                          Peer Address:Port            Process
LISTEN            0                 4096                                0.0.0.0:443                                0.0.0.0:*                                                   
LISTEN            0                 4096                                0.0.0.0:80                                  0.0.0.0:* 
LISTEN            0                 4096                                   [::]:443                                    [::]:*
LISTEN            0                 4096                                   [::]:80                                      [::]:* 

In your opinion - Should i still try to find out where the real problem lies, or can the circumvention be used as a permanent solution, without any security implications?

Edit: I will check the Docker + NAT thing and will give an updated report.
#2
You're a GOD!

Thank you so much! It works now :) Many hours wasted... and still, i don't really understand where the problem lies.

Would you mind sharing some links or information, which explain this behavior and your proposed solution? I'd really like to understand this, so that i could help other people if they have the same problem.

Again, big thank you <3
#3
Interesting...

I followed the Guide for the HTTP and SSH Port aswell, without any luck.

Server seems fine to me, i use a dockerized nginx Webserver. Docker opens Ports automatically on Ubuntu server.
Now i have added 3 UFW rules manually, which allow access from any -> 80, 443 and SSH. Sadly, this didn't change anything either...

Do you have any other idea?
#4
Thank you for your reply!

Of course, i have captured those 4 files at the exact same time on the required devices / vlans. They are all attached below.
Please note that i have captured only Port 443 in these 4 files, i might be able to capture port 80 aswell, but that would result in 8 files i guess.

Don't be confused by the client called "desk" in my client capture, desk is the hostname of my client. The real internal client IP is 10.10.10.100.

I will also setup the same rules for Port 80, like you've said. Maybe this is needed too. Additionally, i will try it with the SSH port too, just for the sake of trying.
#5
Hi all, OPNSense newbie here...

I am having a lot of trouble setting up reflection and hairpin NAT. I have followed the offical best practice on how to configure it. See: https://docs.opnsense.org/manual/how-tos/nat_reflection.html#method-1-creating-manual-port-forward-nat-dnat-manual-outbound-nat-snat-and-automatic-firewall-rules

As stated, Method 1 is the preferred way, but none of the 3 described methods fully work in my case, and i don't know why.

Here's how my network is setup:
I have multiple VLANs / Interfaces (only the relevant ones are listed here):
ID 10 - Internal (10.10.10.0/24)
ID 100 - DMZ (10.10.100.0/24)
Interface WAN - one IP provided via PPPoE
Server IP: 10.10.100.6

Problem: I cannot access my Website from VLAN_10_Internal when using the external DNS Name. Funny thing is, Hairpin NAT works with solution 1, which is good. External access to my website (via Smartphone on LTE) also works perfectly.

I have tried many workarounds / solutions from this forum, all without any luck.Here is how i have setup the rules, following method 1 from the best practice:

Firewall -> Settings -> Advanced
Reflection for port forwards -> Unchecked
Reflection for 1:1 -> Unchecked
Automatic outbound NAT for Reflection -> Unchecked


Firewall -> NAT -> Port Forward
Interface: VLAN_10_Internal, VLAN_100_DMZ, WAN
Protocol: TCP
Source: Any
Source Port Range: Any
Destination: WAN address
Destination Port Range: from HTTPS to HTTPS
Redirect Target IP: Hosts Alias for IP "10.10.100.6"
Redirect Target Port: HTTPS
NAT Reflection: Use System Default
Filter rule association: Ass associated filter rule


Firewall -> NAT -> Outbound
Mode: Hybrid outbound NAT rule generation

Manual rule:
Interface: VLAN_100_DMZ
Protocol: TCP
Source Address: VLAN_100_DMZ net
Source Port: Any
Destination Address: Hosts Alias for IP "10.10.100.6"
Destination Port: HTTPS
Translation/Target: VLAN_100_DMZ address



According to the best practice, this should allow me to access the webserver from "VLAN_10_Internal" via external URL, but this does not work in my case. As already mentioned before, via "VLAN_100_DMZ" the webserver can access itself via external URL. (Hairpin NAT works, DNAT does NOT)

Thanks for any help, it would be greatly appreciated!
cryo

Edit: I have added a screenshot. I can see that the firewall lets traffic pass from my Client in VLAN_10_Internal to the webserver in the DMZ when i try to access it via external URL. But i still get a timeout on the Client side.