You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by "Dan Kirkwood (JIRA)" <ji...@apache.org> on 2017/07/07 19:17:00 UTC
[jira] [Closed] (TC-160) ip6gateway should not be required
[ https://issues.apache.org/jira/browse/TC-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Kirkwood closed TC-160.
---------------------------
> ip6gateway should not be required
> ---------------------------------
>
> Key: TC-160
> URL: https://issues.apache.org/jira/browse/TC-160
> Project: Traffic Control
> Issue Type: Improvement
> Components: Traffic Ops
> Affects Versions: 2.0.0
> Reporter: Dan Kirkwood
> Assignee: Dan Kirkwood
> Fix For: 2.1.0
>
>
> when adding a new server with an ip6 address, Traffic Ops (both GUI and API) require ip6 gateway within the same network as the address.
> But, ip6 gateways commonly use a link-local address (e.g. in the fe80:: range). The check when adding a new server is not valid in this case.
> Traffic Ops should either not require the gateway, loosen the restriction on the gateway address, or eliminate the gateway from the server completely.
> A sample error shown below:
> ```2000:2000:2000::1 and fe80::99 are not in same network```
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)