DHCP TFTP option and multiple subnets BUG?

  • 1
  • Question
  • Updated 1 year ago

I have setup a Network Policy for our Br200 routers for our branch offices.
I have created a network with multiple subnets since we want to control which branch get which network and we want to specify an different TFTP server per subnet.

So the network contains for example:

Subnet selection is then done by device name via "Select subnetworks based on classification rules"

In each subnet there is added 2 DHCP options for PXE booting clients from the local server 
67 String cipcc.0
66 String and so on.

The problem is that the DHCP options from the first subnet are also active in the following subnets.

Using remote sniffer I validated that clients in third network where DHCP option 66 is set to but gets from the first subnet. 

Hivemanger is version 6.6r1 and BR200 are running HiveOS 6.6r1b release build2338
Photo of Brian A

Brian A

  • 5 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 1
Photo of Brian A

Brian A

  • 5 Posts
  • 0 Reply Likes

I have justes looked through the running config on the routers.

The Hivemanager configures the devices with DHCP options from the first entry in the Network list

This is from the last entry in the Network list. The option 66 should have been x.y.4.1

interface mgt0.1 vlan 1
interface mgt0.1 ip x.y.4.126/25
interface mgt0 dhcp-server enable
interface mgt0.1 dhcp-server options default-gateway x.y.4.126
interface mgt0.1 dhcp-server options custom 66 string x.z.32.1
interface mgt0.1 dhcp-server options custom 67 string cipcc.0

Have anyone else seen this behaviour?

For us this is a serious issue. These BR200's are supposed be the new standard router for our stores.


Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2485 Posts
  • 448 Reply Likes
Hi Brian,

You should contact your point of support for this. It looks, prima facie, like there's a bug here and that's the way to get it resolved.


Photo of Holger


  • 1 Post
  • 0 Reply Likes
I second that this is a bug, did you get an update from AH regarding this?
Photo of Brian A

Brian A

  • 5 Posts
  • 0 Reply Likes
Just to finish this. Yes it was fixed in a later release. It's working now.