Firewalld and HTTP protocol.

n00b_noob · 09-26-2020, 02:19 AM

Hello,
I want to know, is it possible to use Firewalld for forward a HTTP request to something else? For example, when a user enter something in its browser then his\her request forward to another place.

Thank you.

berndbausch · 09-26-2020, 09:04 AM

See for example https://access.redhat.com/documentat...ort_forwarding (TLDR: Yes).

n00b_noob · 09-26-2020, 10:36 AM

Quote:

Originally Posted by berndbausch

See for example https://access.redhat.com/documentat...ort_forwarding (TLDR: Yes).

Thank you for the link, but I can't see any HTTP protocol!!!
I want to forward the request in the browser. For example, when a user enter 1.2.3.4 in browser then the request forward to "http://www.example.net".

tshikose · 09-26-2020, 10:54 AM

Hi,

Quote:

Originally Posted by n00b_noob

Thank you for the link, but I can't see any HTTP protocol!!!
.

So, at lest you saw the 80!
That is exactly the port number for HTTP protocol.

berndbausch · 09-26-2020, 11:18 AM

Quote:

Originally Posted by n00b_noob

Thank you for the link, but I can't see any HTTP protocol!!!
I want to forward the request in the browser. For example, when a user enter 1.2.3.4 in browser then the request forward to "http://www.example.net".

Then, on server 1.2.3.4, you need to forward TCP ports 80 and 443 (for HTTPS) as described under "To redirect a port to another port at a different IP address".

n00b_noob · 09-26-2020, 12:51 PM

Could Firewalld support requests that made by Browsers? A user enter 1.2.3.4 IP address in his\her Browser and the website that open is "https://example.net".

scasey · 09-26-2020, 03:16 PM

Quote:

Originally Posted by n00b_noob

Could Firewalld support requests that made by Browsers? A user enter 1.2.3.4 IP address in his\her Browser and the website that open is "https://example.net".

That's typically handled by the web server. A call to a web server by IP will return the first VirtualDomain defined (using apache).

berndbausch · 09-26-2020, 06:59 PM

Quote:

Originally Posted by n00b_noob

Could Firewalld support requests that made by Browsers? A user enter 1.2.3.4 IP address in his\her Browser and the website that open is "https://example.net".

Firewalld's port forwarding supports traffic for a certain port. It is unable to determine whether the request is from a browser or a different piece of software.

n00b_noob · 09-27-2020, 01:01 AM

Quote:

Originally Posted by scasey

That's typically handled by the web server. A call to a web server by IP will return the first VirtualDomain defined (using apache).

I wanted to do it without Apache!

n00b_noob · 09-27-2020, 01:05 AM

Quote:

Originally Posted by berndbausch

Firewalld's port forwarding supports traffic for a certain port. It is unable to determine whether the request is from a browser or a different piece of software.

Thus, forwarding will work in any conditions? Whether from the browser or something else?

berndbausch · 09-27-2020, 02:25 AM

Quote:

Originally Posted by n00b_noob

Thus, forwarding will work in any conditions? Whether from the browser or something else?

Yes.

n00b_noob · 09-27-2020, 03:01 AM

Thank you.
Can I use domain name instead of IP?

Code:

# firewall-cmd --list-forward-ports port=80:proto=tcp:toport=443:toaddr=

berndbausch · 09-27-2020, 04:28 AM

Quote:

Originally Posted by n00b_noob

Thank you.
Can I use domain name instead of IP?

I had a quick look at the manual page but could not find an answer. Why don't you just try?

Quote:

Code:

# firewall-cmd --list-forward-ports port=80:proto=tcp:toport=443:toaddr=

You will need the --add-forward-port option, not --list-forward-ports.