iggames

@iggames@lemmy.world

This profile is from a federated server and may be incomplete. Browse more on the original instance.

iggames,

I think it’s from the boot camp scenes in the movie Full Metal Jacket.

iggames,

Our neighborhood has the Magical Chicken Wing bush. The dog thoroughly inspected it for months afterwards, and still checks on it now and then just in case.

iggames,

No change with allowing 5353 UDP through the firewall, unfortunately. But thank you for the suggestion!

iggames,

Yes, “sane” service is already in the “Allowed” list.

iggames,

Added “mdns” service to allowed list for public zone, still get the SANE error. (Previously added 5353 UDP per another suggestion – sounds like this is the port for mDNS)

iggames,

Added some info to the post. Firewall is blocking 3289 UDP from my printer, so I added 3289 UDP to open ports for “home”, “public”, and “internal” zones. However, I’m still seeing filter_IN_public_REJECT entries in dmesg, so it seems the firewall is still blocking these. Is there a different way I should be telling it to allow requests on this port?

Firewall also allows mdns service (again, in “home”, “public”, and “internal” zones), but I also see entries like this:

[41951.119486] filter_IN_public_REJECT: IN=wlp0s20f0u3 OUT= MAC= SRC=192.168.1.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=10725 DF PROTO=2 MARK=0x3214

It sounds like 224.0.0.1 is related to mdns broadcasts, so it seems firewall is also still blocking these (despite mdns being allowed service).

Am I specifying these in the wrong place? (Per Connections - System Settings, my wifi is in Firewall zone “home”).

  • All
  • Subscribed
  • Moderated
  • Favorites
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #