[f-nsp] Asymmetrical routing on ADX

Drew Weaver drew.weaver at thenap.com
Sat Jun 2 10:16:22 EDT 2012


That's exactly my stance on this issue.

It's especially annoying considering that the two physical ports in question are attached to a VLAN/Virtual Ethernet, I don't understand why it matters which physical interface in the VLAN handles the traffic destined for the VE..

To me that is really broken.

Thanks,
-Drew


-----Original Message-----
From: foundry-nsp-bounces at puck.nether.net [mailto:foundry-nsp-bounces at puck.nether.net] On Behalf Of jeffm at iglou.com
Sent: Friday, June 01, 2012 3:08 PM
To: foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] Asymmetrical routing on ADX

On Fri, June 1, 2012 12:25, Drew Weaver wrote:
> Why is asymmetrical routing bad if you have a complete mesh?

It isn't (even without a complete mesh).

Asymmetric routing is commonplace and normal, if you need a chokepoint to apply some sort of network policy (load balancing, firewalling, etc.) you need to make sure that you make it a chokepoint both coming and going, and if gear can't handle the next-hop (or even the interface that it uses) may be different for transmitted and received traffic, then bug reports need to be filed.


--
Jeff

_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp




More information about the foundry-nsp mailing list