Tag: related

What demons are related to the demon lord Dagon?

I’m planning an underwater adventure for D&D 5e that will contain an underwater portal to Dagon’s layer of the Abyss (the 89th layer, called the Shadowsea, apparently). The portal will have demons spilling out of it, but it will be quite small at this point so it should be something the party should be able to stop; hence I want to know what demons would be thematic for being underwater and being associated with Dagon.

D&D 5e doesn’t contain much information about Dagon (most of what I know of demon lords has come from running Out of the Abyss, in which Dagon does not feature, or the Monster Manual and Mordenkainen’s Tome of Foes, neither of which mention Dagon at all as far I as can tell). The only things I know about Dagon come from the Forgotten Realms Wiki page on Dagon, which is not 5e specific and therefore draws on sources I don’t have (I only have 5e materials).

This wiki page mentions:

Dagon was served by aquatic demons, especially wastrilith, […]

But it doesn’t further elaborate on what these other aquatic demons are.

The only appropriate demon I’ve come across so far is the wastrilith, mentioned above, which appears in 5e in Mordenkainen’s Tome of Foes (since it is associated with water, though the book mentions no relation to Dagon specifically, but that Forgotten Realms Wiki link does), but it’s CR is quite high for the party level range I’m planning. There is also the hydroloth from the same book, but that’s a yugoloth, not a demon, and I’d prefer demons where possible.

What demons would thematically follow Dagon?

Ideally of a lower CR than a wastrilith and ideally from 5e where possible, but neither of those are hard constraints. I’ll accept anything from any edition of D&D.

Related, but about Baphomet: What demons are under the dominion of Baphomet?

Unlike that question, I’m only interested in demons specifically (unless the creature has business existing in the Abyss, such as yugoloth; I assume that pretty much only demons would be there).

A code that I could not fully grasp related to foreach & count_user_posts()

Working on my first WordPress theme, I created a page template for authors based on this tutorial which is itself based on the twenty-fourteen theme.

What I could not understand is this :

$  post_count = count_user_posts( $  contributor_id );

From this code example (check especially the first 10 lines for my first question which will very possibly automatically answer my final questions):

<?php // Output the authors list. $  contributor_ids = get_users( array(   'fields'  => 'ID',   'orderby' => 'post_count',   'order'   => 'DESC',   'who'     => 'authors', ));  foreach ( $  contributor_ids as $  contributor_id ) : $  post_count = count_user_posts( $  contributor_id );   // Move on if user has not published a post (yet).   if ( ! $  post_count ) {     continue;   } ?>  <div class="contributor">   <div class="contributor-info">     <div class="contributor-avatar"><?php echo get_avatar( $  contributor_id, 132 ); ?></div>     <div class="contributor-summary">       <h2 class="contributor-name"><?php echo get_the_author_meta( 'display_name', $  contributor_id ); ?></h2>       <p class="contributor-bio">         <?php echo get_the_author_meta( 'description', $  contributor_id ); ?>       </p>       <a class="button contributor-posts-link" href="<?php echo esc_url( get_author_posts_url( $  contributor_id ) ); ?>">         <?php printf( _n( '%d Article', '%d Articles', $  post_count, 'twentyfourteen' ), $  post_count ); ?>       </a>     </div><!-- .contributor-summary -->   </div><!-- .contributor-info --> </div><!-- .contributor -->  <?php endforeach; ?>

I have checked the Codex for count_user_posts( ) but I could not understand how the code is aligned with the documentation as the output of the foreach loop $ contributor_id is not only the ID but also post_count,desc and authors.

These are supposed to be the second parameters which are optional and are

Single post type or array of post types

as the Codex specifies below:

$ post_type (array|string) (Optional) Single post type or array of post types to count the number of posts for. Default value: ‘post’

So how the values of “post_count” ,”desc” and “authors”. fit with the Codex documentation?

Same question for:

get_avatar( $  contributor_id, 132 )

and

get_the_author_meta( 'display_name', $  contributor_id )

What Same Origin Policy related risks are there with static pages?

I am wondering what risks there are if you have static pages on the same host that don’t trust each other. A key concept of Javascript and web security is the Same Origin Policy (SOP), which is also the reason why we need to avoid XSS. If there’s e.g. a blog on example.org with an admin interface on example.org/admin and an attacker can place some javascript on example.org/foo then the attacker can execute javascript that e.g. will create a new admin account or perform other actions on behalf of the admin. I generally understand how this is happening.

However I wonder the following: If the pages on example.org are all static, i.e. no forms that perform actions or endpoints that act on POST requests, does the SOP still matter?

I was thinking of attacks like: Can example.org/foo/ open example.org/bar/, but with manipulated content? This could be useful e.g. if example.org/foo hosts downloads that an attacker can manipulate or redirect. I have tried a few things, but I wasn’t able to perform such an attack. (One way might be ServiceWorkers, but they are path constrained, which limits possibilities quite a bit.)

And are there other attacks that one should care about in purely static scenarios?

What are all the creatures related to the Far Realms that have stat blocks in 5e?

I’m looking for any and all creatures–specifically those that have stat blocks in 5e (so I’m excluding things from previous editions that don’t have stat blocks in 5e, largely just to narrow the scope of this question)–that are related in some way to the Far Realm.

(What I’m actually after are all of the Lovecraftian creatures, but “what do you think has Lovecraftian influences?” is opinion-based, whereas concrete links in the lore to the Far Realm is objective, hence I’m asking that instead. Furthermore, in the adventure I’m planning, the creatures will have a link to the Far Realm anyway, so the Far Realm link is still relevant to what I’m after.)

Those I know of already (with what evidence I could find from 5e sources of lore) are:

  • Mind Flayers (and other associated creatures, such as Elder Brains, Mindwitnesses, etc):

    Aberrations such as mind flayers and beholders are either from this plane or shaped by its strange influence.

    – p. 68, The Far Realm, Dungeon Master’s Guide

  • Beholders (and other variations, such as Spectators, Gazers, Death’s Kiss, etc):

    Aberrations such as mind flayers and beholders are either from this plane or shaped by its strange influence.

    – p. 68, The Far Realm, Dungeon Master’s Guide

  • Aboleth (I know of no other variations, so this is just “the Aboleth”):

    “Could it be that aboleths are older than the gods … that before the divine ones came to be, such horrors shaped the multiverse? Now there’s a chilling thought.”
    — Vaqir Zekh’r, githzerai philosopher and author of THE FAR REALM: REAL YET UNREAL

    – p. 14, Aboleth, Monster Manual

  • Star Spawn (all 5 variations given in Mordenkainen’s Tome of Foes):

    Heralds of Doom. The creatures known as the star spawn are the heralds, servants, foot soldiers, and lieutenants of the Elder Evils […]

    – p. 234, Star Spawn, Mordenkainen’s Tome of Foes

    Some Elder Evils are alleged to be creatures of the Far Realm […]

    – p. 237, Elder Evils sidebar, Mordenkainen’s Tome of Foes

Are there any other creatures that I’ve missed? Note, that last quote shows that not all “Elder Evils” are related to the Far Realm, so a link to an Elder Evil isn’t by itself enough (although it might still deserve an honourary mention); I’m looking for links to the Far Realm specifically, even if the link is really weak or indirect, such as my Aboleth quote above.

If the setting matters, let’s assume Forgotten Realms, although if the Greyhawk setting or whatever has anything relevant, I’ll accept that too (but it might be the case that the Far Realm is specifically only a thing in the Forgotten Realms setting anyway, in which case this paragraph is redundant).

The link to the Far Realm doesn’t have to be from 5e (for example, if it was established that, for some reason, Gnolls were somehow related to the Far Realm in, say, 3e, then they are valid for this question because there are stat blocks for Gnolls in 5e, even though there is no link between Gnolls and the Far Realm in 5e; however, if 3e said that Bladelings were related to the Far Realm, that would not be a valid answer, since AFAIK there are no official stats for Bladelings in 5e).

Incidentally, the links to the Far Realm I found are quite weak, but this is all 5e has to offer, it seems (at least, from the DMG, MM, VGtM, and MToF), so if anyone wants to include any stronger links to the Far Realms from previous editions’ lore for the creatures I’ve already included, that would be appreciated, but not if that’s all the answer contains, since then it wouldn’t actually answer the question asked, which is “what other creatures are related to the Far Realms?” (unless your answer was also saying “Nope, you’ve found them all”, in which case it would still be a valid answer).

How to navigate between related files?

I am trying to design functionality that allows the user to easily navigate from one file to another within a “master file”.

There is currently a correlation between one another, such as the parent having children files.

I’ve come up with this to navigate between, but it’s not entirely working for the use-case.

enter image description here

Wondering possible variations for navigation that’s similar to this, but may tie in better?

Tree navigation is not possible because there may be sharing of masters for different category of children i.e., a child may have two masters.

Are there any other Gnoll/Hyena related statblocks?

I am planning on building a high-level “Yeenoghian” multi-part epic encounter, using only official material, in the scope of Adventurers League play.

Are there any gnoll/hyena-related statblocks other than the following?

  • Gnoll
  • Gnoll Hunter
  • Gnoll Flesh Gnawer
  • Gnoll Pack Lord
  • Gnoll Fang of Yeenoghu
  • Gnoll Witherling
  • Flind
  • Hyena
  • Giant Hyena
  • Shoosuva
  • Yeenoghu himself

Related here means that the potentially missing statblock(s) would have a strong link of association with gnolls, hyenas or the Demon Lord Yeenoghu, and/or would physically look similar to either of them.

Am I under attack? – Home Network Security Related

I don’t know much about internet security, but my connection has been intermediate for the last few weeks. Today, just on a whim, I took a look at my router log and this is what came up.

