From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Roman Chumakov <roman.chumakov@dtms.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: SIP/SDP Issue
Date: Sat, 4 Apr 2020 16:59:15 -0600 [thread overview]
Message-ID: <CAHmME9rkTZPVGmvOCcemNJwvn-J3+-gdXDVigSm-TOp8vQNsog@mail.gmail.com> (raw)
In-Reply-To: <16959081-aaec-9187-8893-8b627054ec2a@dtms.de>
"It doesn't work with some unspecified software" means that we can't
and won't do anything, since how could we?
- What is the name of the software? Is it open source? Is it free?
Have you reverse engineered any of it?
- What debugging have you done already to conclude it has to do with
the ip address being recognized?
- What debugging have you done already to conclude it has to do with
the sdp proto?
This is a technical mailing list; we need technical details to fix things.
prev parent reply other threads:[~2020-04-04 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 16:44 Roman Chumakov
2020-04-04 22:59 ` Jason A. Donenfeld [this message]
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=CAHmME9rkTZPVGmvOCcemNJwvn-J3+-gdXDVigSm-TOp8vQNsog@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=roman.chumakov@dtms.de \
--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).