July 2024 - NANOG - lists.nanog.org

[Event] Our Networks: Does not (cloud) compute, July 27, Vancouver, BC
by Dawn Walker 04 Jul '24

04 Jul '24

Hello all, sharing an event coming up at the end of the month in Vancouver, BC just after the IETF120 meeting-- It's a mix of community networks, local-first software, solar servers, right to repair, and more! --- *Our Networks 2024: Does not (cloud) compute* July 27, 2024 312 Main, Vancouver, BC Register: https://ournetworks.ca/#register or on luma: https://lu.ma/r3afi0b0 .:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~* What does collaboration and presence look like when a network is optional? What connections are possible when we leave our data at the door and spend a day on local networks? What new metaphors will help us create spaces for meaningful and different relations partially online? Last year provided an opening up a decade after platforms foreclosed on a sense of possibility of an earlier web. Turmoil on social media was the backdrop for creative experimentation with protocols and in networked spaces. Yet despite these new avenues, the myriad problems of being online haven’t been adequately addressed. The internet is dead, long live the internet. Before the previous web took shape and before an “always-on” and powered present, there were multiple ways to connect across boundaries and scales. Data moved by foot or mail across sneakernets, computing was time-shared so multiple users could access scarce resources, and ad hoc networks emerged from transitory LAN parties. Drawing on practices of local-first , solar-powered servers , folk software , and permacomputing , Our Networks 2024 explores transitional technologies and forms of computing that break from always-on connectivity. Over the course of the event, we will investigate histories, tools, and approaches like these that allow us to reframe what computing could mean when the internet, and the cloud, are optional. .:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~*:._.:*~* *Presenters and Program* Over the course of a day we will cover the past, present, and future with short keynote talks, workshops, and activities on the local network. Presenters include: - Lori Emerson will speak about other networks (https://othernetworks.net/) that exist outside of what is now called "the internet" - Joni Schinkel at Small File Media Festival (https://smallfile.ca) will workshop approaches to small footprint web art - Indie Researcher Brooklyn Zelenka will talk to us about the present state of local-first computing - Michelle Kaczmarek from the Share Reuse Repair Initiative (https://www.sharereuserepair.org/) will lead a conversation into computing repair culture - Esther Jang from Seattle Community Network (https://seattlecommunitynetwork.org/) will talk about the possibilities of community-run cellular internet access networks View the program: https://ournetworks.ca/program/ `\\//`,.\|/|//.|/\\|/\\|,\|/ //\|/\|.\\\| // \|\\ |/,\|/\|\\ *Register* Registration is now open for Our Networks 2024: https://ournetworks.ca/#register (suggested $60, sliding scale from $30-120) The event will take place at 312 Main in Vancouver's Downtown Eastside. Venue info: https://312main.ca/#contact-us Map: https://osm.org/go/WJQrPYERu?m=&way=295876023 --..,___.--,--'`,---..-.--+--.,,-,,..._.--..-._.-a:f--..-.-- /<3 orga(a)ournetworks.ca/

1 0

Re: HE.net problem
by Reid Fishler 04 Jul '24

04 Jul '24

