No that's not what I'm trying to say. Here's the FAQ from dyndns.org:
The abuse system automatically blocks any hostname that is repeatedly updated from the same IP. This is done to prevent the abuse that occured far too often in the old system, where a user would simply set their computer to update every 5 minutes, regardless of whether or not their IP address had changed. Updates should only be performed when your IP address has changed, and not on any other interval. The only exception to this rule is if your IP address has not changed in the past 28 days and you want to prevent your hostname from expiring. This is the only way to ensure that your host will not become blocked for abuse. Hosts which remain blocked for abuse for a period of 7 days or more are automatically deleted from our systems and an e-mail notification will be sent. If this happens, the host can simply be re-created, but you should re-examine your update procedure to ensure that abusive updates do not occur in the future. Most blocks are due to client applications automatically sending updates at timed intervals, or at system startup without checking if the IP address has actually changed. If your client doesn't support only sending updates when your IP address has actually changed, please look at our client listing for one that does. If your host has become blocked, use the form below to send a request to be unblocked. Our staff of trained support volunteers will examine your request within 48 hours. Note that if your host has been deleted (as opposed to blocked) for abusive updates, then you should just recreate it. >Let me be sure I understand what you are saying -- the LEAF router itself >cannot connect to members.dyndns.org:80, but a host that is >firewalled/NAT'd behind it can (via a browser)? I'm actually guessing a bit >here, since you say "I can still login through a web browser" but do not >actually say that the browser in question is on a host behind the LEAF >firewall. So the right thing to do is to check your ipchains or ipfilters ruleset. Since I'm not a Shorewal expert, I have to leave it at that, aside from suggesting that you supply the ruleset so those of us with the requisite expertise can look for the problem and suggest a fix. ------------------------------------------------------- This sf.net email is sponsored by: Dice - The leading online job board for high-tech professionals. Search and apply for tech jobs today! http://seeker.dice.com/seeker.epl?rel_code=31 ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
