PPPoE frames are just ethernet frames, and powerline adapters are just ethernet bridges, so it will work.

Using "baby jumbo frames" to your ONT (MTU 1508, so that you get an IP MTU of 1500) may or may not work.

But as others have said, powerline adapters are not really suitable at FTTP speeds. While they may have a "raw" bit rate of say 500Mbps, this is unidirectional, subject to contention, collisions, and noise. Real-world throughput is unlikely to be more than about a third of the headline figure.

For the best reliability, run a CAT5e cable from your ONT to your router.

Thank you so much to everyone who has kindly replied with information and advice.

When fibre gets activated I will try the powerline thing and see if it works. Most likely I will just do the standard set up as recommended by most here:

ONT --> Cat5 --> Modem/Router --> Powerline to some PCs / Wifi for laptops.

ADSLGuide forums are such a great resource! And it's super nice that they use the same efficient software as way back when haha.

Edited by deleted (Mon 12-Jul-21 15:03:24)

In reply to a post by j0hn83:

In reply to a post by Pheasant:

In reply to a post by LucBorg:

I mean:

ONT--> Cat5 powerline ethernet plug --> household copper circuits --> Cat5 powerline ethernet plug --> Fibre Router.

Not sure that setup would work - at least not with the power line adapters I have seen. You would get a physical link connection OK, but I’m not sure that PPPoE would work between the WAN port of the router and the ONT with the power line link.

Not tried it on FTTP but it works perfectly between an FTTC modem and a router doing PPPoE.

It's just Ethernet between 2 points. Not sure why it wouldn't work on FTTP.
I'll test it later today.

In reply to a post by candlerb:

PPPoE frames are just ethernet frames, and powerline adapters are just ethernet bridges, so it will work.

Using "baby jumbo frames" to your ONT (MTU 1508, so that you get an IP MTU of 1500) may or may not work.

But as others have said, powerline adapters are not really suitable at FTTP speeds. While they may have a "raw" bit rate of say 500Mbps, this is unidirectional, subject to contention, collisions, and noise. Real-world throughput is unlikely to be more than about a third of the headline figure.

For the best reliability, run a CAT5e cable from your ONT to your router.

How do you go about addressing them and setting them up on the WAN side of the connection? What if someone plugs in another or more power lines adapter(s)- does that throw a spanner in the works?

I’ve used Devolo dLan (now defunct) and the newer Magic series, but always on the LAN side, so fits in with DHCP and can be administered like any other network device on the LAN.

In reply to a post by Pheasant:

How do you go about addressing them and setting them up on the WAN side of the connection? What if someone plugs in another or more power lines adapter(s)- does that throw a spanner in the works?

It would be the same as plugging your WAN and LAN ports into the same switch. In other words, not a good idea

I haven't used Powerline adapters for a while, but they do need to be paired, and have an encryption key. So in theory you could pair up a couple for use for the WAN link, and then have some more which are independently paired for a LAN connection. It would be like neighbours on the same mains phase, who should be able to work independently.

In reply to a post by Pheasant:

I’ve used Devolo dLan (now defunct) and the newer Magic series, but always on the LAN side, so fits in with DHCP and can be administered like any other network device on the LAN.

I'm pretty sure that the ones I used in the past were managed entirely at layer 2. That is, rather than pick up an IP address via DHCP, you had to use a special management application on the ethernet port which sent non-IP ethernet management frames.

I also have a vague idea I used a Linux implementation of the management application. Could have been one of these:
https://ma.juii.net/blog/powerline-under-linux
https://github.com/serock/pla-util
https://fitzcarraldoblog.wordpress.com/2021/04/23/us...

In reply to a post by candlerb:

I'm pretty sure that the ones I used in the past were managed entirely at layer 2. That is, rather than pick up an IP address via DHCP, you had to use a special management application on the ethernet port which sent non-IP ethernet management frames.

The current bunch from Devolo which I'm familiar with use Layer 3 for management. You can use their discovery protocol program "cockpit" et al to navigate them, but the actual adapter configuration is initiated onto a webpage from the adapter. Stuff like firmware updates etc require internet connectivity.

You're probably right that they would work on the WAN side if its just a straight bridged "pipe", not that I've ever tried, as always have them set up on the LAN side, as I believe they are mostly intended to be used.

With FTTP, you'd probably want to get a set with a GigE port. Maybe the old types with an ordinary Fast Ethernet port would still be OK on FTTC or on something FTTP with a relatively 'slow' profile but a 500M or 900M connection would be pointless. Latency and jitter especially were quite terrible too. Wouldn't be something I'd recommend for FTTP if it could be helped. You simply negate all the good stuff.