On 03/08/2012 11:42 PM, Livingood, Jason wrote:
>
> I think that E2E into the home for SNMP is perhaps one of the
> things that would motivate an ISP to support homenet.
>
>
> E2E network management and/or monitoring, yes. SNMP, at least on a
> public interface, maybe not so much. We may be entering a phase where
> ISPs consider blocking TCP/UDP 161.
>
> The reason is that SNMP is becoming more and more widely abused. I
> still have no idea why for example (1) some gear ships with public as
> the default string and the daemon running by default as such, (2) some
> gear does not present the user with an interface to turn off SNMP or
> change the community string at all (so you may be stuck with on/public).
>
> So maybe on SNMP, tread carefully. ;-)
>
Just to make it clear, I was worrying about the possible use of
multicast to *discover* SNMP devices, and routing versus bridging where
the multicast packet might need forwarding to other networks in the
hime, not SNMP in general. I had noted its possible use to *discover*
printers to initially configure them.
- Jim
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