[UPnP set event: AddPortMapping] from source 192.168.0.28, port 52678, Wed, Nov 27, 2019 07:04:19 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 52678, Wed, Nov 27, 2019 07:04:01 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 52678, Wed, Nov 27, 2019 07:02:56 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 52678, Wed, Nov 27, 2019 07:01:59 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 52678, Wed, Nov 27, 2019 07:00:54 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 52678, Wed, Nov 27, 2019 07:00:37 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 52678, Wed, Nov 27, 2019 06:59:31 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Wed, Nov 27, 2019 06:59:12 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 3074, Wed, Nov 27, 2019 06:58:06 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Wed, Nov 27, 2019 06:57:50 [admin login] from source 192.168.0.102, Wed, Nov 27, 2019 06:57:05 [admin login] from source 192.168.0.102, Wed, Nov 27, 2019 06:56:09 [admin login] from source 192.168.0.102, Wed, Nov 27, 2019 06:44:26 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 3074, Wed, Nov 27, 2019 06:33:33 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Wed, Nov 27, 2019 06:33:15 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 3074, Wed, Nov 27, 2019 06:06:49 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Wed, Nov 27, 2019 06:06:29 [DoS attack: Sync flood] from source: 23.246.13.158, port 443, Wed, Nov 27, 2019 05:48:28 [DoS attack: Sync flood] from source: 173.194.17.168, port 443, Wed, Nov 27, 2019 05:11:39 [DoS attack: Ascend Kill attack] from source: 89.248.168.217, port 60957, Wed, Nov 27, 2019 04:46:25 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 3074, Wed, Nov 27, 2019 04:20:58 [DHCP IP: (192.168.0.111)] to MAC address 00:ce:39:b5:98:92, Wed, Nov 27, 2019 04:20:20 [UPnP set event: DeletePortMapping] from source 192.168.0.11, port 30880, Wed, Nov 27, 2019 04:18:59 [DoS attack: ICMP Ping flood] from source: 27.75.219.3, Wed, Nov 27, 2019 04:08:34 [DoS attack: Sync flood] from source: 103.82.162.94, port 33387, Wed, Nov 27, 2019 04:03:59 [DoS attack: ICMP Ping flood] from source: 36.79.233.78, Wed, Nov 27, 2019 03:37:34 [DoS attack: UDP Scan] from source: 223.71.167.155, port 53824, Wed, Nov 27, 2019 03:25:20 [DoS attack: UDP Scan] from source: 45.143.220.87, port 44864, Wed, Nov 27, 2019 03:08:03 [DoS attack: ICMP Ping flood] from source: 45.248.78.196, Wed, Nov 27, 2019 03:07:11 [UPnP set event: AddPortMapping] from source 192.168.0.11, port 30880, Wed, Nov 27, 2019 03:07:03 [DoS attack: Sync flood] from source: 58.245.142.106, port 64178, Wed, Nov 27, 2019 03:01:32 [UPnP set event: DeletePortMapping] from source 192.168.0.11, port 30880, Wed, Nov 27, 2019 03:01:22 [DoS attack: Sync flood] from source: 13.225.48.135, port 80, Wed, Nov 27, 2019 01:16:38 [DoS attack: Sync flood] from source: 36.224.209.216, port 53337, Wed, Nov 27, 2019 00:34:11 [DHCP IP: (192.168.0.112)] to MAC address 7c:d1:c3:8e:41:90, Wed, Nov 27, 2019 00:26:31 [UPnP set event: AddPortMapping] from source 192.168.0.23, port 9308, Wed, Nov 27, 2019 00:25:21 [DoS attack: Sync flood] from source: 24.231.96.148, port 56238, Wed, Nov 27, 2019 00:25:17 [DHCP IP: (192.168.0.107)] to MAC address 3c:9b:d6:00:75:7c, Wed, Nov 27, 2019 00:25:11 [DHCP IP: (192.168.0.108)] to MAC address 38:8c:50:d4:7a:cd, Wed, Nov 27, 2019 00:25:10 [DoS attack: UDP Scan] from source: 223.71.167.155, port 54458, Wed, Nov 27, 2019 00:20:14 [DHCP IP: (192.168.0.102)] to MAC address 64:6e:69:f6:06:e9, Wed, Nov 27, 2019 00:07:17 [DHCP IP: (192.168.0.100)] to MAC address 5c:f6:dc:65:80:11, Wed, Nov 27, 2019 00:06:05 [DoS attack: Echo char gen] from source: 173.255.234.194, port 59355, Wed, Nov 27, 2019 00:00:28 [DoS attack: ICMP Ping flood] from source: 77.50.80.43, Wed, Nov 27, 2019 00:00:07 [UPnP set event: AddPortMapping] from source 192.168.0.11, port 30880, Wed, Nov 27, 2019 00:00:06 [DHCP IP: (192.168.0.104)] to MAC address 60:6b:ff:ae:ff:6c, Tue, Nov 26, 2019 23:30:35 [DHCP IP: (192.168.0.106)] to MAC address f8:95:ea:70:98:a2, Tue, Nov 26, 2019 23:27:55 [DoS attack: UDP Scan] from source: 146.88.240.4, port 44029, Tue, Nov 26, 2019 23:10:16 [DHCP IP: (192.168.0.103)] to MAC address fc:6b:f0:33:ec:06, Tue, Nov 26, 2019 23:06:24 [DHCP IP: (192.168.0.105)] to MAC address 64:1c:b0:1b:4e:ec, Tue, Nov 26, 2019 23:05:40 [DHCP IP: (192.168.0.101)] to MAC address 98:9c:57:08:27:66, Tue, Nov 26, 2019 23:05:27 [Time synchronized with NTP server] Tue, Nov 26, 2019 23:05:25 [Internet connected] IP address: **.***.***.***, Wed, Dec 31, 1969 18:01:02 [DHCP IP: (192.168.0.109)] to MAC address 54:33:cb:60:3e:a9, Wed, Dec 31, 1969 18:01:01 [Initialized, firmware version: V3.01.43] Thu, Jan 01, 1970 00:00:07 [DoS attack: UDP Scan] from source: 185.94.111.1, port 53516, Tue, Nov 26, 2019 22:42:11 [DoS attack: Echo char gen] from source: 185.164.72.60, port 48699, Tue, Nov 26, 2019 20:25:17 [DoS attack: UDP Scan] from source: 223.71.167.62, port 44119, Tue, Nov 26, 2019 19:05:34 [DoS attack: Echo char gen] from source: 146.88.240.4, port 43504, Tue, Nov 26, 2019 18:16:38 [DoS attack: UDP Scan] from source: 142.93.97.100, port 12326, Tue, Nov 26, 2019 16:48:10 [DoS attack: Echo char gen] from source: 45.67.15.69, port 31989, Tue, Nov 26, 2019 15:29:15 [wireless signal schedule] The 5GHz wireless signal is ON, Tue, Nov 26, 2019 15:00:03 [DoS attack: UDP Scan] from source: 223.71.167.62, port 63926, Tue, Nov 26, 2019 13:05:29 [DoS attack: UDP Scan] from source: 223.71.167.155, port 9980, Tue, Nov 26, 2019 12:39:26 [DoS attack: UDP Scan] from source: 223.71.167.62, port 40459, Tue, Nov 26, 2019 12:21:58 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Tue, Nov 26, 2019 10:07:58 [DoS attack: Sync flood] from source: 180.35.103.2, port 50263, Tue, Nov 26, 2019 10:06:49 [UPnP set event: DeletePortMapping] from source 192.168.0.11, port 30880, Tue, Nov 26, 2019 10:06:02 [DoS attack: UDP Scan] from source: 223.71.167.155, port 59420, Tue, Nov 26, 2019 09:47:37 [DoS attack: Sync flood] from source: 114.27.10.168, port 1030, Tue, Nov 26, 2019 08:56:17 [DoS attack: Sync flood] from source: 217.178.24.50, port 28478, Tue, Nov 26, 2019 08:52:53 [DoS attack: UDP Scan] from source: 223.71.167.62, port 54377, Tue, Nov 26, 2019 08:47:20 [DoS attack: ICMP Ping flood] from source: 182.19.231.126, Tue, Nov 26, 2019 08:13:25 [wireless signal schedule] The 5GHz wireless signal is OFF, Tue, Nov 26, 2019 08:00:03 [DoS attack: ICMP Ping flood] from source: 110.169.248.93, Tue, Nov 26, 2019 06:37:46 [DoS attack: ICMP Ping flood] from source: 211.76.109.4, Tue, Nov 26, 2019 06:24:34 [DoS attack: Sync flood] from source: 74.125.3.72, port 443, Tue, Nov 26, 2019 06:20:12 [DoS attack: UDP Scan] from source: 223.71.167.62, port 44028, Tue, Nov 26, 2019 05:47:45 [DoS attack: UDP Scan] from source: 223.71.167.62, port 55984, Tue, Nov 26, 2019 05:32:24 [DoS attack: ICMP Ping flood] from source: 58.72.41.238, Tue, Nov 26, 2019 04:51:32 [UPnP set event: AddPortMapping] from source 192.168.0.11, port 30880, Tue, Nov 26, 2019 04:46:57 [DoS attack: UDP Scan] from source: 211.150.70.18, port 19030, Tue, Nov 26, 2019 04:40:21 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 3074, Tue, Nov 26, 2019 03:55:45 [DoS attack: UDP Scan] from source: 223.71.167.62, port 29366, Tue, Nov 26, 2019 02:40:29 [UPnP set event: AddPortMapping] from source 192.168.0.23, port 9308, Tue, Nov 26, 2019 00:33:30 [DoS attack: Echo char gen] from source: 71.6.232.5, port 37186, Mon, Nov 25, 2019 23:02:03 [DoS attack: UDP Scan] from source: 223.71.167.155, port 5696, Mon, Nov 25, 2019 22:42:04 [DoS attack: Echo char gen] from source: 184.105.139.69, port 24607, Mon, Nov 25, 2019 22:25:26 [DoS attack: Echo char gen] from source: 146.88.240.4, port 56117, Mon, Nov 25, 2019 20:01:54 [DoS attack: UDP Scan] from source: 146.88.240.4, port 56509, Mon, Nov 25, 2019 19:14:13 [DoS attack: UDP Scan] from source: 223.71.167.62, port 45745, Mon, Nov 25, 2019 18:36:07 [DoS attack: Sync flood] from source: 13.226.96.43, port 80, Mon, Nov 25, 2019 18:01:01 [DoS attack: UDP Scan] from source: 223.71.167.62, port 29129, Mon, Nov 25, 2019 15:07:05 [wireless signal schedule] The 5GHz wireless signal is ON, Mon, Nov 25, 2019 15:00:03 [DoS attack: UDP Scan] from source: 211.150.70.18, port 55813, Mon, Nov 25, 2019 14:04:48 [DoS attack: Ascend Kill attack] from source: 89.248.168.217, port 39991, Mon, Nov 25, 2019 10:38:10 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Mon, Nov 25, 2019 10:13:41 [DoS attack: Echo char gen] from source: 146.88.240.4, port 41651, Mon, Nov 25, 2019 09:56:42 [DoS attack: UDP Scan] from source: 211.150.70.18, port 12879, Mon, Nov 25, 2019 09:15:32 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 3074, Mon, Nov 25, 2019 08:00:15 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Mon, Nov 25, 2019 08:00:15 [wireless signal schedule] The 5GHz wireless signal is OFF, Mon, Nov 25, 2019 08:00:03 [DoS attack: Sync flood] from source: 213.174.137.53, port 443, Mon, Nov 25, 2019 07:58:59 [DoS attack: Sync flood] from source: 206.54.174.4, port 443, Mon, Nov 25, 2019 07:43:51 [DoS attack: Sync flood] from source: 206.54.174.4, port 443, Mon, Nov 25, 2019 07:43:51 [DoS attack: Sync flood] from source: 213.174.137.55, port 443, Mon, Nov 25, 2019 07:24:37 [DoS attack: Sync flood] from source: 213.174.137.55, port 443, Mon, Nov 25, 2019 07:23:08 [DoS attack: UDP Scan] from source: 223.71.167.62, port 16018, Mon, Nov 25, 2019 05:57:52 [DoS attack: Sync flood] from source: 213.174.137.55, port 443, Mon, Nov 25, 2019 05:19:56 [DoS attack: UDP Scan] from source: 146.88.240.4, port 45221, Mon, Nov 25, 2019 05:10:52 [DoS attack: UDP Scan] from source: 223.71.167.155, port 7127, Mon, Nov 25, 2019 04:31:04 [DoS attack: Echo char gen] from source: 80.82.77.245, port 45219, Mon, Nov 25, 2019 04:14:06 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 3074, Mon, Nov 25, 2019 03:30:56 [DoS attack: UDP Scan] from source: 185.94.111.1, port 52483, Mon, Nov 25, 2019 03:14:51 [DoS attack: UDP Scan] from source: 211.150.70.18, port 29658, Mon, Nov 25, 2019 00:59:38 [DoS attack: UDP Scan] from source: 185.94.111.1, port 41418, Sun, Nov 24, 2019 23:59:27 [UPnP set event: AddPortMapping] from source 192.168.0.23, port 9308, Sun, Nov 24, 2019 23:18:20 [DoS attack: Echo char gen] from source: 52.73.169.169, port 40299, Sun, Nov 24, 2019 23:08:34 [DoS attack: Echo char gen] from source: 80.82.77.221, port 55979, Sun, Nov 24, 2019 22:36:20 [DoS attack: UDP Scan] from source: 146.88.240.2, port 50749, Sun, Nov 24, 2019 21:33:07 [DoS attack: UDP Scan] from source: 223.71.167.154, port 10141, Sun, Nov 24, 2019 21:19:42 [DoS attack: UDP Scan] from source: 146.88.240.2, port 48463, Sun, Nov 24, 2019 19:20:20 [DoS attack: UDP Scan] from source: 223.71.167.155, port 10995, Sun, Nov 24, 2019 18:03:41 [wireless signal schedule] The 5GHz wireless signal is ON, Sun, Nov 24, 2019 15:00:03 [DoS attack: UDP Scan] from source: 211.150.70.18, port 16119, Sun, Nov 24, 2019 13:12:19 [DoS attack: Echo char gen] from source: 122.228.19.80, port 17279, Sun, Nov 24, 2019 13:08:17 [DoS attack: UDP Scan] from source: 211.150.70.18, port 50742, Sun, Nov 24, 2019 12:57:27 [DoS attack: Echo char gen] from source: 83.97.20.167, port 29570, Sun, Nov 24, 2019 10:51:25 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Sun, Nov 24, 2019 09:45:41 [DoS attack: UDP Scan] from source: 104.131.209.76, port 35328, Sun, Nov 24, 2019 09:42:45 [wireless signal schedule] The 5GHz wireless signal is OFF, Sun, Nov 24, 2019 08:00:03 [DoS attack: UDP Scan] from source: 211.150.70.18, port 12045, Sun, Nov 24, 2019 07:32:11 [DoS attack: UDP Scan] from source: 146.88.240.4, port 44739, Sun, Nov 24, 2019 05:39:59 [DoS attack: Sync flood] from source: 64.210.158.130, port 443, Sun, Nov 24, 2019 04:32:13 [DoS attack: UDP Scan] from source: 223.71.167.154, port 64828, Sun, Nov 24, 2019 03:35:58 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 3074, Sun, Nov 24, 2019 02:53:54 [DHCP IP: (192.168.0.109)] to MAC address 54:33:cb:60:3e:a9, Sun, Nov 24, 2019 02:51:25 [DoS attack: UDP Scan] from source: 223.71.167.155, port 45675, Sun, Nov 24, 2019 02:09:46 [DoS attack: UDP Scan] from source: 104.152.52.39, port 57860, Sun, Nov 24, 2019 01:06:14 [DoS attack: Echo char gen] from source: 104.152.52.39, port 57860, Sun, Nov 24, 2019 01:02:59 [DoS attack: UDP Scan] from source: 104.152.52.39, port 57860, Sun, Nov 24, 2019 00:56:07 [DoS attack: UDP Scan] from source: 104.152.52.39, port 57860, Sun, Nov 24, 2019 00:45:22 [UPnP set event: AddPortMapping] from source 192.168.0.23, port 9308, Sat, Nov 23, 2019 22:13:09 [DoS attack: UDP Scan] from source: 223.71.167.155, port 37207, Sat, Nov 23, 2019 21:51:36 [DoS attack: Echo char gen] from source: 185.173.35.41, port 64291, Sat, Nov 23, 2019 21:00:10 [DoS attack: Echo char gen] from source: 146.88.240.4, port 54483, Sat, Nov 23, 2019 18:21:02 [DoS attack: UDP Scan] from source: 223.71.167.61, port 39708, Sat, Nov 23, 2019 17:19:02 [DoS attack: Ascend Kill attack] from source: 89.248.168.217, port 42296, Sat, Nov 23, 2019 16:30:58 [DoS attack: Echo char gen] from source: 80.82.77.245, port 53461, Sat, Nov 23, 2019 16:06:56 [wireless signal schedule] The 5GHz wireless signal is ON, Sat, Nov 23, 2019 15:00:03 [DoS attack: Echo char gen] from source: 92.118.37.91, port 14908, Sat, Nov 23, 2019 13:40:52 [DoS attack: Echo char gen] from source: 92.118.37.91, port 55235, Sat, Nov 23, 2019 13:06:31 [DoS attack: Echo char gen] from source: 109.248.11.201, port 50630, Sat, Nov 23, 2019 10:45:29 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Sat, Nov 23, 2019 09:30:03 [DoS attack: UDP Scan] from source: 211.150.70.18, port 10351, Sat, Nov 23, 2019 08:49:49 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 3074, Sat, Nov 23, 2019 08:00:16 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Sat, Nov 23, 2019 08:00:15 [wireless signal schedule] The 5GHz wireless signal is OFF, Sat, Nov 23, 2019 08:00:03 [DoS attack: Sync flood] from source: 159.69.143.224, port 443, Sat, Nov 23, 2019 07:54:04 [DoS attack: Sync flood] from source: 94.130.139.59, port 443, Sat, Nov 23, 2019 07:33:19 [DoS attack: UDP Scan] from source: 211.150.70.18, port 16823, Sat, Nov 23, 2019 07:11:08 [DoS attack: Sync flood] from source: 88.99.166.9, port 443, Sat, Nov 23, 2019 06:35:14 [DoS attack: Echo char gen] from source: 146.88.240.4, port 55002, Sat, Nov 23, 2019 05:57:08 [DoS attack: UDP Scan] from source: 122.228.19.80, port 61126, Sat, Nov 23, 2019 05:56:00 [DoS attack: UDP Scan] from source: 185.94.111.1, port 49382, Sat, Nov 23, 2019 05:21:12 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 3074, Sat, Nov 23, 2019 04:17:33 [DoS attack: Echo char gen] from source: 141.212.123.202, port 42970, Sat, Nov 23, 2019 03:58:19 [DoS attack: UDP Scan] from source: 223.71.167.61, port 17609, Sat, Nov 23, 2019 03:37:28 [DoS attack: UDP Scan] from source: 223.71.167.154, port 53095, Sat, Nov 23, 2019 01:30:17 [UPnP set event: AddPortMapping] from source 192.168.0.23, port 9308, Sat, Nov 23, 2019 00:06:16 [DoS attack: UDP Scan] from source: 146.88.240.4, port 56952, Fri, Nov 22, 2019 21:11:40 [DoS attack: Echo char gen] from source: 45.58.135.186, port 53170, Fri, Nov 22, 2019 18:22:03 [wireless signal schedule] The 5GHz wireless signal is ON, Fri, Nov 22, 2019 15:00:03 [DoS attack: Echo char gen] from source: 92.118.37.91, port 45118, Fri, Nov 22, 2019 11:48:34 [DoS attack: Echo char gen] from source: 92.118.37.91, port 33002, Fri, Nov 22, 2019 11:15:53 [DoS attack: UDP Scan] from source: 223.71.167.155, port 46652, Fri, Nov 22, 2019 10:33:08 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Fri, Nov 22, 2019 10:31:10 [wireless signal schedule] The 5GHz wireless signal is OFF, Fri, Nov 22, 2019 08:00:03 [DoS attack: UDP Scan] from source: 223.71.167.154, port 35421, Fri, Nov 22, 2019 06:49:21 [DoS attack: UDP Scan] from source: 211.150.70.18, port 12598, Fri, Nov 22, 2019 06:15:29 [DoS attack: Sync flood] from source: 213.174.137.135, port 443, Fri, Nov 22, 2019 05:42:15 [DoS attack: Echo char gen] from source: 146.88.240.4, port 57024, Fri, Nov 22, 2019 04:23:20 [DoS attack: Echo char gen] from source: 80.82.77.245, port 34658, Fri, Nov 22, 2019 04:03:24 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 3074, Fri, Nov 22, 2019 03:49:45 [DoS attack: UDP Scan] from source: 223.71.167.155, port 60808, Fri, Nov 22, 2019 03:16:06 [DoS attack: UDP Scan] from source: 211.150.70.18, port 39200, Fri, Nov 22, 2019 02:16:07 [DoS attack: UDP Scan] from source: 211.150.70.18, port 35299, Fri, Nov 22, 2019 02:00:59 [DoS attack: Echo char gen] from source: 184.105.139.77, port 24439, Fri, Nov 22, 2019 00:51:37 [UPnP set event: AddPortMapping] from source 192.168.0.23, port 9308, Fri, Nov 22, 2019 00:12:24 [DoS attack: UDP Scan] from source: 211.150.70.18, port 30931, Thu, Nov 21, 2019 23:06:25 [DoS attack: Ascend Kill attack] from source: 89.248.168.217, port 47518, Thu, Nov 21, 2019 22:20:08 [DoS attack: UDP Scan] from source: 211.150.70.18, port 56282, Thu, Nov 21, 2019 21:14:42 [DoS attack: UDP Scan] from source: 211.150.70.18, port 35255, Thu, Nov 21, 2019 20:44:21 [DoS attack: UDP Scan] from source: 223.71.167.61, port 31588, Thu, Nov 21, 2019 20:13:53 [DoS attack: UDP Scan] from source: 146.88.240.4, port 59565, Thu, Nov 21, 2019 19:05:54 [DoS attack: UDP Scan] from source: 211.150.70.18, port 39519, Thu, Nov 21, 2019 18:36:31 [wireless signal schedule] The 5GHz wireless signal is ON, Thu, Nov 21, 2019 15:00:03 [DoS attack: UDP Scan] from source: 223.71.167.155, port 22201, Thu, Nov 21, 2019 12:53:23 [DoS attack: Echo char gen] from source: 92.118.37.91, port 38196, Thu, Nov 21, 2019 12:35:53 [DoS attack: Echo char gen] from source: 92.118.37.91, port 56177, Thu, Nov 21, 2019 11:59:48 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Thu, Nov 21, 2019 10:08:03 [DoS attack: UDP Scan] from source: 185.94.111.1, port 44870, Thu, Nov 21, 2019 10:05:04 [DoS attack: UDP Scan] from source: 211.150.70.18, port 26178, Thu, Nov 21, 2019 09:22:34 [DoS attack: UDP Scan] from source: 185.94.111.1, port 48420, Thu, Nov 21, 2019 08:02:05 [wireless signal schedule] The 5GHz wireless signal is OFF, Thu, Nov 21, 2019 08:00:03 [DoS attack: Sync flood] from source: 152.195.33.132, port 443, Thu, Nov 21, 2019 07:39:19 [DoS attack: Sync flood] from source: 74.125.3.121, port 443, Thu, Nov 21, 2019 06:39:23 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 3074, Thu, Nov 21, 2019 03:49:15 [DoS attack: UDP Scan] from source: 211.150.70.18, port 43042, Thu, Nov 21, 2019 00:58:31 [DoS attack: Echo char gen] from source: 172.104.51.17, port 53084, Thu, Nov 21, 2019 00:37:39 [UPnP set event: AddPortMapping] from source 192.168.0.23, port 9308, Thu, Nov 21, 2019 00:07:34 [DoS attack: Echo char gen] from source: 82.221.105.6, port 27221, Wed, Nov 20, 2019 22:22:33 [DoS attack: Echo char gen] from source: 146.88.240.4, port 43032, Wed, Nov 20, 2019 21:17:48 [DoS attack: UDP Scan] from source: 146.88.240.4, port 53874, Wed, Nov 20, 2019 20:46:51 [DoS attack: UDP Scan] from source: 211.150.70.18, port 38862, Wed, Nov 20, 2019 17:50:09 [DoS attack: UDP Scan] from source: 211.150.70.18, port 8150, Wed, Nov 20, 2019 16:27:15 [wireless signal schedule] The 5GHz wireless signal is ON, Wed, Nov 20, 2019 15:00:02 [DoS attack: Echo char gen] from source: 80.82.77.245, port 42747, Wed, Nov 20, 2019 14:24:38 [DoS attack: Echo char gen] from source: 137.74.157.89, port 33696, Wed, Nov 20, 2019 09:31:22 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Wed, Nov 20, 2019 09:24:32 [DoS attack: Echo char gen] from source: 50.7.232.154, port 42299, Wed, Nov 20, 2019 09:21:47 [DoS attack: UDP Scan] from source: 211.150.70.18, port 20027, Wed, Nov 20, 2019 08:47:15 [DoS attack: UDP Scan] from source: 211.150.70.18, port 9583, Wed, Nov 20, 2019 08:12:04 [wireless signal schedule] The 5GHz wireless signal is OFF, Wed, Nov 20, 2019 08:00:02 [DoS attack: Sync flood] from source: 209.197.3.68, port 443, Wed, Nov 20, 2019 06:50:51 [DoS attack: UDP Scan] from source: 211.150.70.18, port 59743, Wed, Nov 20, 2019 04:40:35 [DoS attack: Ascend Kill attack] from source: 89.248.168.217, port 34898, Wed, Nov 20, 2019 04:15:53 [DoS attack: Echo char gen] from source: 92.118.37.91, port 34832, Wed, Nov 20, 2019 02:28:36 [DoS attack: UDP Scan] from source: 146.88.240.4, port 48255, Wed, Nov 20, 2019 02:22:48 [DoS attack: Echo char gen] from source: 92.118.37.91, port 64778, Wed, Nov 20, 2019 01:48:08 [UPnP set event: AddPortMapping] from source 192.168.0.28, port 3074, Wed, Nov 20, 2019 00:39:10 [UPnP set event: AddPortMapping] from source 192.168.0.23, port 9308, Wed, Nov 20, 2019 00:38:27 [DHCP IP: (192.168.0.108)] to MAC address 38:8c:50:d4:7a:cd, Wed, Nov 20, 2019 00:38:16 [DoS attack: Echo char gen] from source: 184.105.139.89, port 56943, Tue, Nov 19, 2019 22:32:06 [DoS attack: UDP Scan] from source: 223.71.167.155, port 29704, Tue, Nov 19, 2019 22:11:15 [DoS attack: Echo char gen] from source: 146.88.240.4, port 56312, Tue, Nov 19, 2019 20:19:06 [DoS attack: Echo char gen] from source: 46.161.27.142, port 8080, Tue, Nov 19, 2019 18:41:16 [wireless signal schedule] The 5GHz wireless signal is ON, Tue, Nov 19, 2019 15:00:02 [DoS attack: Echo char gen] from source: 185.106.122.220, port 60712, Tue, Nov 19, 2019 14:46:52 [DoS attack: UDP Scan] from source: 185.94.111.1, port 39928, Tue, Nov 19, 2019 14:30:41 [DoS attack: Echo char gen] from source: 92.118.37.91, port 64166, Tue, Nov 19, 2019 14:05:46 [DoS attack: Echo char gen] from source: 92.118.37.91, port 59761, Tue, Nov 19, 2019 13:25:20 [DoS attack: UDP Scan] from source: 185.94.111.1, port 53063, Tue, Nov 19, 2019 13:08:28 [DHCP IP: (192.168.0.100)] to MAC address 5c:f6:dc:65:80:11, Tue, Nov 19, 2019 10:41:12 [UPnP set event: DeletePortMapping] from source 192.168.0.28, port 3074, Tue, Nov 19, 2019 09:15:04 [DoS attack: Echo char gen] from source: 92.118.37.91, port 38982, Tue, Nov 19, 2019 08:57:44 [DoS attack: Echo char gen] from source: 92.118.37.91, port 56223, Tue, Nov 19, 2019 08:16:36 [wireless signal schedule] The 5GHz wireless signal is OFF, Tue, Nov 19, 2019 08:00:02 [DoS attack: Sync flood] from source: 213.174.154.9, port 443, Tue, Nov 19, 2019 07:00:12 [DHCP IP: (192.168.0.107)] to MAC address 3c:9b:d6:00:75:7c, Tue, Nov 19, 2019 03:59:34 [DHCP IP: (192.168.0.111)] to MAC address 00:ce:39:b5:98:92, Tue, Nov 19, 2019 03:59:27 [DoS attack: UDP Scan] from source: 211.150.70.18, port 26498, Tue, Nov 19, 2019 01:51:22 [DHCP IP: (192.168.0.104)] to MAC address 60:6b:ff:ae:ff:6c, Tue, Nov 19, 2019 01:26:03 [DoS attack: UDP Scan] from source: 146.88.240.4, port 58883, Tue, Nov 19, 2019 01:13:32 [DoS attack: UDP Scan] from source: 211.150.70.18, port 6095, Tue, Nov 19, 2019 01:02:41 [DHCP IP: (192.168.0.103)] to MAC address fc:6b:f0:33:ec:06, Tue, Nov 19, 2019 00:53:31

Does any of this look sinister, or is it just a bunch of false positives?