After a metric ton of screaming, we did get the issue solved. Thanks everyone, and we WILL be following up with the powers that be. Reid On Thu, Jul 4, 2024, 3:31 PM Reid Fishler <rfishler(a)he.net> wrote: > Network Solutions has decided to put our domain name on Client Hold due to > a single phishing complaint about a web page, which happens to just be a > page of information about another domain from bgp.he.net. Network > Solutions has been contacted, and refuses to handle this issue in ANY > expedited manner. Executives from Hurricane have been calling and emailing > Network Solutions for HOURS trying to have this addressed. If anyone has > an escalation contact at Network Solutions, please email it to me at > redhead(a)lightning.net, or rfishler(a)he.net. Thanks. > > Reid Fishler > Sr Director > Hurricane Electric > > > On Thu, Jul 4, 2024 at 3:23 PM Jay Ashworth <jra(a)baylink.com> wrote: > >> I've been informed that the CEO of HE is on this as of 1512EDT. >> >> I approve of the scale of this response. :-) >> >> Cheers, >> -- jra >> >> >> On July 4, 2024 2:55:34 PM EDT, Jay Ashworth <jra(a)baylink.com> wrote: >> >>> We have a report on outages that he.net has been placed in ICANN client >>> hold, and people's DNS service is falling over on this Independence day. If >>> you work in DNS for HE, you might want to look into this. >>> >>> I have double checked the report, and I am seeing the status as well. >>> >>> Hurricane serves lots of dns, I would classify this as a P1 ticket. >>> >>> Cheers, >>> -- jra >>> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> > > > -- > Reid Fishler > Senior Director > Hurricane Electric > +1-510-580-4178 >

1 0

LACNOG 2024 – Call for Presentations (Last 2 weeks)
by Hernan Moguilevsky 03 Jul '24

03 Jul '24

Hi NANOG, A friedly reminder of the CFP for LACNOG 2024. Thanks. Regards. LACNOG 2024 – Call for Presentations LACNOG, the Latin American and Caribbean Network Operators Group, will hold its LACNOG 2024 conference from 7 to 11 October 2024 together with the LACNIC 42 event. The event is scheduled to take place in hybrid format in the city of Asunción, Paraguay. The LACNOG 2024 Program Committee invites the Internet community to submit their presentation proposals for the event. In line with the spirit of LACNOG, topics should be geared towards Internet development in the region. The following is a non-exhaustive list of some of the topics of interest for the LACNOG 2024 meeting: ●Network operation and professional experiences, success stories ●Internet of Things ●MANRS ●Community networks ●IPv6 integration and deployment ●Experiences involving botnets, malware, spam, viruses, denial of service attacks and exploit techniques ●IP network architecture, sizing, configuration, and administration ●Routing and switching protocols, including unicast, multicast, anycast, SDN, etc. ●End-user applications (e.g. e-mail, HTTP, DNS, NFVs, etc.) ●Value-added services such as VPNs, distributed systems, cloud computing, etc. ●Peering, traffic exchange, IXPs ●Network data security and management, attack mitigation ●Network monitoring, performance, measurements, and telemetry ●Network automation, evolution, and convergence ●Infrastructure and physical transport, including optical and wireless networks ●Legislation, regulations, and Internet governance issues ●Research and education ●Technical aspects related to universal acceptance Presentation formats include: ●Lightning talks: Brief, 10-minute presentations (including an additional 5-minute space for questions). ●Presentations: 20-minute presentations (including an additional 5-minute space for questions). Proposals for the event will be selected following the calendar below: ●Reception of proposals: 12 May to 16 July 2024 ●Proposals will be accepted until: 16 July 2024 at 23:59 UTC-3 (Uruguay time) ●Evaluation by the Program Committee: 24 July to 7 August 2024 ●Announcement of results: 10 August 2024 ●Confirmation by selected presenters: 15 August 2024 ●Publication of the preliminary program: between 15 and 21 August 2024 ●Publication of presenters’ bios and photos on the event website: 21 August 2024 ●Submission of final presentations: 10 August to 11 September 2024 ●Final presentations will be accepted until: 11 September 2024 at 23:9 UTC-3 (Uruguay time) ●Event date: 2 to 6 October 2024 Applicants must submit a summary and a draft of the slides for their proposed presentation, along with a brief biography. These must be submitted using the form available at https://eventos.nog.lat/event/27/ If your work is selected, you authorize LACNOG and LACNIC to publish your name, photograph, biography, and final work in the event program. Speakers presenting their work at the LACNOG 2024 conference will receive a certificate acknowledging their participation. Guidelines for Submitting a Presentation for LACNOG including a description of the criteria that will be considered when evaluating each proposal, presentation format and other details are available at https://lacnog.org/seccion/postulacion-trabajos <https://lacnog.org/seccion/postulacion-trabajos> Communications with the Program Committee will be handled through pc(a)lacnog.org <mailto:pc@lacnog.org>. Thanking you in advance, we look forward to receiving your proposals for LACNOG 2024. The Program Committee

