toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

230
active users

#nat

1 post1 participant0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://oldbytes.space/@drscriptt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>drscriptt</span></a></span> Naive question: <em>WHEN</em> does the average <a href="https://infosec.space/tags/Internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Internet</span></a> <a href="https://infosec.space/tags/user" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>user</span></a> ever open up a webpage with an <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IP</span></a> address instead of a <a href="https://infosec.space/tags/domain" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>domain</span></a> or even <a href="https://infosec.space/tags/FQDN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FQDN</span></a>?</p><ul><li>Seriously, the only cases I saw were either some old, non-public - facing server in some B2B/API setting <em>or</em> a test that <a href="https://infosec.space/tags/httpd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>httpd</span></a> / <a href="https://infosec.space/tags/ngnix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ngnix</span></a> / <a href="https://infosec.space/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ssh</span></a> / … function properly on like a <a href="https://infosec.space/tags/VPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VPS</span></a> and that the <a href="https://infosec.space/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS</span></a> hasn't been updated (yet!) to include said host / FQDN in the records, and even then it's <em>bad</em> cuz you'd rather want to use it's FQDN instead because with <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> shortages on one hand and tools like <a href="https://infosec.space/tags/Portainer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Portainer</span></a> on the other, one should not use an <a href="https://infosec.space/tags/IPaddress" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPaddress</span></a> as addressing method because <a href="https://infosec.space/tags/WAF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WAF</span></a> / <a href="https://infosec.space/tags/Proxies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Proxies</span></a> used to <em>"<a href="https://infosec.space/tags/MUX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MUX</span></a>"</em> / <em>"<a href="https://infosec.space/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a>"</em> services under one IP address or <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> block may need that distinction by being queried for a specific FQDN... </li></ul><p>The Idea if !SSL / <a href="https://infosec.space/tags/TLD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TLD</span></a> for <a href="https://infosec.space/tags/IPaddresses" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPaddresses</span></a> makes me <a href="https://www.youtube.com/watch?v=g3j9muCo4o0" rel="nofollow noopener" target="_blank">feel like Jeff Goldblum!</a></p>
argv minus one<p>One of the great and wonderful things about the early <a href="https://mastodon.sdf.org/tags/Internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Internet</span></a> was that you could send a packet, containing whatever bytes you want, to *any* computer, anywhere in the world, at will and without ceremony.</p><p>Then dynamic addressing and <a href="https://mastodon.sdf.org/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a> came along and ruined everything. 😭</p>
mkj<p>Do I have anyone within my reach who would be willing to help me debug a DNAT issue on OPNsense?</p><p>I can sincerely say that it's *probably* trivial, and I am *probably* just missing something obvious; but it's not obvious when you're not quite sure what you're looking for. Reading the documentation, browsing the forum and searching the web has not led me to find a solution.</p><p>Boosts appreciated.</p><p><a href="https://social.mkj.earth/tags/OPNsense" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OPNsense</span></a> <a href="https://social.mkj.earth/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a> <a href="https://social.mkj.earth/tags/DNAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNAT</span></a> <a href="https://social.mkj.earth/tags/network" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>network</span></a> <a href="https://social.mkj.earth/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a> <a href="https://social.mkj.earth/tags/TCPIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TCPIP</span></a></p>
Hubu.de<p><a href="https://mastodon.social/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>news</span></a> ⚡ Gericht: Trumps Einsatz der Nationalgarde in Kalifornien illegal: Ein Bezirksgericht in San Francisco hat die Entsendung der Nationalgarde durch die US-Regierung unter Präsident Donald Trump nach Kali... <a href="https://hubu.de/?p=282515" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">hubu.de/?p=282515</span><span class="invisible"></span></a> | <a href="https://mastodon.social/tags/einsatz" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>einsatz</span></a> <a href="https://mastodon.social/tags/gericht" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gericht</span></a> <a href="https://mastodon.social/tags/kalifornien" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kalifornien</span></a> <a href="https://mastodon.social/tags/nat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nat</span></a></p>
mkj<p><span class="h-card" translate="no"><a href="https://furry.engineer/@lycanmatriarch" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lycanmatriarch</span></a></span> That does sound weird. The LAN-side-of-NAT IP (typically RFC 1918 space) should only show up on the LAN side of NAT. That's kind of the point of NAT.</p><p>Are you *sure* it's your Plex box originating that traffic, and not just some other machine on the network you're on that happens to have the same IP address? Maybe something in the Plex web UI which happens to include a request to its internal IP address and which (obviously) does not get rewritten by the NAT at your home?</p><p><a href="https://social.mkj.earth/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a></p>
Rynn 🌙 Professional Cyberwitch 🌙<p>Hey other <a href="https://furry.engineer/tags/network" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>network</span></a> folks I have a weird <a href="https://furry.engineer/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>firewall</span></a> and <a href="https://furry.engineer/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></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. </p><p>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?</p>
Litchralee_v6<p>What Docker did was to intellectually limit the creativity that users could have had with containers, funneling everyone into the most trivial of network use-cases. When everything is server-client, it's really hard to develop peer-to-peer or avant guard applications.</p><p>The parallels to <a href="https://ipv6.social/tags/LegacyIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LegacyIP</span></a> and <a href="https://ipv6.social/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a> are staggering, as they too stymied progress in other, not-yet imagined scenarios. <a href="https://ipv6.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> should have been the go-to for hyperscalar from day-one. That it wasn't is forever a travesty.</p><p>7/n</p>
Peter N. M. Hansteen<p>EdgeRouter 4 under OpenBSD with Failover WAN <a href="https://www.undeadly.org/cgi?action=article;sid=20250516062907" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">undeadly.org/cgi?action=articl</span><span class="invisible">e;sid=20250516062907</span></a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openbsd</span></a> <a href="https://mastodon.social/tags/octeon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>octeon</span></a> <a href="https://mastodon.social/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a> <a href="https://mastodon.social/tags/router" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>router</span></a> <a href="https://mastodon.social/tags/edgerouter" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>edgerouter</span></a> <a href="https://mastodon.social/tags/wan" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wan</span></a> <a href="https://mastodon.social/tags/failover" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>failover</span></a> <a href="https://mastodon.social/tags/ifstated" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ifstated</span></a> <a href="https://mastodon.social/tags/nat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nat</span></a> <a href="https://mastodon.social/tags/dhcp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dhcp</span></a> <a href="https://mastodon.social/tags/dns" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dns</span></a> <a href="https://mastodon.social/tags/libresoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>libresoftware</span></a> <a href="https://mastodon.social/tags/freesoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freesoftware</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.social/@jschauma" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jschauma</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@ryanc" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ryanc</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>0xabad1dea</span></a></span> yeah, the exhaustion problem would've been shoved back with a <a href="https://infosec.space/tags/64bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>64bit</span></a> or sufficiently delayed by a 40bit number.</p><p>Unless we also hate <a href="https://infosec.space/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a> and expect every device to have a unique static <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IP</span></a> (which is a <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a> nightmare at best that <em>"<a href="https://infosec.space/tags/PrivacyExtensions" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PrivacyExtensions</span></a>"</em> barely fixed.) </p><ul><li>I mean they could've also gone the <a href="https://infosec.space/tags/DECnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DECnet</span></a> approach and use the <a href="https://infosec.space/tags/EUI48" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EUI48</span></a> / <a href="https://infosec.space/tags/MAC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MAC</span></a>-Address (or <a href="https://infosec.space/tags/EUI64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EUI64</span></a>) as static addressing system, but that would've made <a href="https://infosec.space/tags/vendors" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vendors</span></a> and not <a href="https://infosec.space/tags/ISPs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ISPs</span></a> the powerful forces of allocation. (Similar to how technically the <a href="https://infosec.space/tags/ICCID" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ICCID</span></a> dictates <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GSM</span></a> / <a href="https://infosec.space/tags/4G" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>4G</span></a> / <a href="https://infosec.space/tags/5G" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>5G</span></a> access and not the <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IMEI</span></a> unless places like Australia ban imported devices.</li></ul> <p>I guess using a <a href="https://infosec.space/tags/128bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>128bit</span></a> address space was inspired by <a href="https://infosec.space/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ZFS</span></a> doing the same <em>before</em>, as the folks who designed both wanted to design a solution that clearly will outlive them (<em>way harder</em> than COBOL has outlived Grace Hopper)...</p><ul><li>Personally I've only had headaches with <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> because not only do I only have <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4only</span></a> <a href="https://infosec.space/tags/Internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Internet</span></a> but my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ISP</span></a> refuses to allocate even a singe /64 to me (but has no problem throwing in a free /29 of <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a>'s in with my contract!)and stuff like <a href="https://infosec.space/tags/HurricaneElectric" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HurricaneElectric</span></a> / <a href="https://infosec.space/tags/HEnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HEnet</span></a>'s <a href="https://infosec.space/tags/Tunnelbroker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tunnelbroker</span></a> fail face first due to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Geoblocking</span></a> and the fact that <a href="https://infosec.space/tags/ASNs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ASNs</span></a> get geolocated, not their <a href="https://infosec.space/tags/PoPs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PoPs</span></a>... </li></ul><p>If I was <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>BNetzA</span></a></span> I would've mandated <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DualStack</span></a> and banned <a href="https://infosec.space/tags/CGNAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CGNAT</span></a> (or at least the use of CGNAT in <a href="https://infosec.space/tags/RFC1918" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RFC1918</span></a> address spaces) as well as <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DualStackLite</span></a>!</p>
Brigitte<a href="https://pixelfed.social/discover/tags/Kreuzberg?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#Kreuzberg</a> heute<br> <br> Artist: NAT<br> <a href="https://nat-at-art.de/" rel="nofollow noopener" target="_blank">https://nat-at-art.de/</a><br> <br> <a href="https://pixelfed.social/discover/tags/Berlin?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#Berlin</a> <a href="https://pixelfed.social/discover/tags/Streetart?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#Streetart</a> <a href="https://pixelfed.social/discover/tags/NAT?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#NAT</a> <a href="https://pixelfed.social/discover/tags/natatart?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#natatart</a> <a href="https://pixelfed.social/discover/tags/pasteup?src=hash" class="u-url hashtag" rel="nofollow noopener" target="_blank">#pasteup</a>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.online/@herrorange" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>herrorange</span></a></span> how?</p><p>Like I really wounder why...</p><p>Is it due to shitty <a href="https://infosec.space/tags/CGNAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CGNAT</span></a> at the <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ISP</span></a> end and <a href="https://infosec.space/tags/Skype" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Skype</span></a> doing aggresssive <a href="https://infosec.space/tags/HolePunching" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HolePunching</span></a> through any <a href="https://infosec.space/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a> or some other <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ISP</span></a>-side shenanigans?</p>
Dan Wing<p>Ole Trøan discusses mistakes and missed opportunities with <a href="https://infosec.exchange/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> design. <a href="https://medium.com/@oletroan/the-mistakes-and-missed-opportunities-in-ipv6-d88ceb3d7feb" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">medium.com/@oletroan/the-mista</span><span class="invisible">kes-and-missed-opportunities-in-ipv6-d88ceb3d7feb</span></a> <a href="https://infosec.exchange/tags/nat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nat</span></a></p>
Hubu.de<p><a href="https://mastodon.social/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>news</span></a> ⚡ Nato-Generalsekretär mahnt Deutschland zu höheren Militärausgaben: Nato-Generalsekretär Mark Rutte ruft Deutschland auf, sowohl seine Militärausgaben als auch seine Rüstungsproduktion massiv zu erhöhe... <a href="https://hubu.de/?p=264986" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">hubu.de/?p=264986</span><span class="invisible"></span></a> | <a href="https://mastodon.social/tags/deutschland" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>deutschland</span></a> <a href="https://mastodon.social/tags/militaerausgaben" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>militaerausgaben</span></a> <a href="https://mastodon.social/tags/nat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nat</span></a></p>
C.<p><span class="h-card" translate="no"><a href="https://mindly.social/@wanderinghermit" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>wanderinghermit</span></a></span> </p><p>"Silently die" is commonly caused on Linux by the system OOM killer if the program allocates enough memory to drive the system into an out-of-memory state. Turning off overcommit on the system can be used to confirm this, as it will generally result in the Python program running until a MemoryError exception is thrown, and it will exit with a stacktrace rather than be killed before it can do so. Offhand I don't know what the behaviour on other OSes would be.</p><p>The print-prevents-dying thing I have seen before, but only when running programs on a remote machine. If there is no I/O at all happening, a network connection can end up getting reset for various reasons, causing the exit-to-shell behaviour. Adding print statements that happen to get called often enough to prevent this papers over the problem.</p><p>If this is the problem, and you're running over SSH, there are SSH options to make the session not die like this - keepalives.</p><p><a href="https://mindly.social/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSH</span></a> <a href="https://mindly.social/tags/network" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>network</span></a> <a href="https://mindly.social/tags/timeout" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>timeout</span></a> <a href="https://mindly.social/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a> <a href="https://mindly.social/tags/KeepAlive" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>KeepAlive</span></a> <a href="https://mindly.social/tags/die" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>die</span></a></p>
BoxyBSD<p>This weekend we started to integrate the NAT64 support for our free VPS infrastructure to make your life easier. Stay tuned, the global rollout is near :)</p><p><a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/BoxyBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BoxyBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> <a href="https://mastodon.bsd.cafe/tags/Hosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Hosting</span></a> <a href="https://mastodon.bsd.cafe/tags/Provider" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Provider</span></a> <a href="https://mastodon.bsd.cafe/tags/BGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BGP</span></a> <a href="https://mastodon.bsd.cafe/tags/Free" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Free</span></a> <a href="https://mastodon.bsd.cafe/tags/Opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Opensource</span></a> <a href="https://mastodon.bsd.cafe/tags/community" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>community</span></a> <a href="https://mastodon.bsd.cafe/tags/VPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VPS</span></a> <a href="https://mastodon.bsd.cafe/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a> <a href="https://mastodon.bsd.cafe/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> <a href="https://mastodon.bsd.cafe/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> <a href="https://mastodon.bsd.cafe/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a> <span class="h-card" translate="no"><a href="https://mastodon.gyptazy.com/@gyptazy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>gyptazy</span></a></span></p>
napierge<p>Finally run debian12 with gui thanks to vm-bhyve on freebsd14 after several month of tweaking and learning. Really big thank to <span class="h-card" translate="no"><a href="https://mastodon.bsd.cafe/@vermaden" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>vermaden</span></a></span> and his article <a href="https://vermaden.wordpress.com/2023/08/18/freebsd-bhyve-virtualization/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">vermaden.wordpress.com/2023/08</span><span class="invisible">/18/freebsd-bhyve-virtualization/</span></a> ❤️</p><p>But one thing I still dont get it. I have a problem with resolving a DNS on the VM. IP addreses works well but domain names like google.com not at all. I solved it by adding "nameserver 8.8.8.8" in /etc/resolv.conf in VM, but I am not sure if I solve it well and dont understabd why I have to solve it anyway, I do not remeber that I would have to set it.<br>I se vm-bhyve with host wifi wlan interface so I had to set NAT in PF, in article it is a section laptop wifi nat. Is it normal to set resolv.conf file in VM?</p><p><a href="https://mastodon.bsd.cafe/tags/freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freebsd</span></a> <a href="https://mastodon.bsd.cafe/tags/bhyve" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bhyve</span></a> <a href="https://mastodon.bsd.cafe/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>debian</span></a> <a href="https://mastodon.bsd.cafe/tags/nat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nat</span></a> <a href="https://mastodon.bsd.cafe/tags/pf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pf</span></a> <a href="https://mastodon.bsd.cafe/tags/virtualization" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>virtualization</span></a></p>

#Jazz

Here's a great clip from the #NatKingCole Show in the 50's featuring musicians from #NormanGranz 's #JazzAtThePhilharmonic #JATP group including but not limited to Oscar Peterson, Ray Brown, Herb Ellis, Stan Getz, Illinois Jacquet, Coleman Hawkins, Jo Jones & Roy Eldridge.

Most people don't know that #Nat got his start in jazz as a piano player & transitioned to being popular music singer.

There are some get sets w/Nat featuring a variety of JATP musicians which are timeless.

This early 50' period in jazz is called #Modern but I call it #Timeless bc it is my favorite period in American jazz history.

Nat's performance of "Paper Moon" & "Tenderly" are classic.

youtu.be/po9dxA7iFOc

Continued thread

Ok I guess I'll have to give up again quite quickly 😦

#Microsoft #Teams is broken for me as soon as I disable #IPv4. From what I could understand in this horrible mess of a "web app", the reason is probably some #CORS error. I have no idea how that could ever be related to #IPv6 or #NAT or anything. Tried temporarily disabling #NAT64 (to force direct v6 connections), tried adding all of Microsofts v6 networks to the "exclude" option of bind9 to have everything pass #NAT64 *avoiding* native IPv6, tried several ways to disable CORS, nothing helped. 🤬

Anyone know about these issues with teams?

edit: to clarify, "everything" seems to work except for the main purpose: join an actual call ...

Maybe it *is* about time to go #IPv6only. Currently running my desktop without #IPv4 for testing.

The outside #IPv4 world is reachable with #NAT64 provided by #tayga running on my #FreeBSD router/firewall (with pf for stateful #NAT and actual firewalling), great! That's the most important part, I mean, nothing we can do about stubbornly operated v4-only stuff outside.

Now I identify all the stuff still not offering #IPv6 in my home network. Already fixed parts of my mail system and my irssi-proxy (for IRC). But there's more to check ... none of my VPN tunnels currently transport v6 ... and I'm still a bit unsure about all the devices (e.g. switch and access points in my management segment, or stuff like a vacuum robot or a kitchen radio in my IoT segment ... oh boy 😂🙈)