Is it possible to use NAT (or some combination of NAT and other trickery)
to redirect an address on your WAN interface to another external IP address
(not on the WAN interface, but at some other site).
e.g. Site A has Public IP address 1.0.0.1
Site B has Public IP 1.0.0.2
I would like to
I had tried exactly that and it did not seem to go anywhere. But I just
tried it again and it worked perfectly. So simple, thanks a lot. Must have
messed something up the 1st time.
On Sat, May 26, 2012 at 12:18 AM, Chris Buechler c...@pfsense.org wrote:
On Fri, May 25, 2012 at 11:58 PM, Adam
of tries.
On Sat, May 26, 2012 at 12:18 AM, Chris Buechler c...@pfsense.org wrote:
On Fri, May 25, 2012 at 11:58 PM, Adam Stasiak pales...@gmail.com wrote:
Is it possible to use NAT (or some combination of NAT and other
trickery) to
redirect an address on your WAN interface to another external
I've been pounding my head against the wall with this for a while now and
figured maybe I should ask a more general question hoping someone would
have a better idea of how to go about it than I apparently do.
My main site has a limited number of IPs. I have a second site with
additional IPs. I
Not sure if this is helpful to you at all, but I've looked at a possible
workaround for SSL and a lack of public IPs.
Host a virtualized pfsense box with a service provider (I'm using ARP
networks).
Get a /29 (or more as needed).
Set up a tunnel between the virtualized box and your local pfsense
what Seth and Moshe recommended and setup a proxy.
Something to discuss with them about.
** **
Thanks for the advice.
** **
Joe
** **
** **
*From:* list-boun...@lists.pfsense.org [mailto:
list-boun...@lists.pfsense.org] *On Behalf Of *Adam Stasiak
*Sent:* Thursday, July 26
My guess would be you need to forward whatever port you choose for OpenVPN
through the cisco to the pfSense box, and choose the appropriate public IP
when configuring the other end of the tunnel. (I'm assuming you're talking
about setting up a tunnel from one site to another, from your
This may be more than you want cost-wise, but you can pick up smaller SSDs
for just barely under $50:
http://www.newegg.com/Product/Product.aspx?Item=N82E16820148579nm_mc=OTC-FroogleNEWcm_mmc=OTC-FroogleNEW-_-Solid+State+Disk-_-Crucial-_-20148579
that's obviously way more space than you need, and
I did have some issues related to running pfSense off of flash memory on
certain motherboards (Jetway NF96-525-FL). It was some off compatibility
quirk, the same flash memory worked just fine on another board, and that
board was perfectly happy with an old hard drive on the same exact IDE
channel.
I had a similar problem where pfSense wouldn't route packets to remote LAN
over tunnel (it was due to a gateway issue and it wasn't using the default
routes) I think someone mentioned a similar issue.
Maybe it would be worth trying adding an additional gateway (10.100.8.1 or
.2 depending on which
Have you tried openbgpd instead of quagga? We've been using that in a
similar setup without any problems.
On Wed, Mar 13, 2013 at 11:07 AM, master8...@aol.com master8...@aol.comwrote:
I have a network of 6 pfSense routers, all running quagga connected
together with OpenVPN. When the internet
I have a similar setup running over OpenVPN tunnels.
My guess would be you won't be able to do it over an IPSEC tunnel, because
it happens at too low of a level to be able to interact with it using OSPF
or BGP.
I use OpenBGPd (running on the pfsense firewall) and it will fail over to
the secondary
If you want to keep things simpler while testing, you could boot off of a
usb stick or CD drive, rather than installing to the hard drive.
1st of all can you ping from pfsense itself?
To the gateway?
To an outside address (e.g. 8.8.8.8)
What type of connection is it?
Static IP, DHCP, PPPoE (from
So there will be one DC on vlan 1, but it also needs to be reachable from
vlan 2? If that's the case it should just be a matter of adding the
appropriate rules to allow those ports to go from the vlan 1 to the vlan 2
interface. For dhcp you would probably need to set up a forwarder on the
vlan 2
14 matches
Mail list logo