1 0

charging for config changess
by Randy Bush 03 Jul '24

03 Jul '24

has charging for config changes a la https://www.arelion.com/customer-excellence/customer-support/online-technic… become common while i was not looking? admittedly, i have not looked for a long time. randy

9 8

Any representitives from ip2location lurking
by Jim Bonnet 02 Jul '24

02 Jul '24

Hello folks, Are there any folks from ip2location lurking on the list? Could you ping me directly. We have a geofeed issue I'd like to ask about. Thank you. Jim Bonnet Broadcom CloudOPS -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.

2 1

Geolocation IP - www.firstinterstatebank.com
by Jarek Kasjaniuk 01 Jul '24

01 Jul '24

Hello, does anyone have contact to someone from www.firstinterstatebank.com ? Some IP addessess from ASN 31998 can't access their website. We see information like: "we have limited website access for IP addresses outside of the United States and Canada to online banking platforms only." I have sent e-mails to contacts found in ARIN, but no response. Thanks -- Jarek Kasjaniuk

3 3

Re: Looking for DISA/DOD contact
by Mike Tindor 01 Jul '24

01 Jul '24

I guess I could try that. My fear is that it would simply end up being read by the same people you get when you call the DISA helpdesk, and that they would see who it was from, tie it to a closed ticket where they already told me they couldn't help me because I wasn't military or a government contractor. On the other hand, that would at least give me a chance to send all of the truly relevant information that I was not allowed to have added to the ticket when they originally opened it -- all of the network related information, traceroutes, etc. I've been given quite a few suggestions, including this one from you. I'll need to start going through them one by one tomorrow. Thanks Mike On Sun, Jun 30, 2024 at 8:56 PM Brad Knowles <brad(a)his.com> wrote: > Years ago, I was the DISA.MIL Technical POC. And I was a government > civilian, not in the military. I was also the postmaster for DISA.mil. > > I don’t know how they do things these days, but back when I worked there, > a real human being monitored the postmaster(a)disa.mil mailbox, and if they > weren’t the correct party to handle the situation, then they would find out > who the correct party was and forward the e-mail to them. > > Sent from my iPhone > > On Jun 30, 2024, at 7:49 PM, Mike Tindor <mtindor(a)gmail.com> wrote: > > > Thank you. That is helpful. > > Mike > > On Sun, Jun 30, 2024 at 12:31 AM <nanog.org(a)junk-mail.us> wrote: > >> The people at DISA you were dealing w/ aren't a Tier I service desk, >> they're the service desk that lower service desks open tickets w/. >> >> Think of DISA as a Tier I ISP and the normal .mil user as a residential >> user. >> >> See if one of your customers can put you in contact w/ their IT people >> (Usually a S6/G6/N6/A6/J6). 6 means IT or communications, the letter >> prefix is determined by the Military branch and level of the unit (A is Air >> Force, N is Navy, J is Joint, G is Army General Staff, and S is Army Staff). >> >> On Sat, Jun 29, 2024 at 6:25 PM Mike Tindor - mtindor at gmail.com < >> mtindor_at_gmail_com_rgphbc(a)simplelogin.co> wrote: >> >>> Thanks. That makes a little more sense to me. I know the questions >>> DISA asked me when I called them, and I couldn't imagine just having the >>> MIL-side email correspondent open a ticket directly with DISA. They would >>> likely be more overwhelmed than I was. I'll talk to a couple of my >>> customers who do biz with DOD on Monday and will ask them to reach out to >>> their MIL contacts and request that the MIL contacts open a ticket with >>> their IT. >>> >>> Since this has been going on now, some of my customers have switched >>> temporarily to using Gmail/Yahoo just to stay in touch with their MIL >>> contacts. So I know they can get the message through. >>> >>> Mike >>> >>> On Sat, Jun 29, 2024 at 12:55 PM Mike Tindor <mtindor(a)gmail.com> wrote: >>> >>>> Thanks again,Scott. I'll be patient! >>>> >>>> Mike Tindor >>>> >>>> >>>> On Sat, Jun 29, 2024 at 12:18 PM Scott Q. <qmail(a)top-consulting.net> >>>> wrote: >>>> >>>>> All that sounds very familiar, I'm 100% sure it's the same issue. >>>>> >>>>> As I said, there are DISA folks here, they might reach out and give >>>>> you further steps. They did in my case, you just have to be more patient / >>>>> on the ball than I was... >>>>> >>>>> Good luck! >>>>> >>>>> >>>>> On Saturday, 29/06/2024 at 11:44 Mike Tindor wrote: >>>>> >>>>> Scott, >>>>> >>>>> Thanks for responding. Unfortunately, I think my situation is a >>>>> little more dire, or at least involved. I probably should have said this >>>>> before, but I had done TCP 25 outbound testing from our /23 to various .MIL >>>>> MX's that I know were responding and could not establish a connection / get >>>>> an SMTP banner. I could then go to Azure, or Digital Ocean, or somewhere >>>>> else that I have a box and am able to make the outbound connection to the >>>>> same MIL MXs that wouldn't respond to me from our /23. >>>>> >>>>> So it isn't a simple case of DNS not resolving, although we certainly >>>>> did notice that issue. Fortunately, we do have nameservers in place that >>>>> are external to our /23 and which are able to actually do the resolving. >>>>> But your comment does remind that this definitely is not just a TCP 25 >>>>> issue, as the MIL DNS servers are not responding to queries from our /23 >>>>> hosts. >>>>> >>>>> The situation is difficult for multiple reasons: >>>>> >>>>> 1. inabiity to engage somebody from the other end - DISA >>>>> 2. Unwillingness on my part to stab at a hornets nest and poke around >>>>> trying to verify connections (other than TCP 25 to known MIL MXs) in >>>>> DOD-land. >>>>> 3. Not knowing exactly where to go from here >>>>> >>>>> The latest/last thing DISA told me was that I would have to get one of >>>>> the people with MIL email addresses who can't email our customers to >>>>> actually open a ticket with DISA. And that is fraught with problems since >>>>> even if a MIL email user did open a ticket, they would not have any >>>>> information about our network to convey to the Helpdesk -- and would have >>>>> no way of answering questions that the Helpdesk asked, and also wouldn't be >>>>> able to do any troubleshooting. >>>>> >>>>> I did realize a few days ago we had no ROA for the specific /23, and >>>>> so I created one at ARIN. And we had no specific route object published >>>>> for our /23, and I got one added. Been trying to clean up some old (and >>>>> invalid) stuff that is in RADB from our larger /19, since we don't even own >>>>> all the space in the /19 anymore and are only actively using a /23 from >>>>> what we have left. Hoping to get that taken care of Monday. >>>>> >>>>> Everything has worked fine for 26 years, until Jun 1. But things >>>>> change, and I'm obviously behind the times given that I didn't have proper >>>>> ROA and route object in place. >>>>> >>>>> Mike Tindor >>>>> >>>>> On Sat, Jun 29, 2024 at 11:26 AM Scott Q. <qmail(a)top-consulting.net> >>>>> wrote: >>>>> >>>>>> There are DISA folks lurking here. >>>>>> >>>>>> I had a similar issue where our block was labeled as residential by >>>>>> their new firewall, and DISA front-desk isn't yet trained on this mechanism >>>>>> so they can't help. >>>>>> >>>>>> I escalated the issue to a lot of groups but in the end I gave up, >>>>>> too much bureaucracy. The issue is simply DNS - their DNS servers don't let >>>>>> you resolve. So I simply set 8.8.8.8 as the resolver for *.mil and it temp >>>>>> (permanently) fixed the problem. >>>>>> >>>>>> Scott >>>>>> >>>>>> >>>>>> On Saturday, 29/06/2024 at 09:16 Mike Tindor wrote: >>>>>> >>>>>> Hi folks, >>>>>> >>>>>> I'm looking for a DISA/DOD contact who feels that my issue has >>>>>> merit. I've tried the DISA Helpdesk and have been told since I'm a >>>>>> commercial entity with no affiliation with the DOD, they can't help me. >>>>>> >>>>>> The issue at hand is that our /23 netblock has lost communication (at >>>>>> least email TCP 25) with AS345 / AS721 as of May 31, 2024 and I cannot >>>>>> figure out why. We are in a Flexential datacenter in Richmond VA and use >>>>>> Flexential for transport. We cannot send emails to .MIL or receive emails >>>>>> from .MIL. It is not that they are being rejected on either end. The >>>>>> deliveries are timing out and being returned to sender, from both sides. >>>>>> >>>>>> I don't know if DISA/DOD has a block on our ASN and-or /23, or if >>>>>> there is a routing issue somewhere between us and AS345 / AS721. I had >>>>>> asked the Flexential folks to look into it from their side, and they >>>>>> indicated that historic data does indeed show that there TCP 25 >>>>>> communications to and fro between us and AS345 prior to June 1, but nothing >>>>>> from June 1 onward. And all they could say was that they (Flex) were not >>>>>> in any way blocking. And I'd agree with that. >>>>>> >>>>>> As you can imagine, my customers are not happy with not being able to >>>>>> communicate with their family / friends via email in the MIL domains, and >>>>>> our customers who are vendors / contractors cannot do business with the >>>>>> military effectively if they cannot send/receive emails. >>>>>> >>>>>> us --> Flexential --> GTT --> Level3 --> Qwest --> ? --> AS345 / >>>>>> AS721 >>>>>> >>>>>> Any idea where one would go next? Is it likely that any of those >>>>>> entities further upstream like GTT / Level3 / Qwest would even assist since >>>>>> we are not their customer? >>>>>> >>>>>> Thanks for your time! >>>>>> >>>>>> Mike Tindor >>>>>> >>>>>>

