Multi Port - Revision history

Kernelkurtz: Mention iptables compatibility layers

2026-03-23T17:18:26Z

Mention iptables compatibility layers

← Older revision		Revision as of 13:18, 23 March 2026
Line 102:		Line 102:
	If you are unable or prefer not to modify your webserver configuration, you can also use Linux firewall functionality to redirect a range of incoming high ports to the configured webserver listening port. This will work with both Apache and Nginx based Zoneminder installs.		If you are unable or prefer not to modify your webserver configuration, you can also use Linux firewall functionality to redirect a range of incoming high ports to the configured webserver listening port. This will work with both Apache and Nginx based Zoneminder installs.

	The following rules are are for iptables firewalls and ~~are working~~ on my RHEL based ~~server~~. If you use another firewall or frontend such as nftables, firewalld, ufw, etc., you ~~will~~ have to translate them accordingly. AI is very helpful for tasks such as this.		The following rules are are for iptables based firewalls and work on my RHEL and Ubuntu based servers. If you use another firewall or frontend such as nftables, firewalld, ufw, etc., you may have to install a compatibility layer, or otherwise translate them to work with your setup accordingly. AI is very helpful for tasks such as this.

	<pre>iptables -t nat -A PREROUTING -p tcp -m multiport --dports 30000:30100 -j REDIRECT --to-ports 443</pre>		<pre>iptables -t nat -A PREROUTING -p tcp -m multiport --dports 30000:30100 -j REDIRECT --to-ports 443</pre>

Kernelkurtz at 17:29, 14 January 2026

2026-01-14T17:29:01Z

← Older revision		Revision as of 13:29, 14 January 2026
Line 102:		Line 102:
	If you are unable or prefer not to modify your webserver configuration, you can also use Linux firewall functionality to redirect a range of incoming high ports to the configured webserver listening port. This will work with both Apache and Nginx based Zoneminder installs.		If you are unable or prefer not to modify your webserver configuration, you can also use Linux firewall functionality to redirect a range of incoming high ports to the configured webserver listening port. This will work with both Apache and Nginx based Zoneminder installs.

	The following rules are are for iptables firewalls and are working on my RHEL based server. If you use another firewall such as nftables, firewalld, ufw, etc., you will have to translate them accordingly. AI is very helpful for tasks such as this.		The following rules are are for iptables firewalls and are working on my RHEL based server. If you use another firewall or frontend such as nftables, firewalld, ufw, etc., you will have to translate them accordingly. AI is very helpful for tasks such as this.

	<pre>iptables -t nat -A PREROUTING -p tcp -m multiport --dports 30000:30100 -j REDIRECT --to-ports 443</pre>		<pre>iptables -t nat -A PREROUTING -p tcp -m multiport --dports 30000:30100 -j REDIRECT --to-ports 443</pre>

Kernelkurtz at 22:45, 9 January 2026

2026-01-09T22:45:23Z

← Older revision		Revision as of 18:45, 9 January 2026
Line 106:		Line 106:
	<pre>iptables -t nat -A PREROUTING -p tcp -m multiport --dports 30000:30100 -j REDIRECT --to-ports 443</pre>		<pre>iptables -t nat -A PREROUTING -p tcp -m multiport --dports 30000:30100 -j REDIRECT --to-ports 443</pre>

	If you are running a headless Zoneminder install ~~this one~~ rule is all you will need. Replace 30000:30100 with the range of ports you want to redirect. Of course this has to match the multiport starting port in Zoneminder's network settings. You can also use port 80 as destination if you don't use https, or whatever other port your webserver listens on.		If you are running a headless Zoneminder install the above rule is all you will need. Replace 30000:30100 with the range of ports you want to redirect. Of course this has to match the multiport starting port in Zoneminder's network settings. You can also use port 80 as destination if you don't use https, or whatever other port your webserver listens on. You can quickly check it is working by browsing to http(s)://yourzomeminderserver:30099 (or some other redirected port).

	If your ZM server has a graphical Linux install and a directly connected display, you will also need some additional configuration to make this work ~~on the local desktop~~ as ~~internal~~ traffic does not use the same prerouting rules. First you need to enable routing on the localnet network. Only do this if you trust the other devices on your local LAN, don't do this if you connect directly to the internet. Add the following line to /etc/sysctl.conf (or the appropriate location for your distribution).		If your ZM server has a graphical Linux install and a directly connected display, you will also need some additional configuration to make this work as localhost traffic does not use the same prerouting rules. First you need to enable routing on the localnet network. Only do this if you trust the other devices on your local LAN, don't do this if you connect directly to the internet. Add the following line to /etc/sysctl.conf (or the appropriate location for your distribution).

	<pre>net.ipv4.conf.all.route_localnet = 1</pre>		<pre>net.ipv4.conf.all.route_localnet = 1</pre>
