On Fri, Apr 4, 2014 at 11:32 AM, Dave Mill <davemill@gmail.com> wrote:

Just as a quick update on this. It seems likely at this stage that this service has been mis-configured by the UFB provider. The DHCP option seems to commonly be used on Bitstream2 services. No one I've talked to can think of a good reason as to why this would ever be required on a Bitstream3 connection. I know providers that make good use of this on BS2.

I'll update again when this is resolved. I'm confident I'm now getting to the bottom of this issue.

On Friday the provider of this BS3a service found that Option 82 was being set incorrectly. This issue was fixed and the DHCP service started working for our customer. I've confirmed that since the change on Friday Option 82 is no longer present at the service provider handover end of the circuit.

DHCP transaction IDs are still being modified. This does not seem to cause any issues at all.

Thanks for all of the on and off list replies.

Cheers

Dave