<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>NetBSD &amp;mdash; skrot</title>
    <link>https://scrolls.anduin.net/ltning/tag:NetBSD</link>
    <description>Skrot[NO-NB] = junk; these are my retrocomputing notes</description>
    <pubDate>Tue, 17 Nov 2026 19:12:08 +0000</pubDate>
    <item>
      <title>OS/2: Connecting ezIRC/2 to ZNC</title>
      <link>https://scrolls.anduin.net/ltning/os-2-connecting-ezirc-2-to-znc</link>
      <description>&lt;![CDATA[For anyone who has followed my escapades in retrocomputing at all, me &#34;doing silly stuff with old stuff&#34; should not surprise anyone. But on the list of weird problems I&#39;ve decided to tackle, this one might be among the silliest.&#xA;&#xA;Wait, what?&#xA;So I&#39;m a huge OS/2 fan, as I have been since the early 90&#39;s when the first beta versions became availablea id=&#34;n1&#34;[1/a]. The first versions were incredibly painful to run on the hardware I had: My dad&#39;s 25MHz 486 - can&#39;t remember if it was an SX or a DX - had 4MB of RAM. While this did meet the minimum requirements, it was really, really painful. My own 16MHz 386SX at home had all of 5MB, and despite the dog slow CPU (compared to the 486), it practically flew.&#xA;&#xA;Once I got past that initial pain, the wonders of this operating system did not cease to impress me. I remained a fan, and avid user, until around 2003, when I finally switched to FreeBSD even on my desktop and laptop machines.&#xA;&#xA;It should therefore surprise exactly nobody that I&#39;m now running OS/2, 24/7 or at least part-time, on \checks notes\ ...8? machinesa id=&#34;n2&#34;[2/a].&#xA;&#xA;And .. IRC?&#xA;Back in 1996 when I started studying was when I met my first UNIX machines. The computer room at uni was full of Ultrix, HP-UX, Solaris and other things I had heard of but never actually used. I was still using OS/2 privately, but I could not help being fascinated by this new world that opened up to me.&#xA;&#xA;Among the first applications I truly fell in love with was IRC. I don&#39;t even know what the first IRC client I used was, probably ircII or some variant thereof. I soon learned of scripts and such to improve the &#34;user experience&#34;, and before long I was running OpenChat/2 on my OS/2 machines. But since 1996 was already the year of OS/2 Warp 4, I was late to the game: Others had been on IRC for years already, and there were several older IRC applications out there that - at the time - I didn&#39;t know of, nor did I need them.&#xA;&#xA;Fast forward a couple dozen years though, and I find myself running significantly older OS/2 versions - like 2.11 - on machines much older than the PC I had at the time. But since there&#39;s TCP/IP even for this old OS/2 version, I do need to make it &#34;useful&#34;, so off I go looking for IRC clients that work - because my old friend OpenChat/2 requires newer stuff to run.&#xA;&#xA;Enter ezIRC!&#xA;At some point in the mid-90s, Roger Bess released ezIRC. I don&#39;t have a good history for this program, as the only archived website seems to have been published around the time of the last known release. But of all the PM-type (GUI) IRC applications I&#39;ve managed to find, it&#39;s about the only one that works on OS/2 2.x and doesn&#39;t look absolutely bonkers.&#xA;&#xA;Problem is .. it&#39;s old. And, when exposed to &#34;modern&#34; IRC servers, UTF-8, protocol extensions and weird server CAPabilities, it gets real confused, real fast. It also does not support server passwordsa id=&#34;n3&#34;[3/a], so connecting to ZNC is not actully possible.&#xA;&#xA;After a lot of trial and error (and tcpdumping and whatnot), plus some help (and only limited amounts of mockery) from the fine people on \#znc (Libera), I arrived at a solution\^Wworkaround.&#xA;&#xA;As a bonus, this involves the use of another, only slightly newer, piece of hardware.&#xA;&#xA;The solution: Irssi&#xA;One of the possible solutions I was looking for was some kind of IRC proxy. This however does not really seem to be a thing: I found some variants over the theme, but they were either actual bouncers (already got one, thanks!) or they were solving different sets of problems - and in most cases they were horribly obsolete.&#xA;&#xA;As a side note, my requirement for a solution was that it could only involve software that could run on one of my other retro-rigs; the prime candidate being my trusty dual Pentium Pro/P2OD machine running #NetBSD. Turns out, I already had the necessary software installed!&#xA;&#xA;Irssi has a surprisingly useful feature they call Irssiproxy. Basically this sets up a separate listening port in Irssi itself, which allows connecting clients to share the associated IRC network connection with Irssi.&#xA;&#xA;How perfect is this?!? I can configure the networks i need and associated ZNC connections in Irssi, and have it listen on a set of port numbers on my LAN - and ezIRC can connect with no additional hassle.&#xA;&#xA;Except....&#xA;The only real issue I encountered (other than PEBKAC situaitons) was the aforementioned server capability messages which caused ezIRC some confusion. Basically it could join channels and send messages to them, but inbound messages were just dropped on the floor (or, in some cases, shown in the &#34;server messages&#34; window).&#xA;&#xA;I tried connection Irssi directly to the target IRC network (bypassing ZNC), which seemed to solve the problem - but also got in the way of what I tried to achieve.&#xA;&#xA;With some tcpdump and Wireshark work, I found that ZNC adds @time= to the messages. As confirmed by one of the helpful souls on IRC, this is only added if the connecting client asks for it. Luckily the solution is easy: Tell Irssi to skip sending the CAPREQ to ZNC.&#xA;&#xA;The configuration&#xA;First, the server config:&#xA;&#xA;servers = (&#xA;  {&#xA;    address = &#34;znc.example.com&#34;;&#xA;    chatnet = &#34;os2Floppy&#34;;&#xA;    port = &#34;195&#34;;&#xA;    password = &#34;user@client-id/network:password&#34;;&#xA;    usetls = &#34;yes&#34;;&#xA;    tlsverify = &#34;yes&#34;;&#xA;    nocap = &#34;yes&#34;;&#xA;  },&#xA;  {&#xA;    address = &#34;znc.example.com&#34;;&#xA;    chatnet = &#34;os2EFNet&#34;;&#xA;    port = &#34;195&#34;;&#xA;    password = &#34;user@client-id/network:password&#34;;&#xA;    usetls = &#34;yes&#34;;&#xA;    tlsverify = &#34;yes&#34;;&#xA;    nocap = &#34;yes&#34;;&#xA;  },&#xA;  {&#xA;    address = &#34;znc.example.com&#34;;&#xA;    chatnet = &#34;os2Libera&#34;;&#xA;    port = &#34;195&#34;;&#xA;    password = &#34;user@client-id/network:password&#34;;&#xA;    usetls = &#34;yes&#34;;&#xA;    tlsverify = &#34;yes&#34;;&#xA;    nocap = &#34;yes&#34;;&#xA;  }&#xA;);&#xA;&#xA;No channels configured here, as ZNC takes care of that&#xA;channels = ( );&#xA;&#xA;And then the core config; note the proxy section:&#xA;&#xA;settings = {&#xA;  core = {&#xA;    realname = &#34;Eirik Overby&#34;;&#xA;    username = &#34;ltning&#34;;&#xA;    nick = &#34;o-Ltning&#34;;&#xA;    recodetransliterate = &#34;no&#34;;&#xA;  };&#xA;  proxy = {&#xA;    irssiproxybind = &#34;192.88.99.80&#34;; # The local IP&#xA;    irssiproxyports = &#34;os2Floppy=2777 os2EFNet=2778 os2Libera=2779&#34;; # Per-chatnet listening ports&#xA;  };&#xA;};&#xA;&#xA;The chat networks, as used by the server config:&#xA;chatnets = {&#xA;  os2Floppy = { type = &#34;IRC&#34;; };&#xA;  os2EFNet = { type = &#34;IRC&#34;; };&#xA;  os2Libera = { type = &#34;IRC&#34;; };&#xA;};&#xA;&#xA;The result&#xA;And with that, I have a working config. The obligatory screenshot below.&#xA;&#xA;Good luck (if you should end up trying this yourself), and thanks for reading!&#xA;&#xA;ezIRC running on OS/2 2.11&#xA;&#xA;Footnotes&#xA;a id=&#34;fn1&#34;1/a: I spent many hours pestering IBM Norway into sending me a copy of the beta; I&#39;m sure I ended up on some list somewhere.&#xA;a id=&#34;fn2&#34;2/a: The current builds include&#xA;    A 486DX-50 running Warp 3 and Novell Netware 4.12 paravirtualized&#xA;    A 486DRx2-50 (really a 386 with a bit of cache) running Warp 3 and my BBS&#xA;    The subject of this article, a 486DLC-40 running 2.11&#xA;    A dual Pentium 233 MMX running Warp 4.52&#xA;    A 286 running OS/2 1.3 EE(!)&#xA;    A dual Pentium Pro which, when not running NetBSD or DOS runs Warp Server for e-Business&#xA;    An IBM 486slc2 - Leopard or Leopard LX-based, depending on my mood - running Warp 3&#xA;    An IBM PS/2 model P70 luggable running 2.11&#xA;a id=&#34;fn3&#34;3/a: Turns out, it does as of version 1.2o. But given all the other problems, this is mostly of academic interest at this point..&#xA;&#xA;div style=&#34;display: flex; place-content: center;&#34;table style=&#34;width: 80%; border: none; font-size: 0.8em;&#34;&#xD;&#xA;tr style=&#34;border: none;&#34;&#xD;&#xA;td align=&#34;center&#34; style=&#34;border: none;&#34; colspan=&#34;2&#34;hr&#xD;&#xA;~ love over gold ~/td&#xD;&#xA;/tr&#xD;&#xA;tr style=&#34;border: none; background-color: inherit;&#34;&#xD;&#xA;td align=&#34;left&#34; style=&#34;border: none; padding-left: 2em;&#34;a href=&#34;http://floppy.museum&#34;The Floppy Museum/a/td&#xD;&#xA;td align=&#34;right&#34; style=&#34;border: none; padding-right: 2em;&#34;a href=&#34;http://floppy.museum/thispc.htm&#34;About the Museum/a/td&#xD;&#xA;/tr/table/div]]&gt;</description>
      <content:encoded><![CDATA[<p>For anyone who has followed my escapades in retrocomputing at all, me “doing silly stuff with old stuff” should not surprise anyone. But on the list of weird problems I&#39;ve decided to tackle, this one might be among the silliest.</p>

<h2 id="wait-what">Wait, what?</h2>

<p>So I&#39;m a huge <a href="https://en.wikipedia.org/wiki/OS/2" rel="nofollow">OS/2</a> fan, as I have been since the early 90&#39;s when the first beta versions became available[<a id="n1"><a href="#fn1" rel="nofollow">1</a></a>]. The first versions were incredibly painful to run on the hardware I had: My dad&#39;s 25MHz 486 – can&#39;t remember if it was an SX or a DX – had 4MB of RAM. While this did meet the minimum requirements, it was really, really painful. My own 16MHz 386SX at home had all of <em>5</em>MB, and despite the dog slow CPU (compared to the 486), it practically <em>flew</em>.</p>

<p>Once I got past that initial pain, the wonders of this operating system did not cease to impress me. I remained a fan, and avid user, until around 2003, when I finally switched to <a href="https://freebsd.org" rel="nofollow">FreeBSD</a> even on my desktop and laptop machines.</p>

<p>It should therefore surprise exactly nobody that I&#39;m now running OS/2, 24/7 or at least part-time, on *checks notes* ...8? machines[<a id="n2"><a href="#fn2" rel="nofollow">2</a></a>].</p>

<h2 id="and-irc">And .. IRC?</h2>

<p>Back in 1996 when I started studying was when I met my first UNIX machines. The computer room at uni was full of Ultrix, HP-UX, Solaris and other things I had heard of but never actually used. I was still using OS/2 privately, but I could not help being fascinated by this new world that opened up to me.</p>

<p>Among the first applications I truly fell in love with was IRC. I don&#39;t even know what the first IRC client I used was, probably ircII or some variant thereof. I soon learned of scripts and such to improve the “user experience”, and before long I was running OpenChat/2 on my OS/2 machines. But since 1996 was already the year of OS/2 Warp 4, I <em>was</em> late to the game: Others had been on IRC for years already, and there were several older IRC applications out there that – at the time – I didn&#39;t know of, nor did I need them.</p>

<p>Fast forward a couple dozen years though, and I find myself running significantly older OS/2 versions – like 2.11 – on machines much older than the PC I had at the time. But since there&#39;s TCP/IP even for this old OS/2 version, I do need to make it “useful”, so off I go looking for IRC clients that work – because my old friend OpenChat/2 requires newer stuff to run.</p>

<h2 id="enter-ezirc">Enter ezIRC!</h2>

<p>At some point in the mid-90s, Roger Bess released ezIRC. I don&#39;t have a good history for this program, as the only <a href="https://web.archive.org/web/19981201213126/http://www.gryn.org/ezirc/" rel="nofollow">archived website</a> seems to have been published around the time of the last known release. But of all the PM-type (GUI) IRC applications I&#39;ve managed to find, it&#39;s about the only one that works on OS/2 2.x and doesn&#39;t look absolutely bonkers.</p>

<p>Problem is .. it&#39;s old. And, when exposed to “modern” IRC servers, UTF-8, protocol extensions and weird server CAPabilities, it gets real confused, real fast. It also does not support server passwords[<a id="n3"><a href="#fn3" rel="nofollow">3</a></a>], so connecting to <a href="https://wiki.znc.in/ZNC" rel="nofollow">ZNC</a> is not actully possible.</p>

<p>After a lot of trial and error (and <code>tcpdump</code>ing and whatnot), plus some help (and only limited amounts of mockery) from the fine people on #znc (Libera), I arrived at a solution\^Wworkaround.</p>

<p>As a bonus, this involves the use of another, only slightly newer, piece of hardware.</p>

<h2 id="the-solution-irssi">The solution: Irssi</h2>

<p>One of the possible solutions I was looking for was some kind of IRC proxy. This however does not really seem to be a thing: I found some variants over the theme, but they were either actual bouncers (already got one, thanks!) or they were solving different sets of problems – and in most cases they were horribly obsolete.</p>

<p>As a side note, my requirement for a solution was that it could only involve software that could run on one of my other retro-rigs; the prime candidate being my trusty dual Pentium Pro/P2OD machine running <a href="/ltning/tag:NetBSD" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">NetBSD</span></a>. Turns out, I already had the necessary software installed!</p>

<p><a href="https://irssi.org/" rel="nofollow">Irssi</a> has a surprisingly useful feature they call <a href="https://raw.githubusercontent.com/irssi/irssi/refs/heads/master/docs/proxy.txt" rel="nofollow">Irssiproxy</a>. Basically this sets up a separate listening port in Irssi itself, which allows connecting clients to share the associated IRC network connection with Irssi.</p>

<p>How perfect is this?!? I can configure the networks i need and associated ZNC connections in Irssi, and have it listen on a set of port numbers on my LAN – and ezIRC can connect with no additional hassle.</p>

<h3 id="except">Except....</h3>

<p>The only real issue I encountered (other than PEBKAC situaitons) was the aforementioned server capability messages which caused ezIRC some confusion. Basically it could join channels and send messages to them, but inbound messages were just dropped on the floor (or, in some cases, shown in the “server messages” window).</p>

<p>I tried connection Irssi directly to the target IRC network (bypassing ZNC), which seemed to solve the problem – but also got in the way of what I tried to achieve.</p>

<p>With some <code>tcpdump</code> and Wireshark work, I found that ZNC adds <code>@time=</code> to the messages. As confirmed by one of the helpful souls on IRC, this is only added if the connecting client asks for it. Luckily the solution is easy: Tell Irssi to skip sending the <code>CAPREQ</code> to ZNC.</p>

<h2 id="the-configuration">The configuration</h2>

<p>First, the server config:</p>

<pre><code class="language-c">servers = (
  {
    address = &#34;znc.example.com&#34;;
    chatnet = &#34;os2Floppy&#34;;
    port = &#34;195&#34;;
    password = &#34;&lt;user&gt;@&lt;client-id&gt;/&lt;network&gt;:&lt;password&gt;&#34;;
    use_tls = &#34;yes&#34;;
    tls_verify = &#34;yes&#34;;
    no_cap = &#34;yes&#34;;
  },
  {
    address = &#34;znc.example.com&#34;;
    chatnet = &#34;os2EFNet&#34;;
    port = &#34;195&#34;;
    password = &#34;&lt;user&gt;@&lt;client-id&gt;/&lt;network&gt;:&lt;password&gt;&#34;;
    use_tls = &#34;yes&#34;;
    tls_verify = &#34;yes&#34;;
    no_cap = &#34;yes&#34;;
  },
  {
    address = &#34;znc.example.com&#34;;
    chatnet = &#34;os2Libera&#34;;
    port = &#34;195&#34;;
    password = &#34;&lt;user&gt;@&lt;client-id&gt;/&lt;network&gt;:&lt;password&gt;&#34;;
    use_tls = &#34;yes&#34;;
    tls_verify = &#34;yes&#34;;
    no_cap = &#34;yes&#34;;
  }
);

# No channels configured here, as ZNC takes care of that
channels = ( );
</code></pre>

<p>And then the core config; note the <code>proxy</code> section:</p>

<pre><code class="language-c">settings = {
  core = {
    real_name = &#34;Eirik Overby&#34;;
    user_name = &#34;ltning&#34;;
    nick = &#34;o-Ltning&#34;;
    recode_transliterate = &#34;no&#34;;
  };
  proxy = {
    irssiproxy_bind = &#34;192.88.99.80&#34;; # The local IP
    irssiproxy_ports = &#34;os2Floppy=2777 os2EFNet=2778 os2Libera=2779&#34;; # Per-chatnet listening ports
  };
};

# The chat networks, as used by the server config:
chatnets = {
  os2Floppy = { type = &#34;IRC&#34;; };
  os2EFNet = { type = &#34;IRC&#34;; };
  os2Libera = { type = &#34;IRC&#34;; };
};
</code></pre>

<h2 id="the-result">The result</h2>

<p>And with that, I have a working config. The obligatory screenshot below.</p>

<p>Good luck (if you should end up trying this yourself), and thanks for reading!</p>

<p><img src="https://anduin.net/~ltning/ezirc.jpg" alt="ezIRC running on OS/2 2.11"></p>

<h2 id="footnotes">Footnotes</h2>
<ul><li><a id="fn1"><a href="#n1" rel="nofollow">1</a></a>: I spent many hours pestering IBM Norway into sending me a copy of the beta; I&#39;m sure I ended up on some list somewhere.</li>
<li><a id="fn2"><a href="#n2" rel="nofollow">2</a></a>: The current builds include
<ul><li>A 486DX-50 running Warp 3 and Novell Netware 4.12 paravirtualized</li>
<li>A 486DRx2-50 (really a 386 with a bit of cache) running Warp 3 and my BBS</li>
<li>The subject of this article, a 486DLC-40 running 2.11</li>
<li>A dual Pentium 233 MMX running Warp 4.52</li>
<li>A 286 running OS/2 1.3 EE(!)</li>
<li>A dual Pentium Pro which, when not running NetBSD or DOS runs Warp Server for e-Business</li>
<li>An IBM 486slc2 – Leopard or Leopard LX-based, depending on my mood – running Warp 3</li>
<li>An IBM PS/2 model P70 luggable running 2.11</li></ul></li>
<li><a id="fn3"><a href="#n3" rel="nofollow">3</a></a>: Turns out, it does as of version 1.2o. But given all the other problems, this is mostly of academic interest at this point..</li></ul>

<div style="display: flex; place-content: center;"><table style="width: 80%; border: none; font-size: 0.8em;">
<tr style="border: none;">
<td align="center" style="border: none;" colspan="2"><hr>
~ love over gold ~</td>
</tr>
<tr style="border: none; background-color: inherit;">
<td align="left" style="border: none; padding-left: 2em;"><a href="http://floppy.museum" rel="nofollow">The Floppy Museum</a></td>
<td align="right" style="border: none; padding-right: 2em;"><a href="http://floppy.museum/thispc.htm" rel="nofollow">About the Museum</a></td>
</tr></table></div>
]]></content:encoded>
      <guid>https://scrolls.anduin.net/ltning/os-2-connecting-ezirc-2-to-znc</guid>
      <pubDate>Sat, 17 Oct 2026 16:08:02 +0000</pubDate>
    </item>
  </channel>
</rss>