- Test - lists.nanog.org

ElastiFlow Getting Started?
by Mike Hammett 22 Mar '23

22 Mar '23

Does anyone know of a getting started guide for the latest release of ElastiFlow? I went the docker path because I recall setting up a system before that had a lot of work with dependencies and getting things tied together. I got it installed and it seems to run without error, but there's nothing telling me how to actually access the UI. Something is listening on port 8080, but it just gives me a 404. That seems to be pertinent to the API, which I don't care about at this time. That seems like low hanging fruit that the documentation misses. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

4 4

Re: CUPS in a BNG?
by Tom Mitchell 22 Mar '23

22 Mar '23

OK - That makes sense. For scaling a CP, it only about redundancy, correct, but with the DP it's really about scaling up and out. But still, a CP is no longer on the bus with the DP, nor on the network. It's on the WAN/Internet, and latencies are orders of magnitude greater. Is anybody doing this and are those latencies acceptable? On Wed, Mar 22, 2023 at 2:59 PM Joel Halpern <jmh(a)joelhalpern.com> wrote: > With a reasonable design, it separates the scale issues of the control > plane from the scale issues of the data plane. And since the relationship > between those two scale factors is different for different deployments, it > allows you as an operator to build for your needs. It also, with suitable > designs separates the failure modes. > > Whether either of those applies in your case probably depends upon your > needs and what vendors you find useful. > > Yours, > > Joel > On 3/22/2023 5:53 PM, Tom Mitchell wrote: > > What is it about the architecture that makes it a preferred solution. I > get that centralizing the user databases makes sense, but why the control > plane. What benefit does that have? > > -- Tom > > > On Wed, Mar 22, 2023 at 2:17 PM <brian.johnson(a)netgeek.us> wrote: > >> The CUPS makes a lot of sense for this application. Latency is dependent >> on the design, and equipment used. I’ve seen/done several designs for this >> using two different vendors equipment and two different BNG software >> stacks. >> >> When I do a design for BNG from scratch, this is how I do it now. :) >> >> As always… YMMV. >> >> - Brian >> >> On Mar 22, 2023, at 4:02 PM, Tom Mitchell <tmitchell(a)netelastic.com> >> wrote: >> >> Anyone have any thoughts on this CUPS thing? I have a customer asking, >> but it seems the lack of CP resiliency and additional latency between the >> DP and CP make this a really dumb idea. Has anyone tried it? Does it make >> any sense? >> >> Thanks! >> >> >>

1 0

CUPS in a BNG?
by Tom Mitchell 22 Mar '23

22 Mar '23

Anyone have any thoughts on this CUPS thing? I have a customer asking, but it seems the lack of CP resiliency and additional latency between the DP and CP make this a really dumb idea. Has anyone tried it? Does it make any sense? Thanks!

2 2

Spamhaus flags any IP announced by our ASN as a criminal network
by Brandon Zhi 22 Mar '23

22 Mar '23

Hello guy, We recently discovered that any IP address announced by our ASN is blacklisted by Spamhaus, even if we only announced it but not use it. I would like to ask if this is manually set by Spamhaus or is the system misjudgment? Has anyone encountered the same situation as us? Best, *Brandon Zhi* HUIZE LTD www.huize.asia <https://huize.asia/>| www.ixp.su | Twitter This e-mail and any attachments or any reproduction of this e-mail in whatever manner are confidential and for the use of the addressee(s) only. HUIZE LTD can’t take any liability and guarantee of the text of the email message and virus.

14 25

1.1.1.1 support?
by Saku Ytti 22 Mar '23

22 Mar '23

Am I correct to understand that 1.1.1.1 only does support via community forum? They had just enough interest in the service to collect user data to monetise, but 0 interest in trying to figure out how to detect and solve problems? Why not build a web form where they ask you to explain what is not working, in terms of automatically testable. Like no A record for X. Then after you submit this form, they test against all 1.1.1.1 and some 9.9.9.9 and 8.8.8.8 and if they find a difference in behaviour, the ticket is accepted and sent to someone who understands DNS? If there is no difference in behaviour, direct people to community forums. This trivial, cheap and fast to produce support channel would ensure virtually 0 trash support cases, so you wouldn't even have to hire people to support your data collection enterprise. Very obviously they selfishly had no interest in ensuring 1.1.1.1 actually works, as long as they are getting the data. I do not know how to characterise this as anything but unethical. https://community.cloudflare.com/t/1-1-1-1-wont-resolve-www-moi-gov-cy-in-l… https://community.cloudflare.com/t/1-1-1-1-failing-to-resolve/474228 If you can't due to resources or competence support DNS, do not offer one. -- ++ytti, cake having and cake eating user

