 420br
@10.100.2.114, 66.119 | reply to 420br
More stuff.. I've found out a possible way to unlock _any_ firmware.. steps:
1) Run your firmware of choice
2) Find out where it unlocked the firmware (usually c:\windows\~cua - c:\winnt\~cua)
3) Backup the 'defaults' file: XXX-XXXX-XXX.def.enc and close the firmware update.
4) Run the firmware you want to try out
5) Replace its' .def.enc with the one you just backed up..
Simple, eh? 
Also, found more interesting config bits over telnet...
cfg sys - lets you set the modem to router/bridge/both, plus, some other things we have no idea... 
sys
mode = brtr [brg,brtr,rtr]
gw = 0.0.0.0
dns#0 = 0.0.0.0
dns#1 = 0.0.0.0
dns#2 = 0.0.0.0
prof = n
dbtw = n
disf = n
dish = n
dist = n
b1vc = n
sbm = n
kpnp = n
conf = 0
eipp = n
tnet = n
cfg dsl - set log to 1 (cfg dsl{log=1), reboot the modem, check out what else "System Log" spits
dsl
mode = mult [mult,ansi,dmt,lite,emt]
log = 0
mtm = n
msm = n
It's quite interesting.. just out of curiosity, I checked the System Log.. all of a sudden, the pwr light blinked red.. I refreshed and found this:
0000-00-00 00:02:07 E I |ATM |vcc 0/33 responding to probe (code: 0)
0000-00-00 00:02:08 E I |PPP |LCP down
0000-00-00 00:02:08 E I |PPP |IPCP down
0000-00-00 00:02:08 E I |PPPoE |tx PADT, id: 7E68, ac: (NULL), sn: (NULL)
If all of a sudden your modem gets nasty on you and decides to reboot often, you know it's coming from your lovely telco. 
I've also given a try to the "IP Passthru" thing.. well, as the name pointed out.. it passed over the ip to the ethernet card... the downside? I couldn't access anything at all.. telnet/web got borked and I had to reset the modem to default configs... If anyone knows how to put it to work AND keep the router goodies up (telnet/web/ftp), let me know
Cheers,
-420 |
