We did something similar when setting up our data center routers.
Added a public subnet on the LAN side of our own pfSense, NATted to the
Internet. It works because of the NAT so the public IPs don't leave our
office. The data center routers had another public subnet on their LAN side
(since we have a /25 block routed to us), so as I recall there were a few
routing configuration changes to ensure traffic for those IPs was routed back
inside our office and didn't go out to the Internet. But for just one public
IP that isn't necessary.
So I suppose a workaround would be to put the WAN gateway IP in your
own pfSense and the new router would talk to it.
--
Steve Yates
ITS, Inc.
-----Original Message-----
From: List [mailto:list-boun...@lists.pfsense.org] On Behalf Of Mark Wiater
Sent: Thursday, May 18, 2017 8:27 AM
To: list@lists.pfsense.org
Subject: Re: [pfSense] Restoring at remote location before deployment
On 5/17/2017 3:44 PM, Steven Spencer wrote:
> All,
>
> When restoring a configuration for a site, we often do so from the home
> office and then deploy after we are sure hardware is working as
> expected. That means that we are restoring a backup and then on reboot,
> their is no active WAN (because the WAN IP is set for the remote
> location on restore)
I do the same, build up the system in the home office for testing.
I've created a separate environment within the home office that allows
for the unit under test to hit the internet after getting natted to the
home office's ip addr.
esses.
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
_______________________________________________
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold
