*Sent:* Tuesday, October 15, 2019 1:33 PM
*To:* af@af.afmug.com
*Subject:* Re: [AFMUG] asymmetric routing paths
Yeah a router only knows the next hop for a packet not the sequence of
hops it took to get where it is. Consequently if you pick any two
Internet connections and tracert the path in
New term for my vocabulary – LAN weenie.
From: AF On Behalf Of Adam Moffett
Sent: Tuesday, October 15, 2019 1:33 PM
To: af@af.afmug.com
Subject: Re: [AFMUG] asymmetric routing paths
Yeah a router only knows the next hop for a packet not the sequence of hops it
took to get where it is
Yeah a router only knows the next hop for a packet not the sequence of
hops it took to get where it is. Consequently if you pick any two
Internet connections and tracert the path in both directions there's a
very strong chance the path is asymmetric. It's normal and ok. Or in
other words, it'
Normally no issue, the interwebs is asymmetric as it was pointed out to me.
every time ive come across an issue i suspected was related to asymmetry it
ended up being something else, like MTU somewhere. We still have split
prefixes between providers and some on both. Moving the customer lo a
locked
On 10/15/19 10:54 AM, Ken Hohhof wrote:
I have cases where traffic to some customers comes in via upstream
provider A but the return traffic exits my network via upstream provider B.
What kind of problems if any can this cause?
Normal multihoming where you announce your prefixes to everyone
