<?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>Tips and Tux &#187; IMSS</title>
	<atom:link href="http://www.tipsandtux.org/wordpress/tag/imss/feed" rel="self" type="application/rss+xml" />
	<link>http://www.tipsandtux.org/wordpress</link>
	<description>di Linux, Foto, Piante Carnivore e non solo... il informatipapàliticarnivoro</description>
	<lastBuildDate>Fri, 13 Jan 2012 10:15:32 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Configurazione trasparent proxy wccp con ASA &amp; Linux</title>
		<link>http://www.tipsandtux.org/wordpress/configurazione-trasparent-proxy-wccp-con-asa-linux.html</link>
		<comments>http://www.tipsandtux.org/wordpress/configurazione-trasparent-proxy-wccp-con-asa-linux.html#comments</comments>
		<pubDate>Wed, 01 Dec 2010 10:08:27 +0000</pubDate>
		<dc:creator>superpaia</dc:creator>
				<category><![CDATA[Gnu/Linux]]></category>
		<category><![CDATA[Sistemi]]></category>
		<category><![CDATA[Cisco]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[IMSS]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[squid]]></category>

		<guid isPermaLink="false">http://www.tipsandtux.org/wordpress/?p=234</guid>
		<description><![CDATA[http://parvinderbhasin.blogspot.com/2009/06/squid-wccp-and-cisco-asa-setup.html http://wiki.squid-cache.org/ConfigExamples/Intercept/CiscoAsaWccp2 Come stabilire la connessione WCCP tra linux (squid, si intende già configurato) e Cisco ASA (testato con il 5510) Sul linux, con squid &#62;2.6 installato: #modprobe ip_gre #iptunnel add gre1 mode gre remote 192.168.1.254 local 192.168.1.19 dev eth0 i#fconfig gre1 inet 192.168.1.19 netmask 255.255.255.0 up #echo 1 &#62; /proc/sys/net/ipv4/ip_forward #echo 0 &#62; /proc/sys/net/ipv4/conf/default/rp_filter #echo 0 &#62; /proc/sys/net/ipv4/conf/eth0/rp_filter #echo [...]]]></description>
			<content:encoded><![CDATA[<p><span><span style="font-size: x-small;"><a href="https://smtp.infonetsolutions.it/owa/redir.aspx?C=6c2aa5568761476d96b2f32c0a58957d&amp;URL=http%3a%2f%2fparvinderbhasin.blogspot.com%2f2009%2f06%2fsquid-wccp-and-cisco-asa-setup.html" target="_blank">http://parvinderbhasin.blogspot.com/2009/06/squid-wccp-and-cisco-asa-setup.html</a><br />
<a href="https://smtp.infonetsolutions.it/owa/redir.aspx?C=6c2aa5568761476d96b2f32c0a58957d&amp;URL=http%3a%2f%2fwiki.squid-cache.org%2fConfigExamples%2fIntercept%2fCiscoAsaWccp2" target="_blank">http://wiki.squid-cache.org/ConfigExamples/Intercept/CiscoAsaWccp2</a></p>
<p>Come stabilire la connessione WCCP tra linux (squid, si intende già configurato) e Cisco ASA (testato con il 5510)<br />
<span id="more-234"></span><br />
Sul linux, con squid &gt;2.6 installato:<br />
<em>#modprobe ip_gre<br />
#iptunnel add gre1 mode gre remote 192.168.1.254 local 192.168.1.19 dev eth0<br />
i#fconfig gre1 inet 192.168.1.19 netmask 255.255.255.0 up<br />
#echo 1 &gt; /proc/sys/net/ipv4/ip_forward<br />
#echo 0 &gt; /proc/sys/net/ipv4/conf/default/rp_filter<br />
#echo 0 &gt; /proc/sys/net/ipv4/conf/eth0/rp_filter<br />
#echo 0 &gt; /proc/sys/net/ipv4/conf/gre1/rp_filter<br />
#iptables -t nat -A PREROUTING -i gre1 -p tcp -s 192.168.1.0/24 -m tcp &#8211;dport 80 -j REDIRECT &#8211;to-port 8080<br />
#iptables -t nat -A PREROUTING -i eth0 -p tcp -s 192.168.1.0/24 -m tcp &#8211;dport 80 -j REDIRECT &#8211;to-port 8080<br />
</em><br />
sul Cisco:<br />
<em>#access-list proxyclients extended deny tcp host 192.168.1.68 any eq www</em> &lt;&#8212; per ip che devono fare il bypass del trasparent proxy<br />
<em>#access-list proxyclients extended permit tcp 192.168.1.0 255.255.255.0  any eq www </em>&lt;&#8211; ip che saranno soggetti al trasparent proxy<br />
<em> #access-list proxyservers extended permit ip host 192.168.1.19 any </em><br />
<em>#wccp web-cache redirect-list proxyclients group-list proxyservers<br />
#wccp interface  Lan web-cache redirect in<br />
#wccp web-cache</em></p>
<p>per vedere lo stato sul Cisco:<br />
<em> sh wccp web-cache detail</em><br />
e<br />
<em> sh wccp web-cache</em></p>
<p>NB:<br />
<span style="text-decoration: underline;">&#8220;The only topology that the security appliance supports is when client  and cache engine are behind the same interface of the security appliance  and the cache engine can directly communicate with the client without  going through the security appliance.&#8221; </span></span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.tipsandtux.org/wordpress/configurazione-trasparent-proxy-wccp-con-asa-linux.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>IMSS Linux database GRANDE! (IMSS Big disk Size )</title>
		<link>http://www.tipsandtux.org/wordpress/imss-linux-database-grande-imss-big-disk-size.html</link>
		<comments>http://www.tipsandtux.org/wordpress/imss-linux-database-grande-imss-big-disk-size.html#comments</comments>
		<pubDate>Thu, 21 Jan 2010 10:39:34 +0000</pubDate>
		<dc:creator>superpaia</dc:creator>
				<category><![CDATA[Gnu/Linux]]></category>
		<category><![CDATA[IMSS]]></category>
		<category><![CDATA[Paolo san docet]]></category>
		<category><![CDATA[Trend Micro]]></category>

		<guid isPermaLink="false">http://www.tipsandtux.org/wordpress/?p=32</guid>
		<description><![CDATA[Nei server linux usati come gateway di posta elettronica, se c’è IMSS installato si può incombere in problemi di saturazione del disco. Quanto si riceve una notifica tipo questa: The free disk space under /opt/trend/imss on server SMTP is 1227 MB, which is below the threshold. significa che il database di IMSS ha quasi saturato il disco, e bisogna procedere [...]]]></description>
			<content:encoded><![CDATA[<p>Nei server linux usati come gateway di posta elettronica, se c’è IMSS installato si può incombere in problemi di saturazione del disco.</p>
<p>Quanto si riceve una notifica tipo questa:<br />
<em> The free disk space under /opt/trend/imss on server SMTP is 1227 MB, which is below the threshold.</em></p>
<p>significa che il database di IMSS ha quasi saturato il disco, e bisogna procedere all’allegerimento.</p>
<p>Per far ciò:</p>
<p>-      Bypassare IMSS commentando la riga “content_filter = imss:localhost:10025“ in /etc/postfix/main.cf<br />
-      Riavviare postfix (rcpostfix restart)<br />
-      Stoppare i servizi di IMSS<br />
-      Lanciare il comando<br />
/opt/trend/imss/PostgreSQL/bin/vacuumdb -f -a -U imss<br />
e attendere che la procedura termini<br />
-      Avviare i servizi di IMSS<br />
-      Togliere il commento inserito nel file /etc/postfix/main.cf<br />
-      Riavviare postfix<br />
Si può verificare che lo spazio si sia effettivamente liberato con il comando df -h</p>
<p>(procedura testata con successo su Sles 10 e Imss 7.0)</p>
<p><em>[Paolo san docet!]</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.tipsandtux.org/wordpress/imss-linux-database-grande-imss-big-disk-size.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

