Thanks TK. Why is this new algorithm not on the BR1/Mk2? It might be helpful.
We have the same concerns.
For Netflix and the like, we have segmented streaming devices/TVs and do not let them use Speedfusion at all. All other devices go via Speedfusion using an outbound rule. Of course this means you cannot use netflix or other streaming services on other devices such as computers/ipads and it will only work via those designated streaming devices/TVs which is annoying.
1 Like
I notice on the Balance 20X that the band and signal strength information for the secondary LTE bands is not showing up on the status display.
BTW - on the MAX Transit, I have noticed that the bug where sometimes the secondary band would not be labeled correctly seems to now be fixed. Yay!
- Chris
1 Like
Another bug with the Balance 20X - the SSID and signal strength readout on the Status page “Client List” are blank when using the integrated AP:
Another issue - using the SpeedFusion Cloud “Link Wi-Fi to Cloud” feature, the generated SSID is not coming up as a mirror of the default SSID. I am only able to connect to the Bonded SSID with 2.4GHz 802.11n instead of 5GHz 802.11ac.
Also - when connected to the SpeedFusion Cloud SSID I see no evidence in the Status / SpeedFusion dashboard that the traffic to that SSID is actually being routed over the bonded connection.
Chris
Hi Chris. I can’t speak to the last two of the issues you raised but I can say that Peplink has ack’d the first one in my ticket #20070362, found it to be a bug in the UI and indicated it will be fixed in RC3. - Rick
1 Like
Yes, secondary LTE band is not showing up indeed. I can only see that information in InControl 2.
1 Like
This warning disappeared to me after installing RC2.
@Lai - I asked the following in the RC1 thread and never received an answer:
Any status on fixing the broken AP firmware pack upload/storage issue in the Balance series, as documented in ticket number 20050126? That ticket thread ends without resolution, with the statement:
That’s a known issue regarding pack storage. Possibly will be fixed in 8.1.1 GA.
Thanks.
@scuba_steve, yes, as the support personnel feedback, Engineering Team is targeted to fix the reported issue in 8.1.1 GA. Please bear with us.
2 Likes
I’m not able to get T-Mobile to work on either a Peplink MAX Transit CAT18 or an HD1 Dome. I’ve validated it works on pre-8.1.0-RC2 Peplink devices (Peplink MAX Transit CAT12) and other non-Peplink devices.
I’ve tried setting the APN but that doesn’t seem to do anything. I see it try 3G, then sometimes LTE, maybe “Obtaining IP Address” and then resetting, and back through the process again.
Has anyone got T-Mobile (US) working with this RC?
Created ticket 20070618
We only have about three instances of RC2 in use but one is in a Balance 305 with a USB dongle and TMO M2M SIM. Working fine.
1 Like
Out of curiosity, is anyone seeing 3G versus LTE in 8.1.0 ? I never really saw 3g ever before and now I see it frequently. It could be coincidental in that I am paying closer attention since testing 8.1.0 and the tower is having an issue all of the sudden. Just wanted to see if anyone else is experiencing. AT&T in USA on MK2 LTE-A.
Hello Peplink Team,
We have had a Pepwave MAX HD2 Dome go offline during an upgrade to FW 8.1.0 build 4929 from FW 8.0.0s061 build 4233. Upgrade was initiated through InControl2. Is there any prerequisite that would cause this?
Happy to Help,
Marcus 
Hello Peplink Team,
The router has come good by itself overnight, it took about seven (7) hours for the Modems SIMs to establish a connection, these have SIMs that are roaming from Europe.
Diagnostic logs are available for analysis, please PM us for them.
Happy to Help,
Marcus
The ticket was assigned to a reseller to help me with SIM settings. Since this works in non 8.1.0 RC I don’t think a reseller is going to be able to fix this…
@mldowling, we can’t conclude the problem based on the provided screenshots. Please open ticket for us to review the Diagnostic Report.
@stevemitchell, can you share the ticket number?
Thanks.
1 Like
Ticket was further up in the thread - here it is again - 20070618
Thanks!