Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Enable IPv6 support #61

Closed
tophertimzen opened this issue Jan 17, 2019 · 1 comment · Fixed by #356
Closed

Enable IPv6 support #61

tophertimzen opened this issue Jan 17, 2019 · 1 comment · Fixed by #356
Labels
agent affecting natlas-agent enhancement New feature or request server affecting natlas-server
Projects
Scope Management

Comments

@tophertimzen
Copy link
Collaborator

With the rise of companies such as Google transitioning to IPv6 for all of their addressing (internally), Natlas should support IPv6 scanning.
@tophertimzen tophertimzen added the enhancement New feature or request label Jan 17, 2019
@0xdade
Copy link
Member

0xdade commented Jan 22, 2019

This is a moonshot that will probably be open for a very long time. The technical challenges of implementing IPv6 targeting into natlas itself isn't very difficult, but effectively scoping your target ranges to not waste a ton of time and bandwidth scanning non-existent things will be an exercise to the reader.

Furthermore, if we start scanning IPv6 ranges and logging the last time we tried to scan a host, logging information for every IPv6 address we try to scan will become very large very fast.

@0xdade 0xdade added server affecting natlas-server agent affecting natlas-agent labels Feb 6, 2019
@0xdade 0xdade added this to the v0.8 milestone Feb 24, 2019
@0xdade 0xdade removed this from the v0.8 milestone Oct 24, 2019
@0xdade 0xdade added this to To do in Scope Management via automation Jun 29, 2020
@tw-sentry-io tw-sentry-io bot mentioned this issue Jul 26, 2020
Closed
0xdade referenced this issue in 0xdade/natlas Jul 26, 2020
@0xdade
Fix: ipv6 related assumptions, agent support for ipv6 nmap addresses
b233d16 
Closes #355. Closes #61. IPv6 support should work throughout, assuming your agents can route ipv6 addresses.
0xdade referenced this issue in 0xdade/natlas Jul 26, 2020
@0xdade
Fix: ipv6 related assumptions, agent support for ipv6 nmap addresses
02b5ef0 
Closes #355. Closes #61. IPv6 support should work throughout, assuming your agents can route ipv6 addresses.
@0xdade 0xdade mentioned this issue Jul 26, 2020
Merged
Scope Management automation moved this from To do to Done Jul 26, 2020
0xdade added a commit that referenced this issue Jul 26, 2020
@0xdade
Fix: ipv6 related assumptions, agent support for ipv6 nmap addresses
1a9ff14 
Closes #355. Closes #61. IPv6 support should work throughout, assuming your agents can route ipv6 addresses.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
agent affecting natlas-agent enhancement New feature or request server affecting natlas-server
Projects
Scope Management
  
Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix: ipv6 related assumptions, agent support for ipv6 nmap addresses 0xdade/natlas
2 participants
@0xdade @tophertimzen