- NANOG - lists.nanog.org

SAFNOG-3 Meeting - Date Change Updates
by Mark Tinka 04 Apr '16

04 Apr '16

Hello all. Due to an unfortunate set of circumstances, the SAFNOG-3 meeting dates have changed. Please visit the SAFNOG web site for details on this, at the URL below: http://safnog.org/ The SAFNOG-3 meeting is still going ahead as described on the web site. Detailed planning for the meeting is ongoing, and further updates will be communicated to the community in the coming weeks. You may also subscribe to the SAFNOG mailing list for regular updates at the URL below: http://lists.safnog.org/listinfo/safnog We look forward to seeing you all in Windhoek, later this year. For any questions, please send e-mail to: secretariat <at> safnog <dot> org Cheers, Mark Tinka On Behalf of the SAFNOG Management Committee

1 0

What services does Microsoft AS8075 provide when peering at IXPs?
by Eric A Louie 04 Apr '16

04 Apr '16

I had this question posed by a marketing type in my office. Does anyone know the answer? Is it microsoft.com, msdn, outllook365, msn.com, outlook.com, azure, windows updates, xbox? what else is possibly covered or omitted in their peering service? I suppose we have a customer who is an Azure customer that wants to know if their Azure traffic will stay in our network or still go through the Internet. I've tried asking peering(a)microsoft.com twice, but it looks like they have their ignore filter up. Thanks, -e-

3 3

Re: What services does Microsoft AS8075 provide when peering at IXPs?
by Eric Louie 03 Apr '16

03 Apr '16

