401 (edytowany przez MiG25 2022-10-11 10:37:30)

Odp: ZTE MF289F - Porting OpenWRT

Ok , pisaałeś ,żeby włożyć katalog 3ginfo-addon do katalogu 3ginfo , a nie do 3ginfo-lite smile
teraz jest coś więcej:

root@OpenWrt:~# /usr/share/3ginfo/3ginfo.sh
{
"csq":"21",
"signal":"67",
"operator_name":"T-Mobile T-Mobile.pl",
"operator_mcc":"260",
"operator_mnc":"02",
"mode":"LTE_A B20 (800 MHz) / B1 (2100 MHz) / B3 (1800 MHz) / B7 (2600 MHz)",
"registration":"1",
"lac_dec":"0",
"lac_hex":"0",
"cid_dec":"48907532",
"cid_hex":"2EA450C",
"addon":[{"TAC":"59100 (E6DC)"},{"RSSI":"-72 dBm"},{"RSRP":"-104 dBm"},{"RSRQ":"-15 dB"},{"SINR":"-0.4 dB"},{"Primary band":"B20 (800 MHz), 10.0 MHz"},{"PCI":"262"},{"EARFCN":"6350"},{"(S1) band":"B1 (2100 MHz), 15.0 MHz"},{"(S1) PCI":"367"},{"(S1) EARFCN":"225"},{"(S2) band":"B3 (1800 MHz), 10.0 MHz"},{"(S2) PCI":"100"},{"(S2) EARFCN":"1599"},{"(S3) band":"B7 (2600 MHz), 15.0 MHz"},{"(S3) PCI":"118"},{"(S3) EARFCN":"3175"}]
}
root@OpenWrt:~#

ale na stronie nic się nie zmieniło , ciągle prawie ,że nic.

No i mimo tego ustawienia ,też podwójna nazwa.

402

Odp: ZTE MF289F - Porting OpenWRT

W tym będzie podwójnie. easyconfig powinno pokazać inaczej, bo czyta przez ubusa.

ubus call easyconfig modem

Masz dane i dokładnie to sie powinno pokazać na stronie.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

403 (edytowany przez MiG25 2022-10-11 10:56:01)

Odp: ZTE MF289F - Porting OpenWRT

No to się pokazuje dokładnie to , co 3ginfo.sh bez tych addonsow:

root@OpenWrt:~# ubus call easyconfig modem
{
        "csq": "18",
        "signal": "58",
        "operator_name": "T-Mobile",
        "operator_mcc": "260",
        "operator_mnc": "02",
        "mode": "LTE",
        "registration": "1",
        "lac_dec": "0",
        "lac_hex": "0",
        "cid_dec": "0",
        "cid_hex": "0"
}
root@OpenWrt:~#

no prawie , bo tu T-Mobile jest raz...

EDIT: plik 3ginfo.sh też trzeba było podmienić w katalogu 3ginfo-lite , a nie w 3ginfo ....
Teraz już jest lepiej.

404

Odp: ZTE MF289F - Porting OpenWRT

Lite, lite, tak jest. Miało być lite.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

405

Odp: ZTE MF289F - Porting OpenWRT

Hello @cezary,

do you plan to release an prebuild image also for ZTE MF289F?
Tried to translate https://eko.one.pl/?p=easyconfig with google translate... but its not possible...
find your prebuild image amazing.

br
Chris

406

Odp: ZTE MF289F - Porting OpenWRT

tango38317 napisał/a:

Hello @cezary,

do you plan to release an prebuild image also for ZTE MF289F?
Tried to translate https://eko.one.pl/?p=easyconfig with google translate... but its not possible...
find your prebuild image amazing.

br
Chris

I only build stable releases.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

407 (edytowany przez Leo-PL 2022-10-12 15:31:10)

Odp: ZTE MF289F - Porting OpenWRT

The official backport to 22.03 is in the works.

408

Odp: ZTE MF289F - Porting OpenWRT

Hi,
i installed latest nightly build, and the device is working without issues.
only one question regarding the dynamic dhcp interface created after changing the WAN device to QMI Cellular.
The WAN Device with protocol Virtual dynamic interface (DHCP) is not assigned to a firewall zone, and i´m not able to edit this interface. i think this is the reason why i´m not able to configure port forwards.

is this an expected behavior, or did i something wrong, and how can i assign the device to the correct firewall zone?
many thanks
Chris

