For Chorus UFB:
We do not apply DHCP option 82 for Bitstream 3/3a.
If we did, it would make it difficult for you to differentiate DHCP request on different customer VLANs, as they would all get the same DHCP circuit and customer ID information.
Bitstream 3 and 3a are intended to be transparent services - so we don't mess with traffic on these.
Cheers,
Brent
From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Dave Mill
Sent: Friday, 4 April 2014 8:44 a.m.
To: Michael Fincham
Cc: nznog(a)list.waikato.ac.nz
Subject: Re: [nznog] Bitstream 3a DHCP manipulation
Hi Michael
On Thu, Apr 3, 2014 at 11:19 PM, Michael Fincham
1) The transaction ID is changed 2) Option 82 is added. More specifically, sub-option 1 Agent Circuit ID is present and has a valid length. sub-option 2 Agent Remote ID is present, has a length of 0 and no content which wireshark doesn't seem to like much. Do you know if the circuit was ordered with the "DHCP option"?
I've looked through the form with our service delivery team a week or so ago and could see no options relating to DHCP on the form for ordering. I can also see no option regarding DHCP for Bitstream3a in our on-boarding forms. In summary so far. Some replies on list don't believe this is normal behaviour for an ethernet service. Craig Whitmore believes that 0 is a valid length for sub-option 2 under DHCP option 82. I've had some useful replies off list offering to help to sort this out and suggesting/guessing what might be causing this. I'll follow up with these off-list emails today and try and work out what is going wrong here. Note, I'm not trying to 'name and shame' here. Just trying to work out if this is normal for BS3a and if it commonly causes issues. I'll update this list when I know more. Cheers Dave --------------------------------------------------------------------- This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002. ---------------------------------------------------------------------