|
Posted by Bill M. on September 28, 2006, 12:26 am
If you were Registered and logged in, you could reply and use other advanced thread options
On Wed, 27 Sep 2006 10:55:42 GMT, VAXman- @SendSpamHere.ORG wrote:
>>
>>
>>On Tue, 26 Sep 2006 01:00:53 GMT, VAXman- @SendSpamHere.ORG wrote:
>>
>>>>
>>>>Actually, I thought Elmo's suggestion was the simpler one to
>>>>implement. Your initial question implies that you want to know your
>>>>public (WAN) IP address. You can get that from the router, as you
>>>>know, but doing so requires a login/password. You can also do it via
>>>>any of a handful of Internet web sites, and in that case no login is
>>>>required. It's your choice, but the "no login" option seems a bit
>>>>easier in case you've never scripted anything before. If you do have
>>>>that experience or are willing to learn a bit, then either way will
>>>>work equally well.
>>>
>>>I get mine via a simple snmp command:
>>>
>>>$ snmp_request 192.168.2.1 public getnext 1.3.6.1.2.1.4.20.1.1
>>>1.3.6.1.2.1.4.20.1.1.ww.xx.xx.zz = ww.xx.yy.zz
>>
>>Many of us, (me anyway), don't run SNMP at home. I get enough of that
>>crap at work. :)
>
>The question was how to get the address. Whether or not you think SNMP
>is crap is irrelevant. SNMP has been incorporated into most networking
>equipment -- crap or otherwise -- and is a useful way to obtain statis-
>tics and information from the device.
Humor impaired, eh? I know exactly what SNMP is, how to use it, and
what I can do with it. Since I have to deal with it at work and it's
generally unpleasant for me, mostly because of who I have to work with
to get anything done, I choose not to work with it at home. Better?
I still say many of us don't mess with SNMP at home. Maybe we should
just leave it at that.
--
Bill
|