<html><body>
<blockquote>
<div class="message_header"><span>Thu Apr 08 2010 08:01:26 AM CDT</span> <span>from "Andrew Berg" <bahamutzero8825@gmail.com> </span> <span class="message_subject">Subject: Re: [tclug-list] Trying to set up a simple firewall</span></div>
<div class="message_content"><tt>On 4/8/2010 6:59 AM, Adam Morris wrote:</tt><br /><tt>It's done by their ISPs. If they get disconnected from their ISP (e.g.</tt><br /> <tt>modem reset, service outage), they get a new IP address when they</tt><br /> <tt>reconnect. I'm mostly worried about myself. Such a situation is rare,</tt><br /> <tt>but if I get assigned a new IP address, I'm locked out and there's no</tt><br /> <tt>one to let me back in. I could write a script that would replace</tt><br /> <tt>Shorewall's rules file with a similar one that would open up ssh to the</tt><br /> <tt>public so I could log in, but I'd have open ssh to one of my users, all</tt><br /> <tt>of whom (AFAIK) are clueless when it comes to Linux/Unix and the sole</tt><br /> <tt>reason they would have shell access would be to execute the script.</tt><br /></div>
<div class="message_content"><br /></div>
</blockquote>
<div class="message_content">How about port knocking to protect the ssh port instead of block / allow by IP address. The port knocking daemon can add the rule for you in case your IP address changes (or you need to connect from a different location).<br /></div>
<div class="message_content"><br /></div>
<p>Kelly</p>
</body></html>