Hi Todd I found an answer. It's everything public Microsoft. If it's private Office 365 or private Azure, it doesn't come through the peering fabric. Best regards, Eric Sent from my Verizon Wireless 4G LTE smartphone -------- Original message -------- From: Todd Crane <todd.crane(a)n5tech.com> Date: 4/3/2016 16:06 (GMT-08:00) To: Eric A Louie <elouie(a)yahoo.com> Subject: Re: What services does Microsoft AS8075 provide when peering at IXPs? Eric, This may or may not be what your after, but these are the prefixes we receive from them in Phoenix on Phoenix-IX. Peering is requested via the form at http://www.microsoft.com/Peering/PeeringForm. The peering(a)microsoft.com may be setup to ignore everybody that is not an established peer. That is just a guess. We have had no need to contact them, so we haven’t tried. -Todd Prefix Nexthop MED Lclpref AS path * 13.64.0.0/11 206.41.105.44 100 8075 I * 13.104.0.0/14 206.41.105.44 100 8075 I * 13.107.3.0/24 206.41.105.44 100 8075 8068 I * 13.107.4.0/24 206.41.105.44 100 8075 8068 I * 13.107.5.0/24 206.41.105.44 100 8075 8068 I * 13.107.6.0/24 206.41.105.44 100 8075 8068 I * 13.107.7.0/24 206.41.105.44 100 8075 8068 I * 13.107.9.0/24 206.41.105.44 100 8075 8068 I * 13.107.12.0/24 206.41.105.44 100 8075 8068 I * 13.107.13.0/24 206.41.105.44 100 8075 8068 I * 13.107.15.0/24 206.41.105.44 100 8075 8068 I * 13.107.16.0/24 206.41.105.44 100 8075 8068 I * 13.107.18.0/24 206.41.105.44 100 8075 8068 I * 13.107.24.0/24 206.41.105.44 100 8075 8068 I * 13.107.44.0/24 206.41.105.44 100 8075 8068 I * 13.107.58.0/24 206.41.105.44 100 8075 8068 I * 13.107.160.0/24 206.41.105.44 100 8075 8068 I * 13.107.240.0/24 206.41.105.44 100 8075 8068 I * 23.96.0.0/14 206.41.105.44 100 8075 I * 23.100.0.0/15 206.41.105.44 100 8075 I * 23.102.0.0/16 206.41.105.44 100 8075 I * 23.103.64.0/18 206.41.105.44 100 8075 I * 23.103.128.0/17 206.41.105.44 100 8075 I * 40.64.0.0/10 206.41.105.44 100 8075 I * 40.90.4.0/24 206.41.105.44 100 8075 8068 I * 51.8.0.0/16 206.41.105.44 100 8075 I * 51.10.0.0/15 206.41.105.44 100 8075 I * 51.12.0.0/15 206.41.105.44 100 8075 I * 51.18.0.0/16 206.41.105.44 100 8075 I * 51.51.0.0/16 206.41.105.44 100 8075 I * 51.53.0.0/16 206.41.105.44 100 8075 I * 51.103.0.0/16 206.41.105.44 100 8075 I * 51.104.0.0/15 206.41.105.44 100 8075 I * 51.107.0.0/16 206.41.105.44 100 8075 I * 51.116.0.0/16 206.41.105.44 100 8075 I * 51.120.0.0/16 206.41.105.44 100 8075 I * 51.124.0.0/16 206.41.105.44 100 8075 I * 51.132.0.0/16 206.41.105.44 100 8075 I * 51.136.0.0/15 206.41.105.44 100 8075 I * 51.138.0.0/16 206.41.105.44 100 8075 I * 51.140.0.0/14 206.41.105.44 100 8075 I * 51.144.0.0/15 206.41.105.44 100 8075 I * 52.96.0.0/12 206.41.105.44 100 8075 I * 52.112.0.0/14 206.41.105.44 100 8075 I * 52.120.0.0/14 206.41.105.44 100 8075 I * 52.125.0.0/16 206.41.105.44 100 8075 I * 52.126.0.0/15 206.41.105.44 100 8075 I * 52.130.0.0/15 206.41.105.44 100 8075 I * 52.132.0.0/14 206.41.105.44 100 8075 I * 52.136.0.0/13 206.41.105.44 100 8075 I * 52.145.0.0/16 206.41.105.44 100 8075 I * 52.146.0.0/15 206.41.105.44 100 8075 I * 52.148.0.0/14 206.41.105.44 100 8075 I * 52.152.0.0/13 206.41.105.44 100 8075 I * 52.160.0.0/11 206.41.105.44 100 8075 I * 52.224.0.0/11 206.41.105.44 100 8075 I * 64.4.0.0/18 206.41.105.44 100 8075 I * 64.4.48.0/24 206.41.105.44 100 8075 8068 I * 64.41.193.0/24 206.41.105.44 100 8075 20046 I * 65.52.0.0/14 206.41.105.44 100 8075 I * 65.54.0.0/24 206.41.105.44 100 8075 3598 I * 65.54.1.0/24 206.41.105.44 100 8075 3598 I * 65.54.2.0/24 206.41.105.44 100 8075 3598 I * 65.55.28.0/22 206.41.105.44 100 8075 3598 I * 65.55.28.0/23 206.41.105.44 100 8075 3598 ? * 65.55.44.0/24 206.41.105.44 100 8075 8075 I * 65.55.112.0/24 206.41.105.44 100 8075 20046 I * 65.55.117.0/24 206.41.105.44 100 8075 8075 I * 65.55.171.0/24 206.41.105.44 100 8075 20046 I * 65.55.188.0/24 206.41.105.44 100 8075 3598 I * 65.55.230.0/24 206.41.105.44 100 8075 8075 I * 65.55.231.0/24 206.41.105.44 100 8075 8075 I * 65.221.5.0/24 206.41.105.44 100 8075 20046 I * 66.119.144.0/20 206.41.105.44 100 8075 I * 70.37.0.0/17 206.41.105.44 100 8075 I * 70.37.128.0/18 206.41.105.44 100 8075 I * 91.190.216.0/23 206.41.105.44 100 8075 198015 I * 91.190.218.0/23 206.41.105.44 100 8075 198097 I * 91.190.220.0/24 206.41.105.44 100 8075 198097 I * 94.245.64.0/18 206.41.105.44 100 8075 I * 104.40.0.0/13 206.41.105.44 100 8075 I * 104.44.75.0/24 206.41.105.44 100 8075 8068 I * 104.146.0.0/19 206.41.105.44 100 8075 I * 104.146.128.0/17 206.41.105.44 100 8075 I * 104.208.0.0/13 206.41.105.44 100 8075 I * 111.221.16.0/20 206.41.105.44 100 8075 I * 111.221.64.0/18 206.41.105.44 100 8075 I * 131.107.0.0/16 206.41.105.44 100 8075 3598 I * 131.107.0.0/20 206.41.105.44 100 8075 3598 I * 131.107.217.0/24 206.41.105.44 100 8075 3598 I * 131.253.1.0/24 206.41.105.44 100 8075 I * 131.253.5.0/24 206.41.105.44 100 8075 I * 131.253.6.0/24 206.41.105.44 100 8075 I * 131.253.8.0/24 206.41.105.44 100 8075 I * 131.253.12.0/22 206.41.105.44 100 8075 8075 I * 131.253.16.0/23 206.41.105.44 100 8075 23468 I * 131.253.18.0/24 206.41.105.44 100 8075 I * 131.253.21.0/24 206.41.105.44 100 8075 8068 I * 131.253.22.0/23 206.41.105.44 100 8075 23468 I * 131.253.24.0/21 206.41.105.44 100 8075 I * 131.253.32.0/20 206.41.105.44 100 8075 I * 131.253.33.0/24 206.41.105.44 100 8075 I * 131.253.61.0/24 206.41.105.44 100 8075 I * 131.253.62.0/23 206.41.105.44 100 8075 I * 131.253.72.0/22 206.41.105.44 100 8075 8070 I * 131.253.80.0/20 206.41.105.44 100 8075 8070 I * 131.253.112.0/21 206.41.105.44 100 8075 8070 I * 131.253.120.0/22 206.41.105.44 100 8075 8070 I * 131.253.128.0/17 206.41.105.44 100 8075 I * 132.245.0.0/16 206.41.105.44 100 8075 I * 134.170.0.0/16 206.41.105.44 100 8075 I * 137.116.0.0/15 206.41.105.44 100 8075 I * 137.135.0.0/16 206.41.105.44 100 8075 I * 138.91.0.0/16 206.41.105.44 100 8075 I * 138.196.0.0/16 206.41.105.44 100 8075 I * 146.147.0.0/16 206.41.105.44 100 8075 I * 150.171.0.0/16 206.41.105.44 100 8075 I * 157.55.0.0/16 206.41.105.44 100 8075 I * 157.56.0.0/16 206.41.105.44 100 8075 I * 157.58.0.0/16 206.41.105.44 100 8075 3598 I * 157.58.2.0/23 206.41.105.44 100 8075 23468 I * 157.58.192.0/19 206.41.105.44 100 8075 3598 I * 157.58.248.0/23 206.41.105.44 100 8075 3598 ? * 157.60.23.0/24 206.41.105.44 100 8075 I * 157.60.31.0/24 206.41.105.44 100 8075 I * 167.220.0.0/17 206.41.105.44 100 8075 3598 I * 167.220.8.0/24 206.41.105.44 100 8075 3598 I * 167.220.9.0/24 206.41.105.44 100 8075 3598 I * 167.220.10.0/24 206.41.105.44 100 8075 3598 I * 167.220.16.0/20 206.41.105.44 100 8075 3598 I * 167.220.24.0/22 206.41.105.44 100 8075 3598 I * 167.220.28.0/23 206.41.105.44 100 8075 6584 8073 I * 167.220.40.0/21 206.41.105.44 100 8075 3598 I * 167.220.48.0/21 206.41.105.44 100 8075 3598 I * 167.220.64.0/19 206.41.105.44 100 8075 3598 I * 167.220.148.0/22 206.41.105.44 100 8075 3598 I * 167.220.152.0/24 206.41.105.44 100 8075 3598 I * 167.220.192.0/22 206.41.105.44 100 8075 6584 I * 167.220.196.0/22 206.41.105.44 100 8075 6584 I * 167.220.200.0/24 206.41.105.44 100 8075 6584 I * 167.220.201.0/24 206.41.105.44 100 8075 6584 I * 167.220.232.0/22 206.41.105.44 100 8075 8071 I * 167.220.236.0/22 206.41.105.44 100 8075 3598 I * 167.220.240.0/22 206.41.105.44 100 8075 I * 167.220.248.0/21 206.41.105.44 100 8075 3598 I * 168.61.0.0/16 206.41.105.44 100 8075 I * 168.62.0.0/15 206.41.105.44 100 8075 I * 191.232.0.0/13 206.41.105.44 100 8075 I * 192.48.225.0/24 206.41.105.44 100 8075 I * 192.84.159.0/24 206.41.105.44 100 8075 I * 192.84.160.0/23 206.41.105.44 100 8075 I * 192.92.196.0/24 206.41.105.44 100 8075 62540 I * 192.197.157.0/24 206.41.105.44 100 8075 I * 193.149.64.0/19 206.41.105.44 100 8075 I * 193.221.113.0/24 206.41.105.44 100 8075 8075 I * 194.69.96.0/22 206.41.105.44 100 8075 6584 I * 194.69.100.0/22 206.41.105.44 100 8075 6584 I * 194.69.126.0/23 206.41.105.44 100 8075 6584 I * 198.49.8.0/24 206.41.105.44 100 8075 8075 I * 198.105.232.0/22 206.41.105.44 100 8075 3598 I * 198.180.95.0/24 206.41.105.44 100 8075 3598 I * 198.200.130.0/24 206.41.105.44 100 8075 I * 198.206.164.0/24 206.41.105.44 100 8075 I * 199.2.137.0/24 206.41.105.44 100 8075 3598 I * 199.30.16.0/20 206.41.105.44 100 8075 I * 199.60.28.0/24 206.41.105.44 100 8075 I * 199.74.210.0/24 206.41.105.44 100 8075 I * 199.103.90.0/23 206.41.105.44 100 8075 I * 199.103.122.0/24 206.41.105.44 100 8075 I * 199.242.48.0/21 206.41.105.44 100 8075 I * 202.89.224.0/21 206.41.105.44 100 8075 I * 204.14.180.0/24 206.41.105.44 100 8075 8068 I * 204.79.135.0/24 206.41.105.44 100 8075 I * 204.79.179.0/24 206.41.105.44 100 8075 I * 204.79.180.0/24 206.41.105.44 100 8075 62540 I * 204.79.195.0/24 206.41.105.44 100 8075 8075 I * 204.79.197.0/24 206.41.105.44 100 8075 8068 I * 204.79.252.0/24 206.41.105.44 100 8075 8075 I * 204.95.96.0/20 206.41.105.44 100 8075 I * 204.152.140.0/23 206.41.105.44 100 8075 I * 204.176.46.0/24 206.41.105.44 100 8075 20046 I * 204.182.144.0/24 206.41.105.44 100 8075 3598 I * 204.255.244.0/23 206.41.105.44 100 8075 3598 I * 206.138.168.0/21 206.41.105.44 100 8075 I * 206.191.224.0/19 206.41.105.44 100 8075 I * 207.46.0.0/19 206.41.105.44 100 8075 I * 207.46.33.0/24 206.41.105.44 100 8075 I * 207.46.34.0/23 206.41.105.44 100 8075 I * 207.46.36.0/22 206.41.105.44 100 8075 I * 207.46.40.0/21 206.41.105.44 100 8075 I * 207.46.48.0/20 206.41.105.44 100 8075 I * 207.46.64.0/18 206.41.105.44 100 8075 I * 207.46.98.0/24 206.41.105.44 100 8075 8075 I * 207.46.128.0/17 206.41.105.44 100 8075 I * 207.68.128.0/18 206.41.105.44 100 8075 I * 207.82.250.0/23 206.41.105.44 100 8075 I * 208.68.136.0/21 206.41.105.44 100 8075 I * 208.76.45.0/24 206.41.105.44 100 8075 8075 I * 208.76.46.0/24 206.41.105.44 100 8075 8075 I * 208.84.0.0/24 206.41.105.44 100 8075 8075 I * 208.84.1.0/24 206.41.105.44 100 8075 I * 208.84.2.0/24 206.41.105.44 100 8075 8075 I * 208.84.3.0/24 206.41.105.44 100 8075 I * 209.1.15.0/24 206.41.105.44 100 8075 20046 I * 209.1.112.0/23 206.41.105.44 100 8075 I * 209.185.128.0/22 206.41.105.44 100 8075 I * 209.185.240.0/22 206.41.105.44 100 8075 I * 209.240.192.0/19 206.41.105.44 100 8075 I * 213.199.128.0/18 206.41.105.44 100 8075 I * 216.32.180.0/22 206.41.105.44 100 8075 I * 216.32.180.0/24 206.41.105.44 100 8075 20046 I * 216.32.240.0/22 206.41.105.44 100 8075 I * 216.33.240.0/22 206.41.105.44 100 8075 I * 216.34.51.0/24 206.41.105.44 100 8075 20046 I * 2001:df0:7::/48 2001:504:3b::44 100 8075 I * 2001:df0:d7::/48 2001:504:3b::44 100 8075 I * 2001:4898::/32 2001:504:3b::44 100 8075 3598 I * 2001:4899::/32 2001:504:3b::44 100 8075 I * 2001:489a:2000::/35 2001:504:3b::44 100 8075 8070 I * 2404:f800::/32 2001:504:3b::44 100 8075 I * 2404:f801::/32 2001:504:3b::44 100 8075 8071 I * 2404:f801:8028::/48 2001:504:3b::44 100 8075 3598 I * 2404:f801:8030::/48 2001:504:3b::44 100 8075 I * 2404:f801:8058::/48 2001:504:3b::44 100 8075 3598 I * 2404:f801:9000::/48 2001:504:3b::44 100 8075 3598 I * 2404:f801:a808::/48 2001:504:3b::44 100 8075 8071 I * 2603:1000::/25 2001:504:3b::44 100 8075 I * 2620:0:30::/45 2001:504:3b::44 100 8075 I * 2620:1ec::/36 2001:504:3b::44 100 8075 I * 2620:1ec:4::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:5::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:6::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:7::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:a::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:b::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:c::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:34::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:a92::/48 2001:504:3b::44 100 8075 8068 I * 2620:1ec:c11::/48 2001:504:3b::44 100 8075 8068 I * 2801:80:1d0::/48 2001:504:3b::44 100 8075 I * 2a01:110::/32 2001:504:3b::44 100 8075 6584 I * 2a01:110:8008::/48 2001:504:3b::44 100 8075 6584 I * 2a01:110:8012::/48 2001:504:3b::44 100 8075 6584 I * 2a01:110:a008::/48 2001:504:3b::44 100 8075 6584 I * 2a01:111::/32 2001:504:3b::44 100 8075 I * 2a01:111:2003::/48 2001:504:3b::44 100 8075 8068 I * 2a01:111:202c::/48 2001:504:3b::44 100 8075 8068 I * 2a01:111:202e::/48 2001:504:3b::44 100 8075 8068 I > On Apr 1, 2016, at 11:02 AM, Eric A Louie via NANOG <nanog(a)nanog.org> wrote: > > I had this question posed by a marketing type in my office. Does anyone know the answer? > Is it microsoft.com, msdn, outllook365, msn.com, outlook.com, azure, windows updates, xbox? what else is possibly covered or omitted in their peering service? I suppose we have a customer who is an Azure customer that wants to know if their Azure traffic will stay in our network or still go through the Internet. > I've tried asking peering(a)microsoft.com twice, but it looks like they have their ignore filter up. > > Thanks, -e-

