<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	>
<channel>
	<title>Comments for Andryan's Random Notes</title>
	<atom:link href="http://blog.nirkabel.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.nirkabel.org</link>
	<description>This blog is here to stay</description>
	<pubDate>Tue, 06 Jan 2009 01:36:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on MikroTik RouterOS &#8212; BGP by Andryan</title>
		<link>http://blog.nirkabel.org/2007/05/04/mikrotik-routeros-bgp/comment-page-1/#comment-51</link>
		<dc:creator>Andryan</dc:creator>
		<pubDate>Sun, 07 Dec 2008 15:17:18 +0000</pubDate>
		<guid isPermaLink="false">http://andryan.wordpress.com/2007/05/04/mikrotiks-routeros-bgp/#comment-51</guid>
		<description>Hi Arif,

This is the example:
from /routing filter
 0   ;;; Advertise 116.0.0.0/21 to OpenIXP in /24s
     chain=to_OpenIXP prefix=116.0.0.0/21 prefix-length=24 invert-match=no action=accept

 1   ;;; Advertise 61.45.224.0/20 to OpenIXP in /24s
     chain=to_OpenIXP prefix=61.45.224.0/20 prefix-length=24 invert-match=no action=accept

 2   ;;; Advertise only our prefixes to OpenIXP, do not redistribute transit routes to IX
     chain=to_OpenIXP invert-match=no action=discard

 3   ;;; Discard default route from OpenIXP
     chain=from_OpenIXP prefix=0.0.0.0/0 invert-match=no action=discard 

 4   ;;; IX routes should get higher priority
     chain=from_OpenIXP invert-match=no action=accept set-bgp-local-pref=200

5   ;;; Advertise 61.45.224.0/20 to NAP
     chain=to_NAP prefix=61.45.224.0/20 prefix-length=20 invert-match=no action=accept

6   ;;; Advertise 116.0.0.0/21 to NAP
     chain=to_NAP prefix=116.0.0.0/21 prefix-length=21 invert-match=no action=accept

7   ;;; Advertise only our prefixes to NAP, do not redistribute IX routes/other transit routes to this transit
     chain=to_NAP invert-match=no action=discard

8 X ;;; Only use default route from NAP's BGP feed, opposite the following rule
     chain=from_NAP prefix=0.0.0.0/0 invert-match=yes action=discard 

9   ;;; Discard default route from NAP
     chain=from_NAP prefix=0.0.0.0/0 invert-match=no action=discard

from /routing bgp network
 0 A 116.0.0.0/21       no
 1 A 116.0.0.0/24       no
 2 A 116.0.1.0/24       no
 3 A 116.0.2.0/24       no
 4 A 116.0.3.0/24       no
 5 A 116.0.4.0/24       no
 6 A 116.0.5.0/24       no
 7 A 116.0.6.0/24       no
 8 A 116.0.7.0/24       no
 9 A 61.45.224.0/20     no
10 A 61.45.224.0/24     no
11 A 61.45.225.0/24     no
12 A 61.45.226.0/24     no
13 A 61.45.227.0/24     no
14 A 61.45.228.0/24     no
15 A 61.45.229.0/24     no
16 A 61.45.230.0/24     no
17 A 61.45.231.0/24     no
18 A 61.45.232.0/24     no
19 A 61.45.233.0/24     no
20 A 61.45.234.0/24     no
21 A 61.45.235.0/24     no
22 A 61.45.236.0/24     no
23 A 61.45.237.0/24     no
24 A 61.45.238.0/24     no
25 A 61.45.239.0/24     no

Please note that OpenIXP advertises the smaller prefixes (/24) to make sure that local IX traffic takes the OpenIXP path rather than the NAP path. I also choose to drop default route from NAP to receive full BGP feed from my NAP. If you wish to receive only the default route (make sure your NAP does provide a default route otherwise your packets will go nowhere), enable filter #8 and disable #9.