409

Odp: ZTE MF289F - Porting OpenWRT

wan_4 (with dhcp) is dynamically created by qmi handler, and qmi zone is "proper" for for firewall zone.

Polish ISPs block incoming traffic and maybe the same is true for you. In Poland, you first need to purchase a special service (often called "vpn" or "public ip") for external access from internet (and port forwarding).

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

410

Odp: ZTE MF289F - Porting OpenWRT

Cezary napisał/a:

wan_4 (with dhcp) is dynamically created by qmi handler, and qmi zone is "proper" for for firewall zone.

Polish ISPs block incoming traffic and maybe the same is true for you. In Poland, you first need to purchase a special service (often called "vpn" or "public ip") for external access from internet (and port forwarding).


Hi,
in AT you need not to purchase a special service, we can request a public ip and use it for publishing services. i´m able to publish it on my existing Huawei modem, i see the public ip on WAN_4, but WAN_4 does not have a zone, and i´m also not able to assign a zone to WAN_4 - i i try to edit i receive following error:


TypeError
Cannot read properties of null (reading '.name')

If you place mouse on the device wan_4 you see the message: no zone assigned.

In the meantime i found my issue:
forgot to enable DynDNS Client to update ip :-)
tried also to add the WAN_4 interface manually (etc/config/firewall) > that was successfull, but undo this change, and try to make further tests with default config.

br
Chris.

411

Odp: ZTE MF289F - Porting OpenWRT

Although it doesn't look like wan_4 is assigned to the zone from LuCI, it inherits 'wan' zone indeed, you can see that in 'ifstatus wan_4'.

412

Odp: ZTE MF289F - Porting OpenWRT

BTW you can add "option dhcp 0" in wan section. wan will get address directly from qmi, not via dhcp.

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

413

Odp: ZTE MF289F - Porting OpenWRT

Leo-PL napisał/a:

Although it doesn't look like wan_4 is assigned to the zone from LuCI, it inherits 'wan' zone indeed, you can see that in 'ifstatus wan_4'.

Hi Leo-PL,
verified it, you are right, Zone seems to be correct, and only view in Luci is not correct

      "data": {
                "zone": "wan",
                "dhcpserver": "PUBIP",
                "hostname": "fw",
                "leasetime": 7200,
                "zone": "wan"
        }

Cezary,
i i added "option dhcp 0" into wan section, but i´ll reboot my device when i´m back home.. if something goes wrong i´ll get trouble with my family :-)

414 (edytowany przez tango38317 2022-10-13 09:35:53)

Odp: ZTE MF289F - Porting OpenWRT

@Cezary,
i think, you have had a deeper look into the device.
this is a 4CA device, with 4 internal antenna. my device is located in cellar, and i have an external antenna, so i cannot use full capabilities of the device. as i saw it should be possible to add further external anntenas with a small rebuild - but do you know what connector on boar i can use to connect further antennas to this device?
thx
chris

415

Odp: ZTE MF289F - Porting OpenWRT

tango38317 napisał/a:
Leo-PL napisał/a:

Although it doesn't look like wan_4 is assigned to the zone from LuCI, it inherits 'wan' zone indeed, you can see that in 'ifstatus wan_4'.

Hi Leo-PL,
verified it, you are right, Zone seems to be correct, and only view in Luci is not correct

      "data": {
                "zone": "wan",
                "dhcpserver": "PUBIP",
                "hostname": "fw",
                "leasetime": 7200,
                "zone": "wan"
        }

Cezary,
i i added "option dhcp 0" into wan section, but i´ll reboot my device when i´m back home.. if something goes wrong i´ll get trouble with my family :-)

I think this is because LuCI doesn't see 'config interface wan_4' anywhere, and doesn't check the actual status of dynamic interface. This is a common misconception and a thing that could be fixed in future.

416

Odp: ZTE MF289F - Porting OpenWRT

tango38317 napisał/a:

@Cezary,
i think, you have had a deeper look into the device.

No smile I don't even have this model.

this is a 4CA device, with 4 internal antenna. my device is located in cellar, and i have an external antenna, so i cannot use full capabilities of the device. as i saw it should be possible to add further external anntenas with a small rebuild - but do you know what connector on boar i can use to connect further antennas to this device?

Ask @stich86

Masz niepotrzebny router, uszkodzony czy nie - chętnie przygarnę go.

417

