<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Any specific reason that routed daemon is 32-bit in a 64-bit system? in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Any-specific-reason-that-routed-daemon-is-32-bit-in-a-64-bit/m-p/251007#M49103</link>
    <description>&lt;P&gt;Hello everyone.&lt;/P&gt;
&lt;P&gt;We have an open TAC ticket going on for investigation of a persistent memory leak of routed daemon due to OSPF. Even enabling debugging for routed daemon for 'Global' didn't provide much information. And so far, the port fixes provided by R&amp;amp;D didn't help, but they are investigating nevertheless.&lt;/P&gt;
&lt;P&gt;During our conversations with TAC I asked which kinds of analyses are being done. Maybe valgrind or strace or something. In their response they mentioned that routed daemon is a 32-bit process, which makes it difficult to analyze the behavior of rotued, especially in a production environment. So I understand that it can be dangerous and requires in-house replication.&lt;/P&gt;
&lt;P&gt;What I don't understand/know is why routed daemon is 32-bit even though the kernel is 64-bit. Probably this is an ignorant question but it bugs me as much as OSPF bugs routed. I'm sure there's a good reason to keep it 32-bit, so maybe someone can illuminate me on it.&lt;/P&gt;
&lt;P&gt;One potential idea that came to my mind is that routed daemon contains old, complex routing protocol implementations that may have been originally developed for 32-bit systems. But nothing is due to only one reason, so I'm sure there's more to it than I see.&lt;/P&gt;
&lt;P&gt;Thank you in advance.&lt;/P&gt;
&lt;P&gt;Cheers!&lt;/P&gt;</description>
    <pubDate>Wed, 11 Jun 2025 06:36:08 GMT</pubDate>
    <dc:creator>kamilazat</dc:creator>
    <dc:date>2025-06-11T06:36:08Z</dc:date>
    <item>
      <title>Any specific reason that routed daemon is 32-bit in a 64-bit system?</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Any-specific-reason-that-routed-daemon-is-32-bit-in-a-64-bit/m-p/251007#M49103</link>
      <description>&lt;P&gt;Hello everyone.&lt;/P&gt;
&lt;P&gt;We have an open TAC ticket going on for investigation of a persistent memory leak of routed daemon due to OSPF. Even enabling debugging for routed daemon for 'Global' didn't provide much information. And so far, the port fixes provided by R&amp;amp;D didn't help, but they are investigating nevertheless.&lt;/P&gt;
&lt;P&gt;During our conversations with TAC I asked which kinds of analyses are being done. Maybe valgrind or strace or something. In their response they mentioned that routed daemon is a 32-bit process, which makes it difficult to analyze the behavior of rotued, especially in a production environment. So I understand that it can be dangerous and requires in-house replication.&lt;/P&gt;
&lt;P&gt;What I don't understand/know is why routed daemon is 32-bit even though the kernel is 64-bit. Probably this is an ignorant question but it bugs me as much as OSPF bugs routed. I'm sure there's a good reason to keep it 32-bit, so maybe someone can illuminate me on it.&lt;/P&gt;
&lt;P&gt;One potential idea that came to my mind is that routed daemon contains old, complex routing protocol implementations that may have been originally developed for 32-bit systems. But nothing is due to only one reason, so I'm sure there's more to it than I see.&lt;/P&gt;
&lt;P&gt;Thank you in advance.&lt;/P&gt;
&lt;P&gt;Cheers!&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jun 2025 06:36:08 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Any-specific-reason-that-routed-daemon-is-32-bit-in-a-64-bit/m-p/251007#M49103</guid>
      <dc:creator>kamilazat</dc:creator>
      <dc:date>2025-06-11T06:36:08Z</dc:date>
    </item>
    <item>
      <title>Re: Any specific reason that routed daemon is 32-bit in a 64-bit system?</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Any-specific-reason-that-routed-daemon-is-32-bit-in-a-64-bit/m-p/251079#M49125</link>
      <description>&lt;P&gt;While the OS kernel has been 64-bit only since R80.10, there are several userspace processes that are still 32-bit.&lt;BR /&gt;This includes Check Point-specific code (i.e. not components you'd find in RHEL) and/or have specific integrations with Check Point-specific code (ClusterXL and routed, for instance).&lt;/P&gt;
&lt;P&gt;Over time, I presume we will upgrade everything to 64-bit.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jun 2025 19:26:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Any-specific-reason-that-routed-daemon-is-32-bit-in-a-64-bit/m-p/251079#M49125</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2025-06-11T19:26:22Z</dc:date>
    </item>
    <item>
      <title>Re: Any specific reason that routed daemon is 32-bit in a 64-bit system?</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Any-specific-reason-that-routed-daemon-is-32-bit-in-a-64-bit/m-p/251095#M49130</link>
      <description>&lt;P&gt;I actually verified the same in R82, but what&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/7"&gt;@PhoneBoy&lt;/a&gt;&amp;nbsp;said is the same answer I got recently from TAC.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Wed, 11 Jun 2025 22:43:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Any-specific-reason-that-routed-daemon-is-32-bit-in-a-64-bit/m-p/251095#M49130</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-06-11T22:43:43Z</dc:date>
    </item>
  </channel>
</rss>

