Re: [j-nsp] SRX300 DHCPD vs JDHCP - DHCP client issues

[John Jensen]

Thanks for the info Clarke.

Just to provide an update for anyone interested - DX100 did nothing for me.
I also tried the 17.x release train, and while it's still not properly
setting the client-id, I did manage to pick up on some interesting stuff.

1) They've reverted back to legacy DHCP client interface config *style*.
-HOWEVER- this still just appears to turn on the JDHCP client. There is no
more differentiator on the DHCP client aspect of things (set interfaces
ge-0/0/0 unit 0 family inet dhcp vs. set interfaces ge-0/0/0 unit 0 family
inet dhcp-client).

2) The commands to turn on the legacy DHCP server are still available (but
hidden) - you can configure pools etc with the legacy server, but if you
try to turn on a DHCP client on an interface, JUNOS will yell at you
because the configs are incompatible:

set system services dhcp pool 192.168.1.0/24 address-range low 192.168.1.2
set system services dhcp pool 192.168.1.0/24 address-range high
192.168.1.254
set system services dhcp pool 192.168.1.0/24 router 192.168.1.1
set system services dhcp pool 192.168.1.0/24 propagate-settings ge-0/0/0.0
set system services dhcp pool 192.168.2.0/24 address-range low 192.168.2.2
set system services dhcp pool 192.168.2.0/24 address-range high
192.168.2.254
set system services dhcp pool 192.168.2.0/24 router 192.168.2.1
set system services dhcp pool 192.168.2.0/24 propagate-settings ge-0/0/0.0
set system services dhcp pool 192.168.3.0/24 address-range low 192.168.3.2
set system services dhcp pool 192.168.3.0/24 address-range high
192.168.3.254
set system services dhcp pool 192.168.3.0/24 router 192.168.3.1
set system services dhcp pool 192.168.3.0/24 propagate-settings ge-0/0/0.0
set system services dhcp pool 192.168.4.0/24 address-range low 192.168.4.2
set system services dhcp pool 192.168.4.0/24 address-range high
192.168.4.254
set system services dhcp pool 192.168.4.0/24 router 192.168.4.1
set system services dhcp pool 192.168.4.0/24 propagate-settings ge-0/0/0.0
set system services dhcp pool 192.168.5.0/24 address-range low 192.168.5.2
set system services dhcp pool 192.168.5.0/24 address-range high
192.168.5.254
set system services dhcp pool 192.168.5.0/24 router 192.168.5.1
set system services dhcp pool 192.168.5.0/24 propagate-settings ge-0/0/0.0

[edit]
root@FIOS_Quantum_Gateway# load set terminal
[Type ^D at a new line to end input]
set interfaces ge-0/0/0 unit 0 family inet dhcp client-identifier
hexadecimal 01485d36343597
set interfaces ge-0/0/0 unit 0 family inet dhcp retransmission-attempt 6
set interfaces ge-0/0/0 unit 0 family inet dhcp retransmission-interval 4
set interfaces ge-0/0/0 unit 0 family inet dhcp update-server
set interfaces ge-0/0/0 unit 0 family inet dhcp vendor-id FiOS-G1100:
dslforum.org
load complete

[edit]
root@FIOS_Quantum_Gateway# commit and-quit
[edit interfaces ge-0/0/0 unit 0 family inet]
  'dhcp'
Incompatible with the dhcp server configured under 'system services
dhcp'
error: commit failed: (statements constraint check failed)


Pretty interesting - I think the old style DHCP client configs make more
sense than the JDHCP client configs introduced in 15.x - but alas, still no
luck with a working implementation of a hex DHCP client-identifier using
JDHCP.

-JJ

On Tue, Sep 5, 2017 at 11:49 AM, Clarke Morledge  wrote:

> John Jensen,
>
> I can not comment on your specific issue, but I ran into a different DHCP
> issue with the new JDHCP-style format, that forced me to go back to the
> legacy format, which was working just fine.  I am running 15.1X49-D100.6.
>
> Unfortunately, the PR is private, so there are no details. It looks like I
> will be waiting for a new version of JUNOS to come out before I can hope to
> use the new JDHCP method.
>
> Clarke Morledge
> College of William and Mary
> Information Technology - Network Engineering
> Jones Hall (Room 18)
> Williamsburg VA 23187
>
>
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] SRX300 DHCPD vs JDHCP - DHCP client issues

[Clarke Morledge]

John Jensen,

I can not comment on your specific issue, but I ran into a different DHCP 
issue with the new JDHCP-style format, that forced me to go back to the 
legacy format, which was working just fine.  I am running 15.1X49-D100.6.


Unfortunately, the PR is private, so there are no details. It looks like I 
will be waiting for a new version of JUNOS to come out before I can hope 
to use the new JDHCP method.


Clarke Morledge
College of William and Mary
Information Technology - Network Engineering
Jones Hall (Room 18)
Williamsburg VA 23187

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] SRX300 DHCPD vs JDHCP - DHCP client issues

[John Jensen]

Hi!

I was going to ask this on the Juniper support forums but the email that
went out to my company email address is in limbo at the moment, so I
figured this would be as good of a place as any to ask.

I'm working on getting my FiOS routed through my SRX300. A couple different
places on the Internet spoke of shutting off the "old-style" DHCPD in favor
of the "new style" JDHCP. Fine, all well and good. Normally I would have
just not cared about DHCP services, except at the bottom of this page
 it says:


   - Legacy DHCPD (DHCP Daemon) configuration syntax will be hidden
   starting from 15.1X49-D60 


Okay, sure - so I changed to JDHCP. Here's the problem:

FiOS is very particular about the DHCP options sent in the REQUEST/DISCOVER
packets in order to actually obtain a lease. Namely, (I'm pretty sure) it
wants a specific hostname, vendor-id (option 60) and client-id (option 61).
All of these I can set, which is good.

This blog post

gives
a rundown of the config statements for legacy DHCP and what their
equivalent config statements are with JDHCP. But here's the problem. This:

set interfaces ge-0/0/0 unit 0 family inet dhcp client-identifier
hexadecimal 01485d36343597

Is supposed to do the same thing as this:

set interfaces ge-0/0/0 unit 0 family inet dhcp-client client-identifier
user-id hexadecimal 01485d36343597

But on the wire, this isn't the case.

Using legacy DHCP, the first command works like a champ. I get an IP from
FiOS no problem with this config - wireshark properly detects 0x01 type as
ether, and displays the MAC address of the client in the option 61 field.

Now switching to JDHCP and using the second config statement, no matter
what i put for hex or ascii, the DHCP client always inserts the interface
name as a prefix for whatever reason and it's causing my DHCP discovers to
be ignored by FiOS. So basically Wireshark only shows the length of the
option, and you see something like:

=.=.:ge-0/0/0.0:[data]

within the packet data, again regardless of which hex or ascii values I
supply to it.

This box is running 15.1X49-D45. Anyone else experienced weirdness or
undesirable prefixing of option 61 strings?

Thanks.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp