RE: IP Dslams

2019-01-04 Thread Payam Poursaied
Hi Nick

How many devices are you looking for?

Consider ZyXEL 1248: 
https://www.zyxel.com/uk/en/products_services/48-port-Temperature-Hardened-ADSL2--Box-DSLAM-IES-1248-5x-IES-1248-5xA-Series/

 

For PPP and those stuff, you can rely on MikroTik. 

i.e. https://mikrotik.com/product/rb4011igs_rm @199USD you would have PPP(oE) 
aggregation + user manager panel and much more

 

Regards

Payam

 

From: NANOG  On Behalf Of Nick Edwards
Sent: December 28, 2018 5:36 PM
To: nanog@nanog.org
Subject: IP Dslams

 

Howdy,

We have a requirement for an aged care facility to provide voice and data, we 
have the voice worked out, but data, WiFi is out of the question, so are 
looking for IP-Dslams, preferably a system that is all-in-one, or self 
contained, as in contains its own BBRAS/LNS/PPP server/Radius, such as has a 
property managment API, or even just a webpage manager where admin can add in 
new residents when they arive, or delete when they depart I know these used to 
be available  many years ago, but that vendor has like many vanished, only 
requirement is for ADSL2+, prefer units with either 48 ports or multiples of 
(192 etc) and have filtered voice out ports (telco50/rj21 etc)

If anyone knows of such units, would appreciate some details on them,  
brand/model suppliers if known, etc, we can try get out google fu back if we 
have some steering:)

Thank Y'all

(resent - original never made it to the list for some gremlin reason)



Re: Changing upstream providers, opinions/thoughts on 123.net and cogent

2019-01-04 Thread Brandon Martin

To reiterate what's been said...

I would not want to be single-homed to Cogent.  They're fine (and 
generally useful and a reasonable use of your operating money) in a blend.


I'm not familiar with 123.net, but looking briefly at them, they appear 
to be a regional blend.  Much preferable compared to your other option 
assuming they competently operate their network.


FWIW, I wouldn't WANT to be single-homed to anyone, but I'll do it when 
it's the right choice.


If you have to be single-homed, you really have to go with a quality 
upstream, and you're going to pay for it.  If you have the volume and 
connectivity to be multi-homed, do it.  It'll be better in just about 
every way.

--
Brandon Martin


Re: Changing upstream providers, opinions/thoughts on 123.net and cogent

2019-01-04 Thread William Herrin
On Fri, Jan 4, 2019 at 5:40 PM Aaron Henderson  wrote:
> I work for a rural ISP and the powers that be have been thinking about 
> changing our upstream providers. The big names on the table right now are 
> 123.net and Cogent.
>
> I was hoping some of you here might have experience with these providers and 
> could share your experiences and opinions.

Hi Aaron,

I don't know anything about 123.net.

Google "Cogent cake," "cogent sprint," and "cogent telia" for
explanations and examples of how relying on Cogent as your sole
transit provider is likely to bite you in the behind. Using them as a
secondary transit provider in a BGP-managed mix is arguably more
acceptable.

Regards,
Bill Herrin


-- 
William Herrin  her...@dirtside.com  b...@herrin.us
Dirtside Systems . Web: 


Re: Changing upstream providers, opinions/thoughts on 123.net and cogent

2019-01-04 Thread Ben Cannon
Run BGP and use multiple upstream providers as soon as you can.

-Ben

> On Jan 4, 2019, at 4:57 AM, Aaron Henderson  wrote:
> 
> I work for a rural ISP and the powers that be have been thinking about 
> changing our upstream providers. The big names on the table right now are 
> 123.net and Cogent.
> 
> I, along with the people in my circle, do not have any experience with these 
> providers and all we are getting is what sales are dishing us.
> 
> I was hoping some of you here might have experience with these providers and 
> could share your experiences and opinions.
> 
> Thanks,
> 
> A
> 


Re: IP Dslams

2019-01-04 Thread Rob Pickering
Just a thought, would a two wire Ethernet extender technology (eg
Phybridge) provide you with a simpler solution?  xDSL needs a lot of
infrastructure for a low port count (& budget) application.

