[bdNOG] Inbound Traffic Policy..

Md Kamruzzaman kzzaman_sub at yahoo.com
Fri Jul 3 02:55:26 BDT 2015


Hi

I have experienced the same problem with AirTel and SingTel. 
If both DHK com and Link3 have the same upstream and both DHK Com/Link3 advertise same prefix to same upstream then need to TE on ISP side. Please check route server. 

Regards,Kamruzzaman
 


     On Thursday, July 2, 2015 4:04 PM, Mirza Rakib <mmrakib at gmail.com> wrote:
   

 Hi Rana Vai,
As my knowledge and understanding, more specific announcemnet is the best solution rather than as-path prepending which Zobair Vai mentioned. I had have the similar experienced. However, as-path prepending is a nice technique it should work.Expecting more comments regarding as-path prepending in such situation. Someone have more than 3/4 ISP.And subnet and supernet may be difficult in some cases.Regards,
Mirza RakibOn 2 Jul 2015 00:35, "Md. Zobair Khan" <kzobair at gmail.com> wrote:

Hi,

You might want to make your policy with super net and sub net. Do prefix filtering instead of AS filtering. Sometimes the as path prepend do not work due to the traffic policy of upstreams. 
Announce the more specific prefixes (like /24) to Dhakacom and less specifix prefixes (like /22 or /23) to Link3. That way, you should get your inbound traffic via Dhakacom, not via Link3.

BR
Zobair

_______________________________________________
nog mailing list
nog at bdnog.org
http://mailman.bdnog.org/mailman/listinfo/nog



_______________________________________________
nog mailing list
nog at bdnog.org
http://mailman.bdnog.org/mailman/listinfo/nog


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bdnog.org/pipermail/nog/attachments/20150702/986e6bde/attachment.html>


More information about the nog mailing list