seud0nym / tch-gui-unhide

Modify Telstra-branded Technicolor devices to access hidden features
GNU General Public License v3.0
127 stars 15 forks source link

FR Sim card use in bridged mode #163

Closed legend069 closed 1 year ago

legend069 commented 1 year ago

Hey there, is it possible to get the simcard working while it's in bridged mode ?

seud0nym commented 1 year ago

There is a guide here for doing that: https://hack-technicolor.readthedocs.io/en/stable/Unlock/#keep-wwan-functionality-while-homeware-gateway-is-bridged

legend069 commented 1 year ago

There is a guide here for doing that: https://hack-technicolor.readthedocs.io/en/stable/Unlock/#keep-wwan-functionality-while-homeware-gateway-is-bridged

Oh neat thanks, I'll look into that shortly.

I'm wanting to use my 3APs with the 5 Rj45 connections in bridged mode with the back up Sim enabled on all of them. And configure pfsense to have them all as a shared failover gateway.

legend069 commented 1 year ago

just thought i would post an update here while messing about in the DJA0231 i somehow locked myself out. got back into it set it up again and ect, first thing i noticed was the easy mesh discovered the other AP's right away, neat i guess.

continued trying to get it to work with the SIM still active while in bridged mode.. and it works !! yay set the second one up exactly the same(part different IP's ) configured pfsense to add it as another gateway,adjusted gatewaygroups and yes it still works. unplugged main WAN cable it switched over to the simcards IP, marked 1 as down and it switched over to the other. running tracert reports traffic still goes through pfsense, although if i change my gateway on a client to either 1.1 or 1.3 the traffic doesn't go though pfsense, witch is expected and security flaw i guess? (lets see how long it would stay like this before telstra disables the sim cards....)

now for some reason after adjusting 192.168.1.3, 192.168.1.1 can't see it as a booster anymore. 192.168.1.1 can only detect 192.168.1.2 that i have not adjusted yet. maybe it has something to do with the SIM card stuff? ref:https://github.com/seud0nym/tch-gui-unhide/issues/130

seud0nym commented 1 year ago

although if i change my gateway on a client to either 1.1 or 1.3 the traffic doesn't go though pfsense, witch is expected and security flaw i guess?

I would expect that, yes. Security flaw? Not really - it is just a network design issue. Can you configure the firewall on pfsense to prevent it?

now for some reason after adjusting 192.168.1.3, 192.168.1.1 can't see it as a booster anymore. 192.168.1.1 can only detect 192.168.1.2 that i have not adjusted yet. maybe it has something to do with the SIM card stuff?

Definitely not going to be SIM card related.

Easymesh only works if directly connected - if there is a switch in-between or the packets are routed via another gateway, it doesn't work.

lets see how long it would stay like this before telstra disables the sim cards....

If you have more than a small amount of traffic, or it is continuous, then it won't take them very long.

legend069 commented 1 year ago

I would expect that, yes. Security flaw? Not really - it is just a network design issue. Can you configure the firewall on pfsense to prevent it? possible i'll need to look more into it.

Definitely not going to be SIM card related.

Easymesh only works if directly connected - if there is a switch in-between or the packets are routed via another gateway, it doesn't work.

after looking though the config area's i've noticed the IP routing table is different, perhaps this has something to do with the easy mesh issue? below is from a fresh firmware update/config and it has no "reports of SSID's sync'd" image

below is from a old firmware config and it reports in the GUI "X ssid's sync'd from controller" image

legend069 commented 1 year ago

i'm going to assume wl0 -wireless 2.4ghz wl1 -wireless 5ghz wl1_1 - but what is this one ? would it be the 4g sim card connection?

seud0nym commented 1 year ago

The fresh install looks like you haven't run in the bridged-booster script - that is what adds the wireless interfaces to the bridge.

wl1_1 is the wireless backhaul for EasyMesh. It is not used by the bridged_booster configuration, but if you have a "real" Telstra booster device, it does get used.

legend069 commented 1 year ago

ok update here and closing issue after a small hicup with the DJA2031 rebooting midway though installing scripts it auto updated its firmware to type3 (note to self; remove simcard before setting back to factory defaults) @seud0nym possible to add a warning for user to remove simcard if they reset to factory defaults?

i was able to get it do do what i want by fresh installing scripts running ./de-telstra -A ./tch-gui-unhide installed simcard - made sure it was working in this mode.(if you don't install simcard now and get a connection the wifi booster script wont't be able to connect for some reason) it will need to have the dynamic route added before you continue image

ran my edited wifi-booster script (just removed the mobile stuff, i did try setting up a new command to enable mobile, but i wasn't able to figure out the coding) https://github.com/legend069/tch-gui-unhide/blob/master/wifi-booster/bridged-boostern made other changes with ./de-telstra

pfsense still sees it as a gateway and all 3 of my AP's are on load balancing failover whoohoo! (speed tests reports ~100mbps down, the fact that now all sites services take advantage over multi wan is a little annoying but eh)

now i just need to figure out how to route the traffic properly so it all goes though the pfsense. this is fun 😄 I should also adjust pfsense to disable the main gateway everynow and then too so the simcards will have a lower chance of getting disabled.

seud0nym commented 1 year ago

possible to add a warning for user to remove simcard if they reset to factory defaults?

There are 2 options on reset-to-factory-defaults-with-root to prevent OTA updates are reboot:

-c Turns off CWMP so it just can't happen. -d Adds a DNS rewrite so that even if it attempts to download an update, it will fail to resolve the Telstra firmware repository.

But I will think about adding a warning.