On Tue, Jul 31, 2012 at 10:26 AM, Vick Khera <vi...@khera.org> wrote:
> On Mon, Jul 30, 2012 at 6:10 PM, <pfsense-supp...@madcyclist.org.uk> > wrote: > > I have a pfSense 2.0 box connected to an ASDL modem running as a MPoA > > bridge. Basically the ADSM modem does some unspecified manipulation and > > presents the public IP to the LAN connection via DHCP along with gateway > > etc. information allowing the pfSense box to get out onto the internet. > > So your LAN interface on the pfSense box gets a public IP? What > craziness is that? > > I'll assume you mean that your WAN interface on the pfSense is getting > the public IP from the ADSM modem. In this case, just add a rule to > the WAN tab on the firewall to permit https/ssh from your remote fixed > IP from where you wish to monitor it. Vick, I think the issue here is that he wants both a public and a private IP on the same interface. The public one is assigned by DHCP and the private one is assigned manually. Philip, You should be able to use the sections "Configure Virtual IP" and "Configure NAT" in 2.x as they haven't really changed. The one difference is that you *might* be able to use the "IP Alias" type instead of the "Other" type and then not have to configure anything using ifconfig. I am away from the office for the next few days, but if you still need help when I get back I can plug something in on the WAN side of our pfSense and do some testing. Moshe -- Moshe Katz -- mo...@ymkatz.net -- +1(301)867-3732
_______________________________________________ List mailing list List@lists.pfsense.org http://lists.pfsense.org/mailman/listinfo/list
