OPNsense Forum

Archive => 17.1 Legacy Series => Topic started by: With Wings on May 11, 2017, 04:42:46 am

Title: DHCP failover / subnet delay question
Post by: With Wings on May 11, 2017, 04:42:46 am
I'm having issues getting CARP VIP sync to work on Mikrotik switches. Changing the VHID didn't help. So I set all the interfaces to use IP Alias.

XMLRPC sync works just fine for all High Availability settings via a dedicated interface.

DHCP failover didn't work at all using IP Aliases. The interface does say to use CARP, so I am assuming it means CARP VIP, and not High Availability.

All three interfaces were showing either:

'My State':
communications-interrupted
recover

'Peer State':
normal
unknown-state

or vice versa.

Removing the failover IP allows both peers to serve IP addresses.

Typically in this case I will assign a part of the subnet to each peer, or add a subnet delay.

Am I right in thinking that the CARP VIP is the issue, and that I can't use IP Alias for DHCP Failover?
Title: Re: DHCP failover / subnet delay question
Post by: With Wings on May 11, 2017, 04:56:05 am
Also I'm seeing this from a switch on my lab network:

00:00:00:00:01:01
XEROX CORPORATION         2017/05/11 02:39:56    tstp never

Which is apparently a BootP client, getting a perpetual lease from this thread:

https://forum.pfsense.org/index.php?topic=82884.0

Is there a way to disable BootP completely?

Title: Re: DHCP failover / subnet delay question
Post by: With Wings on May 11, 2017, 04:57:29 am
This is the part that is confusing to me:

Services > DHCP > Servers > <Interface> (Tab) > 'Failover Peer IP':

"Machines must be using CARP. Interface's advskew determines whether the DHCPd process is Primary or Secondary. Ensure one machine's advskew<20 (and the other is >20)."

Also, where is the advskew setting located?