QUOTE(kwss @ May 13 2025, 02:16 PM)
There is another problem after they allow MTU 1500.
In IPv6, the BNG will send ICMPv6 Packet Too Big even if the MRU is 1500 and big enough to receive it.
Using IPv4 doesn't face this problem. My guess is they put in this broken workaround because some of their supplied router eats ICMPv6 packet in the name of firewalling.
There are other minor issue with their BNG the last time I test them, such as the weird reuse of magic number.
I also don't quite understand why their L2MTU cannot be increased, considering TM claim's all their MPLS circuit runs 9k MTU worldwide in their marketing material.
Maybe their marketing team lied.
I not sure about my friend on MTU 1500, his IPv6 seem working and no issue either way
If they run L2MTU 9000 bytes, then VRRP and VXLAN overhead not an issue.
I think their their marketing team lied. As this proof MTU stuck at 1488 weird number cause server NGFW rise a suspicion
QUOTE(hsbb @ May 13 2025, 02:20 PM)
The upstream speed not as suscribed although config correctly by GEM/OMCC. For this case need to manually config in the OLT itself. Below is the flow how GPON upstream normally work.
ONU Activation:
When an ONU is activated on a GPON network, the OLT sends PLOAM messages to the ONU to establish communication and discover the available T-CONTs.
Bandwidth Allocation:
Using PLOAM messages, the OLT assigns specific Alloc-IDs to different T-CONTs within the ONU, thereby defining which T-CONT will be used to carry specific user traffic.
Traffic Management:
Once the Alloc-IDs are assigned, the ONU sends upstream traffic based on the allocated bandwidth for each T-CONT, ensuring efficient utilization of the shared fiber.
May I know what T-CONT Entity Id that TM use across vendor? have one TM own standard or varies depend on OLT?
Like in Salak Tinggi, TM downgrading Alcatel OLT to Fiberhome OLT to avoid Nokia Cloud OMCI fee, and cause upload speed issue with FHTT OLT
As I don't have access to OLT, I just guessing across chipset, Huawei HiSilicon, Nokia MediaTek and D-Link/Nijika Realtek,
both use ME 278 0xff00 - 0xff0f (16 T-CONT), some are less, but T-CONT are there waiting to
so, ME 277, 8 queue per T-CONT: 0x8000 - 0x807f
but for D-Link based on Realtek, got extra T-CONT not in use
This post has been edited by Anime4000: May 13 2025, 03:50 PM