1 0

Last call for presentations and Draft programme for RIPE 72
by Benno Overeinder 02 Apr '16

02 Apr '16

Colleagues, A list of currently accepted RIPE 72 presentations is now published at: https://ripe72.ripe.net/programme/meeting-plan/draft-programme/ There are still few slots remaining for a final RIPE 72 programme and RIPE Programme Committee will accept new proposals until 15 April 2016. This is our last call for you to submit your proposals. You can find the CFP for RIPE 72 below, or at https://ripe72.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. Kind regards, Benno Overeinder RIPE PC Chair https://www.ripe.net/participate/meetings/ripe-meetings/pc -------------------->>><<<-------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 72 will take place from 23-27 May 2016 in Copenhagen, Denmark. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 72. See the full descriptions of the different presentation formats, https://ripe72.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than 15 April 2016. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity in operations - Commercial transactions of IPv4 addresses - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange Submissions RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour - Lightning talks: 10 minutes The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe72.ripe.net/submit-topic/submission-form/. - Lightning talks should also be submitted using the meeting submission system (https://ripe72.ripe.net/submit-topic/submission-form/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice---in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. - Due to potential technical issues, presenters/panellists should be physically present at the RIPE Meeting. If you have any questions or requests concerning content submissions, please email pc [at] ripe [dot] net. -- Benno J. Overeinder NLnet Labs http://www.nlnetlabs.nl/

