Home Networking

286 readers

1 users here now

A community to help people learn, install, set up or troubleshoot their home network equipment and solutions.

Rules

Please stay on topic.
Please use the search function to look for keywords related to what you want to ask before posting since most common issues have been answered.
No Ads. This community is for support and discussion. Ads and self promotion are not welcome here.
No product reviews or announcements. If you have a question about a product, be specific about what you want to know.
Be civil. Don't be a jerk. Not being a jerk is surprisingly easy.
No URL shorteners. URL shorteners tend to hide the real use of a link. For this reason, please use normal links, even if they're long.
No affiliate links.
No gatekeeping. With profession shall come professionalism. Extend help without judging others for their ignorance. The same goes for downvoting of comments or posts for "stupid questions" or not being as knowledgeable as others.

founded 1 year ago

MODERATORS

[email protected]

Microsoft Teams and their seemingly bizarre routing (self.homenetworking)

submitted 3 weeks ago by NotAnArdvark to c/[email protected]

3 comments fedilink hide all child comments

Purely a curiosity on my part... But has anyone ever looked at how their Microsoft Teams calls get routed? During Teams calls I'll check OpenWrt to see the endpoint IP I'm sending all my traffic to, then do a traceroute to that IP. So far, I think, it's always been a bizarre path.

For instance, today:

$ tracepath 52.115.76.111
 1?: [LOCALHOST]                      pmtu 1500
 1:  OpenWrt.lan                                           1.200ms 
 1:  OpenWrt.lan                                           1.511ms 
 2:  ...                              15.008ms 
 3:  ...                            18.429ms asymm  4 
 4:  ...                            22.477ms asymm  5 
 5:  six2.microsoft.com                                   39.117ms asymm  6 
 6:  ae32-0.icr02.mwh01.ntwk.msn.net                      40.610ms 
 7:  be-162-0.ibr04.mwh01.ntwk.msn.net                   190.062ms asymm 15 
 8:  be-2-0.ibr04.fra30.ntwk.msn.net                      78.997ms asymm 12 
 9:  be-8-0.ibr02.dsm05.ntwk.msn.net                      77.944ms asymm 12 
10:  51.10.19.124                                         78.474ms asymm 11 
11:  104.44.54.110                                        75.460ms asymm 10 
12:  no reply
^C

I think that:

mwh01 = Moses Lake, WA
fra30 = Frankfurt
dsm05 = Des Moines, Iowa
ibr04 = ??

Assuming I'm right on those names - and the hostnames can be trusted - what a strange way to route traffic...

Most the time when I check these Teams IPs I'm just routing through Southern states before being sent back to the Eastern US, but today's was weird enough I thought I should ask if anyone else ever looks at these things.

top 3 comments

sorted by: hot top controversial new old

[–] [email protected] 1 points 3 weeks ago (1 children)

Were you talking with anyone in Europe, by any chance?

[–] NotAnArdvark 2 points 3 weeks ago (1 children)

No, all within the province. I thought... that would be a funny way to out someone who is "working from home" in Europe.

[–] [email protected] 1 points 3 weeks ago

Yeah, that would be a possibility.

Another thing could be that some of packets are routed out of the optimal path to avoid getting "stuck" in some local maxima? Just a guess, it's been a while since I played with routing tables.