Re: Does the White Russian 0.9 DynDNS client suck just as much?
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 manually
("/etc/init.d/S52ez-ipupdate start"), then logged in to the DynDNS web
UI, and it showed it as updated just now. Alas, I didn't think to
check the web UI for the last update time before starting ez-ipupdate.
But one more thing to look for.
-- Ben
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
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 address I came from. On Sun, June 17, 2007 1:10 pm, Ben Scott said: > 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. :-) >> >> Actually, the "router" to the ISP is the cable or DHL modem, >> not the wrt54g. > > Actually, the WRT54G is normally a router, and likely *the* router. > All the cable modems I've seen have been strictly layer two > devices[1], performing no IP routing functions. "Classic" DSL modems > were the same way. Both bridged Ethernet frames on to the WAN, and IP > level stuff didn't happen until you got to the DSLAM/CMTS at the > CO/headend. This is changing somewhat with DSL; the CPE Verizon has > been providing for the past few years can also act as a NAT router. I > expect the cable industry will get there eventually, too. > > (DSLAM = DSL Access Multiplexer; CMTS = Cable Modem Termination > System: The equipment at the "other end" of your local pipe. CO = > Central Office; Headend = not an acronym (we're not sure how that > happened): The place said equipment is housed. CPE = Customer > Premises Equipment.) > > [1] Well, they often have the ability to be assigned an IP address for > management purposes, but that is as an end-node, not a gateway. > > -- Ben > ___ > gnhlug-discuss mailing list > gnhlug-discuss@mail.gnhlug.org > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > -- John Abreau / Executive Director, Boston Linux & Unix IM: [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] Email [EMAIL PROTECTED] / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
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. This was the first time non-LinkSys firmware had touched this unit. Given the trouble people have been having, I kept a close watch on things. Here's what I saw: 1. Initially, there was nothing for ez-ipupdate. 2. Once the ez-ipupdate package was installed, an /etc/ez-ipupdate.conf file was created with generic values, and an empty /etc/ez-ipupdate/ directory was created. 3. Once I entered stuff into the web UI under "DynDNS", an /etc/ez-ipupdate/ez-ipupdate.conf file was created and populated with correct values, as follows (names and IPs changed to protect the innocent): service-type=dyndns user=username:password host=hostname.dyndns.org max-interval=86400 I note that there is no "interface=" line in the above, same as with mine. The interface is apparently intended to come from the initscript. 4. For my friend, it appeared to work fine right off, apparently getting the interface from the initscript in his case. Relevant log entries: ez-ipupdate[15904]: version 3.0.11b8, interface ppp0, host hostname.dyndns.org, server members.dyndns.org, service dyndns ez-ipupdate[15904]: members.dyndns.org says that your IP address has not changed since the last update ez-ipupdate[15904]: successful update for ppp0->192.0.2.42 (hostname.dyndns.org) Note the interface is "ppp0" (this guy is using Verizon DSL with PPPoE). I don't know why the web UI didn't create a file for you (VirginSnow). I just know it did for me and him. I also don't know why it didn't work for me until I added an "interface=" line, but it worked for him without changes. Clearly, there is some inconsistent behavior here, which is a problem in and of itself. > Update shmupdate. When running ez-ipupdate in the foreground, it told > me that "members.dyndns.org says that your IP address has not changed > since the last update". Had your IP address changed since the last update? In other words, does your DynDNS hostname's address record match your current IP address? If it's the same, that would be a correct diagnostic. It may well be that the protocol being used only allows responses of "Update accepted", "Update failed", or "Update not needed". If so, ez-ipupdate has done all it can. What DynDNS does on the "Update not needed" case would be up to DynDNS. Presumably, they refresh your registration. This is pure speculation on my part, of course. > That begs the questions, WTF is an "update", > did I just do one, and is what I just did what DynDNS requires once > every month? I'm not really sure of the technical details. The general idea is that ez-ipupdate checks in with the DynDNS servers once a day, or when your IP address changes, whichever comes first. The "once a day" part is to refresh your registration, so that DynDNS doesn't expire it. (They want to keep abandoned accounts from cluttering their database.) As long as ez-ipupdate is checking in with the server and getting a response, I believe you are good. It's error messages from ez-ipupdate about not being able to determine the interface or IP address, or not being able to submit the update, that are cause for concern. >>> However, when you *think* you've >>> gotten DynDNS configured but really *haven't*, your hostname is just >>> as expired! >> >> Check the DynDNS web UI for your domain name. It should indicate >> the date of the last update. I know mine does. > > Of course, logging into the DynDNS UI is an easy way to manage my > DynDNS entries. The whole point of installing OpenWRT/ez-ipupdate ... And the whole point of logging in to the DynDNS web UI is to see if ez-ipupdate has successfully refreshed your registration with DynDNS, which is what you were asking about. Are you being obtuse on purpose? -- Ben ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
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. :-) > > Actually, the "router" to the ISP is the cable or DHL modem, > not the wrt54g. Actually, the WRT54G is normally a router, and likely *the* router. All the cable modems I've seen have been strictly layer two devices[1], performing no IP routing functions. "Classic" DSL modems were the same way. Both bridged Ethernet frames on to the WAN, and IP level stuff didn't happen until you got to the DSLAM/CMTS at the CO/headend. This is changing somewhat with DSL; the CPE Verizon has been providing for the past few years can also act as a NAT router. I expect the cable industry will get there eventually, too. (DSLAM = DSL Access Multiplexer; CMTS = Cable Modem Termination System: The equipment at the "other end" of your local pipe. CO = Central Office; Headend = not an acronym (we're not sure how that happened): The place said equipment is housed. CPE = Customer Premises Equipment.) [1] Well, they often have the ability to be assigned an IP address for management purposes, but that is as an end-node, not a gateway. -- Ben ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: FiOS and MythTV? WAS: Re: Does the White Russian 0.9 DynDNS client suck just as much?
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? brain.gears[0].setMotion(new Motion.turning()); I've thought about that too. There is a standard for what FiOS is doing (I think it's IPTV) and the coax IP connection in the router is touted in sales materials. However, beyond a ping, I haven't been able to get a response from the set top boxes. I'd probably have to sniff the coax to see anything. Frankly, I don't want expend effort that might void my contract :-) ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
FiOS and MythTV? WAS: Re: Does the White Russian 0.9 DynDNS client suck just as much?
> 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()); ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
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 hitting the public internet. In >> the case of my home network, running through some cheap consumer-grade >> Netgear job, the only way to find out the public IP address is to scrape >> some web page, and whatismyip.com is probably the easiest one to get at. >> It's certainly easier than getting the password-protected front page the >> router serves up! > > *Pt* White Russian runs on the router. :-) > > -- > -- Thomas Actually, the "router" to the ISP is the cable or DHL modem, not the wrt54g. -- John Abreau / Executive Director, Boston Linux & Unix IM: [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] Email [EMAIL PROTECTED] / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
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 hitting the public internet. In > the case of my home network, running through some cheap consumer-grade > Netgear job, the only way to find out the public IP address is to scrape > some web page, and whatismyip.com is probably the easiest one to get at. > It's certainly easier than getting the password-protected front page the > router serves up! *Pt* White Russian runs on the router. :-) 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) ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
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 about doing stuff
like this. (Newbies, cover your eyes!)
There is a reason for doing this way. I'm open to suggestions. Read on.
# What's my IP?
> lynx -dump -accept_all_cookies http://www.whatismyip.com | egrep
'[0-9]' |
Most DHCP clients will store the current IP in some kind of
lease/cache file. DHCP lease files are usually pretty easy to parse.
But, if you really must get your IP address the hard way, you could
use something with fewer teeth than scraping www.whatismyip.com:
# ifconfig "`route | grep default | awk '{print $8}'`" | \
grep inet | awk '{print $2}' | cut -d : -f 2
If I do that on my linux box it'll *always* say 192.168.1.35 because it's
behind my FiOS router that I can't login to. I don't have direct access to
the IP that FiOS gives the router via IP. So, I go to a web site that tells
me what IP is on the other side of the NAT. I'd love to have a better
solution that works.
The lease files can be parse, but the ISC DHCP server docs say they will not
stay the same so don't parse them. Of course you can say the same about the
Linux API which changes all the time. If it works, use it & fix it when it
doesn't.
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
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 hitting the public internet. In > > the case of my home network, running through some cheap consumer-grade > > Netgear job, the only way to find out the public IP address is to scrape > > some web page, and whatismyip.com is probably the easiest one to get at. > > It's certainly easier than getting the password-protected front page the > > router serves up! > > *Pt* White Russian runs on the router. :-) > :-) ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
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 hitting the public internet. In > the case of my home network, running through some cheap consumer-grade > Netgear job, the only way to find out the public IP address is to scrape > some web page, and whatismyip.com is probably the easiest one to get at. > It's certainly easier than getting the password-protected front page the > router serves up! *Pt* White Russian runs on the router. :-) -- -- Thomas ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
(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.
>
> Please, please, please, folks! Don't even THINK about doing stuff
> like this. (Newbies, cover your eyes!)
>
> > # What's my IP?
> > lynx -dump -accept_all_cookies http://www.whatismyip.com | egrep '[0-9]' |
>
> Most DHCP clients will store the current IP in some kind of
> lease/cache file. DHCP lease files are usually pretty easy to parse.
> But, if you really must get your IP address the hard way, you could
> use something with fewer teeth than scraping www.whatismyip.com:
>
> # ifconfig "`route | grep default | awk '{print $8}'`" | \
> grep inet | awk '{print $2}' | cut -d : -f 2
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 hitting the public internet. In
the case of my home network, running through some cheap consumer-grade
Netgear job, the only way to find out the public IP address is to scrape
some web page, and whatismyip.com is probably the easiest one to get at.
It's certainly easier than getting the password-protected front page the
router serves up!
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
> 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!)
> # What's my IP?
> lynx -dump -accept_all_cookies http://www.whatismyip.com | egrep '[0-9]' |
Most DHCP clients will store the current IP in some kind of
lease/cache file. DHCP lease files are usually pretty easy to parse.
But, if you really must get your IP address the hard way, you could
use something with fewer teeth than scraping www.whatismyip.com:
# ifconfig "`route | grep default | awk '{print $8}'`" | \
grep inet | awk '{print $2}' | cut -d : -f 2
Many DHCP clients can also be told to run a certain command whenever
the IP address changes. On White Russian 0.9, if the file
/etc/udhcpc.user exists, udhcpc will run it whenever it acquires a new
IP address. (In this script, the new IP address is passed as the
value of $ip.)
In this sense, DynDNS clients such as ez-ipupdate can be said to be
misimplemented. ez-ipupdate, for example, uses polling to check if
the specified interface's IP address has changed. The "proper" way to
perform this check would be to include a call to ez-ipupdate in the
script run by the DHCP client. That way, ez-ipupdate would receive
notice of IP changes as soon as they occured, and wouldn't have to
keep checking to see if the address has changed. (This makes me
wonder if I shouldn't be running ez-ipupdate in -d daemon mode.)
But, all aside, arcane hacks do make interesting reading for
nerd-infested mailing lists. :^)
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
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 <[EMAIL PROTECTED]> http://www.code-energy.com/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
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 update process!
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.
#!/bin/sh
# What's my host-ip?
dig @ns15.zoneedit.com $HOST. | grep "^$HOST" | awk
'{print $NF}' > /tmp/zonedit.dig
# What's my IP?
lynx -dump -accept_all_cookies http://www.whatismyip.com | egrep '[0-9]' |
egre
p -iv 'page.|Lines|http:|explained|Anywher|guard|WhatIsMyIP.com' | awk
'{print $
NF}' > /tmp/zonedit.ip
#lynx -source http://www.dnsstuff.com/ | grep 'Your IP' | cut -d' ' -f3 | tr
-d
'[A-z> /tmp/zonedit.ip
# compare them
diff /tmp/zonedit.dig /tmp/zonedit.ip > /tmp/zonedit.mail
if [ $? -eq 0 ]
then
# no update needed
exit 0
fi
# mail status!
echo "dig" >> /tmp/zonedit.mail
cat /tmp/zonedit.dig >> /tmp/zonedit.mail
echo "ip" >> /tmp/zonedit.mail
cat /tmp/zonedit.ip >> /tmp/zonedit.mail
# need to update
#lynx -source -auth=$user:$password "
http://dynamic.zoneedit.com/auth/dynamic.h
tml?host=$HOST" > /tmp/zoneedit
wget -O - --http-user=$user--http-passwd=$password "
http://dynamic.zoneedit.co
m/auth/dynamic.html?host=$HOST"
cat /tmp/zoneedit >> /tmp/zonedit.mail
mail -s 'dd-zonedit' [EMAIL PROTECTED] < /tmp/zonedit.mail
rm /tmp/zonedit.mail
___
gnhlug-discuss mailing list
gnhlug-discuss@mail.gnhlug.org
http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
> 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. Have you installed the X-WRT > extensions to OpenWRT? The webif^2 subsystem is a big improvement, to > the point where I didn't use plain OpenWRT much. With X-WRT, I was Yes, I followed pretty close to exactly the instructions you gave in your OpenWRT talk. > > Note that the settings on the DynDNS page of the webif DON"T ACTUALLY > > CONFIGURE ez-ipupdate! Only the Enable/Disable switch on that page > > has any effect on real life events. All the other settings (service > > type, account name, password, hostname, update interval) just hang out > > in nvram and are never actually used! > > Interesting. I'm pretty sure mine did *something* to the config > file. My conclusion was that it just didn't do enough. After installing and configuring ez-ipupdate, all through the webif^2 UI, there WAS no /etc/ez-ipupdate/ez-ipupdate.conf on my filesystem. I had to read the /etc/init.d/S52ez-ipupdate in order to find out that it was using /etc/ez-ipupdate/ez-ipupdate.conf rather than /etc/ez-ipupdate.conf. > > Even there, the information supplied is extremely limited! > > Yah. ez-ipupdate does indicate in the log when it has sent a DNS > update, though. So you can at least find out if it *thinks* it's > doing something. Update shmupdate. When running ez-ipupdate in the foreground, it told me that "members.dyndns.org says that your IP address has not changed since the last update". That begs the questions, WTF is an "update", did I just do one, and is what I just did what DynDNS requires once every month? Is an "update" when the IP is reported, when a new IP is reported, or when the IP is just checked and determined to be the same? Without debugging output, it's impossible to tell what this obnoxiously terse and cryptic output really means. (Yes, I know of another, non-Linux, operating system which does this too.) > Check the DynDNS web UI for your domain name. It should indicate > the date of the last update. I know mine does. 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 update process! When I first pulled up the DynDNS webif page, it gave me the option of installing one of two different dyndns clients. Maybe next time, I'll try the other one and see if it works any better. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
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 a big improvement, to the point where I didn't use plain OpenWRT much. With X-WRT, I was able to find a Dynamic DNS UI area, install the package from there, and configure it from there. I also found initscripts and such which were attempting to the control ez-ipupdate program. Obviously, something still wasn't working, but it *was* doing *something*. > When the ez-ipupdate package is installed, it installs the config file as > /etc/ez-ipupdate.conf. I just checked, and I do have an /etc/ez-ipupdate.conf file on my home router. But it's stale and looks completely stock. I suspect it's just being ignored. > You have to create you own /etc/ez-ipupdate/ez-ipupdate.conf file ... Mine was already created, although I did add to it. > Note that the settings on the DynDNS page of the webif DON"T ACTUALLY > CONFIGURE ez-ipupdate! Only the Enable/Disable switch on that page > has any effect on real life events. All the other settings (service > type, account name, password, hostname, update interval) just hang out > in nvram and are never actually used! Interesting. I'm pretty sure mine did *something* to the config file. My conclusion was that it just didn't do enough. > ez-ipupdate (though it offers a -q "quiet" switch) doesn't offer > any kind of debugging output. FWIW, there is a foreground mode, but I found it still didn't give any useful information. > But, by default on OpenWRT, does not syslog to /var/log/messages > (or any file under /var/log!). It's a flash ROM filesystem. Flash has a limited number of write cycles. Writing logs to a flash filesystem will eventually result in a dead part, sometimes rather quickly. That's why it doesn't do that. I suggest using syslog's network logging feature to send the messages to a "real" computer (with a hard disk). > Even there, the information supplied is extremely limited! Yah. ez-ipupdate does indicate in the log when it has sent a DNS update, though. So you can at least find out if it *thinks* it's doing something. > So, without access to any debugging output, I'm not even sure if what > I've done will convince ez-ipupdate to update my DynDNS on schedule. Check the DynDNS web UI for your domain name. It should indicate the date of the last update. I know mine does. > I suspect that OpenWRT automagically rebooted me (without notice) > after $arbitrary_configuration_change. OpenWRT seems to like doing > that. With X-WRT (again, I didn't stick with plain OpenWRT much), I found that it usually didn't reboot after a config change. But it may be you're just changing different things than I was. X-WRT also offered a multi-level Save/Review/Commit/Reject system for config changes, so you could see what it was going to do, and batch things together, so you at least get a single reboot. -- Ben ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
> 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* broken in the OpenWRT DDNS subsystem. But > I was able to get the symptom (i.e., DynDNS warning about my expiring > DNS entry) to go away by fiddling with it. I've been too lazy/busy to > dig into root cause yet. I wasn't sure if the problem wasn't just me > until now. I guess it's not just me. > > Anyway, here's what I did. I logged into a root shell on the > LinkSys box. I edited/created the /etc/ez-ipupdate/ez-ipupdate.conf > file to look like this: > > interface=vlan1 > service-type=dyndns > user=notmyusername:notmypassword > pid-file=/var/run/ez-ipupdate.pid > cache-file=/etc/ez-ipupdate/ez-ipupdate.cache > host=notmyhostname.dnsalias.org The problem here seems to be that the ez-ipupdate package is integrated with neither the webif nor the rest of OpenWRT. When the ez-ipupdate package is installed, it installs the config file as /etc/ez-ipupdate.conf. The contents of the file in no way reflect the settings in the webif, and the cache-file setting at the bottom conflicts with where OpenWRT stores the cache file. This is ironic (you might say insidiously misleading) because this setting is in the section of the file labeled "Do not change the lines below". Just rm the whole friggin file: rm /etc/ez-ipupdate.conf. You have to create you own /etc/ez-ipupdate/ez-ipupdate.conf file using the output from: # ez-ipupdate --help # command usage help # echo help | ez-ipupdate -c -# config file help Looking at /etc/init.d/S52ez-ipupdate, it looks like putting the following in /etc/ez-ipupdate/ez-ipupdate.conf should suffice: interface=vlan1 service-type=dyndns user=notmyusername:notmypassword host=notmyhostname.dnsalias.org max-interval=216 Creating this file and manually executing # /etc/init.d/S52ez-ipupdate start at least causes messages concerning successful update to appear in the system log and webif DynDNS configuration page. Note that the settings on the DynDNS page of the webif DON"T ACTUALLY CONFIGURE ez-ipupdate! Only the Enable/Disable switch on that page has any effect on real life events. All the other settings (service type, account name, password, hostname, update interval) just hang out in nvram and are never actually used! Configuring ez-ipupdate on OpenWRT's White Russian 0.9 is about as counterintuitive as it could be. ez-ipupdate (though it offers a -q "quiet" switch) doesn't offer any kind of debugging output. It does write limited satus information to the syslog. But, by default on OpenWRT, does not syslog to /var/log/messages (or any file under /var/log!). Instead, to see the syslog, you have to view the appropriate page on the webif. Even there, the information supplied is extremely limited! So, without access to any debugging output, I'm not even sure if what I've done will convince ez-ipupdate to update my DynDNS on schedule. I gues I'll find out in 5 days. :) > > # date; uptime > > Mon May 14 09:18:51 EDT 2007 > > 09:18:51 up 21:16, load average: 0.00, 0.00, 0.00 > > > > I didn't reboot the box at all yesterday, so the 21:16 is wrong nonetheless. > > I suspect the uptime is correct, and the box has only been up for 21 > hours. The real question is: Why did the box reboot? The nominal I suspect that OpenWRT automagically rebooted me (without notice) after $arbitrary_configuration_change. OpenWRT seems to like doing that. > On a mostly unrelated note, DynDNS emails me when my hostname is > about to expire, so I've never lost the name due to any issues with > LinkSys's firmware, OpenWRT's firmware, or anything else. I've always > had a chance to tweak things first. You may want to look into getting > the same email warning for yourself. Yeah, I get that warning also. However, when you *think* you've gotten DynDNS configured but really *haven't*, your hostname is just as expired! It would be nice if they mailed such warnings a couple more times, i.e. daily. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
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 Russian is pretty old stuff, perhaps you need to update the package? -Bill - Bill McGonigle, Owner Work: 603.448.4440 BFC Computing, LLC Home: 603.448.1668 [EMAIL PROTECTED] Cell: 603.252.2606 http://www.bfccomputing.com/Page: 603.442.1833 Blog: http://blog.bfccomputing.com/ VCard: http://bfccomputing.com/vcard/bill.vcf ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
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., DynDNS warning about my expiring DNS entry) to go away by fiddling with it. I've been too lazy/busy to dig into root cause yet. I wasn't sure if the problem wasn't just me until now. I guess it's not just me. Anyway, here's what I did. I logged into a root shell on the LinkSys box. I edited/created the /etc/ez-ipupdate/ez-ipupdate.conf file to look like this: interface=vlan1 service-type=dyndns user=notmyusername:notmypassword pid-file=/var/run/ez-ipupdate.pid cache-file=/etc/ez-ipupdate/ez-ipupdate.cache host=notmyhostname.dnsalias.org You can probably guess that I've changed the "user" and "host" directives to be generic; change to match your situation. Once I did this, I did "killall ez-ipupdate" (hi, Solaris admins!), then "/etc/init.d/S52ez-ipupdate start", and since then, it's always worked. I know I've had power failures since then, and I also know the unit isn't on a UPS (since the UPS for that room died a while back and I haven't replaced it yet), so the "fix" apparently lives through a power loss. As an aside, one major reason I'm so enthused about OpenWRT is that one *can* fiddle with it. It's not that LinkSys's software is inherently broken and that OpenWRT is inherently not-broken. It's a lot of the same code. The difference is that LinkSys welds the hood shut, while OpenWRT at least gives me the chance to do something about it. (The other major reason I'm enthused about OpenWRT is the spiffy real-time traffic graphs in X-WRT. So cool. :) ) > And there isn't any button labeled "forced update". You can also run "ez-ipupdate" from the shell prompt. Give it a "--help" argument for some fairly useful help. > # date; uptime > Mon May 14 09:18:51 EDT 2007 > 09:18:51 up 21:16, load average: 0.00, 0.00, 0.00 > > I didn't reboot the box at all yesterday, so the 21:16 is wrong nonetheless. I suspect the uptime is correct, and the box has only been up for 21 hours. The real question is: Why did the box reboot? The nominal possible causes are: User action, power problems, software fault, hardware fault. We can rule out user action, since you didn't do anything (right?). Can you comment on power reliability at your installation? If power isn't the cause, either the software is crapping out and leading to a reboot (in which case that's a symptom of something needing fixing), or the hardware is failing (in which case all bets are off anyway). So this may be worth investigating. One thing you can do is, if you've got another *nix machine on your LAN up all the time, is setup a syslog listener on that other machine, and configure OpenWRT to forward all the syslog events to that machine. Then you can have those messages logged permanently, even if the LinkSys box crashes or resets. On a mostly unrelated note, DynDNS emails me when my hostname is about to expire, so I've never lost the name due to any issues with LinkSys's firmware, OpenWRT's firmware, or anything else. I've always had a chance to tweak things first. You may want to look into getting the same email warning for yourself. -- Ben ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
[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 updating at proper intervals? > Those two times should be identical. That's the way uptime works. Unfortunately, I don't use DynDNS, so I can't comment on your problems with that. But have you checked the firewall settings to make sure it can talk to the DynDNS servers? --Bruce ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Does the White Russian 0.9 DynDNS client suck just as much?
> 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. :) In any event, I didn't reboot the box at all yesterday, so the 21:16 is wrong nonetheless. ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Does the White Russian 0.9 DynDNS client suck just as much?
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 expired. :( The webif clearly shows an update interval of 216 seconds (25 days). The DynDNS syslog is empty (meaning that the DynDNS client hasn't done squat since last reboot). And there isn't any button labeled "forced update". What gives? 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 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 updating at proper intervals? OpenWRT was recommended as a way of getting around using Linksys's broken DynDNS client. But this system seems just as broken! ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