6 9

Re: Verizon/Qwest single end-user difficulty vs Xfinity (was Re: NANOG Digest, Vol 182, Issue 14)
by Tom Daly 21 Mar '23

21 Mar '23

Jeff, Since you are using bridge mode, try adjusting down the MTU supported through the network. We have observed that a realistic MTU for Verizon 5G home internet is about 1428 bytes. Good luck, Tom On Sun, Mar 19, 2023 at 8:00 AM <nanog-request(a)nanog.org> wrote: > Send NANOG mailing list submissions to > nanog(a)nanog.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mailman.nanog.org/mailman/listinfo/nanog > or, via email, send a message with subject or body 'help' to > nanog-request(a)nanog.org > > You can reach the person managing the list at > nanog-owner(a)nanog.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of NANOG digest..." > > > Today's Topics: > > 1. Spamhaus flags any IP announced by our ASN as a criminal > network (Brandon Zhi) > 2. Verizon/Qwest single end-user difficulty vs Xfinity (Jeff Woolsey) > 3. Re: Spamhaus flags any IP announced by our ASN as a criminal > network (Tom Beecher) > 4. Re: Verizon/Qwest single end-user difficulty vs Xfinity > (Darin Steffl) > 5. Re: Verizon/Qwest single end-user difficulty vs Xfinity (Joe) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 18 Mar 2023 14:57:12 +0100 > From: Brandon Zhi <Brandon(a)huize.asia> > To: nanog(a)nanog.org > Subject: Spamhaus flags any IP announced by our ASN as a criminal > network > Message-ID: > < > CAAyZddEAu48oYngA6xgwrsijbVf9LiwLHVE5OnO3y+8faUSMLg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello guy, > > We recently discovered that any IP address announced by our ASN is > blacklisted by Spamhaus, even if we only announced it but not use it. > > I would like to ask if this is manually set by Spamhaus or is the system > misjudgment? Has anyone encountered the same situation as us? > > > Best, > > *Brandon Zhi* > HUIZE LTD > > www.huize.asia <https://huize.asia/>| www.ixp.su | Twitter > > > This e-mail and any attachments or any reproduction of this e-mail in > whatever manner are confidential and for the use of the addressee(s) only. > HUIZE LTD can?t take any liability and guarantee of the text of the email > message and virus. >

2 1

GGC need portal access restored
by Seth Mattinen 21 Mar '23

21 Mar '23

I also need someone at GGC to contact me ASAP; a tech showed up on site to replace hardware in a node and I've come to find out my portal access is no longer available and I can't place it into maintenance mode. ~Seth

1 0

Reminder to Submit Presentations for NANOG 88
by Cat Gurinsky 21 Mar '23

21 Mar '23

