Patrick,
For web, you could try here http://checkip.dyndns.org. It will show
Linksys' WAN IP.
If you have a Linux box behind Linksys router, you could use the Python
script I noted previously. Just remark or comment out all the other stuff
such as updating Dyndns.org.
Or you could write a BASH script yourself. You need the following info for
your Linksys router.
Linksys_host=""
Linksys_user=""
Linksys_page="/Status.htm"
>From the Status.htm page, you could parse out the WAN interface. You could
use wget to get the file and just grep the info you wanted and then email
it to you. When everything works, add the script to the crontab.
I don't have a Linksys router to test.
Kai
On Thu, 26 Jul 2001, Grantham, Patrick wrote:
> Again I ask, how could I extract the IP from the linksys router? any ideas
>
> -----Original Message-----
> From: Kai Lien [mailto:kai@lenseco.com]
> Sent: Thursday, July 26, 2001 3:32 PM
> To: slug@nks.net
> Subject: Re: [SLUG] pine question
>
>
>
> Disclaimer: I do not work for www.dyndns.org and the latter do not pay me
> to promote its services.
>
> Based on my experience (almost a year) with dyndns.org, everything has
> been smooth except for the monthly reminder to update the account. That's
> the reason now I am using a Python script that will force an update after
> 25 days automatically. Since the new script, I have not had to manually
> update the account.
>
> I have talked to many people that had problems with
> www.dyndns.org. However, most are due to their update client software. For
> example, instead of checking every hour for IP changes and make updates
> when necessary, people are checking every minute and submit updates
> regardless of IP changes. If just one or two person is doing this, it
> would be okay. However, when there are 10 or more thousands of people
> doing this, it takes a significant hit on your system. To learn more about
> other users of this service, check out news.dyndns.org (news server).
>
> Yes, one can CNAME a fully qualified domain name to your dynamic hostname
> such as yourcompany.dyndns.org. I am using soa.granitecanyon.com as my
> free DNS server to provide this service.
>
>
> Kai
>
>
>
> On Thu, 26 Jul 2001, Ian C. Blenke wrote:
>
> > On Thu, Jul 26, 2001 at 12:09:01PM -0400, Kai Lien wrote:
> > >
> > > Www.dyndns.org wants
> > > some activity (such as an update) within 30 days. Otherwise, they will
> > > consider it an inactive account and drop you.
> >
> > I've had my fill of dyndns' crap. My RR IP rarely changes, and when it
> > does it changes more than once. I'm sick and tired of sending pleading
> > requests to the dyndns admins asking them to re-enable my "abusive"
> account
> > that was obviously DoSing their servers with a half dozen IP changes
> > too quickly.... *sigh*
> >
> > Try staticcling.org - it's free, and run by mahlon - the stinkymeat guy.
> ;)
> >
> > > With all that, you only have to remember your account name with
> > > www.dyndns.org. No more toying around with IP numbers.
> >
> > I go a step farther, and have a CNAME from my native domain point to
> > the dynamic DNS record:
> >
> > home.blenke.com CNAME blenke.staticcling.org
> >
> > Then I build everything around home.blenke.com.
> >
> > > If anyone is interested in the Python or Bash script, drop me an email.
> >
> > Dyndns has irritated me for the last time. I'm tired of feeling like a
> > child when dealing with their system. Update once, you're ok - but if
> > you update too often (or not often enough), they treat you as an
> > abuser or destroy your account. Trying to paste logic around updates
> > per their rules is far too irritating.
> >
> > There are other dynamic DNS places on there as well. Myip.org is too
> > flaky, and Dynip.com isn't free.
> >
> > If staticcling.org ever goes away I'll probably end up hacking
> > together my own scripting system to securely update my external
> > public DNS servers in-place as needed. Then home.blenke.com can
> > become an A record directly and all will be well.
> >
> > I've talked with mahlon though, and he's a good guy. I'll stick with
> > staticcling.org for the time being because of familiarity if nothing
> > else.
> >
> > I've yet to find a dynamic DNS update protocol that is properly
> > encrypted, however. Sending passwords in-the-clear is just wrong.
> >
> > - Ian C. Blenke <ian@blenke.com> <icblenke@nks.net>
> >
>
>
--Kai Lien
Lense Consulting Company www.lenseco.com
Fortune Cookie of the Day:
Of course power tools and alcohol don't mix. Everyone knows power tools aren't soluble in alcohol... -- Crazy Nigel
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 17:00:04 EDT