Bug#731799: Do not work with IPv4 only anymore

2017-11-13 Thread Bernhard Schmidt
Control: fixed -1 0.86-1 On Mon, Dec 09, 2013 at 10:19:47PM +0100, Klaus Ethgen wrote: > Package: mtr-tiny > Version: 0.85-2 > Severity: grave > > The newest version refuse to work on IPv4 only nodes. [...] > For the records, I have no kernel on production systems that have IPv6 > enabled or

Bug#731799: Do not work with IPv4 only anymore

2014-04-28 Thread Rogier Wolff
On Sun, Apr 27, 2014 at 04:29:18PM +0200, Jeroen Massar wrote: This seems completely unrelated to mtr or let alone Debian... If your tunnel is broken, then report that to SixXS, there is a nice ticket system at https://www.sixxs.net/tickets/. Do provide actual details instead of making

Bug#731799: Do not work with IPv4 only anymore

2014-04-28 Thread Jeroen Massar
Note that there are a variety of forums that are a much better place than a Debian mtr package bug report for these kind of questions. On 2014-04-28 09:08, Rogier Wolff wrote: I personally have a good understanding of IPV4 and how I've secured my network against attacks from outside. I know

Bug#731799: Do not work with IPv4 only anymore

2014-04-28 Thread Rogier Wolff
On Mon, Apr 28, 2014 at 09:43:40AM +0200, Jeroen Massar wrote: Note that there are a variety of forums that are a much better place than a Debian mtr package bug report for these kind of questions. I'm not asking for help. I'm trying to communicate that I think that disabling IPV6 is a valid

Bug#731799: Do not work with IPv4 only anymore

2014-04-28 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Rogier, Am Mo den 28. Apr 2014 um 8:08 schrieb Rogier Wolff: [Problems with IPv6] Sorry, that I brought my objection against IPv6 into talk. It might be completely of topic for this bug. Maybe there is a better place to discuss this. Just to

Bug#731799: Do not work with IPv4 only anymore

2014-04-28 Thread Jeroen Massar
On 2014-04-28 10:45, Rogier Wolff wrote: On Mon, Apr 28, 2014 at 09:43:40AM +0200, Jeroen Massar wrote: Note that there are a variety of forums that are a much better place than a Debian mtr package bug report for these kind of questions. I'm not asking for help. I'm trying to communicate

Bug#731799: Do not work with IPv4 only anymore

2014-04-28 Thread Rogier Wolff
On Mon, Apr 28, 2014 at 12:02:50PM +0200, Jeroen Massar wrote: You're saying that masquerading makes my machine wide open? Bingo. It is no more secure than putting it directly on the network. See amongst others http://samy.pl/pwnat/ If I run software on a server inside the NAT it can give

Bug#731799: Do not work with IPv4 only anymore

2014-04-28 Thread Jeroen Massar
On 2014-04-28 13:07, Rogier Wolff wrote: On Mon, Apr 28, 2014 at 12:02:50PM +0200, Jeroen Massar wrote: You're saying that masquerading makes my machine wide open? Bingo. It is no more secure than putting it directly on the network. See amongst others http://samy.pl/pwnat/ If I run

Bug#731799: Do not work with IPv4 only anymore

2014-04-28 Thread Rogier Wolff
On Mon, Apr 28, 2014 at 02:00:47PM +0200, Jeroen Massar wrote: It is only a user-error from the perspective of disabling a current protocol. If you disable IPv4 your host won't even boot, even if you want it to be IPv6 only. Using IPv6 support of the networking API (getaddrinfo() and

Bug#731799: Do not work with IPv4 only anymore

2014-04-28 Thread Jeroen Massar
On 2014-04-28 14:26, Rogier Wolff wrote: On Mon, Apr 28, 2014 at 02:00:47PM +0200, Jeroen Massar wrote: It is only a user-error from the perspective of disabling a current protocol. If you disable IPv4 your host won't even boot, even if you want it to be IPv6 only. Using IPv6 support of the

Bug#731799: Do not work with IPv4 only anymore

2014-04-27 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am Sa den 26. Apr 2014 um 14:59 schrieb Philipp Kern: ~ mtr -4 www.heise.de My traceroute [v0.85] ikki (0.0.0.0)

Bug#731799: Do not work with IPv4 only anymore

2014-04-27 Thread Philipp Kern
On 2014-04-27 09:04, Klaus Ethgen wrote: And exactly that is the problem with IPv6. Due the dynamic nature of IPv6, you might be reachable from the net by accident if you have IPv6 enabled. If you don't use it and don't address it security wise the same that you do IPv4, you will be screwed.

Bug#731799: Do not work with IPv4 only anymore

2014-04-27 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, Am So den 27. Apr 2014 um 9:02 schrieb Philipp Kern: [one problem with automatic IPv6 stuff] You can also turn off the automatic configuration bits. True but your forgot the security best practice. And, who ever knows how to do this!?

Bug#731799: Do not work with IPv4 only anymore

2014-04-27 Thread Jeroen Massar
Klaus Ethgen wrote: But serious, I have no way to file a proper patch as I might accidental break IPv6 stuff as I have no real running IPv6. (My tunnel I have is broken everytime as init7, that provides it for sixxs, seems to not expect long running tunnels and breake it from time to time. So

Bug#731799: Do not work with IPv4 only anymore

2014-04-26 Thread Philipp Kern
Control: severity -1 important On Mon, Dec 09, 2013 at 10:19:47PM +0100, Klaus Ethgen wrote: The newest version refuse to work on IPv4 only nodes. ~ mtr -4 www.heise.de My traceroute [v0.85] ikki (0.0.0.0)

Bug#731799: Do not work with IPv4 only anymore

2014-03-19 Thread Axel Beckert
Hi Robert, Klaus Ethgen wrote: The newest version refuse to work on IPv4 only nodes. [...] Unable to allocate IPv6 socket for nameserver communication: Address family not supported by protocol Any news here? Regards, Axel -- ,''`. | Axel Beckert a...@debian.org,

Bug#731799: Do not work with IPv4 only anymore

2013-12-09 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: mtr-tiny Version: 0.85-2 Severity: grave The newest version refuse to work on IPv4 only nodes. ~ mtr -4 www.heise.de My traceroute [v0.85] ikki (0.0.0.0)