Talk:Slackware template creation - Revision history

Arnoldo: /* Iptables error */

2007-03-07T16:00:42Z

‎Iptables error

Arnoldo: /* Iptables error */

2007-03-07T15:59:30Z

‎Iptables error

Arnoldo: /* Iptables error */

2007-03-07T15:41:08Z

‎Iptables error

Arnoldo: /* Iptables error */

2007-03-07T15:40:50Z

‎Iptables error

Arnoldo: /* Iptables error */

2007-03-07T15:29:11Z

‎Iptables error

Arnoldo: Iptables error

2007-03-07T15:21:14Z

Iptables error

Scythe: Some formatting in my last reply

2006-06-07T09:27:30Z

Some formatting in my last reply

Scythe: Reply to Kir

2006-06-07T09:26:46Z

Reply to Kir

Kir: Replied to /* Typo + IPtables */

2006-06-07T09:05:40Z

Replied to ‎Typo + IPtables

Scythe at 20:54, 6 June 2006

2006-06-06T20:54:52Z

← Older revision		Revision as of 16:00, 7 March 2007
Line 32:		Line 32:
	SOLVED		SOLVED

−	In the ~~<pre>~~<VE>.conf~~</pre>~~ (or in the ~~<pre>~~vz.conf~~</pre>~~) I must include <code>IPTABLES="ipt_state ..."</code>	+	In the <VE>.conf (or in the vz.conf) I must include <code>IPTABLES="ipt_state ..."</code>

← Older revision		Revision as of 15:59, 7 March 2007
Line 32:		Line 32:
	SOLVED		SOLVED

−	In the <VE>.conf I must include <code>IPTABLES="ipt_state"</code>	+	In the <pre><VE>.conf</pre> (or in the <pre>vz.conf</pre>) I must include <code>IPTABLES="ipt_state ..."</code>

← Older revision		Revision as of 15:41, 7 March 2007
Line 32:		Line 32:
	SOLVED		SOLVED

−	In the <VE>.conf I must ~~inlude~~ IPTABLES="ipt_state"	+	In the <VE>.conf I must include <code>IPTABLES="ipt_state"</code>

← Older revision		Revision as of 15:40, 7 March 2007
Line 28:		Line 28:

	Any suggestions?		Any suggestions?
		+
		+
		+	SOLVED
		+
		+	In the <VE>.conf I must inlude IPTABLES="ipt_state"

← Older revision		Revision as of 15:29, 7 March 2007
Line 19:		Line 19:

	The VE based upon che slackware 11 cache returns an error when I add an Iptables rule:		The VE based upon che slackware 11 cache returns an error when I add an Iptables rule:
		+
	<code>iptables -A INPUT -m state --state ESTABLISHED -j ACCEPT</code>		<code>iptables -A INPUT -m state --state ESTABLISHED -j ACCEPT</code>
		+
		+	<code>iptables: Unknown error 4294967295</code>
		+
		+
		+	I think that it depends on the <code>-m state</code> but I do not know how to solve it.
		+
		+	Any suggestions?

← Older revision		Revision as of 15:21, 7 March 2007
Line 12:		Line 12:
	: There is actually no need for iptables modules to be available inside VE for iptables to work, so you got it wrong. I have reverted your last change. No kernel modules are loaded inside VE at all -- so you do not need modutils as well. Also, can you please specify the summary then you are making a change? Otherwise it's not clear from the history page what have changed. It makes sense to select an option "Prompt me when entering a blank edit summary" in your preferences->editing. --[[User:Kir\|Kir]] 05:05, 7 June 2006 (EDT)		: There is actually no need for iptables modules to be available inside VE for iptables to work, so you got it wrong. I have reverted your last change. No kernel modules are loaded inside VE at all -- so you do not need modutils as well. Also, can you please specify the summary then you are making a change? Otherwise it's not clear from the history page what have changed. It makes sense to select an option "Prompt me when entering a blank edit summary" in your preferences->editing. --[[User:Kir\|Kir]] 05:05, 7 June 2006 (EDT)
	:: You are right, I accidentally mixed the openvz.org "official" template cache's root filesystem with my host's own, so I mislooked the /lib/modules directory... I also corrected the typo again (a missing ")" in the "Moving a Sl. installation into a VE" part) which You have included again when reverting my erroneous notice about iptables modules. --[[User:Scythe\|Scythe]] 11:26, 7 June 2006 (CET)		:: You are right, I accidentally mixed the openvz.org "official" template cache's root filesystem with my host's own, so I mislooked the /lib/modules directory... I also corrected the typo again (a missing ")" in the "Moving a Sl. installation into a VE" part) which You have included again when reverting my erroneous notice about iptables modules. --[[User:Scythe\|Scythe]] 11:26, 7 June 2006 (CET)
		+
		+	== Iptables error ==
		+
		+	Hi all,
		+	I have installed a Slackware 11 and all is ok.
		+
		+	The VE based upon che slackware 11 cache returns an error when I add an Iptables rule:
		+	<code>iptables -A INPUT -m state --state ESTABLISHED -j ACCEPT</code>

@@ Line 11: / Line 11: @@
 before cache creation or after VE creation the /lib/modules should be created with the needed iptables modules. --[[User:Scythe|Scythe]] 22:54, 6 June 2006 (CET)
 : There is actually no need for iptables modules to be available inside VE for iptables to work, so you got it wrong. I have reverted your last change. No kernel modules are loaded inside VE at all -- so you do not need modutils as well. Also, can you please specify the summary then you are making a change? Otherwise it's not clear from the history page what have changed. It makes sense to select an option "Prompt me when entering a blank edit summary" in your preferences->editing. --[[User:Kir|Kir]] 05:05, 7 June 2006 (EDT)
