|
|
<- Previous Message | Next Message -> Thread Index
[isp-bgp] RE: Changing inbound traffic
Hi. If bandwidth isn't an issue, you could switch to a failover BGP configuration instead of load sharing. To do this, send a community to transit2 that lowers the localpref of your routes in their AS. Then all traffic will take the path through transit1.
-Ejay
-----Original Message-----
From: Wim Godden [mailto:housing@...Sent: Tuesday, July 01, 2003 7:08 AM
To: isp-bgp@isp-bgp.com
Subject: [isp-bgp] Changing inbound traffic
Hope some of you have suggestions for this :
- We have 2 transit providers (call them transit1 and transit2). Most traffic runs through
transit1, due to the fact that it's a larger and better-connected network.
- Customers from a certain ISP want to connect to us very fast (we have gameservers,
so latency is important).
- The ISP has 2 possible routes to our transit1 : carrier1 and carrier2.
- The fastest route is carrier1 (12ms).
- The other route (via carrier2) is slower (40ms).
- It seems carrier2 is cheaper for them and they've set a preference for that route.
- How can we influence this route, so that carrier1 is used, if it's possible ?
------------------------ANNOUNCEMENT---------------------------------
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
** 802.11 Planet **
The business of hot spots. Wireless ISP business plans.
Wireless network certifications. High-gain antenna design.
Site survey techniques.
June 25 - 27, Boston, MA
http://www.jupiterevents.com//80211/spring03
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
------------------------ANNOUNCEMENT---------------------------------
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
** 802.11 Planet **
The business of hot spots. Wireless ISP business plans.
Wireless network certifications. High-gain antenna design.
Site survey techniques.
June 25 - 27, Boston, MA
http://www.jupiterevents.com//80211/spring03
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
<- Previous Message | Next Message -> Thread Index
|
|