I have no idea if you can split the baseband out to provide POTS over the
same pair, but even if you can't, Ethernet plus a VoIP phone or ATA to each
unit may end up cheaper than a shed load of carrier oriented xDSL infra?

On Mon, 31 Dec 2018 at 19:15, Nick Edwards  wrote:

> Howdy,
> We have a requirement for an aged care facility to provide voice and data,
> we have the voice worked out, but data, WiFi is out of the question, so are
> looking for IP-Dslams, preferably a system that is all-in-one, or self
> contained, as in contains its own BBRAS/LNS/PPP server/Radius, such as has
> a property managment API, or even just a webpage manager where admin can
> add in new residents when they arive, or delete when they depart I know
> these used to be available  many years ago, but that vendor has like many
> vanished, only requirement is for ADSL2+, prefer units with either 48 ports
> or multiples of (192 etc) and have filtered voice out ports (telco50/rj21
> etc)
>
> If anyone knows of such units, would appreciate some details on them,
> brand/model suppliers if known, etc, we can try get out google fu back if
> we have some steering:)
>
> Thank Y'all
>
> (resent - original never made it to the list for some gremlin reason)
>


-- 
--
Rob Pickering, r...@pickering.org


Re: Cleveland/Cincinnati Co-location

2019-01-04 Thread David Kehoe



On Sat, Dec 29, 2018 at 12:13 PM Mark Milhollan 
mailto:m...@pixelgate.net>> wrote:

> On Fri, 28 Dec 2018, Dovid Bender wrote:
>
> >I finally got around to setting up a cellular backup device in our new
> POP.
>
> >When SSH'ing in remotely the connection seems rather slow.
>
> Perhaps using MOSH can help make the interactive CLI session less
> annoying.
>
> >Verizon they charge $500.00 just to get a public IP and I want to avoid
> >that if possible.
>
> You might look into have it call out / maintain a connection back to
> your infrastructure.
>
>
> /mark
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://mailman.nanog.org/pipermail/nanog/attachments/20190103/b4c3f157/attachment-0001.html<http://mailman.nanog.org/pipermail/nanog/attachments/20190103/b4c3f157/attachment-0001.html>>

--

Message: 10
Date: Fri, 4 Jan 2019 11:21:32 +0300
From: Job Snijders mailto:j...@ntt.net>>
To: Dominik Bay mailto:d...@rrbone.net>>
Cc: "nanog@nanog.org<mailto:nanog@nanog.org>" 
mailto:nanog@nanog.org>>
Subject: Re: 192.208.19.0/24<http://192.208.19.0/24> hijack transiting 209, 
286, 3320, 5511,
6461, 6762, 6830, 8220, 9002, 12956
Message-ID:
mailto:CACWOCC8DRPSWCvsa6n-Yyf0LwR=81apcl+havgof9ghwvyh...@mail.gmail.com>>
Content-Type: text/plain; charset="utf-8"

Dear all,

NTT / AS 2914 deployed explicit filters to block this BGP announcement from
AS 4134. I recommend other operators to do the same.

I’d also like to recommend AS 32982 to remove the AS_PATH prepend on the
/24 announcement so the counter measure is more effective.

Kind regards,

Job

On Fri, Jan 4, 2019 at 1:02 Dominik Bay 
mailto:d...@rrbone.net>> wrote:

> I see the follwowing ASN transiting a leak concerning 
> 192.208.19.0/24<http://192.208.19.0/24>
> originated by 4812
>
> 209
> 286
> 3320
> 5400
> 5511
> 6327
> 6461
> 6762
> 6830
> 8218
> 8220
> 8447
> 8551
> 9002
> 12956
>
> The proper source is 32982 (Department of Energy).
> More details to be found here: 
> https://bgpstream.com/event/171779<https://bgpstream.com/event/171779>
> And here: 
> http://lg.ring.nlnog.net/prefix_detail/lg01/ipv4?q=192.208.19.0<http://lg.ring.nlnog.net/prefix_detail/lg01/ipv4?q=192.208.19.0>
>
> Cheers,
> Dominik
>
>
>
-- next part --
An HTML attachment was scrubbed...
URL: 
<http://mailman.nanog.org/pipermail/nanog/attachments/20190104/0c84b757/attachment-0001.html<http://mailman.nanog.org/pipermail/nanog/attachments/20190104/0c84b757/attachment-0001.html>>

