Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • user-manual user-manual
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • user-manualuser-manual
  • Issues
  • #352
Closed
Open
Issue created Sep 01, 2025 by dockx thibault@tdockxDeveloper

IP assignment algorithm should mask broadcast addresses from assignable IP range

Hello FD Team,

We finally got round to integrating our RADIUS and LDAP infrastructure with the new subnet/vlan support, and came across an odd issue.

It appears the IP assignment mechanism isn't masking broadcast addresses. The first and last address in a subnet are not usually assignable.

For example, with subnet 192.168.10.0/24, 192.168.10.0 and 192.168.10.255 are not assignable. Could either:

  • The IP assignment code be updated to reflect this

OR

  • "start" [+ "end"] addresses be added to subnets to artificially constrain IP assignments (this is our preference).

If adding "start" and "end" would be considerable work, we'd be happy to pay for it via proffesional services.

Many Thanks, -Arran

Assignee
Assign to
Time tracking