-
Notifications
You must be signed in to change notification settings - Fork 133
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
Comments
From simon.le...@gmail.com on February 27, 2010 13:51:23 IPv6 support could be added as follows:
|
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 Status: Started |
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 |
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! |
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 |
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
The text was updated successfully, but these errors were encountered: