[
https://issues.apache.org/jira/browse/TC-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15878905#comment-15878905
]
ASF GitHub Bot commented on TC-160:
-----------------------------------
GitHub user dangogh opened a pull request:
https://github.com/apache/incubator-trafficcontrol/pull/300
[TC-160] remove check for ip6 addr and gateway in same network
still allows user to enter, but does not check that address is in the same
network
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dangogh/incubator-trafficcontrol ip6-gateway
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafficcontrol/pull/300.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #300
----
commit c97f24f15e1655a0b2425845891766e2489fe438
Author: Dan Kirkwood <dang...@gmail.com>
Date: 2017-02-21T20:49:41Z
remove check for ip6 addr and gateway in same network
----
> 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
> Fix For: 2.0.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.3.15#6346)
