SCOUG-HELP Mailing List Archives

<< Previous Message << >> Next Message >>

Date:	Sat, 5 Nov 2005 09:33:48 PST8
From:	"Steven Levine" <steve53@earthlink.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: DynDNS setup (was: please test my ftp server - MarkO)

In <436C880E.6E82@peterskye.com>, on 11/05/05
at 02:23 AM, Peter Skye said:

>I didn't think it was special. Did I say "special" somewhere?

You went into great detail about your router/firewall setup.

>I don't need a URL. All I have to do is ask the SMC Barricade. I've had
>a log running on it since 2004-Mar-31 -- want some of my old IP
>addresses?

No. I already have them.

>Getting my IP isn't a problem. I'm just looking for an easy way to post
>it to my DNS provider.

Which is what I provided.

> "... periodically checks whether the IP address stored by the DNS
>server
> is the real current address of the machine that is running INADYN."

For those reading along, this is normal processing for every capable
dyndns client.

>If the docs say "the real current address of the machine that is running
>INADYN" then it seems unlikely that it also checks somewhere else (such
>as an external firewall).

Keep reading (which you did). :-)

>but according to the docs up to that point these have to be running on
>the same machine as inadyn.

I don't read the docs this way.

> '--ip_server_name[:port] url': The client IP is detected by calling
>'url' from this 'ip_server_name:port'. Defaults to checkip.dyndns.org:80
>/.

This is how the useful dyndns clients have operated, ever since routers
and NAT became pervaisive.

>Obviously, then, the inadyn doc needs a fixup ('cause it's wrong!) and
>the "--ip_server_name" parameter *does* allow me to effectively put the
>current IP address on the command line. Exactly what I was looking for.

I recommend you discuss this with the developer
(http://inadyn.ina-tech.net/). I did not read the docs, as you did, but
others might.

>apparently isn't any keyword to identify it -- I guess if inadyn can't
>figure out what a parameter is then it assumes it is an IP server.
>Mighty abnormal way of having someone specify a parameter.

Rather than guessing, look at the source code. Inadyn is a GPL app.

>I do see that the inadyn logging does not work on OS/2. It says so in
>the docs (see the --syslog parameter).

I think you are assuming things again. The docs you are quoting are
unchanged from the the orginal sources. So, to me, they apply only to the
unix, windows and mac versions. The docs says nothing about what an
ecs-os/2 port may or may not do. Makefile.os2 clearly links to syslog.lib
and the defined architecture is linux, so I would expect the os/2 binary
to try to use syslog. I'd say the odds are pretty good that syslog
support will work on os/2.

Steven

--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.67 #10183 Warp4.something/14.100c_W4
www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
----------------------------------------------------------------------

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"postmaster@scoug.com".

=====================================================

Return to [ 05 | November | 2005 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.