Date: Wed, 1 Oct 2014 22:12:19 +0000 (UTC) From: John Case <case@SDF.ORG> To: Michael Sierchio <kudzu@tenebras.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Locked out of FreeBSD EC2 image - trying to figure out why ... Message-ID: <Pine.NEB.4.64.1410012211280.15899@faeroes.freeshell.org> In-Reply-To: <CAHu1Y71Nay5ekXojFn-RDHb4PRmaiBDaunxqdcTy8iaV9YuusQ@mail.gmail.com> References: <Pine.NEB.4.64.1410012025290.15899@faeroes.freeshell.org> <CAHu1Y71Nay5ekXojFn-RDHb4PRmaiBDaunxqdcTy8iaV9YuusQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 1 Oct 2014, Michael Sierchio wrote: > Yes. DHCP responses will come from an RFC1918 network, for example. > This is naive and really unnecessary - just use an appropriate EC2 > security policy. If you insist on using ipfw, you'll need to improve > your understanding of how things work. > > Also - an elastic IP will not persist across stopping and starting an > instance, and you should associate it using a script inside the > instance when it starts. Ok, so the only way for me to rescue this instance (I did not make a snapshot prior to the firewall) is to snapshot it now, and then mount that snapshot on another instance and edit the conf file ... Anything faster and easier than that, or is that my only option ? Thanks.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.4.64.1410012211280.15899>