Line 116:		Line 116:
	<pre>iptables -t nat -I OUTPUT -p tcp -o lo --dport 30000:30100 -j REDIRECT --to-ports 443</pre>		<pre>iptables -t nat -I OUTPUT -p tcp -o lo --dport 30000:30100 -j REDIRECT --to-ports 443</pre>

	That's it~~! You can quickly check it is working by browsing to http(s)://yourzomeminderserver:30099 (or some other redirected port)~~. Be sure to make any rules you add persistent across reboots with whatever firewall management method you are using.		That's it. Be sure to make any rules you add persistent across reboots with whatever firewall management method you are using.

Kernelkurtz: Added test

2026-01-09T16:46:27Z

Added test

← Older revision		Revision as of 12:46, 9 January 2026
Line 116:		Line 116:
	<pre>iptables -t nat -I OUTPUT -p tcp -o lo --dport 30000:30100 -j REDIRECT --to-ports 443</pre>		<pre>iptables -t nat -I OUTPUT -p tcp -o lo --dport 30000:30100 -j REDIRECT --to-ports 443</pre>

	That's it! Be sure to make any rules you add persistent across reboots with whatever firewall management method you are using.		That's it! You can quickly check it is working by browsing to http(s)://yourzomeminderserver:30099 (or some other redirected port). Be sure to make any rules you add persistent across reboots with whatever firewall management method you are using.

Kernelkurtz at 05:44, 9 January 2026

2026-01-09T05:44:37Z

← Older revision		Revision as of 01:44, 9 January 2026
Line 106:		Line 106:
	<pre>iptables -t nat -A PREROUTING -p tcp -m multiport --dports 30000:30100 -j REDIRECT --to-ports 443</pre>		<pre>iptables -t nat -A PREROUTING -p tcp -m multiport --dports 30000:30100 -j REDIRECT --to-ports 443</pre>

	If you are running a headless Zoneminder install ~~that~~ is all you will need. Replace 30000:30100 with the range of ports you want to redirect. Of course this has to match the multiport starting port in Zoneminder's network settings. You can also use port 80 as destination if you don't use https, or whatever other port your webserver listens on.		If you are running a headless Zoneminder install this one rule is all you will need. Replace 30000:30100 with the range of ports you want to redirect. Of course this has to match the multiport starting port in Zoneminder's network settings. You can also use port 80 as destination if you don't use https, or whatever other port your webserver listens on.

	If your ZM server has a graphical Linux install and a directly connected display, you will also need some additional configuration to make this work on the local desktop as internal traffic does not use the same prerouting rules. First you need to enable routing on the localnet network. Only do this if you trust the other devices on your local LAN. Add the following line to /etc/sysctl.conf (or the appropriate location for your distribution).		If your ZM server has a graphical Linux install and a directly connected display, you will also need some additional configuration to make this work on the local desktop as internal traffic does not use the same prerouting rules. First you need to enable routing on the localnet network. Only do this if you trust the other devices on your local LAN, don't do this if you connect directly to the internet. Add the following line to /etc/sysctl.conf (or the appropriate location for your distribution).

	<pre>net.ipv4.conf.all.route_localnet = 1</pre>		<pre>net.ipv4.conf.all.route_localnet = 1</pre>

	You can apply it immediately with sysctl -p. Then you need to add a second firewall rule to redirect the loopback address. Use the same port range and destination port as the previous rule.		You can apply it immediately with sysctl -p. Then you need to add a second firewall rule to redirect the loopback address ports. Use the same port range and destination port as the previous rule.

	<pre>iptables -t nat -I OUTPUT -p tcp -o lo --dport 30000:30100 -j REDIRECT --to-ports 443</pre>		<pre>iptables -t nat -I OUTPUT -p tcp -o lo --dport 30000:30100 -j REDIRECT --to-ports 443</pre>

	That's it! Be sure to make any rules you add persistent across reboots with whatever firewall management method you are using.		That's it! Be sure to make any rules you add persistent across reboots with whatever firewall management method you are using.

