Add IPv6 support to qos.sh #9552
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TheBlueMatt
reviewed
Jan 19, 2017
| #defines the IPv4 address space for which you wish to disable rate limiting | ||
| LOCALNET_V4="192.168.0.0/16" | ||
| #defines the IPv6 address space for which you wish to disable rate limiting | ||
| LOCALNET_V6="2001:0DB8:0400:0A20::/64" |
There was a problem hiding this comment.
Can we default to fe80?
jamesmacwhite
force-pushed
the
qos-ipv6
branch
from
6c37242
to
a558444
Compare
|
@TheBlueMatt Yeah good idea. I've updated |
jamesmacwhite
force-pushed
the
qos-ipv6
branch
from
a558444
to
501fe23
Compare
jamesmacwhite
force-pushed
the
qos-ipv6
branch
from
501fe23
to
fc089ae
Compare
|
utACK fc089ae |
laanwj
added a commit
that referenced
this pull request
Jan 19, 2017
fc089ae Add IPv6 support to qos.sh (James White)
codablock
pushed a commit
to codablock/dash
that referenced
this pull request
Jan 21, 2018
fc089ae Add IPv6 support to qos.sh (James White)
andvgal
pushed a commit
to energicryptocurrency/gen2-energi
that referenced
this pull request
Jan 6, 2019
fc089ae Add IPv6 support to qos.sh (James White)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds support for dual-stack Bitcoin coin nodes who might want to limit v6 traffic as well, if they are allowing incoming connections on both v4 and v6.
It looks like
tcdoesn't work using the same prio value as v4, so it has to be different, hence a different mark value for v6.I have amended
$LOCALNETto be$LOCALNET_V4andLOCALNET_V6respectively. The v6 stuff will not be used if$LOCALNET_V6is blank.