End of NANOG Digest, Vol 132, Issue 4
*


Changing upstream providers, opinions/thoughts on 123.net and cogent

2019-01-04 Thread Aaron Henderson
I work for a rural ISP and the powers that be have been thinking about
changing our upstream providers. The big names on the table right now are
123.net and Cogent.

I, along with the people in my circle, do not have any experience with
these providers and all we are getting is what sales are dishing us.

I was hoping some of you here might have experience with these providers
and could share your experiences and opinions.

Thanks,

A


Re: How to choose a transport(terrestrial/subsea)

2019-01-04 Thread Mehmet Akcin
On Wed, Jan 2, 2019 at 2:04 PM Jason Bothe via NANOG 
wrote:

> KMZs or no business. Period.
>

You can say that in US, EU but you won't be able to in certain places
unless you are willing to take the extra mile and work with people.


Weekly Routing Table Report

2019-01-04 Thread Routing Analysis Role Account
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, 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 http://thyme.rand.apnic.net.

If you have any comments please contact Philip Smith .

Routing Table Report   04:00 +10GMT Sat 05 Jan, 2019

Report Website: http://thyme.rand.apnic.net
Detailed Analysis:  http://thyme.rand.apnic.net/current/

Analysis Summary


BGP routing table entries examined:  732608
Prefixes after maximum aggregation (per Origin AS):  281600
Deaggregation factor:  2.60
Unique aggregates announced (without unneeded subnets):  352811
Total ASes present in the Internet Routing Table: 62818
Prefixes per ASN: 11.66
Origin-only ASes present in the Internet Routing Table:   54157
Origin ASes announcing only one prefix:   23519
Transit ASes present in the Internet Routing Table:8661
Transit-only ASes present in the Internet Routing Table:267
Average AS path length visible in the Internet Routing Table:   4.2
Max AS path length visible:  31
Max AS path prepend of ASN ( 16327)  25
Prefixes from unregistered ASNs in the Routing Table:22
Number of instances of unregistered ASNs:24
Number of 32-bit ASNs allocated by the RIRs:  25373
Number of 32-bit ASNs visible in the Routing Table:   20560
Prefixes from 32-bit ASNs in the Routing Table:   88488
Number of bogon 32-bit ASNs visible in the Routing Table:17
Special use prefixes present in the Routing Table:1
Prefixes being announced from unallocated address space:263
Number of addresses announced to Internet:   2838813409
Equivalent to 169 /8s, 52 /16s and 218 /24s
Percentage of available address space announced:   76.7
Percentage of allocated address space announced:   76.7
Percentage of available address space allocated:  100.0
Percentage of address space in use by end-sites:   99.1
Total number of prefixes smaller than registry allocations:  244490

APNIC Region Analysis Summary
-

Prefixes being announced by APNIC Region ASes:   200435
Total APNIC prefixes after maximum aggregation:   56904
APNIC Deaggregation factor:3.52
Prefixes being announced from the APNIC address blocks:  197571
Unique aggregates announced from the APNIC address blocks:81259
APNIC Region origin ASes present in the Internet Routing Table:9328
APNIC Prefixes per ASN:   21.18
APNIC Region origin ASes announcing only one prefix:   2633
APNIC Region transit ASes present in the Internet Routing Table:   1390
Average APNIC Region AS path length visible:4.1
Max APNIC Region AS path length visible: 26
Number of APNIC region 32-bit ASNs visible in the Routing Table:   4326
Number of APNIC addresses announced to Internet:  769208320
Equivalent to 45 /8s, 217 /16s and 48 /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-139577
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:216909
Total ARIN prefixes after maximum aggregation:   102896
ARIN Deaggregation factor: 2.11
Prefixes being announced from the ARIN address blocks:   216224
Unique aggregates announced from the ARIN address blocks:103607
ARIN Region origin ASes present in the Internet Routing Table:18302
ARIN Prefixes per ASN:11.81
ARIN Regio

