SRX

Expand all | Collapse all

DHCP static binding not working

  • 1.  DHCP static binding not working

    Posted 04-22-2014 04:05

    Hello. Tried to configure static binding in SRX210 (11.4R10.3), it doesn't work. Client is Windows PC. What could be wrong ?

     

    services {...

    dhcp{...

    ...

    static-binding aa:bb:cc:dd:ee:4b {
                    fixed-address {
                        1.2.3.4;
                    }
                    name-server {
                        1.2.3.5;
                        1.2.3.6;
                    }
                    wins-server {
                        1.2.3.5;
                        1.2.3.6;
                    }
                    router {
                        1.2.3.7;
                    }
    ...



  • 2.  RE: DHCP static binding not working

    Posted 04-22-2014 21:29

    Hi,

     

    I would check your security zone to see if the correct interface is permitting DHCP (host-inbound-traffic system-services dhcp).

     

     



  • 3.  RE: DHCP static binding not working

    Posted 04-22-2014 22:40

    Hi, I think yes, because I have another static binding for voip device, and it's working OK.



  • 4.  RE: DHCP static binding not working

    Posted 04-29-2014 09:52

    Best advice I can offer is to stop using the old DHCP configuration under "system services dhcp" and start using "set access address-assignment...".

     

    I'm not sure if you can do that under 11.4 so if not, upgrade to 12.1 if you can and then use the new "access" dhcp configuration.  I've had a lot of problems with the old method on my SRX220 that you're having on your 210, and I've heard others having the same issues as well.  Configuration example would look something like this:

     

    user@host> show configuration access 
    address-assignment {
        pool wired {
            family inet {
                network 192.168.100.0/24;
                range wired {
                    low 192.168.100.2;
                    high 192.168.100.254;
                }
                dhcp-attributes {
                    name-server {
                        8.8.8.8;    or your ISP's DNS server
                    }
                    router {
                        192.168.100.1;
                    }
                }
                host PC-1 {
                    hardware-address 08:60:6e:67:ec:aa;
                    ip-address 192.168.100.2;
                }
                host PC-2 {
                    hardware-address c4:4e:ac:03:4e:ed;
                    ip-address 192.168.100.3;
                }                           
            }
        }
    
    
    user@host> show configuration system services                      
    dhcp-local-server {
        group wired {
            interface vlan.100;  logical or physical interface participating in dhcp

     

    The bindings are configured where you see "host PC-1" and "host PC-2".  I've found this method much more stable/reliable.  Your ip scheme and participating interface will be different as this is just an example.



  • 5.  RE: DHCP static binding not working

     
    Posted 04-29-2014 10:53

    Hi.

     

    What's the best way to exclude a range?  Are we able to specify multiple low-high ranges?

     

    Thanks.

    Sam



  • 6.  RE: DHCP static binding not working

    Posted 04-29-2014 20:20

    Yes you can specify multiple ranges within the same network, excluding addresses you don't want to be used for DHCP, here's an example of multiple ranges on the same pool:

     

    pool test {
            family inet {
                network 192.168.1.0/24;
                range test1 {
                    low 192.168.1.2;
                    high 192.168.1.100;
                }
                range test2 {
                    low 192.168.1.200;
                    high 192.168.1.254;
                }
                dhcp-attributes {
                    name-server {
                        8.8.8.8;
                    }
                    router {
                        192.168.1.1;
                    }
                }
            }
        }
    }
    

     I effectively skipped everything between 192.168.1.101-192.168.1.199.