Project

General

Profile

Actions
Copy link

Bug #3790

closed

Input validation is too strict for IPv6 Prefix ID for Track Interface

Added by Jim Pingle over 10 years ago. Updated almost 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Renato Botelho
Category:
Interfaces
Target version:
2.2
Start date:
08/01/2014
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1-IPv6
Affected Architecture:
All

Description

It is impossible to set both the track interface and an ID higher than 0 in one action, even if it is valid.

For example if the WAN is set to DHCPv6 with a DHCPv6 Prefix Delegation size of "60", the valid prefix IDs are 0 through F.

If you configure an internal interface to Track Interface, then select WAN and enter a higher ID (e.g. 1), then press save, an input validation error is printed saying the ID is invalid. If you select Track Interface and WAN and immediately Save, then enter the ID, the valid is kept.

This affects both 2.1.x and 2.2.

Actions
Copy link
 #1

Updated by Renato Botelho over 10 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #2

Updated by Jim Thompson over 10 years ago

  • Assignee set to Renato Botelho
Actions
Copy link
 #3

Updated by Chris Buechler about 10 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #4

Updated by Anonymous about 10 years ago

A couple of additional items for this that need to be resolved...

- When the prefix selection box first appears, it always seems to show "between 0 and 0", even if a greater range is actually valid. (example: I have a /60 available, but when I add a new interface, it shows "between 0 and 0" when it should show "between 0 and f").

- You can enter a prefix value that is already in use on another interface and you are not alerted that the value is already in use, either on that page immediately or when saving the changes and the page reloads.

Actions
Copy link
 #5

Updated by Chris Buechler about 10 years ago

  • Status changed from Resolved to Confirmed
  • Assignee deleted (Renato Botelho)
Actions
Copy link
 #6

Updated by Jim Thompson about 10 years ago

  • Assignee set to Renato Botelho

re-assigned

Actions
Copy link
 #7

Updated by Renato Botelho about 10 years ago

  • Status changed from Confirmed to Feedback
Actions
Copy link
 #9

Updated by Chris Buechler almost 10 years ago

  • Assignee changed from Renato Botelho to Chris Buechler
  • Affected Version changed from 2.1 to 2.1-IPv6

to me for review

Actions
Copy link
 #10

Updated by Jim Pingle almost 10 years ago

  • Status changed from Feedback to Confirmed

Seems to break when WAN is set to a /64 delegation. Saving LAN with an ID of 0 is rejected, though it is valid.

Actions
Copy link
 #11

Updated by Jim Pingle almost 10 years ago

  • Assignee changed from Chris Buechler to Renato Botelho
Actions
Copy link
 #12

Updated by Renato Botelho almost 10 years ago

  • Status changed from Confirmed to Feedback
Actions
Copy link
 #13

Updated by Chris Buechler almost 10 years ago

  • Status changed from Feedback to Resolved

fixed

Actions
Copy link

Also available in: Atom PDF