Telecom offers only the best efforts channel over PPPoE (PPPoA to
customer, PPPoE to provider over jumbo frame).
To get RT qos, you need IPoE with correct 802.1p marking.
Craig Spiers | Network Manager
Solarix Networks Limited
DDI: +64 9 974 4753 | Mob: +64 21 857 183 | Office: +64 9 974 4750 | FAX: +64 9 974 4760
Email: craig.spiers(a)solarix.co.nz | Web: www.solarix.net.nz
CAUTION: This email is confidential. If it is not intended for you please do not read,
distribute or copy it or any attachments. Please notify the sender by return email and
delete the original message and any attachments.Any views expressed in this email may be
those of the individual sender and may not necessarily reflect the views of Solarix
Please consider the environment before printing this email!
Disclaimer added by CodeTwo Exchange Rules
[mailto:email@example.com] On Behalf Of Nathan Ward
Sent: Sunday, September 19, 2010 8:18 PM
To: NZNOG List
Subject: Re: [nznog] EUBA
On 18/09/2010, at 4:45 PM, Lincoln Reid wrote:
On 18/09/2010 9:40 a.m., Philip D'Ath wrote:
> I'm hoping someone can clarify my understanding of this Telecom
> Wholesale product.
> >From the Telecom wholesale web site I can see that each customer is
> delivered on a separate VLAN. What I'm not sure about is the
> encapsulation of the data being presented form the client.
> At the SP end, do they then need to provide a PPP layer (so
> effectively the VLAN replaces L2TP), or is it delivered ready for you
> to process like any "standard" VLAN
circuit (aka, just needs L3
There are two services provisioned on this product you can use.
On PVC 100 the customer can connect with regular old PPPoA, Telecom
operate a PPPoA
<-> PPPoE bridge which you get delivered at the service
provider end as a double tagged ethernet vlan.
On PVC 110 the customer can connect with rfc2684 style ethernet
deliver ethernet frames over the link. You have to deliver
each frame at the customer end single tagged with vlan 10, this is so
you can set the 802.1p priority bits to make use of the voice traffic
queue they configure. This service is also delivered at the service
provider end as a double tagged service on a different vlan.
We have pretty good success just using these tails with one IP out of
a /30 IP
whacked on each end, but there seems to be a built in
assumption by most of the people we deal with in Telecom that you are
going to stick some sort of PPPoE or something on it anyway.
PPPoE doesn't make sense, unless you run two sessions and put different
802.1p bits on them, or you have some kind of router that can
encapsulate PPPoE frames and mark the underlying ethernet frames based
on the contents of PPP.
DHCP makes much more sense.
NZNOG mailing list