Re: ARIN 8.3
There is no waiting period to receive resources. Also there is an ARIN mailing list for these kind of questions - https://lists.arin.net/mailman/listinfo/arin-ppml On Fri, Mar 24, 2023 at 2:22 PM Nicholas Warren wrote: > https://www.arin.net/participate/policy/nrpm/#eight3 > > > > What are people’s experience with receiving several transfers in a years’ > time? > > > > In 8.3, it states there is a waiting period for transfer sources. There is > nothing about a waiting period for receivers. What’s the likelihood of > there being a waiting period for receivers? If there is a waiting period > for receivers, would section 8.5.7 override that period? > > > > Thanks, > > Nich Warren >
ARIN 8.3
https://www.arin.net/participate/policy/nrpm/#eight3 What are people's experience with receiving several transfers in a years' time? In 8.3, it states there is a waiting period for transfer sources. There is nothing about a waiting period for receivers. What's the likelihood of there being a waiting period for receivers? If there is a waiting period for receivers, would section 8.5.7 override that period? Thanks, Nich Warren
RE: Akvorado Resource Requirements
Thanks, Vincent, I appreciate the feedback. Regards, Graham -Original Message- From: Vincent Bernat Sent: Friday, March 24, 2023 2:35 PM To: Graham Johnston ; nanog@nanog.org Subject: Re: Akvorado Resource Requirements On 2023-03-24 15:01, Graham Johnston via NANOG wrote: > For anyone running Akvorado, can you please comment on resource requirements. > I'm most concerned with CPU and memory, with the assumption that resources > are somewhat linear to flow rate, but also curious about disk usage > secondarily. A VM with 64 GB, 24 vCPU can sustain about 100k flows/s. 1 TB seems enough to keep data for about 5 years at 30k flows/s with the default setup. This is however highly dependent on how well your flows can be compressed. The main table with the default retention can use around 600 GB by itself. The data compresses well outside of the main table. You should test on your setup and let it run for a few days. You can check how much space each table uses and extrapolate depending on the TTL set on each table.
Re: Akvorado Resource Requirements
On 2023-03-24 15:01, Graham Johnston via NANOG wrote: For anyone running Akvorado, can you please comment on resource requirements. I'm most concerned with CPU and memory, with the assumption that resources are somewhat linear to flow rate, but also curious about disk usage secondarily. A VM with 64 GB, 24 vCPU can sustain about 100k flows/s. 1 TB seems enough to keep data for about 5 years at 30k flows/s with the default setup. This is however highly dependent on how well your flows can be compressed. The main table with the default retention can use around 600 GB by itself. The data compresses well outside of the main table. You should test on your setup and let it run for a few days. You can check how much space each table uses and extrapolate depending on the TTL set on each table.
Weekly Global IPv4 Routing Table Report
This is an automated weekly mailing describing the state of the Global IPv4 Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG and the RIPE Routing WG. Daily listings are sent to bgp-st...@lists.apnic.net. For historical data, please see https://thyme.apnic.net. If you have any comments please contact Philip Smith . IPv4 Routing Table Report 04:00 +10GMT Sat 25 Mar, 2023 BGP Table (Global) as seen in Japan. Report Website: https://thyme.apnic.net Detailed Analysis: https://thyme.apnic.net/current/ Analysis Summary BGP routing table entries examined: 916706 Prefixes after maximum aggregation (per Origin AS): 347952 Deaggregation factor: 2.63 Unique aggregates announced (without unneeded subnets): 447433 Total ASes present in the Internet Routing Table: 74277 Prefixes per ASN: 12.34 Origin-only ASes present in the Internet Routing Table: 63736 Origin ASes announcing only one prefix: 26191 Transit ASes present in the Internet Routing Table: 10541 Transit-only ASes present in the Internet Routing Table:437 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 55 Max AS path prepend of ASN (265020) 50 Prefixes from unregistered ASNs in the Routing Table: 1062 Number of instances of unregistered ASNs: 1081 Number of 32-bit ASNs allocated by the RIRs: 41520 Number of 32-bit ASNs visible in the Routing Table: 34390 Prefixes from 32-bit ASNs in the Routing Table: 168886 Number of bogon 32-bit ASNs visible in the Routing Table:64 Special use prefixes present in the Routing Table:1 Prefixes being announced from unallocated address space:504 Number of addresses announced to Internet: 3063124224 Equivalent to 182 /8s, 147 /16s and 145 /24s Percentage of available address space announced: 82.7 Percentage of allocated address space announced: 82.7 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.6 Total number of prefixes smaller than registry allocations: 306925 APNIC Region Analysis Summary - Prefixes being announced by APNIC Region ASes: 242068 Total APNIC prefixes after maximum aggregation: 69187 APNIC Deaggregation factor:3.50 Prefixes being announced from the APNIC address blocks: 236645 Unique aggregates announced from the APNIC address blocks:98042 APNIC Region origin ASes present in the Internet Routing Table: 13391 APNIC Prefixes per ASN: 17.67 APNIC Region origin ASes announcing only one prefix: 3931 APNIC Region transit ASes present in the Internet Routing Table: 1800 Average APNIC Region AS path length visible:4.5 Max APNIC Region AS path length visible: 38 Number of APNIC region 32-bit ASNs visible in the Routing Table: 8674 Number of APNIC addresses announced to Internet: 773729408 Equivalent to 46 /8s, 30 /16s and 44 /24s APNIC AS Blocks4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 64297-64395, 131072-151865 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary Prefixes being announced by ARIN Region ASes:268307 Total ARIN prefixes after maximum aggregation: 122098 ARIN Deaggregation factor: 2.20 Prefixes being announced from the ARIN address blocks: 270513 Unique aggregates announced from the ARIN address blocks:130377 ARIN Region origin ASes present in the Internet Routing Table:19069 ARIN Prefixes per ASN:
Re: Akvorado Resource Requirements
Graham You may want to build a lab and fire a generator at it to gather metrics. Fast search landed on https://github.com/nerdalert/nflow-generator but I am sure there are more. On Fri, Mar 24, 2023 at 8:05 AM Graham Johnston via NANOG wrote: > For anyone running Akvorado, can you please comment on resource > requirements. I'm most concerned with CPU and memory, with the assumption > that resources are somewhat linear to flow rate, but also curious about > disk usage secondarily. > > Thanks, > Graham > -- - Andrew "lathama" Latham -
Re: Hulu US Cogent IPs problem
Maybe try: vx-whitelistrequ...@hulu.com Report back so it can be added to TBW page if it is useful. On Fri, Mar 24, 2023 at 9:31 AM Jose Montero Martín (TRABAJO) < josemonteromar...@gmail.com> wrote: > Good morning, > > Our customers are facing issues accessing Hulu from our Cogent IPs > geolocated in the US. Every time they try to log in they receive the > following prompted message: > "Something went wrong. Please try again later" > > With a big black button "Log out and try again" > > These IPs are perfectly located but we are still having problems. I read > all the thread related in the newsletter and also read the > https://thebrotherswisp.com/index.php/geo-and-vpn/ webpage. > > I also contacted Hulu via customer support and ipad...@hulu.com, also using > Digital Envoy contact webpage and e-mail. I always receive an e-mail > informing us that there is no location or proxy problem either. > > Even further, I tried with another Cogent IP range also located in the US > with success. > > Anyone who can help me even off the list would be appreciated. > > Kind regards, >
Akvorado Resource Requirements
For anyone running Akvorado, can you please comment on resource requirements. I'm most concerned with CPU and memory, with the assumption that resources are somewhat linear to flow rate, but also curious about disk usage secondarily. Thanks, Graham
Hulu US Cogent IPs problem
Good morning, Our customers are facing issues accessing Hulu from our Cogent IPs geolocated in the US. Every time they try to log in they receive the following prompted message: "Something went wrong. Please try again later" With a big black button "Log out and try again" These IPs are perfectly located but we are still having problems. I read all the thread related in the newsletter and also read the https://thebrotherswisp.com/index.php/geo-and-vpn/ webpage. I also contacted Hulu via customer support and ipad...@hulu.com, also using Digital Envoy contact webpage and e-mail. I always receive an e-mail informing us that there is no location or proxy problem either. Even further, I tried with another Cogent IP range also located in the US with success. Anyone who can help me even off the list would be appreciated. Kind regards,
