<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>disable firewall &#8211; it.megocollector.com</title>
	<atom:link href="https://it.megocollector.com/tag/disable-firewall/feed/" rel="self" type="application/rss+xml" />
	<link>https://it.megocollector.com</link>
	<description>The information technology compendium</description>
	<lastBuildDate>Mon, 30 Mar 2026 23:50:17 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>Accessing JBoss on RHEL/CentOS — Firewall Gotcha (and the Right Way to Handle It)</title>
		<link>https://it.megocollector.com/scripts/disable-firewall-on-red-hat-enterprise-linux-rhel/</link>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 23 Sep 2008 17:03:51 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Scripts]]></category>
		<category><![CDATA[Tips and Tricks]]></category>
		<category><![CDATA[CentOS]]></category>
		<category><![CDATA[chkconfig]]></category>
		<category><![CDATA[disable firewall]]></category>
		<category><![CDATA[fedora]]></category>
		<category><![CDATA[iptables]]></category>
		<category><![CDATA[red hat]]></category>
		<category><![CDATA[rhel]]></category>
		<guid isPermaLink="false">https://it.megocollector.com/?p=663</guid>

					<description><![CDATA[While setting up JBoss (with its bundled Tomcat) on a freshly installed Red Hat–based system, everything appeared to be running correctly. The service started cleanly, and the default web interface was bound to port 8080 as expected. However, when attempting to access the application from a remote machine, the connection failed. After a bit of troubleshooting, the issue turned out...]]></description>
		
		
		
			</item>
	</channel>
</rss>
