Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Шварц Сергей Владимирович" <svschwartz@gmail.com>
To: Ibrahim Tachijian <barhom@netsat.se>
Cc: wireguard@lists.zx2c4.com
Subject: Re: debian 8 setup
Date: Mon, 26 Jun 2017 18:40:59 +0300	[thread overview]
Message-ID: <CAEpXMn32ZqHF309UBr2b2+zA=zyScd1k9j7GBAaTD=6qD2Viyg@mail.gmail.com> (raw)
In-Reply-To: <CACTq0bR=+0wB1u6JJk=LuVxxKnPSGWp49bDtOb8oS666zkE8-Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]

Ibrahim,

I've rebooted the server and now it's ok.

Cheers,
Sergey


2017-06-26 14:55 GMT+03:00 Ibrahim Tachijian <barhom@netsat.se>:

> Hello Sergey,
>
> You have probably recently done an apt-get update upgrade that installed a
> newer kernel-image.
> I believe if you run,
>
>
>    - apt-get update and upgrade
>    - reboot
>    - rebuild wireguard from source (make, make install)
>
> Then wireguard should work for you.
>
> On Mon, Jun 26, 2017 at 1:35 PM Шварц Сергей Владимирович <
> svschwartz@gmail.com> wrote:
>
>> Hi guys!
>>
>> I've build debs for jessie from unstable dsc, but wireguard module failed
>> to load
>>
>> [34282909.202963] wireguard: Unknown symbol __sk_mem_reclaim_amount (err
>> 0)
>>
>> am I doing something wrong or is it jessie simply not supported ?
>>
>> Regards,
>> Sergey
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>>
> --
> *Ibrahim Tachijian*
>
> CEO Net Sat AB
> Mobile: +46723321377
> barhom@netsat.se
>
> _________________________
>
>
> *Net Sat ABC/O Jayway AB*Klara Östra Kyrkogata 2B, 1TR, 111 52 Stockholm,
> Sweden
> Office: +46 (0)8 408 394 53
>

[-- Attachment #2: Type: text/html, Size: 3361 bytes --]

  reply	other threads:[~2017-06-26 15:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-26 11:32 Шварц Сергей Владимирович
2017-06-26 11:55 ` Ibrahim Tachijian
2017-06-26 15:40   ` Шварц Сергей Владимирович [this message]
2017-06-26 17:00     ` Baptiste Jonglez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEpXMn32ZqHF309UBr2b2+zA=zyScd1k9j7GBAaTD=6qD2Viyg@mail.gmail.com' \
    --to=svschwartz@gmail.com \
    --cc=barhom@netsat.se \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).