#Firewall

iX MagaziniX-Workshop: Sicherer Betrieb von Windows 11 in UnternehmenLernen Sie an praktischen Beispielen, wie Sie Windows 11 Pro und Enterprise in Ihrem Unternehmen sicher und effektiv einsetzen.<a href="https://www.heise.de/news/iX-Workshop-Sicherer-Betrieb-von-Windows-11-in-Unternehmen-10465534.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon" rel="nofollow noopener" translate="no" target="_blank">https://www.heise.de/news/iX-Workshop-Sicherer-Betrieb-von-Windows-11-in-Unternehmen-10465534.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon</a><a href="https://social.heise.de/tags/Firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firewall</a> <a href="https://social.heise.de/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> <a href="https://social.heise.de/tags/iXWorkshops" class="mention hashtag" rel="nofollow noopener" target="_blank">#iXWorkshops</a> <a href="https://social.heise.de/tags/Malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Malware</a> <a href="https://social.heise.de/tags/Verschl%C3%BCsselung" class="mention hashtag" rel="nofollow noopener" target="_blank">#Verschlüsselung</a> <a href="https://social.heise.de/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> <a href="https://social.heise.de/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#news</a>

Peter N. M. HansteenLong rumored, eagerly anticipated by some, "The Book of PF, 4th edition" <a href="https://nostarch.com/book-of-pf-4th-edition" rel="nofollow noopener" translate="no" target="_blank">https://nostarch.com/book-of-pf-4th-edition</a> is now available for PREORDER. The most up to date guide to the OpenBSD and FreeBSD networking toolset <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#openbsd</a> <a href="https://mastodon.social/tags/freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#freebsd</a> <a href="https://mastodon.social/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#networking</a> <a href="https://mastodon.social/tags/pf" class="mention hashtag" rel="nofollow noopener" target="_blank">#pf</a> <a href="https://mastodon.social/tags/packetfilter" class="mention hashtag" rel="nofollow noopener" target="_blank">#packetfilter</a> <a href="https://mastodon.social/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#firewall</a> <a href="https://mastodon.social/tags/preorder" class="mention hashtag" rel="nofollow noopener" target="_blank">#preorder</a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> (again for the CEST-ish crowd)

The New Oil<a href="https://mastodon.thenewoil.org/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a> asks users to ignore <a href="https://mastodon.thenewoil.org/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> <a href="https://mastodon.thenewoil.org/tags/Firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firewall</a> config errors<a href="https://www.bleepingcomputer.com/news/microsoft/microsoft-asks-users-to-ignore-windows-firewall-config-errors/" rel="nofollow noopener" translate="no" target="_blank">https://www.bleepingcomputer.com/news/microsoft/microsoft-asks-users-to-ignore-windows-firewall-config-errors/</a><a href="https://mastodon.thenewoil.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a>

das nächste bitteIch brauche mal die Hilfe von <a href="https://social.tchncs.de/tags/RethinkDNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#RethinkDNS</a> Nutzern. Ich habe eine neue App installiert und irgendwas wird von RethinkDNS blockiert, sodass die App (vvs mobil) nicht funktioniert. Schaue ich in die Protokolle werden alle DNS Anfragen beantwortet. Auch in der App Übersicht werden alle Verbindungen als erfolgreich angezeigt. Ich habe sowohl mit RDNSplus als auch mit System DNS versucht. Ich habe mit Wireguard Umleitung und ohne probiert. Hat Jemand eine Idee wo ich noch dran schrauben kann? <a href="https://social.tchncs.de/tags/adblocker" class="mention hashtag" rel="nofollow noopener" target="_blank">#adblocker</a> <a href="https://social.tchncs.de/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#firewall</a> <a href="https://social.tchncs.de/tags/fedihelp" class="mention hashtag" rel="nofollow noopener" target="_blank">#fedihelp</a>

HessenheldenAngeschlossen und erstmals gestartet. Was mich wundert dass es sehr warm im Betrieb wird. Ich kann es nicht einschätzen ob das normal ist aber wenn jetzt schon so viel Hitze erzeugt wird, bei wenig last, werden die elektrische Bauteile nicht lange durchhalten.<a href="https://mastodon.social/tags/opnsense" class="mention hashtag" rel="nofollow noopener" target="_blank">#opnsense</a> <a href="https://mastodon.social/tags/cwwk" class="mention hashtag" rel="nofollow noopener" target="_blank">#cwwk</a> <a href="https://mastodon.social/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#firewall</a> <a href="https://mastodon.social/tags/appliance" class="mention hashtag" rel="nofollow noopener" target="_blank">#appliance</a>

BastilleBSD :freebsd:Say I have a table defined in pf.conf that includes both ip4 and ip6 addresses. When I create my rdr or pass rules that reference this table, do I need to create two entries, one for inet and another for inet6?<a href="https://fosstodon.org/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreeBSD</a> <a href="https://fosstodon.org/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#firewall</a> <a href="https://fosstodon.org/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#ipv6</a>

Waidler :mastodon:Endlich funktioniert die Endpoint-Erkennung VLAN-übergreifend wieder bei meinem ROON Server. ROON hätte gerne alle Klienten im gleichen Netzwerksegment. Dann klappt die Erkennung auf Anhieb. Bei mehreren VLANs wird's dann schwierig. Da muß man tiefer in die Trickkiste bei den Multicast-Einstellungen greifen. Alte Firewallregeln in der OPNsense-Firewall entfernt und gut durchdachte neue hinzugefügt und schon funktioniert es wieder VLAN-übergreifend.<a href="https://bayerwald.social/tags/roon" class="mention hashtag" rel="nofollow noopener" target="_blank">#roon</a> <a href="https://bayerwald.social/tags/multicast" class="mention hashtag" rel="nofollow noopener" target="_blank">#multicast</a> <a href="https://bayerwald.social/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#firewall</a> <a href="https://bayerwald.social/tags/opnsense" class="mention hashtag" rel="nofollow noopener" target="_blank">#opnsense</a> <a href="https://bayerwald.social/tags/mdns" class="mention hashtag" rel="nofollow noopener" target="_blank">#mdns</a>

Tech SingerThere are allot of people here who understand the world in my particular way, so I thought I'd throw this out and see if anyone has done this sort of thing before and can save me from wheel reinvention. I have a <a href="https://tweesecake.social/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> machine running <a href="https://tweesecake.social/tags/Windows10" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows10</a> which I want to connect to the internet as follows. It has to be <a href="https://tweesecake.social/tags/portable" class="mention hashtag" rel="nofollow noopener" target="_blank">#portable</a>. It has to have access only to a very specific and limited number of IP addresses and DNS names which I will identify in advance and which I will edit by hand. It has to block access to everything else including Microsoft's machines, Google's machines, Basically, if it's not on my list, the machine will not connect to it. Whether the machine wants to connect to an IP address, a DNS name, or a device on the local network, I want connections to be promptly blocked. By promptly, I mean that I want the machine not to time out trying to connect to the stuff not on my list, I want the machine to be told no as soon as it tries. I want this because the machine shouldn't be waiting to timeout, it should just be doing what I told it without wasting cycles and time trying to talk to devices I don't want it talking to. The obvious solution is some sort of <a href="https://tweesecake.social/tags/whitelisting" class="mention hashtag" rel="nofollow noopener" target="_blank">#whitelisting</a> <a href="https://tweesecake.social/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#firewall</a> or <a href="https://tweesecake.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> system, but I have three problems there. First, I'm <a href="https://tweesecake.social/tags/blind" class="mention hashtag" rel="nofollow noopener" target="_blank">#blind</a> and need <a href="https://tweesecake.social/tags/a11y" class="mention hashtag" rel="nofollow noopener" target="_blank">#a11y</a> with <a href="https://tweesecake.social/tags/Jaws" class="mention hashtag" rel="nofollow noopener" target="_blank">#Jaws</a> and <a href="https://tweesecake.social/tags/NVDA" class="mention hashtag" rel="nofollow noopener" target="_blank">#NVDA</a>. Secondly, as I said, it has to be portable, so I can't carry around a second box with a firewall. Thirdly, the machine has both ireless and ethernet access. I want both ports to have access only to the IPs/names I specify. Whether the machine is connected over ethernet or 802.11, I want those rules to be in effect. I have considered MS' firewall, but am nervous that it will let the machine talk to MS, which I don't want it to. Is any of this even possible? Boosts would be appreciated.

