Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 1 Oct 2014 21:23:17 +0000 (UTC)
From:      John Case <case@SDF.ORG>
To:        freebsd-questions@freebsd.org
Subject:   Locked out of FreeBSD EC2 image - trying to figure out why ...
Message-ID:  <Pine.NEB.4.64.1410012025290.15899@faeroes.freeshell.org>

Next in thread | Raw E-Mail | Index | Archive | Help

I added this ipfw line to my ec2 image and then rebooted it, and am unable 
to connect over the network now:


deny ip from 10.0.0.0/8,172.16.0.0/12,192.168.0.0/16 to any
deny ip from 0.0.0.0/8,169.254.0.0/16,192.0.2.0/24,224.0.0.0/4,240.0.0.0/4 
to any


The private IP that my instance uses is in the 172.31.xx.xx block, so is 
it my blocking of 172.16.0.0/12 that is causing the problem ?


I assigned a fixed "elastic" Ip to the instance in the hopes that amazon 
would fire up the instance and give it that *real* IP when it dhcp'd an 
address, but that doesn't seem to be the case.  Is there any way to force 
amazon to give it a real IP so I can log into this system ?

Thanks.



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?Pine.NEB.4.64.1410012025290.15899>