1 0

Looking for DISA/DOD contact
by Mike Tindor 01 Jul '24

01 Jul '24

Hi folks, I'm looking for a DISA/DOD contact who feels that my issue has merit. I've tried the DISA Helpdesk and have been told since I'm a commercial entity with no affiliation with the DOD, they can't help me. The issue at hand is that our /23 netblock has lost communication (at least email TCP 25) with AS345 / AS721 as of May 31, 2024 and I cannot figure out why. We are in a Flexential datacenter in Richmond VA and use Flexential for transport. We cannot send emails to .MIL or receive emails from .MIL. It is not that they are being rejected on either end. The deliveries are timing out and being returned to sender, from both sides. I don't know if DISA/DOD has a block on our ASN and-or /23, or if there is a routing issue somewhere between us and AS345 / AS721. I had asked the Flexential folks to look into it from their side, and they indicated that historic data does indeed show that there TCP 25 communications to and fro between us and AS345 prior to June 1, but nothing from June 1 onward. And all they could say was that they (Flex) were not in any way blocking. And I'd agree with that. As you can imagine, my customers are not happy with not being able to communicate with their family / friends via email in the MIL domains, and our customers who are vendors / contractors cannot do business with the military effectively if they cannot send/receive emails. us --> Flexential --> GTT --> Level3 --> Qwest --> ? --> AS345 / AS721 Any idea where one would go next? Is it likely that any of those entities further upstream like GTT / Level3 / Qwest would even assist since we are not their customer? Thanks for your time! Mike Tindor

3 8