Mornin'!

I totally agree with you there. I suspect that Askey don't tend to put a lot
of R&D into their products, ie they just incorporate features straight off
the RFCs, test them and then write horribly incomplete manuals! :-)

Thanks to everyone concerned, I now have working SNMP on my RTA210. What I
was missing was simply the 'ip' command before 'snmp access'... But it
wasn't my fault - nobody copied and pasted the 'ip' command into their
postings! *ahem Jared and Michael :-)* SNMP was of course enabled on the
RTA210 but interestingly enough there was no read community string set and
the write community string was set to the admin password I recently set on
the web interface - thus a community string of public or private wouldn't
work.

Steve

-----Original Message-----
From: owner-adsl@unixathome.org [mailto:owner-adsl@unixathome.org]On
Behalf Of Zsolt Brandt
Sent: Friday, 5 July 2002 11:32 p.m.
To: adsl@lists.unixathome.org
Subject: SNMP access on RTA020

hi there. to double check my security setup on my rta020 i had a friend
of mine do a thorough port scan via his Linux setup, and yes, mapping
port 161 to a non existant port does indeed fix the issue. just like
http and telnet. why oh why they dont make these things shut by default
is beyond me. the average user has no idea how vulnerable they are.
cheers, Zsolt

--
This message is part of the NZ ADSL mailing list.
see http://unixathome.org/adsl/ for archives, FAQ,
and various documents.
To unsubscribe: send mail to majordomo@lists.unixathome.org
with "unsubscribe adsl" in the body of the message
-- 
This message is part of the NZ ADSL mailing list. 
see http://unixathome.org/adsl/ for archives, FAQ, 
and various documents. 
To unsubscribe: send mail to majordomo@lists.unixathome.org 
with "unsubscribe adsl" in the body of the message