WireGuard Archive on lore.kernel.org
 help / Atom feed
* Logging remote connecting IP
@ 2019-01-16 15:39 Konstantin Ryabitsev
  2019-01-16 15:52 ` John
  0 siblings, 1 reply; 3+ messages in thread
From: Konstantin Ryabitsev @ 2019-01-16 15:39 UTC (permalink / raw)
  To: wireguard

Hello:

For auditing purposes, I would like to be able to log the remote
endpoint IP for each wg connection on the server side. What's the best
way to do this, preferably using syslog?

Best,
-K
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Logging remote connecting IP
  2019-01-16 15:39 Logging remote connecting IP Konstantin Ryabitsev
@ 2019-01-16 15:52 ` John
  2019-01-16 17:35   ` Konstantin Ryabitsev
  0 siblings, 1 reply; 3+ messages in thread
From: John @ 2019-01-16 15:52 UTC (permalink / raw)
  To: wireguard

[-- Attachment #1.1: Type: text/plain, Size: 553 bytes --]

Enable the debug option when building should print to dmesg.

On Wednesday, January 16, 2019, Konstantin Ryabitsev <
konstantin@linuxfoundation.org> wrote:

> Hello:
>
> For auditing purposes, I would like to be able to log the remote
> endpoint IP for each wg connection on the server side. What's the best
> way to do this, preferably using syslog?
>
> Best,
> -K
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
>


-- 
Sent from Gmail Mobile

[-- Attachment #1.2: Type: text/html, Size: 925 bytes --]

Enable the debug option when building should print to dmesg.<br><br>On Wednesday, January 16, 2019, Konstantin Ryabitsev &lt;<a href="mailto:konstantin@linuxfoundation.org">konstantin@linuxfoundation.org</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello:<br>
<br>
For auditing purposes, I would like to be able to log the remote<br>
endpoint IP for each wg connection on the server side. What&#39;s the best<br>
way to do this, preferably using syslog?<br>
<br>
Best,<br>
-K<br>
______________________________<wbr>_________________<br>
WireGuard mailing list<br>
<a href="mailto:WireGuard@lists.zx2c4.com">WireGuard@lists.zx2c4.com</a><br>
<a href="https://lists.zx2c4.com/mailman/listinfo/wireguard" target="_blank">https://lists.zx2c4.com/<wbr>mailman/listinfo/wireguard</a><br>
</blockquote><br><br>-- <br>Sent from Gmail Mobile<br>

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Logging remote connecting IP
  2019-01-16 15:52 ` John
@ 2019-01-16 17:35   ` Konstantin Ryabitsev
  0 siblings, 0 replies; 3+ messages in thread
From: Konstantin Ryabitsev @ 2019-01-16 17:35 UTC (permalink / raw)
  To: John; +Cc: wireguard

On Wed, Jan 16, 2019 at 10:52:48AM -0500, John wrote:
> > For auditing purposes, I would like to be able to log the remote
> > endpoint IP for each wg connection on the server side. What's the best
> > way to do this, preferably using syslog?
> 
> Enable the debug option when building should print to dmesg.

That's good to know, but not very useful in our case, because we get the
module from Fedora COPR. Moreover, I'd consider ability to log incoming
connections info-level, not debug-level logging.

-K
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-16 15:39 Logging remote connecting IP Konstantin Ryabitsev
2019-01-16 15:52 ` John
2019-01-16 17:35   ` Konstantin Ryabitsev

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com zx2c4-wireguard@archiver.kernel.org
	public-inbox-index wireguard


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/ public-inbox