-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explanation of OMCI_VEIP_SLOT_ID flash option is incomplete #107
Comments
OMCI_VEIP_SLOT_ID DOES control the veip entityID ! but the description is woefully incomplete. before:
after:
|
great finding! |
omci log opened in wireshark and look for veip |
Hi @rajkosto, your finding could be related with "ODI firmware ignore mib 171 VLAN remap"? |
You are able to use treated VLAN in IGD firmware ? Which one ? |
Not an expert like you but my problem seems to be similar, if you want to check more https://github.com/Anime4000/RTL960x/issues/90 |
My problem is that treatment is not working with any firmware, IGD or SFU |
Never tried to get PPPoE to the ODI SFP, always to the router but confident that will work |
the IGD firmware changes DEVICE_TYPE to 0 (bridge) if you have no wan connections defined in it, otherwise DEVICE_TYPE is 1 (router)... you cant be sure it works on the device if it only works with no WAN connections defined |
couple of tests with SFU firmware;
|
try the one i suggested and seen in both Nokia and Huawei ONU, OMCI_VEIP_SLOT_ID = 14 |
OMCI_WAN_QOS_QUEUE_NUM what it means? |
No changes here |
https://github.com/Anime4000/RTL960x/blob/main/Docs/FLASH_GETSET_INFO.md#omci_veip_slot_id here it implies that it controls the VEIP entityId, and that you should set it to 0x0E01 if that's the entityId of your original ONU, but when this value is read it is read as an uint8 so it can only be 0-255, and it also does NOT control the VEIP entityId, which is always 0x0601 (instead it controls a custom option inside the veip MIB data, which we have no idea what it does, as its not part of standard VEIP mib)
The text was updated successfully, but these errors were encountered: