ega last edited by
Currently I have the following deployment without the pfsense 2 is the label for future reference
Customers access the LAN 2 SERVER are customers thanks to ovpn roadwarrior, nothing new with this thank god :)
This is between 2 offices, in these offices will soon make a deployment of a wireless link, so I have an idea and want to discuss it to see if it is viable.
1. As will have an additional means of access, I was thinking hereby assign another network segment (192.168.xx) and set route between pfsense pfsense 1 and 2 for the LAN 1 and LAN 2 can access another's shares.
2. I would like to redundancy between PFsense, which if WAN 1 falls, the one pfsense all traffic diverted towards it to pfsense 2 and Internet (WAN WAN 2 or 3), does this not can do with EIGRP ?
3. Is it possible to be a slave of another pfsense ?, I explain better, in the case of the navigation rules to be established on 1 is automatically duplicated in the other, is this feasible?
4. I´ve read about CARP, but the example offered doesnt applies to this deploiment, really dont know if this is my solution, I'm opened to read comments about it.
For this deployment I'm thinking about buying switch layer 3, not to stay short in terms of interfaces and have more flexibility in implementation, because I was also thinking about send by wireless link WAN 2 and WAN 3 (by VLANs) to pfsense1 and manage there multiwan (and do the same with WAN1 to pfsense 2), but I prefers the idea of EIGRP from what I've read, though I must confess that I have not implemented any so far, I learn riding this;)
The targets that I pursue are:
1.- WAN redundance between offices
2.- LAN resources access redundances, by VPN and LAN.
Needless to say, I am open to reading suggestions, comments and criticisms about my idea
Sorry if this is not the forum to post this ???
Greetings and thanks in advance