Odp: ZTE MF289F - Porting OpenWRT

Cezary napisał/a:

BTW you can add "option dhcp 0" in wan section. wan will get address directly from qmi, not via dhcp.

Hi,
in the meantime i was able to restart WAN device with active "option dhcp 0", now the PUBIP is located on the WAN (QMI Cellular) device. No further Dynamic Virtual DHCP Device is available.

418

Odp: ZTE MF289F - Porting OpenWRT

tango38317 napisał/a:

this is a 4CA device, with 4 internal antenna.

No , this device ( like MF286D) have 5 internal antennas....

From my several tests on different routers ,much better results you get when you simply put router in hermetic box in place ( and instead) of external antenna.
1st becouse it will be hard to place 5 external antennas ( even when thre are 2 in one for MIMO 2x2) ,also becouse of costs , and second on each meter of antenna cable you have losses , higher then frequency is higher.

419

Odp: ZTE MF289F - Porting OpenWRT

tango38317 napisał/a:
Cezary napisał/a:

BTW you can add "option dhcp 0" in wan section. wan will get address directly from qmi, not via dhcp.

Hi,
in the meantime i was able to restart WAN device with active "option dhcp 0", now the PUBIP is located on the WAN (QMI Cellular) device. No further Dynamic Virtual DHCP Device is available.

In this case ou will not get new IP when lease time ends , you have to have some watchdog to restart connection....

420

Odp: ZTE MF289F - Porting OpenWRT

MiG25 napisał/a:
tango38317 napisał/a:

this is a 4CA device, with 4 internal antenna.

No , this device ( like MF286D) have 5 internal antennas....

From my several tests on different routers ,much better results you get when you simply put router in hermetic box in place ( and instead) of external antenna.
1st becouse it will be hard to place 5 external antennas ( even when thre are 2 in one for MIMO 2x2) ,also becouse of costs , and second on each meter of antenna cable you have losses , higher then frequency is higher.


HI,
thanks for your update - i´ll test it. with my old modem the results with external antenna was much better (up to 50 MBIT with external antenna, 2-4 mbit with internal antenna) -but antenna is outside of house, and on top of roof.
i´m living on a moutain (in the back of beyond...).

421 (edytowany przez MiG25 2022-10-13 10:27:46)

Odp: ZTE MF289F - Porting OpenWRT

So hopully when you place modem with internall antenas in hermetic box and put it outside instead external antennas , can be better.

But ofcourse distance to tower should not be like more then 2km... In other case proffesionall directional outside antenna dedicated to only one band can give much better results.. ( but in such case results will not vary ,if it will be router cat.4 or cat.20)...

422

Odp: ZTE MF289F - Porting OpenWRT

MiG25 napisał/a:
tango38317 napisał/a:
Cezary napisał/a:

BTW you can add "option dhcp 0" in wan section. wan will get address directly from qmi, not via dhcp.

Hi,
in the meantime i was able to restart WAN device with active "option dhcp 0", now the PUBIP is located on the WAN (QMI Cellular) device. No further Dynamic Virtual DHCP Device is available.

In this case ou will not get new IP when lease time ends , you have to have some watchdog to restart connection....

HI,
thanks for advisory, i´ll have a look whats the easiest solution for me
br

423

Odp: ZTE MF289F - Porting OpenWRT

MiG25 napisał/a:

So hopully when you place modem with internall antenas in hermetic box and put it outside instead external antennas , can be better.

But ofcourse distance to tower should not be like more then 2km... In other case proffesionall directional outside antenna dedicated to only one band can give much better results.. ( but in such case results will not vary ,if it will be router cat.4 or cat.20)...

In case i´ll add further antennas, do you have information what connectors i can use from board?
thx

424

Odp: ZTE MF289F - Porting OpenWRT

On modem there are standard U.FL/IPX/IPEX (2mm) , then you need 5 pigtails.

425

Odp: ZTE MF289F - Porting OpenWRT

MiG25 napisał/a:

On modem there are standard U.FL/IPX/IPEX (2mm) , then you need 5 pigtails.

Two of them should be joined to maintain MIMO 4x4

ANT4 = MIMO_1
ANT1 = MAIN_HB
ANT0 = MAIN_MLB
ANT2 = AUX
ANT3 = MIMO_0


ANT0+ANT1 should be connect together to a single antenna to have MINO 4x4 (obviously BTS should support)