Good luck!</description>
		<content:encoded><![CDATA[<p>Hi Arif,</p>
<p>This is the example:<br />
from /routing filter<br />
 0   ;;; Advertise 116.0.0.0/21 to OpenIXP in /24s<br />
     chain=to_OpenIXP prefix=116.0.0.0/21 prefix-length=24 invert-match=no action=accept</p>
<p> 1   ;;; Advertise 61.45.224.0/20 to OpenIXP in /24s<br />
     chain=to_OpenIXP prefix=61.45.224.0/20 prefix-length=24 invert-match=no action=accept</p>
<p> 2   ;;; Advertise only our prefixes to OpenIXP, do not redistribute transit routes to IX<br />
     chain=to_OpenIXP invert-match=no action=discard</p>
<p> 3   ;;; Discard default route from OpenIXP<br />
     chain=from_OpenIXP prefix=0.0.0.0/0 invert-match=no action=discard </p>
<p> 4   ;;; IX routes should get higher priority<br />
     chain=from_OpenIXP invert-match=no action=accept set-bgp-local-pref=200</p>
<p>5   ;;; Advertise 61.45.224.0/20 to NAP<br />
     chain=to_NAP prefix=61.45.224.0/20 prefix-length=20 invert-match=no action=accept</p>
<p>6   ;;; Advertise 116.0.0.0/21 to NAP<br />
     chain=to_NAP prefix=116.0.0.0/21 prefix-length=21 invert-match=no action=accept</p>
<p>7   ;;; Advertise only our prefixes to NAP, do not redistribute IX routes/other transit routes to this transit<br />
     chain=to_NAP invert-match=no action=discard</p>
<p>8 X ;;; Only use default route from NAP&#8217;s BGP feed, opposite the following rule<br />
     chain=from_NAP prefix=0.0.0.0/0 invert-match=yes action=discard </p>
<p>9   ;;; Discard default route from NAP<br />
     chain=from_NAP prefix=0.0.0.0/0 invert-match=no action=discard</p>
<p>from /routing bgp network<br />
 0 A 116.0.0.0/21       no<br />
 1 A 116.0.0.0/24       no<br />
 2 A 116.0.1.0/24       no<br />
 3 A 116.0.2.0/24       no<br />
 4 A 116.0.3.0/24       no<br />
 5 A 116.0.4.0/24       no<br />
 6 A 116.0.5.0/24       no<br />
 7 A 116.0.6.0/24       no<br />
 8 A 116.0.7.0/24       no<br />
 9 A 61.45.224.0/20     no<br />
10 A 61.45.224.0/24     no<br />
11 A 61.45.225.0/24     no<br />
12 A 61.45.226.0/24     no<br />
13 A 61.45.227.0/24     no<br />
14 A 61.45.228.0/24     no<br />
15 A 61.45.229.0/24     no<br />
16 A 61.45.230.0/24     no<br />
17 A 61.45.231.0/24     no<br />
18 A 61.45.232.0/24     no<br />
19 A 61.45.233.0/24     no<br />
20 A 61.45.234.0/24     no<br />
21 A 61.45.235.0/24     no<br />
22 A 61.45.236.0/24     no<br />
23 A 61.45.237.0/24     no<br />
24 A 61.45.238.0/24     no<br />
25 A 61.45.239.0/24     no</p>
<p>Please note that OpenIXP advertises the smaller prefixes (/24) to make sure that local IX traffic takes the OpenIXP path rather than the NAP path. I also choose to drop default route from NAP to receive full BGP feed from my NAP. If you wish to receive only the default route (make sure your NAP does provide a default route otherwise your packets will go nowhere), enable filter #8 and disable #9.</p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on MikroTik RouterOS &#8212; BGP by arif</title>
		<link>http://blog.nirkabel.org/2007/05/04/mikrotik-routeros-bgp/comment-page-1/#comment-50</link>
		<dc:creator>arif</dc:creator>
		<pubDate>Tue, 02 Dec 2008 06:06:33 +0000</pubDate>
		<guid isPermaLink="false">http://andryan.wordpress.com/2007/05/04/mikrotiks-routeros-bgp/#comment-50</guid>
		<description>whereis the example configuration, could you share? may be with fake ip address, 
thanks 4 advance</description>
		<content:encoded><![CDATA[<p>whereis the example configuration, could you share? may be with fake ip address,<br />
thanks 4 advance</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Update initrd with mkinitrd to install new (different) hardware on Linux by Demetri Mouratis</title>
		<link>http://blog.nirkabel.org/2008/03/19/update-initrd-with-mkinitrd-to-install-new-different-hardware-on-linux/comment-page-1/#comment-49</link>
		<dc:creator>Demetri Mouratis</dc:creator>
		<pubDate>Fri, 21 Nov 2008 19:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://andryan.wordpress.com/?p=47#comment-49</guid>
		<description>Good reference.  I'm glad to hear you figured it out.</description>
		<content:encoded><![CDATA[<p>Good reference.  I&#8217;m glad to hear you figured it out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hello Kitty Online on Mac OS X with CrossOver by marine_maiden</title>
		<link>http://blog.nirkabel.org/2008/11/01/hello-kitty-online-on-mac-os-x-with-crossover/comment-page-1/#comment-46</link>
		<dc:creator>marine_maiden</dc:creator>
		<pubDate>Sun, 16 Nov 2008 05:06:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.nirkabel.org/?p=66#comment-46</guid>
		<description>LOL
You should put that in the site when it's finished later. :p</description>
		<content:encoded><![CDATA[<p>LOL<br />
You should put that in the site when it&#8217;s finished later. :p</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Passive FTP workaround for Plesk&#8217;s proftpd by Russell</title>
		<link>http://blog.nirkabel.org/2006/01/23/passive-ftp-workaround-for-plesks-proftpd/comment-page-1/#comment-5</link>
		<dc:creator>Russell</dc:creator>
		<pubDate>Tue, 13 May 2008 00:08:18 +0000</pubDate>
		<guid isPermaLink="false">http://andryan.wordpress.com/2006/01/23/passive-ftp-workaround-for-plesks-proftpd/#comment-5</guid>
		<description>Make sure if you place the PassivePorts 49152 65534 that you place it between the  tags and not just anywhere.</description>
		<content:encoded><![CDATA[<p>Make sure if you place the PassivePorts 49152 65534 that you place it between the  tags and not just anywhere.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on krb5-telnet != telnet-server by Andryan</title>
		<link>http://blog.nirkabel.org/2008/05/08/krb5-telnet-telnet-server/comment-page-1/#comment-39</link>
		<dc:creator>Andryan</dc:creator>
		<pubDate>Thu, 08 May 2008 00:46:40 +0000</pubDate>
		<guid isPermaLink="false">http://andryan.wordpress.com/?p=54#comment-39</guid>
		<description>Because these servers are connected to an internal network which is isolated and sniffing is impossible. Anyway, that was my task at work and there is &lt;strong&gt;no&lt;/strong&gt; security concern.

Before you post your comment, this is my technical notes and I don't need people telling me that telnet is insecure. The idea of this blog is to share knowledge that is probably not documented elsewhere. I know what I'm doing, people.

For those who need this information, they should know what they are doing and know the risks involved by using telnet.</description>
		<content:encoded><![CDATA[<p>Because these servers are connected to an internal network which is isolated and sniffing is impossible. Anyway, that was my task at work and there is <strong>no</strong> security concern.</p>
<p>Before you post your comment, this is my technical notes and I don&#8217;t need people telling me that telnet is insecure. The idea of this blog is to share knowledge that is probably not documented elsewhere. I know what I&#8217;m doing, people.</p>
<p>For those who need this information, they should know what they are doing and know the risks involved by using telnet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on krb5-telnet != telnet-server by jaoswald</title>
		<link>http://blog.nirkabel.org/2008/05/08/krb5-telnet-telnet-server/comment-page-1/#comment-38</link>
		<dc:creator>jaoswald</dc:creator>
		<pubDate>Wed, 07 May 2008 22:29:36 +0000</pubDate>
		<guid isPermaLink="false">http://andryan.wordpress.com/?p=54#comment-38</guid>
		<description>Why, out of curiosity, do you feel the need to enable a doubly-insecure option?

Anyone who sniffs your root password (sent unencrypted by telnet) will then be able to own your system.</description>
		<content:encoded><![CDATA[<p>Why, out of curiosity, do you feel the need to enable a doubly-insecure option?</p>
<p>Anyone who sniffs your root password (sent unencrypted by telnet) will then be able to own your system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on krb5-telnet != telnet-server by Kongo Kalle</title>
		<link>http://blog.nirkabel.org/2008/05/08/krb5-telnet-telnet-server/comment-page-1/#comment-37</link>
		<dc:creator>Kongo Kalle</dc:creator>
		<pubDate>Wed, 07 May 2008 20:38:34 +0000</pubDate>
		<guid isPermaLink="false">http://andryan.wordpress.com/?p=54#comment-37</guid>
		<description>They have put notes in about it, its written pretty clearly:

TELNET IS DEAD, USE SSH!</description>
		<content:encoded><![CDATA[<p>They have put notes in about it, its written pretty clearly:</p>
<p>TELNET IS DEAD, USE SSH!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Passive FTP workaround for Plesk&#8217;s proftpd by Amed</title>
		<link>http://blog.nirkabel.org/2006/01/23/passive-ftp-workaround-for-plesks-proftpd/comment-page-1/#comment-4</link>
		<dc:creator>Amed</dc:creator>
		<pubDate>Thu, 24 Apr 2008 22:44:54 +0000</pubDate>
		<guid isPermaLink="false">http://andryan.wordpress.com/2006/01/23/passive-ftp-workaround-for-plesks-proftpd/#comment-4</guid>
		<description>hey thanks, it helped alot</description>
		<content:encoded><![CDATA[<p>hey thanks, it helped alot</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RP-PPPoE server problem in Fedora Core 5, 6, Fedora 7, 8 by Aland</title>
		<link>http://blog.nirkabel.org/2007/06/22/rp-pppoe-server-problem-in-fedora-core-5-6-fedora-7-8/comment-page-1/#comment-33</link>
		<dc:creator>Aland</dc:creator>
		<pubDate>Tue, 15 Apr 2008 22:27:06 +0000</pubDate>
		<guid isPermaLink="false">http://andryan.wordpress.com/2007/06/22/rp-pppoe-server-problem-in-fedora-core-5-6/#comment-33</guid>
		<description>Realmente no core 7 e 8 apos fazer toda configuração do pppoe-setup...
quando ele consegue conectar ele perde todas as rotas... nem o proprio ip local LAN ou WAN ele consegue pingar...
problema grave se fosse so em casa blz.. mas tem empresas que usam adsl com ip dinamico....
quero migrar para o core 7 ou 8 e nao posso por este problema.
Grato pela atenção e conto com a colaboracao na solucao deste problema.</description>
		<content:encoded><![CDATA[<p>Realmente no core 7 e 8 apos fazer toda configuração do pppoe-setup&#8230;<br />
quando ele consegue conectar ele perde todas as rotas&#8230; nem o proprio ip local LAN ou WAN ele consegue pingar&#8230;<br />
problema grave se fosse so em casa blz.. mas tem empresas que usam adsl com ip dinamico&#8230;.<br />
quero migrar para o core 7 ou 8 e nao posso por este problema.<br />
Grato pela atenção e conto com a colaboracao na solucao deste problema.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
