Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Infoblox and iPXE
2014-11-12, 15:12
Post: #7
RE: Infoblox and iPXE
(2014-11-11 05:35)jov0 Wrote:  Michael here is an example output for when the Firewall is enabled and cuts off the dhcp acknowledgement from 172.23.223.141. Because 10.64.38.20 is physically closer, 172.23.223.141 acks almost always come in second and consequently are dropped by the firewall. This is a combination of design issues between infoblox's fail over setup and Cisco's firewall abilities for this variety of traffic. We do not see the same behavior using Etherboot or gPXE in that it either they do not care who is sending the ack or are making the request against first offer versus the last. I would test this for sure, but the last gpxe src from 2011 does not compile.

Thanks. Are you able to disable either of the DHCP servers from responding to the initial DHCPDISCOVER?

If not, then as a workaround you could delete the check in dhcp_request_rx() in net/udp/dhcp.c:

Code:
if ( server_id.s_addr != dhcp->server.s_addr )
  return;

Michael
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Messages In This Thread
Infoblox and iPXE - jov0 - 2014-11-07, 00:01
RE: Infoblox and iPXE - mcb30 - 2014-11-07, 15:03
RE: Infoblox and iPXE - jov0 - 2014-11-10, 04:27
RE: Infoblox and iPXE - mcb30 - 2014-11-10, 15:30
RE: Infoblox and iPXE - jov0 - 2014-11-11, 05:35
RE: Infoblox and iPXE - mcb30 - 2014-11-12 15:12
RE: Infoblox and iPXE - jov0 - 2014-11-13, 02:56
RE: Infoblox and iPXE - isi_spike - 2014-11-10, 21:48
RE: Infoblox and iPXE - jov0 - 2014-12-04, 20:42
RE: Infoblox and iPXE - robinsmidsrod - 2014-12-06, 21:21



User(s) browsing this thread: 1 Guest(s)