Re: IP Dslams

2019-01-04 Thread Brandon Martin

On 1/4/19 12:53 PM, Shawn L via NANOG wrote:
The "newer" replacement for the 42xx series was the bitstorm 
(Bitstorm-RP2-152-AC), and they came in AC as well and 48 ports -- in a 
1.5 U I think .


Yep, that's probably the one you want to look at.  I've got one on a 
shelf.  Looks like a nice box.  Pity it has no firmware on it.


It does not have POTS built in, so you'd have to generate that somehow. 
 An old Adit 600 with a bunch of FXS cards and CMG router might do it 
on the cheap.

--
Brandon Martin


Re: IP Dslams

2019-01-04 Thread Shawn L via NANOG

The "newer" replacement for the 42xx series was the bitstorm 
(Bitstorm-RP2-152-AC), and they came in AC as well and 48 ports -- in a 1.5 U I 
think .
 

-Original Message-
From: "Blake Hudson" 
Sent: Friday, January 4, 2019 12:47pm
To: nanog@nanog.org
Subject: Re: IP Dslams


I was thinking the same thing. They're a few years out of support, but the 
Zhone 42xx IP DSLAM provides a 1Gbps ethernet uplink and 24 ADSL2+ DSL user 
ports per 1U chassis (stackable to achieve 192 ports total). Wish they were 
available in AC for non-telco use.
 [ http://support.zhone.com/support/manuals/docs/42/4200-A2-GN21-40.pdf ]( 
http://support.zhone.com/support/manuals/docs/42/4200-A2-GN21-40.pdf )

 You could pair these with a pfSense appliance (or an x86 PC running the free 
software) to provide DHCP, DNS, etc - or use the built in pfSense captive 
portal to provide additional authentication and accounting per user. pfSense 
can provide NAT and FW if needed, or these features can be disabled to use 
globally routable IP4/IP6 addresses.

 As far as support goes, backup your pfsense and DLSAM configs when you finish 
the project and the subscriber accounts and DSL modems could be maintained by a 
local admin through the pfSense web interface with no need to touch the DSLAMs 
or anything CLI.

 --Blake


Shawn L via NANOG wrote on 1/4/2019 8:59 AM:
Might want to look for old Zhone ip bitstorm dslams.  There should be a bunch 
on the used market.  They do all of the ATM conversions internally so you just 
need to feed them with ethernet.
 

 -Original Message-
 From: "Nick Edwards" [  ]( 
mailto:nick.z.edwa...@gmail.com )
 Sent: Friday, January 4, 2019 9:36am
 To: "Brandon Martin" [  ]( 
mailto:lists.na...@monmotha.net )
 Cc: "NANOG" [  ]( mailto:nanog@nanog.org )
 Subject: Re: IP Dslams




They don't have a large budget and although I'm yet to get prices on adtran's 
(understandable, holidays 'n all) I doubt it will fit within their budget, it's 
looking more like getting a few planet dslams and configuring a linux box as 
the bng, been 10 years since I've had to do that kind of setup, memories hazy, 
but I know it worked, and well, so thanks to all for suggestions but the 
adtrans and nokias are not for those on shoe string budgets, which wouldnt even 
allow me to include an asr1k for the bng, and although it would allow for, I'd 
rather not grab an ebay 7200/7300 :)


On Wed, Jan 2, 2019 at 10:52 PM Brandon Martin <[ lists.na...@monmotha.net ]( 
mailto:lists.na...@monmotha.net )> wrote:On 1/2/19 6:47 AM, Nick Edwards wrote:
 > There are 260 villas, and no coax.

 Is there a logical way to distribute the termination?  You might be able 
 to get better performance (not that you perhaps care, in this case) at 
 minimal additional cost if you can do building-local termination of each 
 customer circuit and then backhaul on e.g. bonded VDSL2 or G.FAST over 
 shorter distances (perhaps hopping building to building).

 I'm assuming there's no data grade copper or fiber if there's no coax. 
 Obviously if you've got those, distributed termination makes even more 
 sense.

 If you do want a centralized solution, an Adtran TA5006 (the small 
 chassis) with 6x 48 port VDSL2 combo modules (with or without vectoring, 
 depending on your needs) would do the job (though it fills the chassis 
 and doesn't allow for expansion, so the full-size TA5000 may be 
 desirable).  I've played (and am playing with) the same system but with 
 GPON termination and have been happy with it so far.
 -- 
 Brandon Martin

Re: IP Dslams

2019-01-04 Thread Blake Hudson
I was thinking the same thing. They're a few years out of support, but 
the Zhone 42xx IP DSLAM provides a 1Gbps ethernet uplink and 24 ADSL2+ 
DSL user ports per 1U chassis (stackable to achieve 192 ports total). 
Wish they were available in AC for non-telco use.

http://support.zhone.com/support/manuals/docs/42/4200-A2-GN21-40.pdf

You could pair these with a pfSense appliance (or an x86 PC running the 
free software) to provide DHCP, DNS, etc - or use the built in pfSense 
captive portal to provide additional authentication and accounting per 
user. pfSense can provide NAT and FW if needed, or these features can be 
disabled to use globally routable IP4/IP6 addresses.


As far as support goes, backup your pfsense and DLSAM configs when you 
finish the project and the subscriber accounts and DSL modems could be 
maintained by a local admin through the pfSense web interface with no 
need to touch the DSLAMs or anything CLI.


--Blake

Shawn L via NANOG wrote on 1/4/2019 8:59 AM:


Might want to look for old Zhone ip bitstorm dslams.  There should be 
a bunch on the used market.  They do all of the ATM conversions 
internally so you just need to feed them with ethernet.



-Original Message-
From: "Nick Edwards" 
Sent: Friday, January 4, 2019 9:36am
To: "Brandon Martin" 
Cc: "NANOG" 
Subject: Re: IP Dslams

They don't have a large budget and although I'm yet to get prices on 
adtran's (understandable, holidays 'n all) I doubt it will fit within 
their budget, it's looking more like getting a few planet dslams and 
configuring a linux box as the bng, been 10 years since I've had to do 
that kind of setup, memories hazy, but I know it worked, and well, so 
thanks to all for suggestions but the adtrans and nokias are not for 
those on shoe string budgets, which wouldnt even allow me to include 
an asr1k for the bng, and although it would allow for, I'd rather not 
grab an ebay 7200/7300 :)


