Project

General

Profile

Bug #9596

DHCPv6 Range should not be mandatory if Stateless DHCP selected as router mode

Added by Rosario Esposito 10 months ago. Updated 22 days ago.

Status:
Resolved
Priority:
Low
Category:
DHCP (IPv6)
Target version:
Start date:
06/20/2019
Due date:
% Done:

100%

Estimated time:
Affected Version:
Affected Architecture:

Description

I'm using Stateless DHCP router mode, as described in docs:

"The firewall will send out RA packets and addresses can be assigned to clients by SLAAC while providing additional information such as DNS and NTP from DHCPv6."

I think, in this case, DHCPv6 range should not be a mandatory field in DHCPv6 Server tab.
The DHCPv6 should only pass additional info to clients, not the IP address.

Associated revisions

Revision 5c533d72 (diff)
Added by Viktor Gurov about 1 month ago

DHCPv6 range is not mandatory for Stateless DHCP. Issue #9596

History

#1 Updated by Jim Pingle 8 months ago

  • Category set to DHCP (IPv6)

#3 Updated by Jim Pingle about 1 month ago

  • Status changed from New to Pull Request Review
  • Target version set to 2.5.0

#4 Updated by Renato Botelho about 1 month ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Renato Botelho
  • % Done changed from 0 to 100

PR has been merged. Thanks!

#5 Updated by Viktor Gurov 22 days ago

  • Status changed from Feedback to Resolved

works as expected on 2.5.0.a.20200317.1949

I see the route to the default gateway via interface:

# netstat -rn | grep 1.1
192.168.1.1      0c:0d:52:c9:50:01  UHS      vtnet0

Also available in: Atom PDF