Outline ·
[ Standard ] ·
Linear+
Home Networking Why our Fiber Internet still using PPPoE, not IPoE, Reasons stick with old protocol PPPoE
|
TSAnime4000
|
Mar 24 2020, 01:38 PM, updated 6y ago
|
|
Many overseas fiber isp using IPoE because no overhead like PPPoE. Why in fiber internet in Malaysia still using PPPoE?
Limitation of PPPoE: 1. Overhead, small MTU size 2. Single Threaded, no acceleration, make router CPU work hard 3. Since single thread, induce additional latency when in high speed 4. Prone to disconnect in high speed active sessions 5. Cannot use packet inspection/protection, PPPoE force to run as software, not hardware.
|
|
|
|
|
|
TSAnime4000
|
Mar 24 2020, 02:53 PM
|
|
QUOTE(cba5566 @ Mar 24 2020, 02:15 PM) IPoE not support multiple users as compare to PPPoE. Multi ISP, can use VLAN IPoE, but why same ISP for multiple sessions? limited to single VLAN and GPON speed QUOTE(Alpha_Tay @ Mar 24 2020, 02:47 PM) Yes, identify user at ONU side (DHCP Identity) and user simply change router and set WAN as DHCP, is more like Plug n Play, no need to remember Username and Password More important, no unconditional disconnect like PPPoE did, horrible while playing games
|
|
|
|
|
|
TSAnime4000
|
Mar 24 2020, 04:46 PM
|
|
QUOTE(rizvanrp @ Mar 24 2020, 03:19 PM) Agree on all the downsides you stated but ISPs here use PPPoE because it was the most compatible accounting method that would directly integrate into their existing billing and customer record management systems. In the case of Unifi, TM is paying the price for this decision in the form of constant capacity and hardware upgrades to the PPPoE access concentrator/BRAS as each of these devices need to handle 60-80k concurrent PPPoE sessions per zone on average. The other reason is security. Security policies such as unicast reverse-path forwarding to prevent IP spoofing is easier to implement when all your customer traffic is isolated within a PPPoE session. IPOE requires all your devices on the access network to be DHCP aware and to filter incoming traffic based on the DHCP lease that was issued to the client device. Your DHCP relays also need to assign IP addresses on a per-subscriber circuit ID basis (see DHCP Option 82) rather than by MAC address to prevent lease exhaustion attacks (remember, if you're not doing CGNAT you're issuing public IPv4 addresses here). It's also more difficult to achieve all of this when you go with a multi-vendor (Huawei/Alcatel/Fiberhome) and multi-access technology (GPON/VDSL2) deployment.  Understood, plus ISP driven from DSL which is they can use same machine. Year 2020, PPPoE not develop to Hardware Accelerated, beside NAT Hardware Accelerated.
|
|
|
|
|
|
TSAnime4000
|
Jun 24 2020, 01:27 PM
|
|
I was configuring company lease internet, 10Gbps with PPPoE.
it seem PPPoE unable to achieve 10G speed, only one core CPU maxout 100% usage by "pppd" process.
it seem PPPoE bottleneck for fast internet
|
|
|
|
|
|
TSAnime4000
|
Jun 24 2020, 05:47 PM
|
|
QUOTE(Candy12 @ Jun 24 2020, 04:22 PM) No managed IP direct MetroEthernet solution? Maxis 10G backhaul to where? I don't know, I just got this job as company want me to achieve 9 or 10G and find a solution » Click to show Spoiler - click again to hide... « No wonder many previous technician quit, this is huge mess to fix speed issue, I feel want to quit also.
|
|
|
|
|