@Noah_Helterbrand you should be able to login with your Peplink ID on https://ticket.peplink.com if you are a partner. There you can create tickets directly, which will reach Peplink Support directly.
Not sure if it might be different in other regions, but for EU it works great for us.
Works at Brazil, without issues…
Yes, I can login and create tickets without issue, and I do periodically for fusionhub/IC2 issue. However in this case because it is a hardware device, peplink’s policy seems to be that I can only go through our distributor for support, even as a partner.
Trust me I’ve tried. I found out about it because I opened a ticket and just got “sorry, you must go through your distributor for support.”
If that policy has changed recently, then I haven’t received any notices about it.
Do allow me to explain the support policy.
For any issues related to product/firmware/hardware, we are always welcome to work direct with our valuable customer/partner. This is to make sure we have the faster response time to identify and resolve the reported issues.
I have created a ticket for the above and let us work from there. This will allow us more easy to look at the reported issues.
Ticket : PTS#25020446
Thank You
Is the Incontrol based IGMP snooping profiles supposed to work on these new switches or only on the older SD-series?
The IC2 IGMP option is not supported the new switches for now. We will improve the IC2 WebUI to remark about this.
Thank you for raise this up 
Will IGMP be supported in the new switches? Crestron NVX is breaking the network without IGMP.
Yeah, we’re using AVPro Edge MXNet and, like other MoIP solutions, requires IGMP snooping, so we’re continuing to use Netgear for now.
Yes , IGMP snooping are in the feature roadmap for the PoE 2.5G Switch. When we have confirmed the feature timeline, I will update again
Added a remark for the IGMP option to avoid the confusion
We are hitting the same roadblock, i would want to prevent us to revert to a different brand. How soon do you think a update will be shared about a timeline.
I know you most prob wont have a answer to this, however i want to prevent a redesign in our case as much as possible.
Can you create a ticket ? We can definitely help to review and see what we can help here 
Thank you for Your swift reply Just created the ticket
Number: 25020665
Does this mean I have to move all my VLANs over to InControl?
Can’t tag the ports otherwise.
I moved VLANs to incontrol and started tagging ports, then lost connection to the switch.
Edit:
Ok, after tagging ports, it removes the default VLAN ID 1, which the switch needs. I added the default VLAN 1.
Note cannot use 192.168.1.1, it conflicts with Starlink. I made defualt VLAN 1 192.168.50.1… odd but it works.
Had to manually move all VLANs over to incontrol, including reservations. Not sure if this was the correct way to do it.
When will switch controller / 8.5.2 be released?
Sorry for the total newbie post… just fumbling my way though it. This was way easier on the old rugged switches.
I don’t understand what you mean. Are you saying that I can now (as a partner) bypass our distributor and work directly with peplink on hardware and firmware issues?
I appreciate the ticket opened. These switches are carrying critical connections and we are restricted from making config changes or performing testing outside of specific windows and without the vendor on the phone with us while configuration/testing is being performed. Before I proceed with your ticket, will you be able to provide contact information so that we can schedule a time with the client to be able to work on the issues in real time to meet their requirements?
