Orbi Voice RBS40V Firmware V2.5.1.2 has typo in "Public_UPNP_gatedesc.xml" file... Help!

[Route66Scott]

After setting up my Orbi system I discovered that the RBS40V satellite is causing my computers and media server to throw up constant errors. 

My Plex server has been repeating this set of errors every 14 seconds:

XML: Entity: line 2:
XML: parser
XML: error :
XML: attributes construct error
XML: <root xmlns="urn:schemas-upnp-org:device-1-0"<%pnpx_root_desc();%>>
XML: ^
Error parsing content.
Error parsing XML: Error parsing file.
SSDP: Error parsing device schema for http://192.168.2.3:80/Public_UPNP_gatedesc.xml

I examined the Public_UPNP_gatedesc.xml file in my browser, and determined that there is a typo in line 2:

<root xmlns="urn:schemas-upnp-org:device-1-0"<%pnpx_root_desc();%>>

Yep, it's that extra >.

I submitted the bug to Netgear support, but never received a reply. As Netgear doesn't appear terribly proactive on their support or their firmware updates, I looked into dealing with this myself. I assumed I could telnet into the RBS40V, as one can into the RBR50 router, but there does not appear to be any way to enable this on the RBS40V. (I've googled it to death.)

So...

1. Is there any reasonable way to reach someone at Netgear who can make this depressingly simple change to their firmware, and issue an update?

2. Does anyone have a way to telent into the RBS40V satellite? 

(And yes, it's too late for me to simply return this mesh system and replace it with something else...)

>

[cgullett]

I don’t have your model, but I do have a RBW30 with exactly the same problem involving Plex. On the RBW30, RBS50 and RBR50 you change the page on your URL to /debug.htm and there is a checkbox To enable telnet. On the RBW30 the setting is persistent, on my 50s it does not survive a reboot.

[Route66Scott]

The RBS40V does have a debug.htm page, but it has different settings and switches than the routers. It doesn't have a checkbox to enable telnet.

I've spent far too much time researching this with no luck. It's disappointing that this is all because of a single character typo. 

[Blanca_O]

Hi @Route66Scott

Let me check on this. I will get back to you for any updates.

Regards, 
Blanca 
Community Team

[Route66Scott]

Thank you, Blanca.

[Blanca_O]

Hi @Route66Scott

This has been forwarded already to engineers. They requested to capture logs. Please check you inbox for additional information. 

Regards,
Blanca
Community Team

[patimages]

Same issue on RBS850-RBR850

[leoaraucosta]

Hi,

Any news about enable telnet? I have Orbi Voice RBS40V Firmware V2.5.1.2 and doesn't have a checkbox to enable telnet.

Thanks!!

[Mstrbig]

My RBS40V has an Alexa MRM Debug Mode checkbox at the bottom.

[CrimpOn]

---

@Mstrbig wrote:

My RBS40V has an Alexa MRM Debug Mode checkbox at the bottom.

---

Was that in regard to telnet?  I checked the Alexa MRM Debug, but that does not enable telnet.

Wondering if one of the hacks that enabled telnet on the Nighthawk products would work on the RBS40V

[Route66Scott]

I would be able to fix this issue if there was telnet access. But that doesn't fix a bug that affects every one of these devices. 

I was contacted directly about this issue, and asked for logs. But after downloading the logs from both of my RBS40V units I was never given the info on where to send those logs. 

I assume that Netgear outsources their coding, as there's no reason for this to still be an issue through multiple firmware revisions, when it's been pointed out as an issue. 

[Mstrbig]

---

@Route66Scott wrote:

After setting up my Orbi system I discovered that the RBS40V satellite is causing my computers and media server to throw up constant errors. 

I examined the Public_UPNP_gatedesc.xml file in my browser, and determined that there is a typo in line 2:

<root xmlns="urn:schemas-upnp-org:device-1-0"<%pnpx_root_desc();%>>

Yep, it's that extra >.

---

That is not a typo as it is not a double >.

Look closely at <root xmlns="urn:schemas-upnp-org:device-1-0"<%pnpx_root_desc();%>>. In layman's  terms you will see the beginning routine's "<" then the sub-routine's "<". At the end, the first ">" is for the sub-routine and the second ">" is closing the routine..

For the record my PLEX server is running with no issues, and my setup includes an RBS40V.

IMHO the error is caused by something missing: 

Plex server parsing errors are usually caused by corrupted or missing dynamic-link library (DLL) files. Related errors mostly occur when a program mishandles the file during use. The most common problem happens within the Windows registry, where applications look up the location of DLL files they need. And because they are critical files, when a DLL file becomes unavailable, you will see a generated error. 

[Route66Scott]

I’m not running Windows.

Grab a copy of the Public_UPNP_gatedesc.xml file and have a look. Or drop it into your favorite code editor.

[Mstrbig]

---

@Route66Scott wrote:
I’m not running Windows.

Grab a copy of the Public_UPNP_gatedesc.xml file and have a look. Or drop it into your favorite code editor.

---

I did, and the line you state is wrong, is exactly the same as several Public_UPNP_gatedesc.xml files I looked at.

Again, I'm not seeing the issue with my RBS40v or any other Orbi device. You said you are not running Windows, as I am running the latest Pro with all the latest updates. I have also downloaded the ncessary libraries. So maybe the issue lies with your libraries not being up to date?

Don't know for sure as I don't need it, but this may help with the UPNP issues users are seeing.

Fix the UPnP issue in double NAT environment | Database & Cloud (dbcloudsvc.com)

[schumaku]

The problem here is that non-NAT-router satellite MUST NOT have a gateway description - which is most likely incomplete, thus causing the problems...  well known from some Netgear business wireless access points which can be operated in router mode, and the XML isn't adjusted accordingly, making Plex (and other software evaluating the UPnP SSDP stuff) cry.

[schumaku]

Correction... the <%pnpx_root_desc();%> junk part has to go ... looks like a variable (duplicated!) not properly set at build time:

<root xmlns="urn:schemas-upnp-org:device-1-0"<%pnpx_root_desc();%>>

Must be:

<root xmlns="urn:schemas-upnp-org:device-1-0">

[schumaku]

Can anybody grab the complete XML?

As this is a satellite, it must show up like this (example borrowed from a WAC505) - if they use the gateway template it will be wrong:

<root xmlns="urn:schemas-upnp-org:device-1-0">
<specVersion>
<major>1</major>
<minor>0</minor>
</specVersion>
<device>
<deviceType>urn:schemas-upnp-org:device:WLANAccessPointDevice:1</deviceType>
<friendlyName>WAC505-2</friendlyName>
<manufacturer>NETGEAR</manufacturer>
<manufacturerURL>http://www.netgear.com/</manufacturerURL>
<modelDescription>Access Point</modelDescription>
<modelName>AC WiFi Business Access Point WAC505</modelName>
<modelNumber>WAC505_V9.1.0.13</modelNumber>
<modelURL>https://www.netgear.com/business/products/wireless/business-wireless/WAC505.aspx</modelURL>
<serialNumber>XXXXXX</serialNumber>
<cloudStatus>1</cloudStatus>
<UDN>uuid:XXXXX</UDN>
<presentationURL>http://1.2.3.4/</presentationURL>
</device>
</root>

[raychen]

It should be router to handle UPnP instead of satellite. UPnP will be removed in new firmware.

[Mstrbig]

---

@raychen wrote:

It should be router to handle UPnP instead of satellite. UPnP will be removed in new firmware.

---

The router does handle UPnP instead of the satellite. I doubt UPnP will be removed from future router firmware. 

[schumaku]

---

@raychen wrote:

It should be router to handle UPnP instead of satellite.

---

Of course the router does the UPnP discovery and UPnP PMP (gateway) handling - as a InternetGatewayDevice profile.

In my opinion UPnP should be retained for the discovery - as a WLANAccessPointDevice profile - as it is on the wireless access points.

---

@raychen wrote:

UPnP will be removed in new firmware.

---

Ray, what is your role here?