Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #179068

Re: TTL expired in transit to qemu virtual machine.

Show all headers | View raw

On Mon, 20 Mar 2017, Mimiko wrote:
> On 18.03.2017 07:22, Igor Cicimov wrote:
>>     >uname -a
>>     Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.84-1 x86_64 GNU/Linux
>> 
>> That's an really old kernel, I don't start anything virtual these days 
>> without at least 3.13.x kernel.
>
> I regularly do apt-get upgrade, but not to next Debian version. So, how this 
> kernel be old for Debian 7?

TLDR:

  1. I have no clues to offer regarding OP's virtualisation/networking
  troubles, but I wish them the best of fortune.

  2. OP's kernel version does not look quite current to me, even for
  wheezy (debian 7) and it might be a matter of concern (though I claim
  no particular expertise).

Longer version:

It is not clear to me whether your question

> I regularly do apt-get upgrade, but not to next Debian version. So, how this 
> kernel be old for Debian 7?

is a request for information, or merely rhetorical (ie, an assertion
that your kernel is in fact current relative to debian 7).

In case you were asking, I'm still using debian 7 too,

   $ cat /etc/debian_version
   7.11

and, for what it's worth, in case it interests you

   $ uname -a
   Linux leviathan 3.2.0-4-686-pae #1 SMP Debian 3.2.86-1 i686 GNU/Linux

I notice the version you posted here (3.2.84-1) is slightly older than
mine. If like myself you plan on running the 3.2.0-4-* release for a
while, It might[1] be worth upgrading at least to version 3.2.86-1:

   https://security-tracker.debian.org/tracker/CVE-2016-5195

There is also a newer kernel release available, for those who choose
to install it explicitly[3], from the wheezy-backports repository[2],
(see the 3.16.0-0.bpo releases near the end):

   $ apt-cache search '^linux-image-*'
   linux-image-3.2.0-4-486 - Linux 3.2 for older PCs
   linux-image-3.2.0-4-686-pae - Linux 3.2 for modern PCs
   linux-image-3.2.0-4-686-pae-dbg - Debugging symbols for Linux 3.2.0-4-686-pae
   linux-image-3.2.0-4-amd64 - Linux 3.2 for 64-bit PCs
   linux-image-3.2.0-4-rt-686-pae - Linux 3.2 for modern PCs, PREEMPT_RT
   linux-image-3.2.0-4-rt-686-pae-dbg - Debugging symbols for Linux 3.2.0-4-rt-686-pae
   linux-image-2.6-486 - Linux for older PCs (dummy package)
   linux-image-2.6-686 - Linux for modern PCs (dummy package)
   linux-image-2.6-686-bigmem - Linux for PCs with 4GB+ RAM (dummy package)
   linux-image-2.6-686-pae - Linux for modern PCs (dummy package)
   linux-image-2.6-amd64 - Linux for 64-bit PCs (dummy package)
   linux-image-486 - Linux for older PCs (meta-package)
   linux-image-686 - Linux for modern PCs (dummy package)
   linux-image-686-bigmem - Linux for PCs with 4GB+ RAM (dummy package)
   linux-image-686-pae - Linux for modern PCs (meta-package)
   linux-image-amd64 - Linux for 64-bit PCs (meta-package)
   linux-image-rt-686-pae - Linux for modern PCs (meta-package), PREEMPT_RT
   linux-image-3.16.0-0.bpo.4-586 - Linux 3.16 for older PCs
   linux-image-3.16.0-0.bpo.4-686-pae - Linux 3.16 for modern PCs
   linux-image-3.16.0-0.bpo.4-686-pae-dbg - Debugging symbols for Linux 3.16.0-0.bpo.4-686-pae
   linux-image-3.16.0-0.bpo.4-amd64 - Linux 3.16 for 64-bit PCs
   linux-image-586 - Linux for older PCs (meta-package)
   linux-image-686-pae-dbg - Debugging symbols for Linux 686-pae configuration (meta-package)

But regarding backports, do see https://backports.debian.org/FAQ/

| Q: Is there security support for packages from backports.debian.org?
| 
| A: Unfortunately not. This is done on a best effort basis by the
| people who track the package, usually the ones who originally did
| upload the package into backports. When security related bugs are
| fixed in Debian unstable the backporter is permitted to upload the
| package from directly there instead of having to wait until the fix
| hits testing. You can see the open issues for wheezy-backports in
| the security tracker (though there may be false positives too, the
| version compare isn't perfect yet)

[1] The security-tracker page for CVE-2016-5195 lists version 78-1 as
     'vulnerable', and 86-1 as 'fixed'. It is unclear to me what this
     is supposed to say about OP's kernel, which is apparently at 84-1.

[2] https://backports.debian.org/Instructions/#index2h2
[3] https://backports.debian.org/Instructions/#index3h2

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

TTL expired in transit to qemu virtual machine. Mimiko <vbvbrj@gmail.com> - 2017-03-17 12:00 +0100
  Re: TTL expired in transit to qemu virtual machine. Dominik George <nik@naturalnet.de> - 2017-03-17 12:30 +0100
    Re: TTL expired in transit to qemu virtual machine. Mimiko <vbvbrj@gmail.com> - 2017-03-20 07:30 +0100
  Re: TTL expired in transit to qemu virtual machine. Igor Cicimov <icicimov@gmail.com> - 2017-03-18 06:30 +0100
    Re: TTL expired in transit to qemu virtual machine. Mimiko <vbvbrj@gmail.com> - 2017-03-20 07:50 +0100
      Re: TTL expired in transit to qemu virtual machine. davidson@freevolt.org - 2017-03-21 01:30 +0100
        Re: TTL expired in transit to qemu virtual machine. Mimiko <vbvbrj@gmail.com> - 2017-03-23 07:40 +0100
          Re: TTL expired in transit to qemu virtual machine. Greg Wooledge <wooledg@eeg.ccf.org> - 2017-03-23 13:20 +0100
            Re: TTL expired in transit to qemu virtual machine. Mimiko <vbvbrj@gmail.com> - 2017-03-24 12:00 +0100

csiph-web