NANOG Community, The NANOG Program Committee (PC) would like to remind you that we are accepting proposals for in-person or live remote presentations at all sessions of NANOG 88, a hybrid meeting, taking place in Seattle, Washington on 12-14 Jun 2023. Below is a summary of key details and dates from the Call For Presentations on the NANOG website, which can be found at https://www.nanog.org/program/call-presentations/. Requested Topics: Based on feedback from our survey results, we have seen numerous requests for the following topics: - Network Automation - practical uses, how to get started - Network Future - forecast for changes in technology, design, applications - Research & Education - what research is happening now in network operations - Security - developments in, problems/solutions, various protocols of - Tutorials - all levels, IPv6, BGP, Segment Routing, DNS, MPLS, VXLAN We are looking to schedule over 1,600 minutes of content between General Session and Breakout Rooms for NANOG 88, and have confirmed 300 minutes already - so don’t wait! Presentation abstracts and draft slides should be submitted no later than Monday, 24 Apr 2023 to be considered for NANOG 88. Presentations may cover current technologies, soon-to-be deployed technologies, and industry innovation. Vendors are welcome to submit talks which cover relevant technologies and capabilities, but presentations should not be promotional, or discuss proprietary solutions. The primary speaker, moderator, or author should submit a presentation proposal and abstract via the Program Committee Tool at: https://www.nanog.org/meetings/submit-presentation/ <https://www.nanog.org/meetings/submit-presentation/> - Sign in with your Profile Account - Select the type of talk you propose to present, and complete the form Timeline for submission and proposal review: - Submitter enters abstract (and draft slides if possible) in the Program Committee Tool prior to the deadline for slide submission. - PC performs initial review and assigns a “shepherd” to help develop the submission — typically within 2 weeks. - Submitter develops draft slides of talk if not already submitted with the initial proposal. Please submit initial draft slides early — the PC does not evaluate submissions until draft slides are available for review. NANOG Staff is available to assist with slide templates upon request from the submitter. - Panel and Track submissions should provide a topic list and intended/confirmed participants in the abstract. - PC reviews the slides and continues to work with Submitter as needed to develop the topic. - FINAL SUBMISSION DEADLINE Draft presentation slides should be submitted prior to the published deadline for slides (24 Apr 2023). - PC evaluates submissions to determine presentations for the agenda (posted on 26 May 2023). - Submitters notified. - Agenda assembled and posted. - Final presentation slides must be submitted prior to the published deadline for slides (5 Jun 2023 for in person + live remote presentations). If you think you have an interesting topic but want feedback or suggestions for developing an idea into a presentation, please email the PC ( nanogpc(a)nanog.org) and a representative will respond to you in a timely manner. Otherwise, submit your talk, tutorial, track, or panel proposal to the Program Committee Tool at your earliest convenience. We look forward to reviewing your submission! NANOG 88 Calendar of Events Date Event/Deadline Wed, 21 Mar 2023 CFP Reminder Announcement Mon, 24 Apr 2023 DRAFT Presentation Slides Due Mon, 15 May 2023 Topics List Published Fri, 26 May 2023 Meeting Agenda Published Mon, 5 Jun 2023 Final Slides DUE Sun, 11 Jun 2023 On-Site Lightning Talk Submissions Open Final slides for accepted presentations must be submitted by Monday, 5 Jun 2023. Materials received after that date may be updated on the website after the completion of the conference. We look forward to seeing you in February! Sincerely, Cat Gurinsky Program Committee Chair Sent on behalf of the NANOG PC

1 0

Re: Spamhaus flags any IP announced by our ASN as a criminal network
by George Toma 21 Mar '23

21 Mar '23

I do not believe ASN sharing is illegal or prohibited, it's not prohibited in LACNIC and in APNIC policy I also could not find anything about ASN sharing, only APNIC policy states: "2.3. Autonomous System (AS) An Autonomous System (AS) is a connected group of one or more IP prefixes run by one or more network operators under a single and clearly defined routing policy. 2.3.1. Autonomous System Number (ASN) An Autonomous System Number (ASN) is a unique two- or four-byte number associated with an AS. The ASN is used as an identifier to allow the AS to exchange dynamic routing information with other Autonomous Systems." Nothing prohibiting ASN sharing and 2.3 specifically states "run by one or more network operators... single routing policy" Regards George On Tue, Mar 21, 2023 at 8:00 AM <nanog-request(a)nanog.org> wrote: > Message: 19 > Date: Mon, 20 Mar 2023 16:24:09 -0400 > From: ayang(a)august.tw > To: Collider <large.hadron.collider(a)gmx.com> > Cc: nanog(a)nanog.org > Subject: Re: Spamhaus flags any IP announced by our ASN as a criminal > network > Message-ID: <5b7ed1b1fbff65dfc63d188c2e1f95af(a)august.tw> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Several Huize ASNs, e.g. AS47158 and AS141011, were revoked due to RIR > policy violations, which include prohibited sharing of ASNs with third > parties, IP hijacking, and malicious path prepending. > > Given this history, it is not surprising that Spamhaus would blacklist > IP addresses associated with their ASN. In my opinion, such action is > well-justified. > > Best regards, > August Yang >

3 3

Anyone from Google Global Cache ?
by George Toma 21 Mar '23

21 Mar '23

Hello, Is there someone on this list from the Google Global Cache program (GGC) who could contact me off-list? If so I would greatly appreciate that. I would need a favor to get some information and look up a case because the responses to the tickets in the ISP portal I am getting are not giving me any meaningful answers. Thank you Regards George Toma

1 0