Newbie here, Help Identify chipset


More at: https://drive.google.com/drive/folders/1H5PZAM9ke6i2OU2WGfo_XYf86ffLhlbt?usp=sharing
MAC: BCF87E80B7C2
It shows as Openwrt in WifiMan app.
Manufacturer is Arcadyan
This router is locked down by Reliance Jio India and is a part of 5g Home wifi solution called AirFibre. This is indoor unit. Outdoor unit is 5G esim enabled receiver works on PoE.

This router does not have option to disable wifi, have different names for 2.4 and 5. No option to change channel or channel width, cannot block devices. It's a Wifi 6 router.

Those pics are pretty useless with the shielding intact.

UART seems to be J1, you might get lucky if you connect to it.

4 Likes

intresting, i am from CS background, hardware hacking is something new for me.

CS, as in Counter Strike?

2 Likes

I would assume Computer Science. :wink:

1 Like

Post a close-up of the 'J1' region, ideally both sides.

I agree with Frollic, that looks like a (almost surely 3.3V) UART (serial port).

The close-ups will probably confirm:

Pin1 (Left-Most): VCC, usually not needed, use "normal" power supply to power device.
Pin2: TX-Pin, for information/data flowing OUT of the device, connect to RX on USB-3.3V-UART adapter.
Pin3: RX-Pin, for commands/data INTO the device, connect to TX on USB-UART. May need a drop a drop of solder on the jumper pad just below to complete path.
Pin4: Ground. If you look closely, it will be connected to the surrounded grounding plane on at least 3 sides. Check on your close-up pictures. Connect with GND on the USB-UART.

You may not need to solder anything: Often you can get away with wedging/holding the UART-Adapters Pins inplace, and bridging with the tip of a screwdriver. Beware, RX, TX are often "mislabeled" ( =seen from the other/wrong perspective), so swap them, if you get nothing. Adjust speed down from 115200, if you get garbled data.

If you do get output, post it all here too.

Probably OEM did not care changing visible strings in visible UI - namely miniupnp. To approximate age of installed OpenWRT fork check its versions -

Not getting anything interesting

<root xmlns="urn:schemas-upnp-org:device-1-0" configId="1337">
<specVersion>
<major>1</major>
<minor>1</minor>
</specVersion>
<device>
<deviceType>urn:schemas-upnp-org:device:InternetGatewayDevice:2</deviceType>
<friendlyName>OpenWRT router</friendlyName>
<manufacturer>OpenWRT</manufacturer>
<manufacturerURL>http://www.openwrt.org/</manufacturerURL>
<modelDescription>OpenWRT router</modelDescription>
<modelName>OpenWRT router</modelName>
<modelNumber>1</modelNumber>
<modelURL>http://www.openwrt.org/</modelURL>
<serialNumber>00000000</serialNumber>
<UDN>uuid:00000000-0000-0000-0000-000000000000</UDN>
<serviceList>
<service>
<serviceType>urn:schemas-upnp-org:service:Layer3Forwarding:1</serviceType>
<serviceId>urn:upnp-org:serviceId:L3Forwarding1</serviceId>
<SCPDURL>/L3F.xml</SCPDURL>
<controlURL>/ctl/L3F</controlURL>
<eventSubURL>/evt/L3F</eventSubURL>
</service>
<service>
<serviceType>urn:schemas-upnp-org:service:DeviceProtection:1</serviceType>
<serviceId>urn:upnp-org:serviceId:DeviceProtection1</serviceId>
<SCPDURL>/DP.xml</SCPDURL>
<controlURL>/ctl/DP</controlURL>
<eventSubURL>/evt/DP</eventSubURL>
</service>
</serviceList>
<deviceList>
<device>
<deviceType>urn:schemas-upnp-org:device:WANDevice:2</deviceType>
<friendlyName>WANDevice</friendlyName>
<manufacturer>MiniUPnP</manufacturer>
<manufacturerURL>http://miniupnp.free.fr/</manufacturerURL>
<modelDescription>WAN Device</modelDescription>
<modelName>WAN Device</modelName>
<modelNumber>20231227</modelNumber>
<modelURL>http://miniupnp.free.fr/</modelURL>
<serialNumber>00000000</serialNumber>
<UDN>uuid:00000000-0000-0000-0000-000000000000</UDN>
<UPC>000000000000</UPC>
<serviceList>
<service>
<serviceType>urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1</serviceType>
<serviceId>urn:upnp-org:serviceId:WANCommonIFC1</serviceId>
<SCPDURL>/WANCfg.xml</SCPDURL>
<controlURL>/ctl/CmnIfCfg</controlURL>
<eventSubURL>/evt/CmnIfCfg</eventSubURL>
</service>
</serviceList>
<deviceList>
<device>
<deviceType>urn:schemas-upnp-org:device:WANConnectionDevice:2</deviceType>
<friendlyName>WANConnectionDevice</friendlyName>
<manufacturer>MiniUPnP</manufacturer>
<manufacturerURL>http://miniupnp.free.fr/</manufacturerURL>
<modelDescription>MiniUPnP daemon</modelDescription>
<modelName>MiniUPnPd</modelName>
<modelNumber>20231227</modelNumber>
<modelURL>http://miniupnp.free.fr/</modelURL>
<serialNumber>00000000</serialNumber>
<UDN>uuid:00000000-0000-0000-0000-000000000000</UDN>
<UPC>000000000000</UPC>
<serviceList>
<service>
<serviceType>urn:schemas-upnp-org:service:WANIPConnection:2</serviceType>
<serviceId>urn:upnp-org:serviceId:WANIPConn1</serviceId>
<SCPDURL>/WANIPCn.xml</SCPDURL>
<controlURL>/ctl/IPConn</controlURL>
<eventSubURL>/evt/IPConn</eventSubURL>
</service>
<service>
<serviceType>urn:schemas-upnp-org:service:WANIPv6FirewallControl:1</serviceType>
<serviceId>urn:upnp-org:serviceId:WANIPv6Firewall1</serviceId>
<SCPDURL>/WANIP6FC.xml</SCPDURL>
<controlURL>/ctl/IP6FCtl</controlURL>
<eventSubURL>/evt/IP6FCtl</eventSubURL>
</service>
</serviceList>
</device>
</deviceList>
</device>
</deviceList>
<presentationURL>http://192.168.31.1/</presentationURL>
</device>
</root>

Could be a date...

wrong date? or maybe build number

I guess that will he miniunup version.

miniupnpd build date
version would be like Miniupnpd version 2.3.3