Re: Sufficient Buffer Sizes

2024-01-03 Thread Saku Ytti
On Wed, 3 Jan 2024 at 01:05, Mike Hammett wrote: > It suggests that 60 meg is what you need at 10G. Is that per interface? Would > it be linear in that I would need 600 meg at 100G? Not at all. You need to understand WHY buffering is needed, to determine how much you want to offer buffering.

Re: Sufficient Buffer Sizes

2024-01-03 Thread Maurice Brown
Threads like this are why I subscribe to this. On Wed, Jan 3, 2024 at 12:27 AM Saku Ytti wrote: > On Wed, 3 Jan 2024 at 01:05, Mike Hammett wrote: > > > It suggests that 60 meg is what you need at 10G. Is that per interface? > Would it be linear in that I would need 600 meg at 100G? > > Not at

Rackspace contact

2024-01-03 Thread Nathan Book via NANOG
Can someone at Rackspace contact me off list? We have issues reaching a Rackspace customer's site. Thanks, *Nathan Book* | IT/Broadband Specialist | GMN Broadband

Re: Sufficient Buffer Sizes

2024-01-03 Thread Dale W. Carder
Thus spake Mike Hammett (na...@ics-il.net) on Tue, Jan 02, 2024 at 05:02:22PM -0600: > While attempting to ascertain how big of switch buffers I needed in a 100G > switch, I rediscovered this article where I first learned about switch > buffers. > > https://fasterdata.es.net/network-tuning/rout

RPKI's 2023 Year in Review - growth, governments, and innovation

2024-01-03 Thread Job Snijders via NANOG
Dear all, Happy new year everyone! Having just closed chapter 2023 - let's look back at the previous year. In this memo I'll share some RPKI statistics, summarize highlights from the IETF Standards Development process, and reflect on emerging trends. Year to Year Growth of the distributed RPKI

Issue with Geolocation in Lasvegas

2024-01-03 Thread Raja Sekhar Gullapalli via NANOG
Team, We are having issues in our lasvegas office & it shows geolocation in all browsers as Israel instead of US region when we access news.google.com in our PC. Our public ip is 129.46.96.20. Can you help to whom we can contact to resolve the issue. Regards, Raja

Re: Issue with Geolocation in Lasvegas

2024-01-03 Thread Christopher Hawker
Looks like (according to RDNS) it's a "global NAT" address. Is it only being used in the continental US, or other countries? If the former, check that geofeeds are correctly configured and registered with Google in their ISP Portal. If the latter, you're going to encounter issues. Regards, Chris

Re: Issue with Geolocation in Lasvegas

2024-01-03 Thread Peter Potvin via NANOG
For Google-related sites specifically and if you haven't already, it's worth publishing an RFC8805-compliant geofeed and submitting it to them via their ISP portal at https://isp.google.com/ if you have an account with the announcing ASN affiliated to it. This is assuming that the IP you specified

RE: Issue with Geolocation in Lasvegas

2024-01-03 Thread Raja Sekhar Gullapalli via NANOG
Hi Christopher, It is used only in continental US & we also reported this issue to at n...@google.com. Any further info to be provided to resolve this issue. Regards, Raja From: Christopher Hawker Sent: Thursday, January 4, 2024 12:54 PM To: Raja Sekhar Gullapalli Cc

Re: Issue with Geolocation in Lasvegas

2024-01-03 Thread Christopher Hawker
As Peter and I have mentioned, you'll need to register a geofeed with Google. An example can be downloaded from https://isp.google.com/static/downloads/example-geo-feed.csv and registered in the ISP Portal. Having said that, it may be worthwhile checking-in with your internal IP Network Operations