One more data point in this sea of uncertainty:
Still running OpenWRT 0.9 (White Russian) on my home LinkSys router.
I got the DynDNS hostname about to expire message today. Logging
in to the router, I found ez-ipupdate simply wasn't running. No idea
why. Uptime is 28 days. I started it
OK, I had assumed cable and DSL modems behaved the same. My DSL modem
has a static internal IP address, and transparently handles the
external dynamic address. The only way I've been able to detect
the external address from a script is to ssh to an external shell
account and then look at what
On 6/15/07, John Abreau [EMAIL PROTECTED] wrote:
On Fri, June 15, 2007 11:03 am, Thomas Charron said:
On 6/15/07, Stephen Ryan [EMAIL PROTECTED] wrote:
Actually, that gives the IP address of this machine, not the IP address
of the router ...
*Pt* White Russian runs on the router. :-)
On 6/14/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
After installing and configuring ez-ipupdate, all through the webif^2
UI, there WAS no /etc/ez-ipupdate/ez-ipupdate.conf on my filesystem.
FWIW, I just did an install of OpenWRT 0.9 and X-WRT on a friend's
LinkSys WRT54GS v1.1 router.
On 6/14/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Of course, logging into the DynDNS UI is an easy way to manage my
DynDNS entries. The whole point of installing OpenWRT/ez-ipupdate
(with which fact I opened my initial post on this subject) was to
avoid having to do this by automating the
We do have a page specifically for clients that are compliant to our
protocol. The UNIX specific client page is:
http://www.dyndns.com/support/clients/unix.html
I asked our client certification guy what he would recommend for OpenWRT
and he suggested the inadyn client.
--
Cole Tuininga
Date: Fri, 15 Jun 2007 08:42:28 -0400
From: Tom Buskey [EMAIL PROTECTED]
I've been using zonedit and a cronjob script to check if my router's IP
changed.
It's got some old cruft in it.
Please, please, please, folks! Don't even THINK about doing stuff
like this. (Newbies, cover your eyes!)
On Fri, 2007-06-15 at 11:03 -0400, Thomas Charron wrote:
On 6/15/07, Stephen Ryan [EMAIL PROTECTED] wrote:
Actually, that gives the IP address of this machine, not the IP address
of the router, which, given that it's IP address might change, is quite
likely doing address translation before
On 6/15/07, Thomas Charron [EMAIL PROTECTED] wrote:
On 6/15/07, Stephen Ryan [EMAIL PROTECTED] wrote:
Actually, that gives the IP address of this machine, not the IP address
of the router, which, given that it's IP address might change, is quite
likely doing address translation before
On 6/15/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Date: Fri, 15 Jun 2007 08:42:28 -0400
From: Tom Buskey [EMAIL PROTECTED]
I've been using zonedit and a cronjob script to check if my router's IP
changed.
It's got some old cruft in it.
Please, please, please, folks! Don't even THINK
(sorry, meant to send this to the list)
On Fri, 2007-06-15 at 10:35 -0400, [EMAIL PROTECTED] wrote:
Date: Fri, 15 Jun 2007 08:42:28 -0400
From: Tom Buskey [EMAIL PROTECTED]
I've been using zonedit and a cronjob script to check if my router's IP
changed.
It's got some old cruft in it.
On Fri, June 15, 2007 11:03 am, Thomas Charron said:
On 6/15/07, Stephen Ryan [EMAIL PROTECTED] wrote:
Actually, that gives the IP address of this machine, not the IP address
of the router, which, given that it's IP address might change, is quite
likely doing address translation before
FiOS uses another brand (Acctron?). It's got an IP to coax connector for
IPTV. Each TV set top box on coax has an IP address (192.168.1.100 and up)
Hm. Do you think it'd be possible to use this as a signal source for
a MythTV box? brain.gears[0].setMotion(new Motion.turning());
On 6/15/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
FiOS uses another brand (Acctron?). It's got an IP to coax connector
for
IPTV. Each TV set top box on coax has an IP address (192.168.1.100 and
up)
Hm. Do you think it'd be possible to use this as a signal source for
a MythTV box?
Date: Mon, 14 May 2007 18:49:07 -0400
From: Ben Scott [EMAIL PROTECTED]
On 5/14/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OpenWRT was recommended as a way of getting around using Linksys's
broken DynDNS client. But this system seems just as broken!
I suspect something *is*
On 6/14/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
The problem here seems to be that the ez-ipupdate package is
integrated with neither the webif nor the rest of OpenWRT.
Hmmm. It was better than that for me. Have you installed the X-WRT
extensions to OpenWRT? The webif^2 subsystem is
Date: Thu, 14 Jun 2007 16:05:37 -0400
From: Ben Scott [EMAIL PROTECTED]
On 6/14/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
The problem here seems to be that the ez-ipupdate package is
integrated with neither the webif nor the rest of OpenWRT.
Hmmm. It was better than that for me.
Per Ben's recommendation, after last month's SLUG talk on OpenWRT, I
upgraded my Linksys box to White Russian 0.9. I installed ez-ipupdate
and configured it with my DynDNS settings in webif^2 (the spiffy hot
rod web interface recommended by the same).
And... this morning, my DynDNS hosname
Date: Mon, 14 May 2007 09:22:02 -0400
From: [EMAIL PROTECTED]
Interestingly, the box reports the current time as its uptime:
# date; uptime
Mon May 14 09:18:51 EDT 2007
09:18:51 up 21:16, load average: 0.00, 0.00, 0.00
*blink* Duh. That IS the date. Too early for network emergencies.
[EMAIL PROTECTED] wrote:
# date; uptime
Mon May 14 09:18:51 EDT 2007
09:18:51 up 21:16, load average: 0.00, 0.00, 0.00
The system's uptime and date (which is synchronized with an NTP
server) appear identical - to the second. Could it be that this is
preventing the DynDNS daemon from
On 5/14/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
OpenWRT was recommended as a way of getting around using Linksys's
broken DynDNS client. But this system seems just as broken!
I suspect something *is* broken in the OpenWRT DDNS subsystem. But
I was able to get the symptom (i.e.,
On May 14, 2007, at 09:22, [EMAIL PROTECTED] wrote:
And... this morning, my DynDNS hosname expired. :(
I had the same problem on older versions of DD-WRT. Perhaps they
share a client.
The update logic was wrong there if your DHCP address didn't change
over the course of a month.
White
22 matches
Mail list logo
