Skip to Content.
Sympa Menu

wg-multicast - Windows multicast route metric

Subject: All things related to multicast

List archive

Windows multicast route metric


Chronological Thread 
  • From: "Julian Y. Koh" <>
  • To:
  • Subject: Windows multicast route metric
  • Date: Tue, 29 Jan 2008 18:10:31 -0600

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Question for the group: how does Windows decide what metric to assign to
its multicast route 224.0.0.0/240.0.0.0 in its routing table?

The reason I ask is that all the computers I've seen on our network have a
metric of 20. When people connect to our Juniper SSL VPN appliance with
the Network Connect full tunnel client, the Network Connect client enters
another 224.0.0.0/4 route with a metric of 10 pointing at the SSL VPN
adapter, which overrides the metric of 20, thus killing the ability of the
client to receive multicast on our network (since we don't deliver
multicast via our VPNs).

Juniper is telling me that all of their Windows machines have a metric of
10 for their multicast routes. And indeed, when I did a fresh install of
XP SP2 in VMWare, it ends up with metric 10 on the multicast route. And
when I boot with Boot Camp on my MacBook Pro using that same Windows
installation, it has a metric 10 multicast route.

Totally wacky, and Google is not helping me out today.

Thanks in advance for any assistance! Let me know if you need more info.


-----BEGIN PGP SIGNATURE-----
Version: 9.7.0.1012

wj8DBQFHn8B2DlQHnMkeAWMRAmR3AJ9GLy13ef693y9lV2SPkWiPGTk+WQCgqq1i
EOEOUuAPjjYxJ1YLDEnj/g4=
=fPAY
-----END PGP SIGNATURE-----

--
Julian Y. Koh
<mailto:>
Network Engineer <phone:847-467-5780>
Telecommunications and Network Services Northwestern University
PGP Public Key:<http://bt.ittns.northwestern.edu/julian/pgppubkey.html>



Archive powered by MHonArc 2.6.16.

Top of Page