[AusNOG] Juniper SRX300 on Aussie Broadband NBN HFC - DHCP Issue

Tim Dykes ttdykes at gmail.com
Fri Jan 15 16:45:45 EST 2021

Updates after a day of research and discussion with JTAC....

JTAC say there were known issues with how jdhcpd handled client-identifier
and that caused these issues. That was fixed in junos:19.2R3 junos:19.3R3
junos:19.4R3 junos:20.1R2 junos:20.2R2 junos:20.3R1

There were reports that the order that the DHCP options were listed was
causing problems. Packet captures from our SRX seem to rule that out, they
look fine.

Another forum says the SRX has a 255 end of option.. option, and that
causes the problem but all vendors I have checked today also sent that...
so dont think thats it.

 I've received two reports of it working for people without any issues, and
2 reports of it having issues. The firmware versions that it works fine on
are both different and one of them is even 15X.

I can't find any PR's to match what I am seeing so I can only assume they
are private.

PPPOE seems to be fine across the board on HFC.

Putting down as many notes here as possible so next time someone is trying
to get a link up like this there is some reference material to go off.

I have to wait until late next week for the end client to update their SRX
to a newer code base inline with what JTAC say so until then I can't put
this issue to bed.

Tim Dykes

On Thu, 14 Jan 2021 at 14:40, Simon Dixon <simon at dicko.net.au> wrote:

> Guessing your RE traffic CoS bits are set to default try setting them to
> BE with the following config
> set class-of-service host-outbound-traffic ieee-802.1 default be
> Regards
> Simon.
> On Thu, 14 Jan 2021 at 11:17, Tim Dykes <ttdykes at gmail.com> wrote:
>> Hey Guys,
>> Anyone out there running a Juniper SRX on a NBN HFC link with Aussie BB?
>> I'm having issues that sound like a DHCP problem where we can't get an
>> address. Searching around we have found references to a DHCP issue where
>> the juniper sends DHCP options out of order (or that NBN fiddles with
>> options in a way that only effects Juniper) but cannot find any definitive
>> answer or anything saying this was true/false fixed or unrelated.
>> We are running JunOS 19X so would assume any horrible non compliant DHCP
>> bugs would be fixed.
>> Anyone able to throw me a working config or verify that there is/was a
>> known issue with this.
>> Thanks.
>> /Tim
>> _______________________________________________
>> AusNOG mailing list
>> AusNOG at lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20210115/3b93da22/attachment.html>

More information about the AusNOG mailing list