1 0

PlayStation Network blocking an IP
by Velocity Lists 01 Apr '16

01 Apr '16

Can someone form Sony's Playstation network give me call or contact me offlist. One of our apartment complexes has been reporting errors of PS4s not working for a few days then they start working again. PSN Support is telling the users to call us. We have diagnosed it and PSN is blocking the IP of the complex and it has nothing to do with us. Velocity Online Rodger Lewis rclewis(a)velocityonline.net 850-205-4638 x201

4 3

Fri AM AT&T outage
by Jay R. Ashworth 01 Apr '16

01 Apr '16

I heard speculation from many quarters that this may have been related to the Verizon splashcut to Frontier -- which, regardless of what Frontier was telling us, I was pretty sure would be more than just varying which light switch for a building sign was the one turned on. Has anyone heard anything they're allowed to repeat, yet, which confirms or denies? On a related[1] topic: I see on Craigs that Frontier is hiring through a sub for transport staff for their new NOC, which I think is going to be located in SPBGFLXA89H; that building has about 3 completely empty floors, and has for over 20 years. (OK, it did when I toured it in 91; dunno what's there now. :-) Cheers, -- jra [1]maybe -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274

5 5

Weekly Routing Table Report
by Routing Analysis Role Account 01 Apr '16

01 Apr '16

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, AusNOG, SANOG, PacNOG, SAFNOG, PaNOG, SdNOG, BJNOG, CaribNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 02 Apr, 2016 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 588557 Prefixes after maximum aggregation (per Origin AS): 216385 Deaggregation factor: 2.72 Unique aggregates announced (without unneeded subnets): 288091 Total ASes present in the Internet Routing Table: 53275 Prefixes per ASN: 11.05 Origin-only ASes present in the Internet Routing Table: 36612 Origin ASes announcing only one prefix: 15734 Transit ASes present in the Internet Routing Table: 6406 Transit-only ASes present in the Internet Routing Table: 178 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 37 Max AS path prepend of ASN ( 40285) 34 Prefixes from unregistered ASNs in the Routing Table: 966 Unregistered ASNs in the Routing Table: 358 Number of 32-bit ASNs allocated by the RIRs: 13295 Number of 32-bit ASNs visible in the Routing Table: 10257 Prefixes from 32-bit ASNs in the Routing Table: 40054 Number of bogon 32-bit ASNs visible in the Routing Table: 13 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 379 Number of addresses announced to Internet: 2806633732 Equivalent to 167 /8s, 73 /16s and 213 /24s Percentage of available address space announced: 75.8 Percentage of allocated address space announced: 75.8 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.1 Total number of prefixes smaller than registry allocations: 192525 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 150775 Total APNIC prefixes after maximum aggregation: 41981 APNIC Deaggregation factor: 3.59 Prefixes being announced from the APNIC address blocks: 160950 Unique aggregates announced from the APNIC address blocks: 65681 APNIC Region origin ASes present in the Internet Routing Table: 5146 APNIC Prefixes per ASN: 31.28 APNIC Region origin ASes announcing only one prefix: 1183 APNIC Region transit ASes present in the Internet Routing Table: 903 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 35 Number of APNIC region 32-bit ASNs visible in the Routing Table: 1966 Number of APNIC addresses announced to Internet: 751627332 Equivalent to 44 /8s, 204 /16s and 236 /24s Percentage of available APNIC address space announced: 87.8 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 131072-135580 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: 180018 Total ARIN prefixes after maximum aggregation: 89009 ARIN Deaggregation factor: 2.02 Prefixes being announced from the ARIN address blocks: 185195 Unique aggregates announced from the ARIN address blocks: 87864 ARIN Region origin ASes present in the Internet Routing Table: 16394 ARIN Prefixes per ASN: 11.30 ARIN Region origin ASes announcing only one prefix: 5882 ARIN Region transit ASes present in the Internet Routing Table: 1713 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 37 Number of ARIN region 32-bit ASNs visible in the Routing Table: 1099 Number of ARIN addresses announced to Internet: 1101578560 Equivalent to 65 /8s, 168 /16s and 193 /24s Percentage of available ARIN address space announced: 58.3 ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-395164 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 141552 Total RIPE prefixes after maximum aggregation: 69988 RIPE Deaggregation factor: 2.02 Prefixes being announced from the RIPE address blocks: 150107 Unique aggregates announced from the RIPE address blocks: 92701 RIPE Region origin ASes present in the Internet Routing Table: 18072 RIPE Prefixes per ASN: 8.31 RIPE Region origin ASes announcing only one prefix: 7912 RIPE Region transit ASes present in the Internet Routing Table: 2997 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 26 Number of RIPE region 32-bit ASNs visible in the Routing Table: 4606 Number of RIPE addresses announced to Internet: 704360576 Equivalent to 41 /8s, 251 /16s and 176 /24s Percentage of available RIPE address space announced: 102.4 RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 196608-204287 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 61798 Total LACNIC prefixes after maximum aggregation: 12183 LACNIC Deaggregation factor: 5.07 Prefixes being announced from the LACNIC address blocks: 75832 Unique aggregates announced from the LACNIC address blocks: 35811 LACNIC Region origin ASes present in the Internet Routing Table: 2470 LACNIC Prefixes per ASN: 30.70 LACNIC Region origin ASes announcing only one prefix: 578 LACNIC Region transit ASes present in the Internet Routing Table: 551 Average LACNIC Region AS path length visible: 4.7 Max LACNIC Region AS path length visible: 25 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 2386 Number of LACNIC addresses announced to Internet: 170590976 Equivalent to 10 /8s, 43 /16s and 3 /24s Percentage of available LACNIC address space announced: 101.7 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-265628 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 14280 Total AfriNIC prefixes after maximum aggregation: 3183 AfriNIC Deaggregation factor: 4.49 Prefixes being announced from the AfriNIC address blocks: 16094 Unique aggregates announced from the AfriNIC address blocks: 5693 AfriNIC Region origin ASes present in the Internet Routing Table: 732 AfriNIC Prefixes per ASN: 21.99 AfriNIC Region origin ASes announcing only one prefix: 179 AfriNIC Region transit ASes present in the Internet Routing Table: 167 Average AfriNIC Region AS path length visible: 4.6 Max AfriNIC Region AS path length visible: 25 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 200 Number of AfriNIC addresses announced to Internet: 78107392 Equivalent to 4 /8s, 167 /16s and 211 /24s Percentage of available AfriNIC address space announced: 77.6 AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5594 4192 76 China Education and Research 7545 3275 352 190 TPG Telecom Limited 4766 3151 11142 1117 Korea Telecom 17974 2912 914 96 PT Telekomunikasi Indonesia 9829 2446 1457 446 National Internet Backbone 4755 2100 432 245 TATA Communications formerly 9808 1854 8717 30 Guangdong Mobile Communicatio 4808 1650 2290 531 CNCGROUP IP network China169 4788 1528 645 62 TM Net, Internet Service Prov 9583 1519 121 564 Sify Limited Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 22773 3345 2948 148 Cox Communications Inc. 6389 2357 3687 42 BellSouth.net Inc. 18566 2209 394 276 MegaPath Corporation 20115 1920 1931 402 Charter Communications 30036 1737 344 237 Mediacom Communications Corp 6983 1691 849 231 EarthLink, Inc. 4323 1570 1004 386 tw telecom holdings, inc. 209 1553 4636 1235 Qwest Communications Company, 701 1382 11446 661 MCI Communications Services, 11492 1270 235 601 CABLE ONE, INC. Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 39891 2708 143 10 SaudiNet, Saudi Telecom Compa 20940 2425 933 1761 Akamai International B.V. 34984 1962 323 415 TELLCOM ILETISIM HIZMETLERI A 8551 1259 376 54 Bezeq International-Ltd 6849 1158 355 21 JSC "Ukrtelecom" 12479 1140 980 86 France Telecom Espana SA 8402 1101 544 15 OJSC "Vimpelcom" 13188 1079 98 69 TOV "Bank-Inform" 31148 1035 47 41 Freenet Ltd. 6830 891 2712 464 Liberty Global Operations B.V Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 10620 3448 542 134 Telmex Colombia S.A. 8151 2217 3310 542 Uninet S.A. de C.V. 7303 1521 940 245 Telecom Argentina S.A. 11830 1479 368 51 Instituto Costarricense de El 6503 1433 453 56 Axtel, S.A.B. de C.V. 6147 1050 377 27 Telefonica del Peru S.A.A. 3816 994 478 185 COLOMBIA TELECOMUNICACIONES S 26615 993 2325 34 Tim Celular S.A. 7738 990 1882 40 Telemar Norte Leste S.A. 28573 884 2172 160 NET Serviços de Comunicação S Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1217 402 40 Link Egypt (Link.NET) 8452 679 1472 15 TE-AS 37611 643 48 2 Afrihost-Brevis Computer Serv 36903 584 294 104 Office National des Postes et 36992 506 1357 25 ETISALAT MISR 37492 382 233 65 Orange Tunisie 29571 295 37 12 Cote d'Ivoire Telecom 24835 290 146 12 Vodafone Data 2018 249 327 74 TENET (The UNINET Project) 36947 234 807 13 Telecom Algeria Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5594 4192 76 China Education and Research 10620 3448 542 134 Telmex Colombia S.A. 22773 3345 2948 148 Cox Communications Inc. 7545 3275 352 190 TPG Telecom Limited 4766 3151 11142 1117 Korea Telecom 17974 2912 914 96 PT Telekomunikasi Indonesia 39891 2708 143 10 SaudiNet, Saudi Telecom Compa 9829 2446 1457 446 National Internet Backbone 20940 2425 933 1761 Akamai International B.V. 6389 2357 3687 42 BellSouth.net Inc. Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 10620 3448 3314 Telmex Colombia S.A. 22773 3345 3197 Cox Communications Inc. 7545 3275 3085 TPG Telecom Limited 17974 2912 2816 PT Telekomunikasi Indonesia 39891 2708 2698 SaudiNet, Saudi Telecom Compa 6389 2357 2315 BellSouth.net Inc. 4766 3151 2034 Korea Telecom 9829 2446 2000 National Internet Backbone 18566 2209 1933 MegaPath Corporation 4755 2100 1855 TATA Communications formerly Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 30662 UNALLOCATED 8.2.129.0/24 3356 Level 3 Communicatio 53506 UNALLOCATED 8.17.102.0/23 3356 Level 3 Communicatio 46467 UNALLOCATED 8.19.192.0/24 46887 Lightower Fiber Netw 16589 UNALLOCATED 8.20.247.0/24 35838 CCANET Limited 16589 UNALLOCATED 8.26.56.0/24 35838 CCANET Limited 46473 UNALLOCATED 8.27.122.0/24 3356 Level 3 Communicatio 46473 UNALLOCATED 8.27.124.0/24 3356 Level 3 Communicatio 27205 UNALLOCATED 8.38.16.0/21 3356 Level 3 Communicatio 15347 UNALLOCATED 8.224.147.0/24 12064 Cox Communications I 33628 UNALLOCATED 12.0.239.0/24 1239 Sprint Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 5.100.241.0/24 23456 32bit Transition AS 23.226.112.0/20 62788 >>UNKNOWN<< 23.249.144.0/20 40430 colo4jax, LLC 27.100.7.0/24 56096 >>UNKNOWN<< 37.46.10.0/23 36351 SoftLayer Technologies Inc. 37.46.14.0/24 36351 SoftLayer Technologies Inc. 37.46.15.0/24 36351 SoftLayer Technologies Inc. 41.73.1.0/24 37004 >>UNKNOWN<< 41.73.2.0/24 37004 >>UNKNOWN<< 41.73.3.0/24 37004 >>UNKNOWN<< Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:16 /9:13 /10:36 /11:101 /12:267 /13:512 /14:1028 /15:1759 /16:12962 /17:7554 /18:12732 /19:25789 /20:38145 /21:40033 /22:65050 /23:56554 /24:324329 /25:552 /26:593 /27:410 /28:45 /29:32 /30:14 /31:1 /32:30 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 39891 2664 2708 SaudiNet, Saudi Telecom Compa 22773 2525 3345 Cox Communications Inc. 18566 2111 2209 MegaPath Corporation 30036 1551 1737 Mediacom Communications Corp 6389 1499 2357 BellSouth.net Inc. 6983 1340 1691 EarthLink, Inc. 10620 1333 3448 Telmex Colombia S.A. 34984 1247 1962 TELLCOM ILETISIM HIZMETLERI A 11492 1175 1270 CABLE ONE, INC. 6849 976 1158 JSC "Ukrtelecom" Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1650 2:740 4:20 5:2030 6:28 8:941 12:1781 13:38 14:1661 15:45 16:2 17:75 18:20 20:48 23:1443 24:1804 27:2256 31:1757 32:54 33:2 34:2 35:5 36:257 37:2258 38:1184 39:24 40:87 41:2811 42:387 43:1694 44:41 45:1775 46:2469 47:72 49:1132 50:841 51:8 52:143 54:198 55:3 56:6 57:45 58:1535 59:868 60:569 61:1821 62:1475 63:1915 64:4466 65:2164 66:4330 67:2163 68:1102 69:3272 70:1048 71:470 72:1982 74:2550 75:340 76:413 77:1329 78:1267 79:843 80:1333 81:1358 82:938 83:684 84:803 85:1593 86:469 87:1015 88:561 89:1947 90:168 91:6048 92:859 93:2315 94:2316 95:2311 96:465 97:357 98:955 99:45 100:70 101:1024 103:10210 104:2263 105:153 106:392 107:1085 108:668 109:2125 110:1248 111:1649 112:958 113:1138 114:1036 115:1697 116:1542 117:1420 118:2139 119:1576 120:518 121:1169 122:2221 123:2004 124:1616 125:1756 128:716 129:380 130:411 131:1306 132:625 133:174 134:448 135:123 136:370 137:332 138:1717 139:224 140:250 141:466 142:640 143:877 144:605 145:162 146:850 147:678 148:1461 149:494 150:654 151:766 152:606 153:275 154:587 155:947 156:491 157:473 158:345 159:1099 160:459 161:742 162:2304 163:547 164:750 165:1038 166:314 167:1104 168:1689 169:632 170:1581 171:265 172:530 173:1676 174:723 175:903 176:1672 177:4044 178:2239 179:1126 180:2063 181:1710 182:1924 183:677 184:790 185:6077 186:3051 187:2082 188:2149 189:1741 190:7655 191:1224 192:8935 193:5729 194:4363 195:3767 196:1704 197:1130 198:5517 199:5639 200:6961 201:3708 202:10113 203:9627 204:4643 205:2687 206:2986 207:3074 208:4064 209:3788 210:3948 211:2039 212:2636 213:2188 214:832 215:72 216:5746 217:1932 218:764 219:566 220:1681 221:857 222:663 223:961 End of report

