ons 2010-06-09 klockan 20:51 -0500 skrev Luis Daniel Lucio Quiroz: > So i understand by now > it is kind imposible to do a > > cache_peer 10.200.0.0 sibling 3128 3130 multicast-responder > nor > cache_peer 10.200.255.255 sibling 3128 3130 multicast-responder Correct. But as Amos said it should be possible with some coding to support a multicast cache_peer template with an attached acl defining valid responders. Or alternatively you can just preconfigure a bunch of multicast peers for each IP that may be used. These are not used unless there is a response from that IP in response to the multicast query. Regards Henrik