-:: You are right, I accidentally mixed the openvz.org "official" template cache's root filesystem with my host's own, so I mislooked the /lib/modules directory...
+:: You are right, I accidentally mixed the openvz.org "official" template cache's root filesystem with my host's own, so I mislooked the /lib/modules directory... I also corrected the typo again (a missing ")" in the "Moving a Sl. installation into a VE" part) which You have included again when reverting my erroneous notice about iptables modules. --[[User:Scythe|Scythe]] 11:26, 7 June 2006 (CET)

← Older revision		Revision as of 09:26, 7 June 2006
Line 11:		Line 11:
	before cache creation or after VE creation the /lib/modules should be created with the needed iptables modules. --[[User:Scythe\|Scythe]] 22:54, 6 June 2006 (CET)		before cache creation or after VE creation the /lib/modules should be created with the needed iptables modules. --[[User:Scythe\|Scythe]] 22:54, 6 June 2006 (CET)
	: There is actually no need for iptables modules to be available inside VE for iptables to work, so you got it wrong. I have reverted your last change. No kernel modules are loaded inside VE at all -- so you do not need modutils as well. Also, can you please specify the summary then you are making a change? Otherwise it's not clear from the history page what have changed. It makes sense to select an option "Prompt me when entering a blank edit summary" in your preferences->editing. --[[User:Kir\|Kir]] 05:05, 7 June 2006 (EDT)		: There is actually no need for iptables modules to be available inside VE for iptables to work, so you got it wrong. I have reverted your last change. No kernel modules are loaded inside VE at all -- so you do not need modutils as well. Also, can you please specify the summary then you are making a change? Otherwise it's not clear from the history page what have changed. It makes sense to select an option "Prompt me when entering a blank edit summary" in your preferences->editing. --[[User:Kir\|Kir]] 05:05, 7 June 2006 (EDT)
		+	:: You are right, I accidentally mixed the openvz.org "official" template cache's root filesystem with my host's own, so I mislooked the /lib/modules directory...
		+	I also corrected the typo again (a missing ")" in the "Moving a Sl. installation into a VE" part) which You have included again when reverting my erroneous notice about iptables modules. --[[User:Scythe\|Scythe]] 11:26, 7 June 2006 (CET)

← Older revision		Revision as of 09:05, 7 June 2006
Line 10:		Line 10:
	Also, I forgot to mention that IPtables needs modules from the running kernel in the VE to work, so		Also, I forgot to mention that IPtables needs modules from the running kernel in the VE to work, so
	before cache creation or after VE creation the /lib/modules should be created with the needed iptables modules. --[[User:Scythe\|Scythe]] 22:54, 6 June 2006 (CET)		before cache creation or after VE creation the /lib/modules should be created with the needed iptables modules. --[[User:Scythe\|Scythe]] 22:54, 6 June 2006 (CET)
		+	: There is actually no need for iptables modules to be available inside VE for iptables to work, so you got it wrong. I have reverted your last change. No kernel modules are loaded inside VE at all -- so you do not need modutils as well. Also, can you please specify the summary then you are making a change? Otherwise it's not clear from the history page what have changed. It makes sense to select an option "Prompt me when entering a blank edit summary" in your preferences->editing. --[[User:Kir\|Kir]] 05:05, 7 June 2006 (EDT)

← Older revision		Revision as of 20:54, 6 June 2006
Line 5:		Line 5:
	Actually, since you do not run anything inside the temporary VE (777) which requires an IP address, you can omit the step of setting VE's OSTEMPLATE, an IP address and a hostname. This was done for Debian specifically because you have to run <tt>apt update</tt> and <tt>apt upgrade</tt> commands, which requires network to be working. So you can edit that out to simplify things. I have not done it yet because you might have other reasons to leave it. --[[User:Kir\|Kir]] 15:43, 6 June 2006 (EDT)		Actually, since you do not run anything inside the temporary VE (777) which requires an IP address, you can omit the step of setting VE's OSTEMPLATE, an IP address and a hostname. This was done for Debian specifically because you have to run <tt>apt update</tt> and <tt>apt upgrade</tt> commands, which requires network to be working. So you can edit that out to simplify things. I have not done it yet because you might have other reasons to leave it. --[[User:Kir\|Kir]] 15:43, 6 June 2006 (EDT)
	: I have actually removed these settings from the text, since it looks like they are not needed, and you forgot to run <tt>vzctl set --ipdel</tt> so OS template cache ends up with the IP address which is wrong. So I followed the easy path and instead of adding the procedure of removing VE IP I just removed the adding of it! Also note that setting OSTEMPLATE is actually needed for <tt>vzctl set --ipadd</tt> to work. --[[User:Kir\|Kir]] 16:15, 6 June 2006 (EDT)		: I have actually removed these settings from the text, since it looks like they are not needed, and you forgot to run <tt>vzctl set --ipdel</tt> so OS template cache ends up with the IP address which is wrong. So I followed the easy path and instead of adding the procedure of removing VE IP I just removed the adding of it! Also note that setting OSTEMPLATE is actually needed for <tt>vzctl set --ipadd</tt> to work. --[[User:Kir\|Kir]] 16:15, 6 June 2006 (EDT)
		+
		+	== Typo + IPtables ==
		+	I corrected a typo.
		+	Also, I forgot to mention that IPtables needs modules from the running kernel in the VE to work, so
		+	before cache creation or after VE creation the /lib/modules should be created with the needed iptables modules. --[[User:Scythe\|Scythe]] 22:54, 6 June 2006 (CET)