[f-nsp] Multiple Internet Providers
Joseph Hardeman
jwhardeman at gmail.com
Sun Apr 26 21:24:08 EDT 2009
Niels,
Thank you for your reply. After adding the following global policy and
then we decided to split the two incoming internet connections on to
their own VLAN's both of my circuits came up and both are responding.
Added:
ip policy prefer-direct-route
!
vlan 5 name FirstCircuit by port
untagged ethe 1/1
!
vlan 6 name SecondCircuit by port
untagged ethe 1/2
My ip route entries were correct so that the distance for both 0.0.0.0
0.0.0.0 entries for the circuits were at distance 240 which allows BGP
route table to be checked first
Again, thank you for the quick response.
Joe
> ------------------------------
>
> Message: 2
> Date: Sat, 25 Apr 2009 18:45:15 +0200
> From: Niels Bakker <niels=foundry-nsp at bakker.net>
> Subject: Re: [f-nsp] Multiple Internet Providers
> To: foundry-nsp at puck.nether.net
> Message-ID: <20090425164515.GP9502 at burnout.tpb.net>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> * jwhardeman at gmail.com (Joseph Hardeman) [Sat 25 Apr 2009, 18:24 CEST]:
>
>> I am new to the list and new to configuring multiple internet providers.
>>
>> We are adding a second internet provider to our BI8000 and I am not able
>> to get the routing right. Everything wants to go out of the default
>> route. How do I need to configure the routing so that when I ping my
>> second providers IP on our interface it responds properly? We have
>> several IP ranges, including a /25 that is coming from the first
>> provider and we are adding additional /24's coming from our new provider
>> and I want to make sure I can route these back to the proper provider.
>>
>> I think I am missing something simple, but for the life of me I can't
>> quite catch it.
>>
>
> IP routing is done based solely on destination IP address. It looks
> like you're trying to multihome but not in the proper way (i.e., with
> your own ASN and IP space from an RIR, running eBGP with all your
> upstream providers). You'll have to investigate PBR to do what you
> want, it seems.
>
> Either that, or you use very confusing terminology on what you mean with
> "route back." Posting your config and/or a network diagram with actual
> numbers may help the list understand your situation better.
>
>
> -- Niels.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20090426/f4771b49/attachment.html>
More information about the foundry-nsp
mailing list