Rebase on Firmware 2.2.0 (fix IPv6)

tjeh commented 4 years ago

I have successfully installed 2.2.0 (on DGA4132) via Ansuel GUI. Prior to the GUI modification I noticed that i.e. they have a working IPv6 in PPPoe.

So how do we get the ball rolling on the rebase?

FrancYescO commented 4 years ago

so with 2.2.0 the modem connect the WAN in both ipv4 and ipv6 (TIM?) out of the box? are you sure this was not happening on 2.1.0 or other 2.0.0> firmware?

tjeh commented 4 years ago

I cant speak to other version as I went straight to 2.2.0. For me the issue is, that 2.2.0 TIM allows IP6@WAN whereas 2.2.0 TIM + GUI strangely does not.

I did check (git comparison on unpacked squash image) 1.0.3 TIM vs 2.2.0 TIM and they made noumerus changes to files.

Whats the base firmware for the GUI modifications?

Ansuel commented 4 years ago

Can you pls give me more info? A ipv6 test?

Il Mar 27 Ago 2019, 15:38 tjeh notifications@github.com ha scritto:

I cant speak to other version as I went straight to 2.2.0. For me the issue is, that 2.2.0 TIM allows IP6@WAN whereas 2.2.0 TIM + GUI strangely does not.

I did check (git comparison on unpacked squash image) 1.0.3 TIM vs 2.2.0 TIM and they made noumerus changes to files.

Whats the base firmware for the GUI modifications?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Ansuel/tch-nginx-gui/issues/788?email_source=notifications&email_token=AE2ZMQUVJC6RQZRRV7B3MK3QGUU6XA5CNFSM4IP7L2Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5HYOIY#issuecomment-525305635, or mute the thread https://github.com/notifications/unsubscribe-auth/AE2ZMQU57WUC3ELLGP35OJDQGUU6XANCNFSM4IP7L2QQ .

FrancYescO commented 4 years ago

Basically is 2.0.0, but if usefull/needed also other things from other firmware are taken...

Do you confirm also from, ie https://test-ipv6.com/ you get all tests passed?

tjeh commented 4 years ago

ok so while messing around I managed to get the following "zombie" mode for my DGA4132:

recieved device with 1.1.0 stock TIM GUI
downgraded via CSRF token / Postman to 1.0.3_closed
rooted device (without firmware flash)
installed Ansuel GUI manually
rebooted (waiting for Bank2 to Bank1 copy to complete)
once everything settled, deleted /root/GUI.tar.gz
upgrade to 2.2.0_closed via Ansuel GUI (checking delete config and root only)
now I have a 2.2.0 stock TIM GUI, rooted root/root, with WebGUI access admin/admin

I guess this would be now a good start to apply the only the necessary fixes to:

disable: CWMP, any callbacks to e.g TIM, any unwanted users (/etc/passwd...)
enable: bridge mode, elevate admin to (tech or whatever is the highest auth level)

If these modifications are done on a *.patch level (rather than replacing the ie. *.lua files), this might make things easier to apply your modifications on other (as in ie. DGA4310, ...) firmware images / or future updated firmware images?

FrancYescO commented 4 years ago

4130 and 4132 have very little difference so yes a patch file with a designed starting firmware can be enought but lot of files integrated in the repo (init.d, transformer mappers upgrade scripts etc..) to port these where they are missing (GUI installed on older firmware/totally different devices)

if you want a "clean" starting point to compare dirs for a rebase you could just extract rbi (https://github.com/FrancYescO/tch_firmware_extracted/tree/AGTEF_2.2.0_001) or look at the /rom folder on your device than compare with the content of this repo (and if you find equal files, is just to be sure these will be ported on all devices/firmwares where this GUI will be installed)