We have an IP system that makes use of BOOTP for updating our embedded devices over IP. The main app uses DHCP for its IP configuration.
Our devices are usually on the network of the customer, the customer manages the network infrastructure. We provide a server machine that hosts a DHCP and BOOTP server, thus our ownership. Till recently we never had any issues. There's one customer where BOOTP communication doesn't work while DHPC is working perfectly between same endpoints. I wiresharked the interface of our server machine: BOOTP- packet isn't received. This while DHCP- is coming in OK. Both packets have ethernet-destination broadcast. Bot UDP on destination port 67. No firewall on our server machine. In fact DHCP is an extension of BOOTP.
If I tell this to the customer that I think their equipment is probably blocking this, I get a negative response. In my opinion there must be something - I believe a managed switch - that blocks this BOOTP packet. Does someone has any tips:
- Is it a common practice to block BOOTP on a managed enterprise network?
- How defend/elaborate this towards the customer in order to make him take (more) actions. Can I push him in the right direction, what to verify?
- Any other remarks suggestions, experiences...