I think ntop is right, sort of - if your multicast groups are remote, then ntop's correct. If not, well, your parameter setting sounds right.
Don't want to change the code - if we treated it as LOCAL, then it would be a problem as you couldn't force it non-local. This should be an FAQ entry. Please write it up and I'll add it. -----Burton > -----Original Message----- > From: pc [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 26, 2003 9:07 PM > To: [EMAIL PROTECTED] > Subject: Issues w/ ntop 2.2.93 <snip/> > multicast traffic considered remote> > > Multicast traffic is considered 'remote' traffic by ntop. Is this appropriate? I have locally added 224.0.0.0/8 to my --local-subnets and this workaround is effective for the moment. This is not a new issue either. _______________________________________________ Ntop-dev mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
