----- Original Message ----- > > That was my hope, to save public subnet IP space. The answer appears > to be no, but now that I have a couple of boxen in my test lab, it > would be easy to find out. I'll post to the list with the results > later, although my hopes aren't very high for the intended result. > :) >
Just had a few minutes to test this. I have a public CARP VIP assigned to the WAN, but changed the WAN direct assigned public IP's to private IPs (10.10.10.x). The results are, as expected, not desirable. All connectivity was lost on the WAN, as well as the systems giving the following alert (scrolling yellow box at top of web UI): "[CARP]Sorry but we could not find a matching real interface subnet for the virtual IP address MY.PUB.LIC.IP" So, to confirm, it does *NOT* work to assign a different subnet/IP to the interface when using CARP, and apparently by design. That answers that, it is what it is. --Tim _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
