Problem with traceroute - Buster stock / Stretch kernels 4.19 / 5.0

Hi, I've already reported part of this to glibc mailing list since I was suspecting its incompatibility with newer kernel. https://lists.debian.org/debian-glibc/2019/03/msg00029.html My daemons started to stuck with kernel 4.19 / 5.0. Today I discovered there is always process of traceroute, which

Re: problem with traceroute

Scott Barker <[EMAIL PROTECTED]> writes: > Interesting. I've had no problems at all with BIND... If you're running a 1.2.x kernel and an unstable bind, zone transfers from your machine will fail (because it attempts to get the ip options, something not supported in 1.2.x, and on failure drops the

Re: problem with traceroute

Mark Eichin said: > There are actually a number of "unstable" packages that don't work > under 1.2.13 -- most have explicit dependencies (diald used to, for > example) but some don't. BIND, for example, needs the "ip_options" > support that was added in 1.3 (though I've submitted a reasonably > cle

Re: problem with traceroute

Scott Barker <[EMAIL PROTECTED]> writes: > traceroute: IP_HDRINCL: Protocol not available I've also noticed this under 1.2.13. (the same package works fine on my 1.3.79 machine, and I should really update both kernels...) There are actually a number of "unstable" packages that don't work under 1.

problem with traceroute

Since upgrading netstd to version 2.03-1, I'm getting the following error out of traceroute: traceroute: IP_HDRINCL: Protocol not available Is this because I'm still running a 1.2.13 kernel? Is the above protocol something new in 1.3.xx? -- Scott Barker Linux Consultant [EMAIL PROTECTED] http: