NR7101 Firmwares
supajo
Posts: 1
Hallo :-) where can i download acutal firmware files?
In particular i am searching for
„V1.00(ABUV.6)b2_E0“
„RG502QEAAAR11A07M4G“
Others get these updates over the air.
The support page / download library is just unsatisfying
In particular i am searching for
„V1.00(ABUV.6)b2_E0“
„RG502QEAAAR11A07M4G“
Others get these updates over the air.
The support page / download library is just unsatisfying
0
All Replies
-
yep, im trying to find the ABUV.6 firmware, seems it is still in beta.
R11A07 instead is already available. there is also a DFOTA for it. try ask customer service, they should be able to provide it.0 -
supajo said:Hallo :-) where can i download acutal firmware files?
In particular i am searching for
„V1.00(ABUV.6)b2_E0“
„RG502QEAAAR11A07M4G“
Others get these updates over the air.
The support page / download library is just unsatisfying
ABUV.6 is still in beta, and i can give you the link. I have been using it for a few time now, and everything is ok.
But be warned there are a few things that can happen, i had mine ending up in a loop, when i use DSS + double cell lock, so be carefull.
100ABUV6b1_0221
https://drive.google.com/file/d/19il1MN_64QTsvv-28iTv3j8sBloe9Guq/view?usp=sharing
RG502QEAAAR11A06M4G-RG502QEAAAR11A07M4G.zip
https://drive.google.com/file/d/1wpOqRDv2ZS0nTw7VgrYmXqdc-Ba1FMwu/view?usp=sharing
0 -
Any changelog available for the latest firmware and modem ?0
-
No change log that I know @Lmic
The following thread might also be helpful, https://community.zyxel.com/en/discussion/13206/connection-troubles-with-nr7101-after-every-24-48-hours#latest
Kind regards,
Tony0 -
Lmic said:Any changelog available for the latest firmware and modem ?
As you can see, R13 line, is the new qualcomm binary, and it adds 5G CA.
Unfortunately, there is no Dfota for that, not sure if there will ever be.
And customer service refuse me to give me instructions on how to update the module with Qfirehose whit their firmware, so the only way to go to R13 atm, is to switch to ROOter, upload R13, then get back to zyxel firmware.
But its not something for the faint of heart let's say.
Also V6 sort of support it, i expect for the stable V6 to have full R13 support.1 -
Hello @n_o
Here is an article that might also help, see https://support.zyxel.eu/hc/en-us/articles/4407744420370-NR7101-5G-Signal-Best-way-to-achieve-it-and-explanation-of-Cellular-Band
This article might also help you in Germany, see https://support.zyxel.eu/hc/en-us/articles/360021563900-NR7101-Connectivity-issues-and-firmware-fix-for-unsupported-frequency-bands-5G-NSA-B8-N1-
Kind regards,
Tony0 -
Saw this on a forum.....
If anyone of you also uses Telekom D1 (APN internet.t-d1.de) with a public IPv4 address that allows accepting incoming connections, I can advise you to daily reboot the device (to force obtaining a new modem dial and fresh IPv4 address).
I noticed that roughly after 24...48 hours of uptime Telekom blocked incoming connections partially, mainly originating from Telekom mobile data clients like my phone.
It's kind of obscure, because connections originating from Telekom or O2 DSL I've tested still could connect to my server running on T-D1.
I read somewhere on telekom-hilft.de in a forum thread, that this is intended behaviour of Telekom to keep business users away from running permanent servers with a static IP address while on mobile data APN internet.t-d1.de.
The workaround is: Put a daily reboot of your Quectel NR 7101 in place and since I did that, my incoming connections worked - regardless where they originated from.
0 -
SELBERG said:Saw this on a forum.....
If anyone of you also uses Telekom D1 (APN internet.t-d1.de) with a public IPv4 address that allows accepting incoming connections, I can advise you to daily reboot the device (to force obtaining a new modem dial and fresh IPv4 address).
I noticed that roughly after 24...48 hours of uptime Telekom blocked incoming connections partially, mainly originating from Telekom mobile data clients like my phone.
It's kind of obscure, because connections originating from Telekom or O2 DSL I've tested still could connect to my server running on T-D1.
I read somewhere on telekom-hilft.de in a forum thread, that this is intended behaviour of Telekom to keep business users away from running permanent servers with a static IP address while on mobile data APN internet.t-d1.de.
The workaround is: Put a daily reboot of your Quectel NR 7101 in place and since I did that, my incoming connections worked - regardless where they originated from.
if this only effects incomming connections from other telekom mobile devices , its not a problem for most use cases.
0 -
n_o said:SELBERG said:Saw this on a forum.....
If anyone of you also uses Telekom D1 (APN internet.t-d1.de) with a public IPv4 address that allows accepting incoming connections, I can advise you to daily reboot the device (to force obtaining a new modem dial and fresh IPv4 address).
I noticed that roughly after 24...48 hours of uptime Telekom blocked incoming connections partially, mainly originating from Telekom mobile data clients like my phone.
It's kind of obscure, because connections originating from Telekom or O2 DSL I've tested still could connect to my server running on T-D1.
I read somewhere on telekom-hilft.de in a forum thread, that this is intended behaviour of Telekom to keep business users away from running permanent servers with a static IP address while on mobile data APN internet.t-d1.de.
The workaround is: Put a daily reboot of your Quectel NR 7101 in place and since I did that, my incoming connections worked - regardless where they originated from.
if this only effects incomming connections from other telekom mobile devices , its not a problem for most use cases.i did a test with DTAG on a business contract and it seems they also throttle the upload speed somewhere after around 20 gigabyte in 24 hours to only 10mbit/s. download stays fine. so unless you reboot to get a new wan ip. the link will stay throttled.could Zyxel not implement a daily reboot in the schedule?i know it is possible to select a specific date and reboot it for example every sunday.but in case of above. we would require a daily reboot to prevent such undocumented business practices.1
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 144 Nebula Ideas
- 94 Nebula Status and Incidents
- 5.6K Security
- 238 USG FLEX H Series
- 267 Security Ideas
- 1.4K Switch
- 71 Switch Ideas
- 1.1K Wireless
- 40 Wireless Ideas
- 6.3K Consumer Product
- 247 Service & License
- 384 News and Release
- 83 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.2K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 83 About Community
- 71 Security Highlight