1 0

shipping from US to Telstra (ex-Pacnet) facility, 11 Chun Kwong St, Hong Kong
by Joe Abley 31 Mar '16

31 Mar '16

Hi all, If anybody has recently managed to ship equipment from the US to the Pacnet (now Telstra) facility at 11 Chun Kwong St, Hong Kong and doesn't mind comparing notes, any chance you could drop me a line off-list? We have some shipping confusion, and it would be great to see an example of paperwork that is known not to have failed. Thanks, Joe

1 0

Capacity planning , transit vs last mile
by Jean-Francois Mezei 31 Mar '16

31 Mar '16

Canada is to hold a 3 week long hearing on discussing whether the internet is important and whether the farcical 5/1 speed promoted by the government is adequate. In this day and age, it would be easy to just set FTTP as target technology and be done with it, but too many want to have a policy that is technologically neutral. To this end, I will not only be proposing that subsidized deployments not only meet advertised service speed standards, but also a capacity per end user metric for the last mile technology as well as for the backhaul/transit. (One of the often subsidized companies deploys fixed wireless which delivers the advertised speed for the first week, but routinely gets oversubscribed after a while and customers feel like on dialup.) I know that for sufficiently large ISPs, they currently provision just over 1mbps of transit capacity per end user (so 800-1000 customers per 1gbps of transit). The number rises by over 30% a year as usage grows. (The CRTC can get exact figure from telecom operators and generate aggregate industry-wide growth in traffic to do yearly standard adjustment). QUESTION: Say the policy is 1mbps per customer if 1000 customer or more. Is there some formula (approx or precise) to calculate how that 1mbps changes for smaller samples ? (like 500 customers, 200 ? ) And on the last mile portion where one has typically few users on each shared capacity segment (fixed wireless, FTTP, cable), are there fairly standard oversubscription ratios based on average service speed that is sold in that neighbourhood ? (for instance if I have 100 customers with average subscibed speed of 15mbps, how much capacity should the antenna serving those customers have ? I realise that each ISP guards its oversubscription ratios as very proprietary, but aren't there generic industry-wide recommendations ? My goal is to have some basic standards that prevent gross over subscription that result in unusable service. As well, I want that a company pitching a broadband deployment be able to demonstrate that the technology being deployed will last X years because it has sufficient capacity to handle the number of customers as well as the predicted growth in usage each year. Any help ? comments on whether this is crazy ? sanity check ?

5 6

tel script
by Robert Drake 29 Mar '16

29 Mar '16

This is a program for logging into devices. You can find it here: https://github.com/rfdrake/tel I don't like to self promote things, but I'm interested in feedback. I'm also interested in alternatives if someone wrote something better. I started it a long time ago as a lighter clogin which didn't hang as much. Moving from expect to perl cut and bunch of the cruft out because of how verbose the TCL language is. My script is now larger than clogin and no longer consists of a single file. It's also arguably much cruftier in places, but it's gained some features I think people may like: Color syntax highlighting for "show interface" and some other commands An attempt to make backspace work on platforms with differing opinions of ^H vs ^? Run multiple script files and multiple devices in the same command (tel -x script1.txt -x script2.txt router router2 router3) Unified logout command: ctrl-d send slow (tel -s .5 -x script1.txt router) for sending scripts to devices with buffering issues send slow interactively (tel -S .5 router) for cut and paste to devices with buffering issues (some terminal emulators will do this if it's the only thing you need) change your device profile after login (tel -A zhone oob-test-lab:2004) helpful if you login through an out of band console which is made by one vendor into a device made by another vendor Support for KeePass, Pass, PWSafe3, and Gnome/KDE/MacOS Keyring, as well as a combination of these for storing passwords in encrypted files The entire thing is very customizeable for people who know perl or scripting languages. It's designed for NOC use on bounce servers where the administrator might setup the global profile in /etc/telrc, then the individual users would make their own profiles in their home directories to override individual settings. Limitations: I'm pretty sure I tried to build this on Cygwin once and it failed for reasons that probably can never be fixed. I've also never tested on MacOSX. I've run it successfully on various Linux as well as FreeBSD and OpenBSD.

1 0