Kernelkurtz: Added firewall redirect method

2026-01-08T23:06:47Z

Added firewall redirect method

@@ Line 91: / Line 91: @@
 [[File:Firefox About Config Edit.png|900px|||]]
 ===Resources===
 The forum will have a number of posts regarding this change. It has been discussed extensively. Such as:
@@ Line 96: / Line 97: @@
 [[Category:Dummies_Guide]]

Burger at 14:22, 16 March 2024

2024-03-16T14:22:37Z

← Older revision		Revision as of 10:22, 16 March 2024
Line 1:		Line 1:
	All browsers currently have a limitation where there can only be 6 connections to a server. This can be gotten around by using multi port, or by adjusting ~~the~~ Firefox about:config setting.		All browsers currently have a limitation where there can only be 6 connections to a server. This can be gotten around by using multi port, or by adjusting a Firefox about:config setting.

	==Apache Settings for Multi Port==		==Apache Settings for Multi Port==

Burger: /* Resources */

2024-03-16T14:22:13Z

Resources

← Older revision		Revision as of 10:22, 16 March 2024
Line 92:		Line 92:
	[[File:Firefox About Config Edit.png\|900px\|\|\|]]		[[File:Firefox About Config Edit.png\|900px\|\|\|]]
	===Resources===		===Resources===
	The ~~forums~~ will have a number of posts regarding this change. It has been discussed extensively. Such as:		The forum will have a number of posts regarding this change. It has been discussed extensively. Such as:
	* [https://forums.zoneminder.com/viewtopic.php?f=32&t=23417&p=89249 ZM Forums: Problems when two people are watching live]		* [https://forums.zoneminder.com/viewtopic.php?f=32&t=23417&p=89249 ZM Forums: Problems when two people are watching live]

	[[Category:Dummies_Guide]]		[[Category:Dummies_Guide]]

Burger: /* Firefox About:Config */

2024-03-16T14:19:55Z

Firefox About:Config

← Older revision		Revision as of 10:19, 16 March 2024
Line 89:		Line 89:
	In Firefox you can make a change to the configuration to get cameras to display. First go to [https://support.mozilla.org/en-US/kb/about-config-editor-firefox about:config ]. And search for, then adjust [http://kb.mozillazine.org/Network.http.max-persistent-connections-per-server Network.http.max-persistent-connections-per-server]. The max persistent connections per server must be > 6 in order to see > 6 camera streams. It can be set to any number, so perhaps you might set it to 100 or 150.		In Firefox you can make a change to the configuration to get cameras to display. First go to [https://support.mozilla.org/en-US/kb/about-config-editor-firefox about:config ]. And search for, then adjust [http://kb.mozillazine.org/Network.http.max-persistent-connections-per-server Network.http.max-persistent-connections-per-server]. The max persistent connections per server must be > 6 in order to see > 6 camera streams. It can be set to any number, so perhaps you might set it to 100 or 150.

	[]
	[[File:Firefox About Config Edit.png\|900px\|\|\|]]		[[File:Firefox About Config Edit.png\|900px\|\|\|]]
	===Resources===		===Resources===

Burger: /* Firefox About:Config */

2024-03-16T14:19:42Z

Firefox About:Config

← Older revision		Revision as of 10:19, 16 March 2024
Line 89:		Line 89:
	In Firefox you can make a change to the configuration to get cameras to display. First go to [https://support.mozilla.org/en-US/kb/about-config-editor-firefox about:config ]. And search for, then adjust [http://kb.mozillazine.org/Network.http.max-persistent-connections-per-server Network.http.max-persistent-connections-per-server]. The max persistent connections per server must be > 6 in order to see > 6 camera streams. It can be set to any number, so perhaps you might set it to 100 or 150.		In Firefox you can make a change to the configuration to get cameras to display. First go to [https://support.mozilla.org/en-US/kb/about-config-editor-firefox about:config ]. And search for, then adjust [http://kb.mozillazine.org/Network.http.max-persistent-connections-per-server Network.http.max-persistent-connections-per-server]. The max persistent connections per server must be > 6 in order to see > 6 camera streams. It can be set to any number, so perhaps you might set it to 100 or 150.

			[]
			[[File:Firefox About Config Edit.png\|900px\|\|\|]]
	===Resources===		===Resources===
	The forums will have a number of posts regarding this change. It has been discussed extensively. Such as:		The forums will have a number of posts regarding this change. It has been discussed extensively. Such as: