<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span style="font-size:large">It was quite frustrating since we did not have the background in networking software</span></blockquote><div><br></div><div>You clearly still do not, if you sincerely believe that commenting out a single function in every vendor software implementation is all that it would take. </div><div><br></div><div>No need to respond ; I will be filtering all future messages from you to /dev/null . Good luck with your efforts.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Mar 26, 2022 at 12:42 PM Abraham Y. Chen <<a href="mailto:aychen@avinta.com">aychen@avinta.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div><font size="4">Hi, Paul:</font></div>
<div><font size="4"><br>
</font></div>
<div><font size="4">1) " ... may be in
fact: /writing/* and */deploying/* the code ... ": Having no
idea why and how the 240/4 netblock became so mysteriously kept
away from being used while the IPv4 was officially already on
its way to "Sun Set", we started the conventional approach as
you stated. It was quite frustrating since we did not have the
background in networking software. One day, we came across a
short program code fragment that did the function of <i><b>disabling</b></i>
240/4 addressed IP packets. It is the "there exists an example"
moment for us, like proofing a mathematics theorem. After all,
there was no magic separating 240/4 from the rest of the IPv4
address pool to start with. </font><font size="4"><font size="4">It cleared our mind about this particular task.</font>
Now, we only cite this reference to challenge those software
engineers who may state that using the 240/4 in their code is a
lot more involved. .... Q.E.D. 😉</font></div>
<div><font size="4"><br>
</font></div>
<div><font size="4">Regards,</font></div>
<div><font size="4"><br>
</font></div>
<div><font size="4"><br>
</font></div>
<div><font size="4">Abe (2022-03-26 12:37
EDT)</font><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>On 2022-03-26 09:52, Paul Rolland
wrote:<br>
</div>
<blockquote type="cite">
<pre>Hello,
On Sat, 26 Mar 2022 09:35:30 -0400
"Abraham Y. Chen" <a href="mailto:aychen@avinta.com" target="_blank"><aychen@avinta.com></a> wrote:
</pre>
<blockquote type="cite">
<pre>touching the hardware, by implementing the EzIP technique (*/disabling/*
the program code that has been */disabling/* the use of the 240/4
netblock), an existing CG-NAT module becomes a RAN! As to universal
</pre>
</blockquote>
<pre>Have you ever considered that this may be in fact:
*/writing/* and */deploying/* the code that will allow the use of 240/4 the
way you expect
Paul
</pre>
</blockquote>
<p><br>
</p>
<div id="gmail-m_-7532339818749475379DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br>
<table style="border-top:1px solid rgb(211,212,222)">
<tbody><tr>
<td style="width:55px;padding-top:13px"><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon" target="_blank"><img src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif" alt="" width="46" height="29" style="width: 46px; height: 29px;"></a></td>
<td style="width:470px;padding-top:12px;color:rgb(65,66,78);font-size:13px;font-family:Arial,Helvetica,sans-serif;line-height:18px">Virus-free. <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link" style="color:rgb(68,83,234)" target="_blank">www.avast.com</a>
</td>
</tr>
</tbody></table><a href="#m_-7532339818749475379_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"> </a></div></div>
</blockquote></div>