Single carrier multi-circuit asynchronous routing issue
aaron.millisor at bright.net
Tue Jan 20 18:21:32 UTC 2009
Thank you both. Strict mode uRPF was indeed the problem. Took awhile for
them to fix it for me, but at least it's fixed.
Anders Lindbäck wrote:
> On 7 jan 2009, at 21.05, Niels Bakker wrote:
>> * aaron.millisor at bright.net (Aaron Millisor) [Wed 07 Jan 2009, 20:53
>>> If I were to prepend the network 126.96.36.199 to come in on 'sprint 1',
>>> but have a route to 188.8.131.52 via 'sprint 2' so that traffic comes in
>>> on one circuit but returns on the other, routing is broken. If I
>>> change my route so that packets directed to 184.108.40.206 return on the
>>> same circuit that the traffic is received on, everything works fine.
>> You might be running into uRPF (unicast reverse path forward
>> -- Niels.
> Strict-mode uRPF will couse this, I am sure sprint support can help you
> with it..
> Anders Lindbäck
> anders.lindback at dnz.se
More information about the NANOG