<div dir="ltr">"policy" What policy? Where is that "policy" published?</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 9, 2023 at 1:22 PM Leon Zetekoff <<a href="mailto:wa4zlw@backwoodswireless.net">wa4zlw@backwoodswireless.net</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">Right understand...I wasn't presented an option...let me get chris' <br>
email....guess you are not in the loop, i guess noone is.<br>
<br>
"Hi Leon,<br>
<br>
I can assign you a new range, we are retiring the old regional <br>
assignments as they expire, in favour of a more efficient assignment <br>
policy based on use case.<br>
<br>
Are these IPs for use on the IPIP Mesh? Or for standalone use?<br>
<br>
Thanks,<br>
Chris - G1FEF<br>
—<br>
<br>
ARDC Administrator"<br>
<br>
73 leon<br>
<br>
On 8/9/2023 12:14 PM, Charles J. Hargrove wrote:<br>
> OK. Let me put a VERY fine point on this situation with your new<br>
> 44Net allocation:<br>
><br>
> - I am not the coordinator for 44.63.x.x, but G1FEF is the coordinator<br>
> - I do not know his logic or planned use of that address space<br>
> - The eleven states and HamGates that I coordinate are different subnets<br>
><br>
> Unless things are openly discussed by ARDC staff, the various local 44Net<br>
> coordinators and affected user population of all subnets, then I can not<br>
> confidently solve problems in an address space that I am not controlling<br>
> and working with. I would not want to mess up another's area of <br>
> responsibility.<br>
><br>
> On 8/9/2023 12:04 PM, Leon Zetekoff wrote:<br>
>> ok I'm working but 44.94.17.129 has a problem at his end<br>
>><br>
>> D:\Old Drive C>tracert <a href="http://n2nov.ampr.org" rel="noreferrer" target="_blank">n2nov.ampr.org</a><br>
>><br>
>> Tracing route to <a href="http://n2nov.ampr.org" rel="noreferrer" target="_blank">n2nov.ampr.org</a> [44.68.41.1]<br>
>> over a maximum of 30 hops:<br>
>><br>
>> 1 3 ms 5 ms 2 ms <a href="http://t40.wa4zlw.org" rel="noreferrer" target="_blank">t40.wa4zlw.org</a> [10.195.10.3]<br>
>> 2 4 ms 3 ms 2 ms <a href="http://core100.wa4zlw.ampr.org" rel="noreferrer" target="_blank">core100.wa4zlw.ampr.org</a> [44.63.18.113]<br>
>> 3 45 ms 45 ms 44 ms <a href="http://gw.n2nov.ampr.org" rel="noreferrer" target="_blank">gw.n2nov.ampr.org</a> [44.68.41.2]<br>
>> 4 50 ms 46 ms 44 ms <a href="http://n2nov.ampr.org" rel="noreferrer" target="_blank">n2nov.ampr.org</a> [44.68.41.1]<br>
>><br>
>> Trace complete.<br>
>><br>
>> D:\Old Drive C><br>
>><br>
>> 73 leon<br>
>><br>
>> On 8/9/2023 11:20 AM, Leon Zetekoff wrote:<br>
>>><br>
>>> here's what I'm seeing in the MTK<br>
>>><br>
>>> 73 leon<br>
>>><br>
>>> On 8/9/2023 11:18 AM, Leon Zetekoff wrote:<br>
>>>> Hi Charles...I changed my Mikrotik over to the new allocation <br>
>>>> yesterday but something is not working. I asked chris about my <br>
>>>> original allocation and he said I can't have it back since they are <br>
>>>> doing this new stuff. He allocated the new block to me yesterday.<br>
>>>><br>
>>>> If you want to get on an email thread with him or whatever you want <br>
>>>> to do please let me know.<br>
>>>><br>
>>>> Just don't need this hassle of things not working.<br>
>>>><br>
>>>> 73 leon<br>
>>>><br>
>>>> On 8/9/2023 9:16 AM, Charles J. Hargrove wrote:<br>
>>>>> The VPN data for your Mikrotik will not work with your state Hamgate<br>
>>>>> unless your allocation matches the state (44.56.xxx.xxx). Since <br>
>>>>> your new<br>
>>>>> allocation of <a href="http://44.63.18.112/28" rel="noreferrer" target="_blank">44.63.18.112/28</a> was issued by someone else, you <br>
>>>>> would need<br>
>>>>> to put in a new request to switch back to your old allocation.<br>
>>>>><br>
>>>>> On 8/9/2023 9:08 AM, Leon Zetekoff wrote:<br>
>>>>>> hi charles....well I am on the new allocation but the mikrotik <br>
>>>>>> script is not working right so I reached out to marius.<br>
>>>>>><br>
>>>>>> All this happened yesterday. IMHO big deal if you don't hit the <br>
>>>>>> portal in a year. do ISPs shut you down only if you dont pay your <br>
>>>>>> bill :-)<br>
>>>>>><br>
>>>>>> 73 leon<br>
>>>>>><br>
>>>>>> On 8/9/2023 8:41 AM, Charles J. Hargrove wrote:<br>
>>>>>>> That cancellation was done at the ARDC level in one of their <br>
>>>>>>> purges.<br>
>>>>>>> I can reissue your old subnet and get you going from there. Just <br>
>>>>>>> let me<br>
>>>>>>> know as you are putting in your request so that I can approve it <br>
>>>>>>> immediately.<br>
>>>>>>><br>
>>>>>>> On 8/9/2023 8:31 AM, Leon Zetekoff wrote:<br>
>>>>>>>> Hi Charles! I just went through this because I missed the <br>
>>>>>>>> messages that I needed to get into the portal once a year and <br>
>>>>>>>> then finally I was turned off.<br>
>>>>>>>><br>
>>>>>>>> So I lost my original <a href="http://44.56.53.1/28" rel="noreferrer" target="_blank">44.56.53.1/28</a> and now have <a href="http://44.63.18.112/28" rel="noreferrer" target="_blank">44.63.18.112/28</a><br>
>>>>>>>><br>
>>>>>>>> Trying to get things back up and running is a PITA.<br>
>>>>>>>><br>
>>>>>>>> 73 leon wa4zlw<br>
>>>>>>>><br>
>>>>>>>> On 8/8/2023 11:03 AM, Charles J. Hargrove wrote:<br>
>>>>>>>>> There seems to be a push by the technical committee of ARDC to <br>
>>>>>>>>> form the<br>
>>>>>>>>> 44Net address space along perceived use rather by <br>
>>>>>>>>> area/region/state use.<br>
>>>>>>>>> The plans are to be "finalized" by the end of the year, <br>
>>>>>>>>> although some new<br>
>>>>>>>>> procedures are already being carried out which has caused <br>
>>>>>>>>> problems for new<br>
>>>>>>>>> users in our network and area.<br>
>>>>>>>>><br>
>>>>>>>>> For the foreseeable future, pass the word with any forwarding <br>
>>>>>>>>> partners,<br>
>>>>>>>>> new users and local clubs to NOT file for an allocation on the <br>
>>>>>>>>> 44Net portal,<br>
>>>>>>>>> but instead contact me directly at <a href="mailto:n2nov@n2nov.net" target="_blank">n2nov@n2nov.net</a> for a <br>
>>>>>>>>> conversation<br>
>>>>>>>>> and I can walk them through it in real time so that it can not <br>
>>>>>>>>> be short<br>
>>>>>>>>> circuited in the process. The state hamgates for Maryland and <br>
>>>>>>>>> Delaware<br>
>>>>>>>>> just went live this weekend, complete with a central bbs for <br>
>>>>>>>>> message<br>
>>>>>>>>> forwarding and Wireguard VPN servers for anyone to make use <br>
>>>>>>>>> of. The past<br>
>>>>>>>>> 18 months have been rolling along for increasing connectivity <br>
>>>>>>>>> and usefulness.<br>
>>>>>>>>> Let's see what we can do to keep it that way and to improve <br>
>>>>>>>>> functionality.<br>
><br>
<br>
</blockquote></div>