On Wed, Jan 2, 2019 at 10:52 PM Brandon Martin 
mailto:lists.na...@monmotha.net>> wrote:


On 1/2/19 6:47 AM, Nick Edwards wrote:
> There are 260 villas, and no coax.

Is there a logical way to distribute the termination?  You might
be able
to get better performance (not that you perhaps care, in this
case) at
minimal additional cost if you can do building-local termination
of each
customer circuit and then backhaul on e.g. bonded VDSL2 or G.FAST
over
shorter distances (perhaps hopping building to building).

I'm assuming there's no data grade copper or fiber if there's no
coax.
Obviously if you've got those, distributed termination makes even
more
sense.

If you do want a centralized solution, an Adtran TA5006 (the small
chassis) with 6x 48 port VDSL2 combo modules (with or without
vectoring,
depending on your needs) would do the job (though it fills the
chassis
and doesn't allow for expansion, so the full-size TA5000 may be
desirable).  I've played (and am playing with) the same system but
with
GPON termination and have been happy with it so far.
-- 
Brandon Martin






(FIXED) Re: 192.208.19.0/24 hijack transiting 209, 286, 3320, 5511, 6461, 6762, 6830, 8220, 9002, 12956

2019-01-04 Thread Dominik Bay
Thanks for your efforts in filtering and liaising with CN!

This issue has been fixed by ~ 1430 UTC today.


0x28B95CE4E3F0918D.asc
Description: application/pgp-keys


Re: IP Dslams

2019-01-04 Thread Mikael Abrahamsson

On Sat, 29 Dec 2018, Nick Edwards wrote:


Howdy,
We have a requirement for an aged care facility to provide voice and data,
we have the voice worked out, but data, WiFi is out of the question, so are
looking for IP-Dslams, preferably a system that is all-in-one, or self
contained, as in contains its own BBRAS/LNS/PPP server/Radius, such as has
a property managment API, or even just a webpage manager where admin can


Are you sure you need all of that?

When I designed ADSL solutions ~15 years ago I built with Paradyne DSLAM 
with ethernet uplink, then we used rfc 1483 bridged over ATM, so no need 
for PPP, radius or anything. It was just IPoETHERNEToATM and all the 
regular IPoE mechanisms could be used (DHCP etc).


So we just bundled the DSLAM with an L3 switch and that was that. One vlan 
per customer which solved the customer isolation problem. Customer could 
run modem in either bridged mode or terminate the IPoETHoATM PVC on the RG 
itself.


--
Mikael Abrahamssonemail: swm...@swm.pp.se


Re: IP Dslams

2019-01-04 Thread Jeff Shultz
You might start hunting on the used market for Occam/Calix B6 equipment,
specifically the B6-252 ADSL2+ and POTS card and the 12 slot chassis.

You'll have to put in some supporting infrastructure, but they do work
well, and I know of at least two aftermarket repair places that will repair
them for a reasonable (for the telecom world) cost.

On Fri, Jan 4, 2019, 06:38 Nick Edwards  They don't have a large budget and although I'm yet to get prices on
> adtran's (understandable, holidays 'n all) I doubt it will fit within their
> budget, it's looking more like getting a few planet dslams and configuring
> a linux box as the bng, been 10 years since I've had to do that kind of
> setup, memories hazy, but I know it worked, and well, so thanks to all for
> suggestions but the adtrans and nokias are not for those on shoe string
> budgets, which wouldnt even allow me to include an asr1k for the bng, and
> although it would allow for, I'd rather not grab an ebay 7200/7300 :)
>
> On Wed, Jan 2, 2019 at 10:52 PM Brandon Martin 
> wrote:
>
>> On 1/2/19 6:47 AM, Nick Edwards wrote:
>> > There are 260 villas, and no coax.
>>
>> Is there a logical way to distribute the termination?  You might be able
>> to get better performance (not that you perhaps care, in this case) at
>> minimal additional cost if you can do building-local termination of each
>> customer circuit and then backhaul on e.g. bonded VDSL2 or G.FAST over
>> shorter distances (perhaps hopping building to building).
>>
>> I'm assuming there's no data grade copper or fiber if there's no coax.
>> Obviously if you've got those, distributed termination makes even more
>> sense.
>>
>> If you do want a centralized solution, an Adtran TA5006 (the small
>> chassis) with 6x 48 port VDSL2 combo modules (with or without vectoring,
>> depending on your needs) would do the job (though it fills the chassis
>> and doesn't allow for expansion, so the full-size TA5000 may be
>> desirable).  I've played (and am playing with) the same system but with
>> GPON termination and have been happy with it so far.
>> --
>> Brandon Martin
>>
>

-- 
Like us on Social Media for News, Promotions, and other information!!

   
      
      
      














_ This message 
contains confidential information and is intended only for the individual 
named. If you are not the named addressee you should not disseminate, 
distribute or copy this e-mail. Please notify the sender immediately by 
e-mail if you have received this e-mail by mistake and delete this e-mail 
from your system. E-mail transmission cannot be guaranteed to be secure or 
error-free as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses. The sender therefore does 
not accept liability for any errors or omissions in the contents of this 
message, which arise as a result of e-mail transmission. _



Re: IP Dslams

2019-01-04 Thread Shawn L via NANOG

Might want to look for old Zhone ip bitstorm dslams.  There should be a bunch 
on the used market.  They do all of the ATM conversions internally so you just 
need to feed them with ethernet.
 

-Original Message-
From: "Nick Edwards" 
Sent: Friday, January 4, 2019 9:36am
To: "Brandon Martin" 
Cc: "NANOG" 
Subject: Re: IP Dslams




They don't have a large budget and although I'm yet to get prices on adtran's 
(understandable, holidays 'n all) I doubt it will fit within their budget, it's 
looking more like getting a few planet dslams and configuring a linux box as 
the bng, been 10 years since I've had to do that kind of setup, memories hazy, 
but I know it worked, and well, so thanks to all for suggestions but the 
adtrans and nokias are not for those on shoe string budgets, which wouldnt even 
allow me to include an asr1k for the bng, and although it would allow for, I'd 
rather not grab an ebay 7200/7300 :)


