Re: [leaf-user] screen blank (not leaf specific)

2003-12-06 Thread Jeff Newmiller
On Fri, 5 Dec 2003, Ryan M. Waters wrote: > Under every version of bering (or any other distribution of linux) I've > used, the screen will go blank after X amount of time. For the purposes > of seeing stats and risking screen burn-in, how does one turn this off? From http://leaf.sourceforge.

[leaf-user] Required EZ-IPUpdate Client Upgrade Notice

2003-12-06 Thread Greg Morgan
Has anyone else received an ez-ipupdate client upgrade request from dyndns.org? Most of the message carried on about problems with the Linksys WRT54G router. In a small little paragraph in both the email message and the web page below it talks about version 3.0.11b8 of ez-ipupdate being requi

Re: [leaf-user] Required EZ-IPUpdate Client Upgrade Notice

2003-12-06 Thread Jacques Nilo
Le Samedi 6 Décembre 2003 09:37, Greg Morgan a écrit : > Has anyone else received an ez-ipupdate client upgrade request from > dyndns.org? Most of the message carried on about problems with the > Linksys WRT54G router. In a small little paragraph in both the email > message and the web page below

Re: [leaf-user] Required EZ-IPUpdate Client Upgrade Notice

2003-12-06 Thread Greg Morgan
Jacques Nilo wrote: Le Samedi 6 Décembre 2003 09:37, Greg Morgan a écrit : Updated. http://leaf.sourceforge.net/devel/jnilo/packages/ezipupd.lrp Jacques Thanks for your quick response Jacques. If anyone else has to update to this version perform the following steps. It works because there are

Re: [leaf-user] Required EZ-IPUpdate Client Upgrade Notice

2003-12-06 Thread Greg Morgan
Jacques, Problem solved. I received confirmation from dyndns.org tech support that your package update is working as intended. They also went on to say, "... the version of ez-ipupdate you're using now identifies itself differently from the Linksys version, so you should not have any problems

[leaf-user] Re: Bering/IPSec/WiFi/Win2K/Shorewall (update)

2003-12-06 Thread Christopher Harewood
Lynn: I've read about the differing subnets; in fact, it was your doc that has helped to get me thus far. However, changing the laptop IP to 192.168.3.9 produces the following result: Laptop: "Negotiating IP Security" ad infinitum Bering auth.log: Dec 6 18:15:11 ice pluto[16903]: "w2kwifi"