[INSTRM-267] Update document and configuration for DHCP lease range Created: 20/Dec/17  Updated: 26/Mar/18

Status: In Progress
Project: Instrument control development
Component/s: ics_dnsmasq
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Normal
Reporter: shimono Assignee: shimono
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

This is my fault and shall be noted at the initial moment, but we need a fix on DHCP lease range configuration.

For now, dhcp-range for the production is defined as:

dhcp-range=133.40.164.1,133.40.164.239,72h
dhcp-range=tag:!known,133.40.164.240,133.40.164.255,6h
dhcp-range=133.40.165.0,133.40.165.254,72h

and this will make

  • registered hosts in hosts/macs files are assigned as defined (in two ranges w/o tag:!known)
  • registered hosts only in macs files are assigned from two ranges w/o tag:!known
  • unregistered hosts are assigned from any range

So, we need to

  • add tag:known for two (tag:!known could be better to be kept?)
  • if we allow registered hosts in macs (e.g. temporal tool for AIT or engineering) but not in hosts, we shall have a flag to filter and guide them all in specified range

how do you think, all? > cloomis, Yoshida, Hiroshige, kyono

 Comments   
Comment by cloomis [ 22/Dec/17 ]

We have been using the following successfully:

dhcp-range=tag:!known,10.1.255.2,10.1.255.254,5m
dhcp-range=tag:known,10.1.1.1,10.1.99.254,4h

so I agree with adding the known tag.

Comment by shimono [ 27/Dec/17 ]

Thank you for guideline. So,

  • we shall have tag:known in configuration
  • adding registered hostname without IP address shall not be an option
    right? I will update files and push PR following these.
Comment by shimono [ 10/Jan/18 ]

Added a branch for dnsmasq configuration.
Documentation is blocked by INSTRM-71 and should be branched/updated after that is approved and merged.

Comment by shimono [ 12/Mar/18 ]

code (dnsmasq) merged, but needs update on document (SSN-00028).

Comment by shimono [ 26/Mar/18 ]

cloomis considering having pairs of non-ip-address assigned hostname and MAC addresses, such as additional NICs (some are used for bonding, or V-LAN) or default network switch MAC addresses, we shall flag them not to eat non-assigned IP addresses within statically assigned to subsystem.
So, I will try to add something like tag:/set:nia (no ip assigned) or something to flag them.

Generated at Sat Feb 10 16:23:14 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.