On Wed, Jan 2, 2019 at 10:52 PM Brandon Martin <[ lists.na...@monmotha.net ]( 
mailto:lists.na...@monmotha.net )> wrote:On 1/2/19 6:47 AM, Nick Edwards wrote:
 > There are 260 villas, and no coax.

 Is there a logical way to distribute the termination?  You might be able 
 to get better performance (not that you perhaps care, in this case) at 
 minimal additional cost if you can do building-local termination of each 
 customer circuit and then backhaul on e.g. bonded VDSL2 or G.FAST over 
 shorter distances (perhaps hopping building to building).

 I'm assuming there's no data grade copper or fiber if there's no coax. 
 Obviously if you've got those, distributed termination makes even more 
 sense.

 If you do want a centralized solution, an Adtran TA5006 (the small 
 chassis) with 6x 48 port VDSL2 combo modules (with or without vectoring, 
 depending on your needs) would do the job (though it fills the chassis 
 and doesn't allow for expansion, so the full-size TA5000 may be 
 desirable).  I've played (and am playing with) the same system but with 
 GPON termination and have been happy with it so far.
 -- 
 Brandon Martin

Re: IP Dslams

2019-01-04 Thread Nick Edwards
They don't have a large budget and although I'm yet to get prices on
adtran's (understandable, holidays 'n all) I doubt it will fit within their
budget, it's looking more like getting a few planet dslams and configuring
a linux box as the bng, been 10 years since I've had to do that kind of
setup, memories hazy, but I know it worked, and well, so thanks to all for
suggestions but the adtrans and nokias are not for those on shoe string
budgets, which wouldnt even allow me to include an asr1k for the bng, and
although it would allow for, I'd rather not grab an ebay 7200/7300 :)

On Wed, Jan 2, 2019 at 10:52 PM Brandon Martin 
wrote:

> On 1/2/19 6:47 AM, Nick Edwards wrote:
> > There are 260 villas, and no coax.
>
> Is there a logical way to distribute the termination?  You might be able
> to get better performance (not that you perhaps care, in this case) at
> minimal additional cost if you can do building-local termination of each
> customer circuit and then backhaul on e.g. bonded VDSL2 or G.FAST over
> shorter distances (perhaps hopping building to building).
>
> I'm assuming there's no data grade copper or fiber if there's no coax.
> Obviously if you've got those, distributed termination makes even more
> sense.
>
> If you do want a centralized solution, an Adtran TA5006 (the small
> chassis) with 6x 48 port VDSL2 combo modules (with or without vectoring,
> depending on your needs) would do the job (though it fills the chassis
> and doesn't allow for expansion, so the full-size TA5000 may be
> desirable).  I've played (and am playing with) the same system but with
> GPON termination and have been happy with it so far.
> --
> Brandon Martin
>


Re: 192.208.19.0/24 hijack transiting 209, 286, 3320, 5511, 6461, 6762, 6830, 8220, 9002, 12956

2019-01-04 Thread Job Snijders
Dear all,

NTT / AS 2914 deployed explicit filters to block this BGP announcement from
AS 4134. I recommend other operators to do the same.

I’d also like to recommend AS 32982 to remove the AS_PATH prepend on the
/24 announcement so the counter measure is more effective.

Kind regards,

Job

On Fri, Jan 4, 2019 at 1:02 Dominik Bay  wrote:

>  I see the follwowing ASN transiting a leak concerning 192.208.19.0/24
> originated by 4812
>
> 209
> 286
> 3320
> 5400
> 5511
> 6327
> 6461
> 6762
> 6830
> 8218
> 8220
> 8447
> 8551
> 9002
> 12956
>
> The proper source is 32982 (Department of Energy).
> More details to be found here: https://bgpstream.com/event/171779
> And here: http://lg.ring.nlnog.net/prefix_detail/lg01/ipv4?q=192.208.19.0
>
> Cheers,
> Dominik
>
>
>