Kevin Karhan :verified:<a href="https://grapheneos.social/@GrapheneOS" class="u-url mention" rel="nofollow noopener" target="_blank">@GrapheneOS</a> <a href="https://fedi.omada.cafe/@fluffery" class="u-url mention" rel="nofollow noopener" target="_blank">@fluffery</a> <a href="https://chaos.social/@maumau" class="u-url mention" rel="nofollow noopener" target="_blank">@maumau</a> <a href="https://social.tchncs.de/@BryanGreyson" class="u-url mention" rel="nofollow noopener" target="_blank">@BryanGreyson</a> <a href="https://mas.to/@fairphone" class="u-url mention" rel="nofollow noopener" target="_blank">@fairphone</a> I.e. <a href="https://mstdn.social/@BrodieOnLinux" class="u-url mention" rel="nofollow noopener" target="_blank">@BrodieOnLinux</a> could not use any of those because they don't support <a href="https://infosec.space/tags/VoLTE" class="mention hashtag" rel="nofollow noopener" target="_blank">#VoLTE</a> (not just in <a href="https://infosec.space/tags/Australia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Australia</a>) and thus would be blocked by the <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#IMEI</a>-<a href="https://infosec.space/tags/Firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firewall</a>! <a href="https://www.youtube.com/watch?v=zIJavqEzEIw" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=zIJavqEzEIw</a>

LinuxiacIPFire 2.29 Core Update 195 open-source firewall is out, adding long-awaited WireGuard VPN support and easy-to-configure tunneling options. <a href="https://linuxiac.com/ipfire-2-29-core-update-195-firewall-brings-native-wireguard-support/" rel="nofollow noopener" translate="no" target="_blank">https://linuxiac.com/ipfire-2-29-core-update-195-firewall-brings-native-wireguard-support/</a><a href="https://mastodon.social/tags/ipfire" class="mention hashtag" rel="nofollow noopener" target="_blank">#ipfire</a> <a href="https://mastodon.social/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#firewall</a> <a href="https://mastodon.social/tags/wireguard" class="mention hashtag" rel="nofollow noopener" target="_blank">#wireguard</a> <a href="https://mastodon.social/tags/vpn" class="mention hashtag" rel="nofollow noopener" target="_blank">#vpn</a> <a href="https://mastodon.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensource</a>

B'ad Samurai 🐐A list of 3rd party file mirrors you may not want users accessing.<a href="https://github.com/BadSamuraiDev/bs-lists/blob/main/file-mirrors.txt" rel="nofollow noopener" translate="no" target="_blank">https://github.com/BadSamuraiDev/bs-lists/blob/main/file-mirrors.txt</a><a href="https://infosec.exchange/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://infosec.exchange/tags/list" class="mention hashtag" rel="nofollow noopener" target="_blank">#list</a> <a href="https://infosec.exchange/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#firewall</a>

heise online EnglishCisco: Fresh firewalls from 1.5 to 400 Gbit/s throughputCisco completes its security portfolio with new firewalls, CVE protection on data center switches and uniform guidelines.<a href="https://www.heise.de/en/news/Cisco-Fresh-firewalls-from-1-5-to-400-Gbit-s-throughput-10452465.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon" rel="nofollow noopener" translate="no" target="_blank">https://www.heise.de/en/news/Cisco-Fresh-firewalls-from-1-5-to-400-Gbit-s-throughput-10452465.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon</a><a href="https://social.heise.de/tags/Cisco" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cisco</a> <a href="https://social.heise.de/tags/Firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firewall</a> <a href="https://social.heise.de/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> <a href="https://social.heise.de/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://social.heise.de/tags/Switch" class="mention hashtag" rel="nofollow noopener" target="_blank">#Switch</a> <a href="https://social.heise.de/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#news</a>

iX MagazinCisco: Frische Firewalls von 1,5 bis 400 Gbit/s DurchsatzCisco komplettiert sein Sicherheitsportfolio mit neuen Firewalls, CVE-Schutz auf Rechenzentrumsswitchen und einheitlichen Richtlinien.<a href="https://www.heise.de/news/Cisco-Frische-Firewalls-von-1-5-bis-400-Gbit-s-Durchsatz-10451983.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon" rel="nofollow noopener" translate="no" target="_blank">https://www.heise.de/news/Cisco-Frische-Firewalls-von-1-5-bis-400-Gbit-s-Durchsatz-10451983.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon</a><a href="https://social.heise.de/tags/Cisco" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cisco</a> <a href="https://social.heise.de/tags/Firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firewall</a> <a href="https://social.heise.de/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> <a href="https://social.heise.de/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://social.heise.de/tags/Switch" class="mention hashtag" rel="nofollow noopener" target="_blank">#Switch</a> <a href="https://social.heise.de/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#news</a>

iX MagaziniX-Workshop: Sicherer Betrieb von Windows 11 in UnternehmenLernen Sie an praktischen Beispielen, wie Sie Windows 11 Pro und Enterprise in Ihrem Unternehmen sicher und effektiv einsetzen.<a href="https://www.heise.de/news/iX-Workshop-Sicherer-Betrieb-von-Windows-11-in-Unternehmen-10443417.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon" rel="nofollow noopener" translate="no" target="_blank">https://www.heise.de/news/iX-Workshop-Sicherer-Betrieb-von-Windows-11-in-Unternehmen-10443417.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon</a><a href="https://social.heise.de/tags/Firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firewall</a> <a href="https://social.heise.de/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> <a href="https://social.heise.de/tags/iXWorkshops" class="mention hashtag" rel="nofollow noopener" target="_blank">#iXWorkshops</a> <a href="https://social.heise.de/tags/Malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Malware</a> <a href="https://social.heise.de/tags/Verschl%C3%BCsselung" class="mention hashtag" rel="nofollow noopener" target="_blank">#Verschlüsselung</a> <a href="https://social.heise.de/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> <a href="https://social.heise.de/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#news</a>

𝕂𝚞𝚋𝚒𝚔ℙ𝚒𝚡𝚎𝚕Rethinking Regex: Smarter detection for a modern threat landscapeUsing regular expressions, or regex, was once a convenient and powerful way for web application firewalls (WAFs) to find malicious code in web requests.🛡️ <a href="https://www.scworld.com/resource/rethinking-regex-smarter-detection-for-a-modern-threat-landscape" rel="nofollow noopener" translate="no" target="_blank">https://www.scworld.com/resource/rethinking-regex-smarter-detection-for-a-modern-threat-landscape</a><a href="https://chaos.social/tags/regex" class="mention hashtag" rel="nofollow noopener" target="_blank">#regex</a> <a href="https://chaos.social/tags/thread" class="mention hashtag" rel="nofollow noopener" target="_blank">#thread</a> <a href="https://chaos.social/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#firewall</a> <a href="https://chaos.social/tags/code" class="mention hashtag" rel="nofollow noopener" target="_blank">#code</a> <a href="https://chaos.social/tags/web" class="mention hashtag" rel="nofollow noopener" target="_blank">#web</a> <a href="https://chaos.social/tags/itsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#itsec</a> <a href="https://chaos.social/tags/request" class="mention hashtag" rel="nofollow noopener" target="_blank">#request</a> <a href="https://chaos.social/tags/webapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#webapp</a> <a href="https://chaos.social/tags/threat" class="mention hashtag" rel="nofollow noopener" target="_blank">#threat</a> <a href="https://chaos.social/tags/waf" class="mention hashtag" rel="nofollow noopener" target="_blank">#waf</a> <a href="https://chaos.social/tags/itsecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#itsecurity</a> <a href="https://chaos.social/tags/websecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#websecurity</a>

GNU/Linux.chiptables-Regeln erstellen und dauerhaft speichern (Iptables Teil 2)In diesem Artikel erkläre ich, wie man eigene Firewall-Regeln mit iptables erstellt und dauerhaft speichert. Mit dabei: eine Einführung in die wichtigsten Begriffe wie INPUT, OUTPUT, DROP und conntrack. <a href="https://social.anoxinon.de/tags/iptables" class="mention hashtag" rel="nofollow noopener" target="_blank">#iptables</a> <a href="https://social.anoxinon.de/tags/iptables_persistent" class="mention hashtag" rel="nofollow noopener" target="_blank">#iptables_persistent</a> <a href="https://social.anoxinon.de/tags/Firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firewall</a> <a href="https://social.anoxinon.de/tags/Netzwerksicherheit" class="mention hashtag" rel="nofollow noopener" target="_blank">#Netzwerksicherheit</a> <a href="https://social.anoxinon.de/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://social.anoxinon.de/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a><a href="https://gnulinux.ch/iptables-regeln-erstellen-und-dauerhaft-speichern-iptables-teil-2" rel="nofollow noopener" translate="no" target="_blank">https://gnulinux.ch/iptables-regeln-erstellen-und-dauerhaft-speichern-iptables-teil-2</a>

» Aakerbeere 🏖️ :mastodon:💬 Hallo <a href="https://mastodon.social/@rdns" class="u-url mention" rel="nofollow noopener" target="_blank">@rdns</a>,warum zeigt mir <a href="https://mastodon.social/tags/RETHINK" class="mention hashtag" rel="nofollow noopener" target="_blank">#RETHINK</a> falsche Informationen zu der IP-Adresse an?Der Server ist nicht in Australien, sondern in der Schweiz<a href="https://mastodon.social/tags/Firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#Firewall</a>

nickbeardedHad a beer. Got an idea.Why not use a live USB with BashCore in a dust-collector old pc as a smart home firewall?🧱 Block IoT devices from phoning home 🔒 Route traffic through a hardened CLI 📡 SSH in, control everythingNo install. No bloat. Just power. 💪👉 <a href="https://bashcore.org" rel="nofollow noopener" translate="no" target="_blank">https://bashcore.org</a><a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.social/tags/iot" class="mention hashtag" rel="nofollow noopener" target="_blank">#iot</a> <a href="https://mastodon.social/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#firewall</a> <a href="https://mastodon.social/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a> <a href="https://mastodon.social/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://mastodon.social/tags/bashcore" class="mention hashtag" rel="nofollow noopener" target="_blank">#bashcore</a>

Pseudo NymIt's dangerous to go alone. Here. Take this.<a href="https://mastodon.online/tags/infosec" class="mention hashtag" rel="nofollow noopener" target="_blank">#infosec</a> <a href="https://mastodon.online/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> <a href="https://mastodon.online/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#firewall</a> Note: this is totally how cybersecurity works.

Rynn the Cyberwitch 🌙Hey other <a href="https://furry.engineer/tags/network" class="mention hashtag" rel="nofollow noopener" target="_blank">#network</a> folks I have a weird <a href="https://furry.engineer/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#firewall</a> and <a href="https://furry.engineer/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#NAT</a> question. I'm looking at the firewall traffic log where my work laptop (I'm in the office) is the source, and I'm looking at the traffic connecting to my home plex server. The plex server is a private IP behind NAT. In the log I show the putbound traffic from my work laptop to my home router IP, but I also see a following entry with the private IP that my router is forwarding plex's port traffic to. I thought anything done behind NAT wouldn't show up, especially because I'm only looking at the initial communication out, and not the return communication from my server to my me. Is my understanding of NAT wrong?

Recent searches

Search options

Administered by:

Server stats: