44net

44net@mailman.ampr.org

2 participants
3170 discussions

Start a nNew thread

Test

by lleachii＠aol.com

Testing again. Still not receiving emails for months.73,Lynwood KB3VWG

2 years, 3 months

ATTN Chris G1FEF

by Tony Langdon

Hi Chris, contacting you via the list. Can you please do something about your system's hard reliance on SORBS data to block mail. I am unable to contact you privately, because this is blocking Gmail's servers. -- 73 de Tony VK3JED/VK3IRL http://vkradio.com

2 years, 3 months

answering questions about BGP assignment locations, address space plans

by Rosy Schechter - KJ7RYV

Dear 44Net mailing list members, Weaving through many of the messages from the past few weeks, I’m aware that folks have some questions around why G1FEF has been organizing BGP requests in 44.31/16. Behind these questions, in some cases, is a sense of uncertainty around whether or not ARDC is going to sell any more address space. Some members of the TAC have requested that I speak to you all about these issues, and to create space where you can ask questions. So here we go G1FEF has been putting BGP allocations into 44.31/16 for a few reasons: * Currently there are BGP “holes” randomly scattered throughout our address space. This makes it harder to manage, especially when trying to spot unauthorized announcements, which we get a lot of. * We inherited the “give a /16 to every region or country” practice from the 1990’s which has resulted in extremely sparse use of the space. We'd be better “netizens” if we used the space more effectively. * The HAMNET issue (needing a static set of addresses for BGP routing) is also a consideration, as they are the largest consumers of our address space by far. All told, Chris is doing his best to engage in best practices absent a more robust policy around BGP. Creating that policy is definitely on the list, and ideally fits into a greater vision around next steps for the address space (PoPs? Better organizing assignments for one reason or another? etc.). Data from our recent assessment is helping us to put together that vision. Thank you to all of you who shared your thoughts. In terms of whether ARDC is planning to sell more addresses: while it may happen at some point in the future, there are no current plans, short or medium term, to do so. The non-inconsequential effort involved in overcoming the tax and operational implications of such a move would only make sense after taking into account the views of the 44Net community on a vision for overall address space usage and associated future plans. In the meantime, many thanks for your patience amid the uncertainty. Feel free to ask any questions you may have. Sincerely,  Rosy -- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org

2 years, 4 months

Problem with axip links

by Dalibor Berka

Hello Since 1 week I started to have problems with ampr-ripd settiing. The reception of response packets from 169.228.34.84 on port 520 udp are not coming. Before abt 1 week the reception went normally. The problem occures at all IPs of 44.63.16.116/28 subnet. Below examples: For OK0NMG-5: [root@ok0nmg ~]# ifconfig tunl0 tunl0: flags=4289<UP,RUNNING,NOARP,MULTICAST> mtu 1480 inet 44.63.16.110 netmask 255.255.255.255 tunnel txqueuelen 0 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 20599 bytes 5164325 (4.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 For OK2PEN-5 tunl0: flags=4289<UP,RUNNING,NOARP,MULTICAST> mtu 1480 inet 44.63.16.112 netmask 255.255.255.255 tunnel txqueuelen 0 (IPIP Tunnel) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 892 bytes 223304 (218.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 For OK2KOJ-5 tunl0 Link encap:IPIP Tunnel HWaddr inet addr:44.63.16.111 Mask:255.255.255.255 UP RUNNING NOARP MULTICAST MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:106074 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:27842124 (26.5 MiB) All setting in amprnet portal are correct and reset. 73 Dalibor OK2PEN (PY2ZEN)

2 years, 4 months

Linux distribution for PI and for HAMnet

by Frederic Zulian

Hello, Which distribution do you recommend for a PI and only use for hamnet ? I'm trying with a Debian and lxqt. What do you think about this choice ? 73 F1sxo Frédéric ZULIAN

2 years, 5 months

IP address allocation

by bpurgar＠gmail.com

Hello I'm wondering who else I should contact (I contacted the local coordinator for 44.170.0.0/16 but he doesn't seem to want to resolve my request) to get an IP address or range. Berry - 9a3bex

2 years, 5 months

Fwd: ARDC is moving to a new grant application system (Hypha)

by John D. Hays

Hello ARDC Grant Applicant or Awardee, As we all know, the only constant in life is change. Here at ARDC, we are making a big one: switching to a new grant application software called Hypha. It’s open source and has a ton of great features that will make the application process easier for applicants, reviewers, and staff. You can see the new system here: https://grants.ardc.net And read more about it here: <https://www.ampr.org/new-grants-management-system-to-make-applying-for-and-…> https://www.ampr.org/new-grants-management-system-to-make-applying-for-and-… Here’s what this change means for you: - *All applications submitted July 15, 2022, and earlier will remain on the old system:* https://mailman.ampr.org/hotcrp. We won’t be getting rid of this database anytime soon, so don’t worry about your information getting lost. - *All applications submitted July 16, 2022, and after will need to be entered in the new system:* https://grants.ardc.net. This includes in-progress applications. The questions are exactly the same, so it should be easy enough to copy over. If you plan on submitting any new applications, you’ll need to create a new account on https://grants.ardc.net by clicking the Apply button. If you have any questions about the new system, or are having trouble applying for a grant, contact us by emailing help(a)ardc.net. Thanks for everything that you do. Sincerely, The ARDC Grants Team

2 years, 5 months

Time to say "Goodbye" ?

by Toussaint OTTAVI

Hi all, Here's what I received that morning from Vultr (my BGP provider), just after a bunch of monitoring alarms : > The prefix owner has requested we remove the following prefix from your account: > > 44.190.11.0/24 > > If you have any questions regarding this request, please reach out to the prefix owner for more information, thanks! Then, our whole island of Corsica is completely disconnected from the rest of the world ! Without any advice. That becomes really annoying. No more comments for today, because I do not have the right words in English to tell my exact feeling. Maybe it's just time to say goodbye. 73 de TK1BI

2 years, 5 months

DNS changes

by kayne.kruse＠gmail.com

Hi, I live in Texas and have no 'coordinator', Ccould someone reach out my email about ampr.org dns edits for my block? Regards, Kayne - N9SEO

2 years, 5 months

FIOS Router CR1000A

by Mark Herson, N2MH

Hello to the Group, I have just upgraded my FIOS service in New Jersey and with it came a new router - something called a CR1000A. It has a Verizon brand on it but I suspect it is made under contract by someone else. Has anyone on the group used this router and have been successful in getting it to forward Protocol 4 packets? It does have a DMZ, but I'd rather not use it if possible. I think I have been able to define Protocol 4 into it but I am unable to have it forward those packets to my ipip tunnel machine. 73, Mark, N2MH n2mh.ampr.org http://n2mh-web.n2mh.ampr.org

2 years, 5 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net