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.

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

Lack of IPv6 support #1

Closed
sleinen opened this issue Feb 22, 2015 · 5 comments
Closed

Lack of IPv6 support #1

sleinen opened this issue Feb 22, 2015 · 5 comments

Comments

@sleinen
Copy link
Owner

sleinen commented Feb 22, 2015

From simon.le...@gmail.com on March 11, 2009 09:48:02

What steps will reproduce the problem? 1. Start the samplicator on some port
2. Send UDP packets to that port over IPv6 What is the expected output? What do you see instead? Expected: The packets should be replicated to the configured destinations.
Instead, they are dropped by the host's network stack, because the
samplicator process uses an IPv4-only socket.

Similarly, when IPv6 addresses are specified as destinations, the
samplicator complains about malformed addresses.

Ideally, the samplicator should even be able to receive datagrams over IPv4
and distribute them over IPv6 and vice versa.

Original issue: http://code.google.com/p/samplicator/issues/detail?id=1

@sleinen
Copy link
Owner Author

sleinen commented Feb 22, 2015

From simon.le...@gmail.com on February 27, 2010 13:51:23

IPv6 support could be added as follows:

  • In all places where IPv4 addresses are accepted (-s option, receiver addresses on
    the command line or in configuration files, and source address ranges in
    configuration files), we will accept IPv4 addresses, IPv6 addresses, or hostnames.
  • In source address range specifications in configuration files, the current (old)
    code understands IPv4 netmasks with the syntax 1.2.3.0/255.255.255.0. We will extend
    the syntax to accept CIDR prefix lengths, e.g. 1.2.3.0/24. For IPv6, only prefix
    lengths will be permitted.
  • There will be additional command-line options -4' and-6', which will select a
    specific address family when hostnames are used, or when the default (unspecific)
    listening address is used.
  • Source address spoofing will be implemented in a different way for IPv6, namely
    using IN6_PKTINFO. This requires the spoofed source address to be configured as a
    local address on the machine.

@sleinen
Copy link
Owner Author

sleinen commented Feb 22, 2015

From simon.le...@gmail.com on March 03, 2010 13:57:35

I have some code, but I'm not quite happy about it: The IPv6 code may have portability
issues, and I'm not sure about the usefulness of the new limited spoofing, where the
spoofed source addresses must be configured on the machine samplicator runs on. In
addition, I reorganized the code throughly, so it'll be a while until I get to commit
this to the trunk. If anyone wants a pretest snapshot to help me weed out obvious
bugs, please let me know.

Status: Started

@sleinen
Copy link
Owner Author

sleinen commented Feb 22, 2015

From simon.le...@gmail.com on September 25, 2011 15:38:42

Basic support for IPv6 has finally been checked in. Please review revision r126 : https://code.google.com/p/samplicator/source/detail?r=126

Status: Fixed

@sleinen
Copy link
Owner Author

sleinen commented Feb 22, 2015

From morty.ab...@gmail.com on October 19, 2011 12:41:48

Any chance of getting spoofing for IPv6? I don't need this yet, but I eventually might. Thanks!

@sleinen
Copy link
Owner Author

sleinen commented Feb 22, 2015

From simon.le...@gmail.com on October 20, 2011 15:27:16

Good question, and maybe I shouldn't have closed this issue so fast. Let's discuss IPv6 spoofing mode support in issue #17 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant