FTTC Ordered. Is using Linux's PPPoE ok?

[Rik]

Part of me says I only use 15gb/month, the other part says buy it now. I could then host races on my connection, using the faster upload speed. 

That's the trouble, isn't it, Glenn. We feel we could do more if we had it...

[Glenn]

I did host races on my ADSL, but my long line is not stable enough, the drivers were complaining of wild pings.

That's the trouble, isn't it, Glenn. We feel we could do more if we had it...

[Rik]

I did host races on my ADSL, but my long line is not stable enough, the drivers were complaining of wild pings.

Are you sure that wasn't wild pigs?

[Glenn]

It's just as well it was a driving game, the minimum pings were in the high 80's, peaking over 500 at times when someone forgot to turn of Outlook 

[Rik]

Oops.

[esh]

Using Linux pppoe was very easy.

I simply ran pppoe-setup followed by pppoe-start

Note: The ethernet port you use to connect to the VDSL modem does not end up with its own IP address! This had me confused for a while. 

Glad it's working. Also, yes... since PPPoE isn't an IP protocol you won't get an IP address with it Literally it is "point to point", hence addresses should be redundant info.

[Rik]

Being totally ignorant in this area, how do you then connect it to a network, esh?

[esh]

You have to route it, or bridge it (eth0->ppp0). The server has two (or more) network ports, one on TCP/IP to your LAN, and the PPPoE port to the DSL modem. This is fairly trivial to do in Linux. PPPoE, being ethernet packets, does contain the target MAC address in the packet header to ensure its destination. But obviously this cannot go past more than one hop (gateway) because MAC information is no longer kept beyond that (hence point to point). I believe PPPoE can support multiple clients connecting to a host, but in this case it would be nonsense as each one would try and take hold of the DSL connection and cause madness.

[Rik]

Thanks, esh.