T1 ?????

[barebottoms]

Yes it is possible to bond Multiple xDSL lines. Multilink PPP will do it. The Netopia edge routing ND (see Damaged I pay attention), supports this. You can even use the Netopia as an Edge bridge, and use the V.35 connect it to a Cisco. If you have a Cisco with multiple serial interfaces, and X number of Netopia's then you can even bond more channels.

I've boned about 10 FR connections in a lab once to do some testing.

G.Lite protocol specifies that you can go up 7.XX megs. Can't remember exactly, very weak in xDSL.

 

[Damaged]

Never said 'ya didn't barebottoms. Now if you can just tell me why I'm getting out of sequence OAM packets on an ATM interface on our new Juniper M20....

 

[barebottoms]

Sorry, didn't take Junipers offer. Too far of a commute for me.
Ask for Rob Kim

 

[ParadigmShift]

Well, it's school time boys. Comming from someone that HAS owned a DS1 loop(running HDSL btw) let me just rectify some stuff.

DSL flavors are better if you're not thinking of running some zero-downtime company. If you just want to host a domain, or setup a VPN link to work, or something of that matter go with consumer or commercial grade SDSL.

DSL is digital subcriber lines, high speed transmition over residual copper. Two transmition protocols I have seen so far are PPPoE and ATM, I believe ATM to be the superior protocol.

SDSL has a max speed of 1.544 Mbps up and downstream, and usually commercial grade providers will give you multiple IP CIDR blocks. We have a /20 on our SDSL.

ADSL has a max downstream of around 8Mbps with a max upstream of 1.544. As for bonding this gets tricky, you would need to be bound on bother upstream and downstream, then have something aggrigate it. This works with Multilink PPPoE probably the easiest, but I really don't know how well that would do without the upstream box routing correctly.

Bonding these sort of lines is tough, definatly not impossible, and really not the best solution.

If you do need a fully supported DS1 connection, which is time proven tech and very reliable, then here's some info: DS1 is the digital signalling standard, it is 24 multiplexed DS0 channels (these can either be 64k or 56k (8k used for signaling). Encapsulation/Transmition protocols include HDSL, HDLC. Let me inform you though, DS1 connections ARE pricy. Very pricy.

I paid $550 for a local loop and 950 bucks for service. Usually you can get loop price down to around 180 bucks depending on location. Most companies will rent you a router, but I find a problem with that. Most don't allow you to admin it, which is very problematic if you want to do anything special with it, like throddle trafic or change ACLs.

A good Cisco 26xx is going to cost you around 3000 bucks.

Oh and reguarding the OC-12 comment, my high traffic colocation site only has 6 bonded T3s and a OC-3, most of the Internets backbone are only OC-3s and OC-12s. No one man could ever afford one.

Oh and T3s == 45Mbps.

Adam

 

[Damaged]

Errr a /20 on an SDSL connection? What on earth would you need that much IP space on a DSL connection? Just curious.

 

[ParadigmShift]

Hah, did I say /20. Sorry my mind wasn't working, I typed that out pretty fast .

/26, oh to have a /20 hehe.

Adam

 

[Damaged]

LOL! Okay. That number is believable. I was like a /20!! I'm scratching my head wondering what on earth you might need 4094 host addresses for on an SDSL connection. I won't do the possible supernetting possibilities.

Paricularly since we just got issued an additional /18 from ARIN, when we requested a /16. I think we'll get the /16, they just want some better documentation of our current space usage and our future needs.

For those show don't know what the difference in IP space b/w a /18 and a /16 is, in host addresses it amounts to 49,152 host addresses more in a /16 than in a /18 (2^14 versus 2^16). Not small amount.