I'm not sure I follow...the 192.168.50.x subnet would use 192.168.50.1 as its gateway and 10.10.10.111 would be the NATted WAN IP. I don't see how that's a problem for other PCs in 10.10.10.x? Unless 10.10.10.111-113 are in use on it?
This reads like you added the computer and server to the WAN side of pfSense, so they would not be using pfSense at all. You can't connect the networks through pfSense and around it at the same time... -- Steve Yates ITS, Inc. Justin Edmands wrote on Mon, Jul 27 2015 at 3:53 pm: > I have setup a dual gateway setup I have created to test a future project > of adding another gateway to our production setup. I added two computers > next to me connected to a switch and the "WAN" IPs are IPs from our regular > subnet. The LAN is a subnet that we don't use normally. > > my computer - 10.10.10.58 > random server - 10.10.10.43 > > devpfsense WAN CARP IP - 10.10.10.111 > devpfsense1 WAN - 10.10.10.112 > devpfsense2 WAN - 10.10.10.113 > > devpfsense LAN CARP IP - 192.168.50.1 > devpfsense1 LAN - 192.168.50.10 > devpfsense2 LAN - 192.168.50.11 > > > I connect all of this up. CARP works just fine. I edit a few things and > everything syncs over to the secondary gateway. The problem is that the > "WAN" IPs being set are wreaking havoc on my regular network where the > 10.10.10.XXX IPs reside. > > It is as if I am creating some form of a loop or broadcast storm. > > Am I supposed to enable something like HSRP or VVRP to tell my regular > network that these two "WAN" IPs work together and form 10.10.10.111? _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
