Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    System log tun_wg0: loop detected

    Scheduled Pinned Locked Moved General pfSense Questions
    22 Posts 3 Posters 3.0k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • stephenw10S
      stephenw10 Netgate Administrator @pfguy2018
      last edited by

      Can we see the logs?

      Can we see the WG config?

      I assume this is in 2.5.2?

      Steve

      P 2 Replies Last reply Reply Quote 0
      • P
        pfguy2018 @stephenw10
        last edited by

        @stephenw10
        Here is a snippet of the log, containing the entry before and after:
        Dec 6 12:30:00 php 85969 rc.update_urltables: /etc/rc.update_urltables: Starting up.
        Dec 6 11:22:57 kernel tun_wg0: loop detected
        Dec 6 11:22:52 kernel tun_wg0: loop detected
        Dec 6 11:22:47 kernel tun_wg0: loop detected
        Dec 6 11:22:41 kernel tun_wg0: loop detected
        Dec 6 11:22:40 kernel tun_wg0: loop detected
        Dec 6 11:22:37 kernel tun_wg0: loop detected
        Dec 6 11:22:36 kernel tun_wg0: loop detected
        Dec 6 11:22:36 kernel tun_wg0: loop detected
        Dec 6 11:22:35 kernel tun_wg0: loop detected
        Dec 6 11:22:31 kernel tun_wg0: loop detected
        Dec 6 11:22:29 kernel tun_wg0: loop detected
        Dec 6 11:22:26 kernel tun_wg0: loop detected
        Dec 6 11:22:26 kernel tun_wg0: loop detected
        Dec 6 11:22:24 kernel tun_wg0: loop detected
        Dec 6 11:22:21 kernel tun_wg0: loop detected
        Dec 6 11:22:19 kernel tun_wg0: loop detected
        Dec 6 11:22:16 kernel tun_wg0: loop detected
        Dec 6 11:22:14 kernel tun_wg0: loop detected
        Dec 6 11:22:11 kernel tun_wg0: loop detected
        Dec 6 11:22:09 kernel tun_wg0: loop detected
        Dec 6 11:22:09 kernel tun_wg0: loop detected
        Dec 6 11:22:08 kernel tun_wg0: loop detected
        Dec 6 11:22:05 kernel tun_wg0: loop detected
        Dec 6 11:22:04 kernel tun_wg0: loop detected
        Dec 6 11:22:03 kernel tun_wg0: loop detected
        Dec 6 11:21:59 kernel tun_wg0: loop detected
        Dec 6 11:21:59 kernel tun_wg0: loop detected
        Dec 6 11:21:58 kernel tun_wg0: loop detected
        Dec 6 11:08:52 kernel tun_wg0: loop detected
        Dec 6 11:08:46 kernel tun_wg0: loop detected
        Dec 6 11:08:43 kernel tun_wg0: loop detected
        Dec 6 11:08:41 kernel tun_wg0: loop detected
        Dec 6 11:08:37 kernel tun_wg0: loop detected
        Dec 6 11:08:36 kernel tun_wg0: loop detected
        Dec 6 11:08:35 kernel tun_wg0: loop detected
        Dec 6 11:08:35 kernel tun_wg0: loop detected
        Dec 6 11:08:32 kernel tun_wg0: loop detected
        Dec 6 11:08:31 kernel tun_wg0: loop detected
        Dec 6 11:08:27 kernel tun_wg0: loop detected
        Dec 6 11:08:26 kernel tun_wg0: loop detected
        Dec 6 11:08:25 kernel tun_wg0: loop detected
        Dec 6 11:08:25 kernel tun_wg0: loop detected
        Dec 6 11:08:22 kernel tun_wg0: loop detected
        Dec 6 11:08:20 kernel tun_wg0: loop detected
        Dec 6 11:08:20 kernel tun_wg0: loop detected
        Dec 6 11:08:20 kernel tun_wg0: loop detected
        Dec 6 11:08:18 kernel tun_wg0: loop detected
        Dec 6 11:08:18 kernel tun_wg0: loop detected
        Dec 6 11:08:17 kernel tun_wg0: loop detected
        Dec 6 11:08:17 kernel tun_wg0: loop detected
        Dec 6 11:08:17 kernel tun_wg0: loop detected
        Dec 6 11:08:16 kernel tun_wg0: loop detected
        Dec 6 11:08:16 kernel tun_wg0: loop detected
        Dec 6 11:08:15 kernel tun_wg0: loop detected
        Dec 6 11:08:14 kernel tun_wg0: loop detected
        Dec 6 11:08:14 kernel tun_wg0: loop detected
        Dec 6 11:08:14 kernel tun_wg0: loop detected
        Dec 6 11:08:14 kernel tun_wg0: loop detected
        Dec 6 11:08:14 kernel tun_wg0: loop detected
        Dec 6 11:08:14 kernel tun_wg0: loop detected
        Dec 6 11:08:13 kernel tun_wg0: loop detected
        Dec 6 11:08:13 kernel tun_wg0: loop detected
        Dec 6 11:08:12 kernel tun_wg0: loop detected
        Dec 6 11:08:10 kernel tun_wg0: loop detected
        Dec 6 11:08:07 kernel tun_wg0: loop detected
        Dec 6 11:08:05 kernel tun_wg0: loop detected
        Dec 6 11:08:02 kernel tun_wg0: loop detected
        Dec 6 11:07:59 kernel tun_wg0: loop detected
        Dec 6 11:07:56 kernel tun_wg0: loop detected
        Dec 6 11:07:54 kernel tun_wg0: loop detected
        Dec 6 11:07:51 kernel tun_wg0: loop detected
        Dec 6 11:07:49 kernel tun_wg0: loop detected
        Dec 6 11:07:46 kernel tun_wg0: loop detected
        Dec 6 11:07:44 kernel tun_wg0: loop detected
        Dec 6 11:07:41 kernel tun_wg0: loop detected
        Dec 6 11:07:38 kernel tun_wg0: loop detected
        Dec 6 11:07:35 kernel tun_wg0: loop detected
        Dec 6 11:07:33 kernel tun_wg0: loop detected
        Dec 6 11:07:30 kernel tun_wg0: loop detected
        Dec 6 11:07:28 kernel tun_wg0: loop detected
        Dec 6 11:07:25 kernel tun_wg0: loop detected
        Dec 6 11:07:23 kernel tun_wg0: loop detected
        Dec 6 11:07:20 kernel tun_wg0: loop detected
        Dec 6 11:07:17 kernel tun_wg0: loop detected
        Dec 6 11:07:15 kernel tun_wg0: loop detected
        Dec 6 11:07:12 kernel tun_wg0: loop detected
        Dec 6 11:07:10 kernel tun_wg0: loop detected
        Dec 6 11:07:04 kernel tun_wg0: loop detected
        Dec 6 11:03:00 kernel tun_wg0: loop detected
        Dec 6 11:02:55 kernel tun_wg0: loop detected
        Dec 6 11:02:52 kernel tun_wg0: loop detected
        Dec 6 11:02:50 kernel tun_wg0: loop detected
        Dec 6 11:02:47 kernel tun_wg0: loop detected
        Dec 6 11:02:45 kernel tun_wg0: loop detected
        Dec 6 11:02:45 kernel tun_wg0: loop detected
        Dec 6 11:02:43 kernel tun_wg0: loop detected
        Dec 6 11:02:42 kernel tun_wg0: loop detected
        Dec 6 11:02:41 kernel tun_wg0: loop detected
        Dec 6 11:02:40 kernel tun_wg0: loop detected
        Dec 6 11:02:40 kernel tun_wg0: loop detected
        Dec 6 11:02:40 kernel tun_wg0: loop detected
        Dec 6 11:02:40 kernel tun_wg0: loop detected
        Dec 6 11:02:34 kernel tun_wg0: loop detected
        Dec 6 11:02:29 kernel tun_wg0: loop detected
        Dec 6 11:02:24 kernel tun_wg0: loop detected
        Dec 6 11:02:19 kernel tun_wg0: loop detected
        Dec 6 11:02:14 kernel tun_wg0: loop detected
        Dec 6 11:02:08 kernel tun_wg0: loop detected
        Dec 6 10:52:27 kernel tun_wg0: loop detected
        Dec 6 10:52:23 kernel tun_wg0: loop detected
        Dec 6 10:52:22 kernel tun_wg0: loop detected
        Dec 6 10:52:16 kernel tun_wg0: loop detected
        Dec 6 10:48:14 kernel tun_wg0: loop detected
        Dec 6 10:48:09 kernel tun_wg0: loop detected
        Dec 6 10:48:04 kernel tun_wg0: loop detected
        Dec 6 10:47:59 kernel tun_wg0: loop detected
        Dec 6 10:47:53 kernel tun_wg0: loop detected
        Dec 6 10:47:48 kernel tun_wg0: loop detected
        Dec 6 10:47:43 kernel tun_wg0: loop detected
        Dec 6 10:47:38 kernel tun_wg0: loop detected
        Dec 6 10:47:33 kernel tun_wg0: loop detected
        Dec 6 10:47:28 kernel tun_wg0: loop detected
        Dec 6 10:47:23 kernel tun_wg0: loop detected
        Dec 6 10:47:17 kernel tun_wg0: loop detected
        Dec 6 10:47:12 kernel tun_wg0: loop detected
        Dec 6 10:47:07 kernel tun_wg0: loop detected
        Dec 6 10:42:20 kernel tun_wg0: loop detected
        Dec 6 10:42:15 kernel tun_wg0: loop detected
        Dec 6 10:42:10 kernel tun_wg0: loop detected
        Dec 6 10:42:04 kernel tun_wg0: loop detected
        Dec 6 10:41:59 kernel tun_wg0: loop detected
        Dec 6 10:37:29 kernel tun_wg0: loop detected
        Dec 6 10:37:29 kernel tun_wg0: loop detected
        Dec 6 10:37:28 kernel tun_wg0: loop detected
        Dec 6 10:37:26 kernel tun_wg0: loop detected
        Dec 6 10:37:26 kernel tun_wg0: loop detected
        Dec 6 10:37:26 kernel tun_wg0: loop detected
        Dec 6 10:37:24 kernel tun_wg0: loop detected
        Dec 6 10:37:19 kernel tun_wg0: loop detected
        Dec 6 10:37:14 kernel tun_wg0: loop detected
        Dec 6 10:37:09 kernel tun_wg0: loop detected
        Dec 6 10:37:03 kernel tun_wg0: loop detected
        Dec 6 10:32:57 kernel tun_wg0: loop detected
        Dec 6 10:32:52 kernel tun_wg0: loop detected
        Dec 6 10:32:47 kernel tun_wg0: loop detected
        Dec 6 10:32:42 kernel tun_wg0: loop detected
        Dec 6 10:32:42 kernel tun_wg0: loop detected
        Dec 6 10:32:37 kernel tun_wg0: loop detected
        Dec 6 10:32:36 kernel tun_wg0: loop detected
        Dec 6 10:32:31 kernel tun_wg0: loop detected
        Dec 6 10:32:30 kernel tun_wg0: loop detected
        Dec 6 10:32:26 kernel tun_wg0: loop detected
        Dec 6 10:32:24 kernel tun_wg0: loop detected
        Dec 6 10:32:21 kernel tun_wg0: loop detected
        Dec 6 10:32:21 kernel tun_wg0: loop detected
        Dec 6 10:32:19 kernel tun_wg0: loop detected
        Dec 6 10:32:18 kernel tun_wg0: loop detected
        Dec 6 10:32:18 kernel tun_wg0: loop detected
        Dec 6 10:32:18 kernel tun_wg0: loop detected
        Dec 6 10:32:18 kernel tun_wg0: loop detected
        Dec 6 10:32:16 kernel tun_wg0: loop detected
        Dec 6 10:32:11 kernel tun_wg0: loop detected
        Dec 6 10:32:09 kernel tun_wg0: loop detected
        Dec 6 10:32:05 kernel tun_wg0: loop detected
        Dec 6 10:07:36 kernel tun_wg0: loop detected
        Dec 6 10:07:31 kernel tun_wg0: loop detected
        Dec 6 10:07:25 kernel tun_wg0: loop detected
        Dec 6 10:07:20 kernel tun_wg0: loop detected
        Dec 6 10:07:15 kernel tun_wg0: loop detected
        Dec 6 10:07:10 kernel tun_wg0: loop detected
        Dec 6 10:03:51 kernel tun_wg0: loop detected
        Dec 6 10:03:48 kernel tun_wg0: loop detected
        Dec 6 10:03:46 kernel tun_wg0: loop detected
        Dec 6 10:03:41 kernel tun_wg0: loop detected
        Dec 6 10:03:36 kernel tun_wg0: loop detected
        Dec 6 10:03:31 kernel tun_wg0: loop detected
        Dec 6 10:03:26 kernel tun_wg0: loop detected
        Dec 6 10:03:21 kernel tun_wg0: loop detected
        Dec 6 10:03:15 kernel tun_wg0: loop detected
        Dec 6 10:03:10 kernel tun_wg0: loop detected
        Dec 6 10:03:05 kernel tun_wg0: loop detected
        Dec 6 10:03:00 kernel tun_wg0: loop detected
        Dec 6 10:02:55 kernel tun_wg0: loop detected
        Dec 6 10:02:51 kernel tun_wg0: loop detected
        Dec 6 10:02:50 kernel tun_wg0: loop detected
        Dec 6 10:02:44 kernel tun_wg0: loop detected
        Dec 6 10:02:39 kernel tun_wg0: loop detected
        Dec 6 10:02:34 kernel tun_wg0: loop detected
        Dec 6 10:02:29 kernel tun_wg0: loop detected
        Dec 6 10:02:24 kernel tun_wg0: loop detected
        Dec 6 10:02:23 kernel tun_wg0: loop detected
        Dec 6 10:02:18 kernel tun_wg0: loop detected
        Dec 6 10:02:13 kernel tun_wg0: loop detected
        Dec 6 09:53:48 kernel tun_wg0: loop detected
        Dec 6 09:53:43 kernel tun_wg0: loop detected
        Dec 6 09:53:38 kernel tun_wg0: loop detected
        Dec 6 09:53:32 kernel tun_wg0: loop detected
        Dec 6 09:53:27 kernel tun_wg0: loop detected
        Dec 6 09:53:22 kernel tun_wg0: loop detected
        Dec 6 09:53:18 kernel tun_wg0: loop detected
        Dec 6 09:53:17 kernel tun_wg0: loop detected
        Dec 6 09:53:12 kernel tun_wg0: loop detected
        Dec 6 09:53:08 kernel tun_wg0: loop detected
        Dec 6 09:53:07 kernel tun_wg0: loop detected
        Dec 6 09:53:04 kernel tun_wg0: loop detected
        Dec 6 09:53:01 kernel tun_wg0: loop detected
        Dec 6 09:53:01 kernel tun_wg0: loop detected
        Dec 6 09:53:00 kernel tun_wg0: loop detected
        Dec 6 09:52:59 kernel tun_wg0: loop detected
        Dec 6 09:52:59 kernel tun_wg0: loop detected
        Dec 6 09:52:59 kernel tun_wg0: loop detected
        Dec 6 09:52:58 kernel tun_wg0: loop detected
        Dec 6 09:52:58 kernel tun_wg0: loop detected
        Dec 6 09:52:57 kernel tun_wg0: loop detected
        Dec 6 09:52:57 kernel tun_wg0: loop detected
        Dec 6 09:52:57 kernel tun_wg0: loop detected
        Dec 6 09:52:57 kernel tun_wg0: loop detected
        Dec 6 09:52:56 kernel tun_wg0: loop detected
        Dec 6 09:52:56 kernel tun_wg0: loop detected
        Dec 6 09:52:56 kernel tun_wg0: loop detected
        Dec 6 09:52:53 kernel tun_wg0: loop detected
        Dec 6 09:52:51 kernel tun_wg0: loop detected
        Dec 6 09:52:48 kernel tun_wg0: loop detected
        Dec 6 09:52:45 kernel tun_wg0: loop detected
        Dec 6 09:52:43 kernel tun_wg0: loop detected
        Dec 6 09:52:40 kernel tun_wg0: loop detected
        Dec 6 09:52:38 kernel tun_wg0: loop detected
        Dec 6 09:52:35 kernel tun_wg0: loop detected
        Dec 6 09:52:33 kernel tun_wg0: loop detected
        Dec 6 09:52:30 kernel tun_wg0: loop detected
        Dec 6 09:52:27 kernel tun_wg0: loop detected
        Dec 6 09:52:25 kernel tun_wg0: loop detected
        Dec 6 09:52:22 kernel tun_wg0: loop detected
        Dec 6 09:52:19 kernel tun_wg0: loop detected
        Dec 6 09:52:17 kernel tun_wg0: loop detected
        Dec 6 09:52:14 kernel tun_wg0: loop detected
        Dec 6 09:52:12 kernel tun_wg0: loop detected
        Dec 6 09:52:09 kernel tun_wg0: loop detected
        Dec 6 09:52:07 kernel tun_wg0: loop detected
        Dec 6 09:52:02 kernel tun_wg0: loop detected
        Dec 6 09:48:40 kernel tun_wg0: loop detected
        Dec 6 09:48:35 kernel tun_wg0: loop detected
        Dec 6 09:48:30 kernel tun_wg0: loop detected
        Dec 6 09:48:24 kernel tun_wg0: loop detected
        Dec 6 09:48:24 kernel tun_wg0: loop detected
        Dec 6 09:48:19 kernel tun_wg0: loop detected
        Dec 6 09:48:19 kernel tun_wg0: loop detected
        Dec 6 09:48:14 kernel tun_wg0: loop detected
        Dec 6 09:48:14 kernel tun_wg0: loop detected
        Dec 6 09:48:09 kernel tun_wg0: loop detected
        Dec 6 09:48:09 kernel tun_wg0: loop detected
        Dec 6 09:48:04 kernel tun_wg0: loop detected
        Dec 6 09:48:04 kernel tun_wg0: loop detected
        Dec 6 09:47:59 kernel tun_wg0: loop detected
        Dec 6 09:47:59 kernel tun_wg0: loop detected
        Dec 6 09:47:53 kernel tun_wg0: loop detected
        Dec 6 09:47:53 kernel tun_wg0: loop detected
        Dec 6 09:47:48 kernel tun_wg0: loop detected
        Dec 6 09:47:48 kernel tun_wg0: loop detected
        Dec 6 09:47:43 kernel tun_wg0: loop detected
        Dec 6 09:47:43 kernel tun_wg0: loop detected
        Dec 6 09:47:38 kernel tun_wg0: loop detected
        Dec 6 09:47:38 kernel tun_wg0: loop detected
        Dec 6 09:47:33 kernel tun_wg0: loop detected
        Dec 6 09:47:32 kernel tun_wg0: loop detected
        Dec 6 09:47:28 kernel tun_wg0: loop detected
        Dec 6 09:47:27 kernel tun_wg0: loop detected
        Dec 6 09:47:22 kernel tun_wg0: loop detected
        Dec 6 09:47:22 kernel tun_wg0: loop detected
        Dec 6 09:47:18 kernel tun_wg0: loop detected
        Dec 6 09:47:17 kernel tun_wg0: loop detected
        Dec 6 09:47:12 kernel tun_wg0: loop detected
        Dec 6 09:47:12 kernel tun_wg0: loop detected
        Dec 6 09:47:07 kernel tun_wg0: loop detected
        Dec 6 09:47:07 kernel tun_wg0: loop detected
        Dec 6 09:47:02 kernel tun_wg0: loop detected
        Dec 6 09:47:02 kernel tun_wg0: loop detected
        Dec 6 09:44:03 kernel tun_wg0: loop detected
        Dec 6 09:43:45 kernel tun_wg0: loop detected
        Dec 6 09:43:40 kernel tun_wg0: loop detected
        Dec 6 09:43:39 kernel tun_wg0: loop detected
        Dec 6 09:43:35 kernel tun_wg0: loop detected
        Dec 6 09:43:30 kernel tun_wg0: loop detected
        Dec 6 09:43:27 kernel tun_wg0: loop detected
        Dec 6 09:43:25 kernel tun_wg0: loop detected
        Dec 6 09:43:21 kernel tun_wg0: loop detected
        Dec 6 09:43:20 kernel tun_wg0: loop detected
        Dec 6 09:43:20 kernel tun_wg0: loop detected
        Dec 6 09:43:20 kernel tun_wg0: loop detected
        Dec 6 09:43:14 kernel tun_wg0: loop detected
        Dec 6 09:43:09 kernel tun_wg0: loop detected
        Dec 6 09:43:04 kernel tun_wg0: loop detected
        Dec 6 09:42:59 kernel tun_wg0: loop detected
        Dec 6 09:42:54 kernel tun_wg0: loop detected
        Dec 6 09:42:49 kernel tun_wg0: loop detected
        Dec 6 09:42:43 kernel tun_wg0: loop detected
        Dec 6 09:42:38 kernel tun_wg0: loop detected
        Dec 6 09:42:33 kernel tun_wg0: loop detected
        Dec 6 09:42:28 kernel tun_wg0: loop detected
        Dec 6 09:42:23 kernel tun_wg0: loop detected
        Dec 6 09:42:17 kernel tun_wg0: loop detected
        Dec 6 09:42:12 kernel tun_wg0: loop detected
        Dec 6 09:42:07 kernel tun_wg0: loop detected
        Dec 6 09:31:58 kernel tun_wg0: loop detected
        Dec 6 09:31:53 kernel tun_wg0: loop detected
        Dec 6 09:28:49 kernel tun_wg0: loop detected
        Dec 6 09:28:44 kernel tun_wg0: loop detected
        Dec 6 09:28:33 apcupsd 94530 Power is back. UPS running on mains.
        Dec 6 09:28:32 apcupsd 94530 Power failure.
        Dec 6 09:18:36 kernel tun_wg0: loop detected
        Dec 6 09:18:30 kernel tun_wg0: loop detected
        Dec 6 09:18:25 kernel tun_wg0: loop detected
        Dec 6 09:18:20 kernel tun_wg0: loop detected
        Dec 6 09:18:15 kernel tun_wg0: loop detected
        Dec 6 09:18:10 kernel tun_wg0: loop detected
        Dec 6 09:18:05 kernel tun_wg0: loop detected
        Dec 6 09:18:00 kernel tun_wg0: loop detected
        Dec 6 09:17:55 kernel tun_wg0: loop detected
        Dec 6 09:17:49 kernel tun_wg0: loop detected
        Dec 6 09:17:44 kernel tun_wg0: loop detected
        Dec 6 09:17:39 kernel tun_wg0: loop detected
        Dec 6 09:17:34 kernel tun_wg0: loop detected
        Dec 6 09:17:29 kernel tun_wg0: loop detected
        Dec 6 09:17:24 kernel tun_wg0: loop detected
        Dec 6 09:17:18 kernel tun_wg0: loop detected
        Dec 6 09:17:13 kernel tun_wg0: loop detected
        Dec 6 09:17:08 kernel tun_wg0: loop detected
        Dec 6 09:17:03 kernel tun_wg0: loop detected
        Dec 6 09:16:58 kernel tun_wg0: loop detected
        Dec 6 09:14:13 kernel tun_wg0: loop detected
        Dec 6 09:14:04 kernel tun_wg0: loop detected
        Dec 6 09:13:58 kernel tun_wg0: loop detected
        Dec 6 09:13:42 kernel tun_wg0: loop detected
        Dec 6 09:13:38 kernel tun_wg0: loop detected
        Dec 6 09:13:37 kernel tun_wg0: loop detected
        Dec 6 09:13:32 kernel tun_wg0: loop detected
        Dec 6 09:13:27 kernel tun_wg0: loop detected
        Dec 6 09:13:21 kernel tun_wg0: loop detected
        Dec 6 09:13:19 kernel tun_wg0: loop detected
        Dec 6 09:13:16 kernel tun_wg0: loop detected
        Dec 6 09:13:11 kernel tun_wg0: loop detected
        Dec 6 09:13:10 kernel tun_wg0: loop detected
        Dec 6 09:13:06 kernel tun_wg0: loop detected
        Dec 6 09:13:05 kernel tun_wg0: loop detected
        Dec 6 09:13:05 kernel tun_wg0: loop detected
        Dec 6 09:13:03 kernel tun_wg0: loop detected
        Dec 6 09:13:01 kernel tun_wg0: loop detected
        Dec 6 09:13:01 kernel tun_wg0: loop detected
        Dec 6 09:13:00 kernel tun_wg0: loop detected
        Dec 6 09:12:59 kernel tun_wg0: loop detected
        Dec 6 09:12:58 kernel tun_wg0: loop detected
        Dec 6 09:12:58 kernel tun_wg0: loop detected
        Dec 6 09:12:58 kernel tun_wg0: loop detected
        Dec 6 09:12:58 kernel tun_wg0: loop detected
        Dec 6 09:12:56 kernel tun_wg0: loop detected
        Dec 6 09:12:50 kernel tun_wg0: loop detected
        Dec 6 09:12:45 kernel tun_wg0: loop detected
        Dec 6 09:12:40 kernel tun_wg0: loop detected
        Dec 6 09:12:35 kernel tun_wg0: loop detected
        Dec 6 09:12:35 kernel tun_wg0: loop detected
        Dec 6 09:12:29 kernel tun_wg0: loop detected
        Dec 6 09:12:24 kernel tun_wg0: loop detected
        Dec 6 09:12:19 kernel tun_wg0: loop detected
        Dec 6 09:12:18 kernel tun_wg0: loop detected
        Dec 6 09:12:18 kernel tun_wg0: loop detected
        Dec 6 09:12:18 kernel tun_wg0: loop detected
        Dec 6 09:12:14 kernel tun_wg0: loop detected
        Dec 6 09:12:08 kernel tun_wg0: loop detected
        Dec 6 09:12:04 kernel tun_wg0: loop detected
        Dec 6 09:07:01 kernel tun_wg0: loop detected
        Dec 6 09:07:00 kernel tun_wg0: loop detected
        Dec 6 09:07:00 kernel tun_wg0: loop detected
        Dec 6 09:07:00 kernel tun_wg0: loop detected
        Dec 6 09:07:00 kernel tun_wg0: loop detected
        Dec 6 09:06:59 kernel tun_wg0: loop detected
        Dec 6 09:06:59 kernel tun_wg0: loop detected
        Dec 6 09:06:58 kernel tun_wg0: loop detected
        Dec 6 09:06:58 kernel tun_wg0: loop detected
        Dec 6 09:06:58 kernel tun_wg0: loop detected
        Dec 6 09:06:56 kernel tun_wg0: loop detected
        Dec 6 09:03:39 kernel tun_wg0: loop detected
        Dec 6 09:03:34 kernel tun_wg0: loop detected
        Dec 6 09:03:29 kernel tun_wg0: loop detected
        Dec 6 09:03:23 kernel tun_wg0: loop detected
        Dec 6 09:03:18 kernel tun_wg0: loop detected
        Dec 6 09:03:13 kernel tun_wg0: loop detected
        Dec 6 09:03:08 kernel tun_wg0: loop detected
        Dec 6 09:03:03 kernel tun_wg0: loop detected
        Dec 6 09:02:57 kernel tun_wg0: loop detected
        Dec 6 09:02:52 kernel tun_wg0: loop detected
        Dec 6 09:02:47 kernel tun_wg0: loop detected
        Dec 6 09:02:42 kernel tun_wg0: loop detected
        Dec 6 09:02:37 kernel tun_wg0: loop detected
        Dec 6 09:02:32 kernel tun_wg0: loop detected
        Dec 6 09:02:26 kernel tun_wg0: loop detected
        Dec 6 09:02:21 kernel tun_wg0: loop detected
        Dec 6 09:02:16 kernel tun_wg0: loop detected
        Dec 6 09:02:11 kernel tun_wg0: loop detected
        Dec 6 09:02:06 kernel tun_wg0: loop detected
        Dec 6 09:02:01 kernel tun_wg0: loop detected
        Dec 6 08:59:01 php-fpm 605 /index.php: Successful login for user 'admin' from: 192.168.133.21 (Local Database)
        Dec 6 08:52:20 kernel tun_wg0: loop detected
        Dec 6 08:52:19 kernel tun_wg0: loop detected
        Dec 6 08:52:19 kernel tun_wg0: loop detected
        Dec 6 08:52:18 kernel tun_wg0: loop detected
        Dec 6 08:52:17 kernel tun_wg0: loop detected
        Dec 6 08:52:17 kernel tun_wg0: loop detected
        Dec 6 08:52:17 kernel tun_wg0: loop detected
        Dec 6 08:52:17 kernel tun_wg0: loop detected
        Dec 6 08:52:17 kernel tun_wg0: loop detected
        Dec 6 08:52:14 kernel tun_wg0: loop detected
        Dec 6 08:52:09 kernel tun_wg0: loop detected
        Dec 6 08:52:03 kernel tun_wg0: loop detected
        Dec 6 08:51:58 kernel tun_wg0: loop detected
        Dec 6 08:51:53 kernel tun_wg0: loop detected
        Dec 6 02:45:19 php 79996 [Snort] The Rules update has finished.

        1 Reply Last reply Reply Quote 0
        • P
          pfguy2018 @stephenw10
          last edited by

          @stephenw10 said in System log tun_wg0: loop detected:

          Can we see the WG config?

          What exactly should I be showing here? Not sure what it is that would be helpful to share?

          P 1 Reply Last reply Reply Quote 0
          • P
            pfguy2018 @pfguy2018
            last edited by

            I think I might have figured out the problem. Somehow when WG was set up, I created both an interface group (WireGuard) and an interface (WireGuardVPN - which was a member of the group). I wonder whether traffic was being passed back and forth between those 2? I deleted both and set up just an interface. Will see if that fixes the problem.

            1 Reply Last reply Reply Quote 0
            • stephenw10S
              stephenw10 Netgate Administrator
              last edited by

              It shouldn't be unless you have something bridged. That only governs where/how the firewall rules are applied.

              P 2 Replies Last reply Reply Quote 0
              • P
                pfguy2018 @stephenw10
                last edited by

                @stephenw10
                Hmm. I will monitor the logs over the next few days to see whether that message comes back or not.

                1 Reply Last reply Reply Quote 0
                • P
                  pfguy2018 @stephenw10
                  last edited by

                  @stephenw10 said in System log tun_wg0: loop detected:

                  It shouldn't be unless you have something bridged. That only governs where/how the firewall rules are applied.

                  I checked the system log again today, and found tons of the same message (tun_wg0: loop detected).

                  I have nothing bridged (i.e. under interfaces -- bridges, there is nothing listed)

                  Is there anything else I can check to shed some light on this?

                  FWIW, the WG connections appear to be functioning just fine, even when these messages are appearing in the log.

                  stephenw10S 1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator @pfguy2018
                    last edited by

                    That log message is generated by this:
                    https://github.com/pfsense/FreeBSD-src/blob/RELENG_2_5_2/sys/net/if.c#L4010

                    So I would expect it's because you have somehow configured some sort of recursion. Like maybe a peer endpoint inside the tunnel interface subnet.

                    Steve

                    P 1 Reply Last reply Reply Quote 0
                    • P
                      pfguy2018 @stephenw10
                      last edited by

                      @stephenw10

                      Not exactly sure what that means. But my configuration is:
                      "Wireguard" interface (OPT1) is assigned to tun_wg0 with static IPv4 192.168.133.1/24
                      Peers are (manually) assigned IP addresses between 192.168.133.20 through 192.168.133.60
                      DNS is 192.168.133.1
                      What would be the source of the recursion?

                      1 Reply Last reply Reply Quote 0
                      • stephenw10S
                        stephenw10 Netgate Administrator
                        last edited by

                        The peers can have an IP that's inside the subnet as long as that's not the end point IP. Each peer doesn't really care about other other peers IP since routing is all done on the keys.

                        Steve

                        P 1 Reply Last reply Reply Quote 0
                        • P
                          pfguy2018 @stephenw10
                          last edited by

                          @stephenw10
                          Understood. So does that help to identify the source of the loop? I am not sure where I messed up.

                          1 Reply Last reply Reply Quote 0
                          • stephenw10S
                            stephenw10 Netgate Administrator
                            last edited by

                            Normally the remote access style you have doesn't have endpoints set for the peers. They are are set as dynamic. So that wouldn't apply.

                            P 1 Reply Last reply Reply Quote 0
                            • P
                              pfguy2018 @stephenw10
                              last edited by

                              @stephenw10
                              Oh - could that be the issue then? Should I be setting them all to dynamic? If I do that, do I have to enable the DHCP server on the Wireguard interface?

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by

                                No, normally clients are statically configured with an IP within the 'tunnel subnet'.

                                See: https://docs.netgate.com/pfsense/en/latest/recipes/wireguard-ra.html

                                Steve

                                P 1 Reply Last reply Reply Quote 0
                                • P
                                  pfguy2018 @stephenw10
                                  last edited by

                                  @stephenw10
                                  Those are the exact instructions I followed. I am getting confused here. For my setup, what is the difference between "peers" (which you said should have a dynamic address) and "clients" (which you said should have a static address)?

                                  In case it matters, the devices connecting remotely are configured as follows:

                                  [Interface]
                                  PrivateKey = XXX
                                  ListenPort = 51820
                                  DNS = 192.168.133.1
                                  Address = 192.168.133.20/32 (for example - each device has a different IP)

                                  [Peer]
                                  PublicKey = YYY
                                  AllowedIPs = 0.0.0.0/0
                                  Endpoint = dynDNS address to my pfSense install (dynamic.example.com:51820)
                                  PSK enabled ZZZ

                                  Does that help identify the source of the loop?

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    That's fine.

                                    The 'client' peers endpoint should be set as dynamic at the 'server' end.
                                    But set as a static IP in the tunnel subnet at the client itself.

                                    P 1 Reply Last reply Reply Quote 0
                                    • P
                                      pfguy2018 @stephenw10
                                      last edited by

                                      @stephenw10 said in System log tun_wg0: loop detected:

                                      The 'client' peers endpoint should be set as dynamic at the 'server' end.

                                      You mean on pfSense-VPN-WireGuard-Peers, under each peer, the box for "dynamic endpoint" should be checked?

                                      I can do this, but I was hoping to have rules applied to different groups of peers. i.e. the "admin" group (my devices) with addresses 192.168.133.20-192.168.133.29 are allowed to access LAN addresses through the VPN. Peers with addresses outside this range are blocked from LAN access, and can only tunnel through to the web.

                                      Can that still be accomplished if I use dynamic addresses? Will setting the IP address as static in the client WG install take care of this?

                                      1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        Yes that should be checked. You only add an IP there if the peers have a static public IP which is very unlikely in a 'road warrior' scenario.
                                        If you have added the internal private IP of each peer there that is telling the server end to connect the tunnel to the peer across it's existing tunnel! Hence the recursion and loop error.

                                        Steve

                                        P 1 Reply Last reply Reply Quote 0
                                        • P
                                          pfguy2018 @stephenw10
                                          last edited by

                                          @stephenw10
                                          Now I get it. I have made that change.
                                          Thank you for working this through with me - really appreciate the help!

                                          1 Reply Last reply Reply Quote 0
                                          • stephenw10S
                                            stephenw10 Netgate Administrator
                                            last edited by

                                            No problem. Been a while since I revisited some of that. 😉

                                            tylereversT 1 Reply Last reply Reply Quote 0
                                            • P pfguy2018 referenced this topic on
                                            • stephenw10S stephenw10 referenced this topic on
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.