With average, consumer-level, LAN equipment Walter is correct. Merely setting up a VLAN won't work, assuming your PC wants to still see the rest of the world through the same NIC it is using to see the ANAN. And, as he says, the gold standard is a separate NIC dedicated only to the ANAN. Read more about this here:
https://community.apache-labs.com/viewtopic.php?f=22&t=4127But...
It seems you are using a managed switch. If the switch supports
IGMP snooping, and if the Telus router and any downstream MoCA devices also support IGMP, then activating IGMP snooping on the switch might help keep any undesired UDP multicast packets off of the PC and ANAN switch ports. If that doesn't work or isn't possible then your best bet remains as another NIC in the PC and a dedicated connection.
The following is TLDR for network geeks only
If you use pro-level LAN equipment like I do, you can
define a VLAN in the router and the switch and thereby keep unwanted UDP multicast traffic limited to the switch ports where it needs to go. For instance, I have IPTV service through my provider. They provide a very nice router, but I kicked that to the curb and provisioned all Ubiquiti equipment here, routers and switches. In the router I've got UDP multicast packets blocked from the default (and guest) VLANs and routed onto a dedicated IPTV VLAN. With an IPTV VLAN setup in my switches that traffic goes only to the IPTV set-top boxes. Sure, it's on the router and switch backplanes, but there is plenty of bandwidth there. This has the additional benefit of security against unwanted IoT-style cyber-intrusions via the set-top boxes.
I've had to have the provider come out a couple of times to fix stuff on their side of the demark. Both times they were flabbergasted. "You can't do that, it's impossible, you HAVE to use our router!". Nope, sorry, don't need to, don't want to, look here, it actually does work
)
