Can't disable force_dns

All about firmwares for routers. Support for RouterTech firmwares is here too.
Post Reply
User avatar
mysticalos
Experienced
Experienced
Posts: 237
Joined: Sun Feb 25, 2007 11:46 pm
Location: Georgia, USA
Contact:

Can't disable force_dns

Post by mysticalos » Sun Mar 02, 2014 9:36 am

So, I mistook block.sh with adblock.sh and ran it. Now I cannot undo the damage it's brought. This information from docs is not valid

"block_baddies_undo.sh - to undo what was done by block_baddies.sh (the router will be rebooted afterwards). To prevent this command being executed accidentally, you will need to give it the parameters: "--confirmed --proceeed". Any other thing, and it will not run"

Here is my output of me trying just this, as well as various other things

BusyBox v1.19.3 (2012-01-30 23:09:05 GMT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

Code: Select all

/var # block_baddies_undo.sh --confirmed --proceeed
Wrong or unsufficient parameters.
/var # block_baddies_undo.sh
Wrong or unsufficient parameters.
/var # block_baddies_undo.sh --confirmed --proceeed
Wrong or unsufficient parameters.
/var # block_baddies_undo.sh--confirmed --proceeed
-sh: block_baddies_undo.sh--confirmed: not found
/var # block_baddies_undo.sh -confirmed -proceeed
Wrong or unsufficient parameters.
/var # 
I tried removing the force_dns entry from bootloader environment and then rebooted router, but despite being apsent from bootloader

Code: Select all

BUILD_OPS	0x301
bootloaderVersion	1.4.0.4
ProductID	AR7RD
SerialNumber	none
IPA	192.168.1.1
MEMSZ	0x01000000
FLASHSZ	0x00400000
MODETTY0	9600,n,8,1,hw
MODETTY1	9600,n,8,1,hw
CPUFREQ	211968000
MIPSFREQ	211968000
SYSFREQ	105984000
PROMPT	(psbl)
MAC_PORT	0
BOOTCFG	m:f:"mtd1"
mtd2	0x90000000,0x90010000
mtd3	0x90010000,0x90020000
mtd4	0x90020000,0x90400000
StaticBuffer	384
vlynq_polarity	low
pppoe_relay_enabled	1
DSL_BIT_TMODE	1
sar_ipacemax	6
DSL_UPG_DONE	1
vcc_encaps0	0.0
vcc_encaps1	0.0
vcc_encaps2	0.0
vcc_encaps3	0.0
vcc_encaps4	0.0
vcc_encaps5	0.0
vcc_encaps6	0.0
vcc_encaps7	0.0
usb_vid	0x0451
usb_pid	0x6060
HWA_RNDIS	00:E0:A6:66:41:EB
HWA_HRNDIS	00:E0:A6:66:41:E1
WLAN_HWADDR	00:12:0E:54:E9:A4
wlanwepkey0	00:30:0A:77:0C:83
autopvc_enable	1
connection5-mac	00-10-b5-06-6f-63

connection6-mac	00-10-b5-06-6f-63

connection7-mac	00-10-b5-06-6f-63

TR69_USERNAME	00E0A6-111
TR69_PASSWORD	00E0A6-111
HWRevision	402H
WLAN_HWADDR1	02:30:1A:54:E9:A4
WLAN_HWADDR2	02:30:2A:54:E9:A4
WLAN_HWADDR3	02:30:3A:54:E9:A4
IPA_SVR	192.168.1.2
WLAN_EEPROM0	021156041B06001200000601095612000000010D56A9000000026D546274EB0A
WLAN_EEPROM1	30000000013984000100000101854C1068900105850600100001298507000000
WLAN_EEPROM2	01C1850000300001C585000000000111850000FFFF0115850000F0FF01A58500
WLAN_EEPROM3	8000000109850000800201010C03000000012184000000800181851D00030001
WLAN_EEPROM4	55090100000001E5580200000001F1580800000001D5581000000001B1580400
WLAN_EEPROM5	0000000000000000000C00C300FE0008011401260144014D014F0165019F01AF
WLAN_EEPROM6	01B70101390000110004010101000501060002010201021E000A000205020411
WLAN_EEPROM7	2244030610203031324004095449204143583130300507544920546573740108
WLAN_EEPROM8	1E221464036401690502000037007000A800E60004044410D9034510F803185A
WLAN_EEPROM9	4000145A1800020E0801C9000A01A1025000D50176095000E2000A0108035000
WLAN_EEPROM10	B80176090107100000400000010000050400010100000000FFFFFFFFFDFDFDFD
WLAN_EEPROM11	FBF4F4F4F40E0409090909090909090909090909090909090909090909090909
WLAN_EEPROM12	090909090909090909090909090909090909090909090909090909090909090E
WLAN_EEPROM13	0100000000000000000000000000000302A318A3180700012000000000000000
WLAN_EEPROM14	00000000000000000000000000000000000000000000000000
NVS_TFTP_LOAD	0
HWA_0	00:30:0A:F7:B0:00
HWA_3	00:30:0A:F7:B0:01
WLAN_HWADDR0	00:30:0A:EB:74:62
wan_br_mac	00:30:0A:EB:74:62
FirstUseDate	2002-09-08T12:01:26
memchk.sh	1
cron_enable	1
connection1-mac	00-30-88-23-1d-05

connection1	0x1e38

connection0-mac	00-30-88-23-1d-05

connection0	0xff2e

cron_la.sh	1
checkmargins.sh	1
RT_cmd_4	write_crontab.sh '5' '2' '*' '*' '*' 'clearlog.sh && dmesg -c'
TZ	EST+05:00EDT
rshaper_enable	1
mtd1	0x90020090,0x900a0000
mtd0	0x900a0000,0x90400000
min_margins	4 10 reboot
RT_init_rshaper1	rshaperctl 192.168.1.4 114688
RT_init_rshaper3	rshaperctl 192.168.1.8 114688
modulation	0xff
RT_init_rshaper2	rshaperctl 192.168.1.5 114688
adblock	exit large
It still runs

Code: Select all

Jan 30 23:10:14 | AP is disabled
Jan 30 23:10:14 | Valid Configuration Tree
Jan 30 23:10:14 | NTP Polling Timer for DHCP Started succesfully.
Jan 30 23:10:14 | DSL Polling Timer Started succesfully.
Jan 30 23:10:14 | PSP Boot environment  Modem Modulation Change: 0xff
Jan 30 23:10:15 | Firewall NAT service started
Jan 30 23:10:15 | Bridge Created: br0
Jan 30 23:10:16 | Bridge VLAN0 add eth0
Jan 30 23:10:16 | Bridge VLAN AUTO OFF.
Jan 30 23:10:16 | Bridge VLAN0 add eth1
Jan 30 23:10:16 | Bridge VLAN AUTO OFF.
Jan 30 23:10:16 | Bridge VLAN0 add eth2
Jan 30 23:10:16 | Bridge VLAN AUTO OFF.
Jan 30 23:10:16 | Bridge VLAN0 add eth3
Jan 30 23:10:16 | Bridge VLAN AUTO OFF.
Jan 30 23:10:17 | Bridge Created: br1
Jan 30 23:10:17 | Bridge Created: br2
Jan 30 23:10:20 | Bridge Interface Added: eth0
Jan 30 23:10:22 | Bridge Interface Added: eth1
Jan 30 23:10:24 | Bridge Interface Added: eth2
Jan 30 23:10:25 | Bridge Interface Added: eth3
Jan 30 23:10:27 | routertech_misc_inits.sh: Loading the rshaper module. Configure it with rshaperctl. 
Jan 30 23:10:27 | USB is disabled 
Jan 30 23:10:27 | DSL Carrier is down
Jan 30 23:11:07 | DSL Carrier is up
Jan 30 23:11:07 | sar read trained mode (3)(ADSL_G.dmt.bis)
Jan 30 23:11:07 | ---}}} Start of connection delayed for 2 sec
Jan 30 23:11:07 | PPPoA launch delay.
Jan 30 23:11:09 | PPPoA Launch after conn delay timeout ...
Jan 30 23:11:10 | pppd 2.4.4 started by root, uid 0
Jan 30 23:11:10 | Connect: ppp0 {--} 
Jan 30 23:11:10 | PAP authentication succeeded
Jan 30 23:11:10 | local  IP address 75.89.212.114
Jan 30 23:11:10 | remote IP address 75.89.208.1
Jan 30 23:11:10 | primary   DNS address 166.102.165.11
Jan 30 23:11:10 | secondary DNS address 166.102.165.13
Jan 30 23:11:10 | PPPoA Connect with IP Address 75.89.212.114 
Jan 30 23:11:10 | PPPoA Connection Successfully Established 
Jan 30 23:11:10 | PPPoA Connect with Gateway IP Address: 75.89.208.1 
Mar  2 02:10:02 | PPPD Successfully Started 
Mar  2 02:10:03 | miniupnpcmd.sh: upnpd initialized 
Mar  2 02:10:03 | HTTP listening on port 5000
Mar  2 02:10:15 | force_dns: Received: "208.67.222.123 208.67.220.123 208.67.222.123" 
Mar  2 02:10:30 | onconnectWAN: Starting adblock_multi with parameters "exit large" 
Mar  2 02:10:37 | adblock.sh: wgot conf file from www.mvps.org 
Mar  2 02:10:44 | adblock_multi.sh: Clearing the dnsmasq cache 
Mar  2 02:10:45 | adblock_multi.sh: Restarting dnsmasq 
Mar  2 02:10:48 | onconnectWAN: Crond is already running. 
Mar  2 02:10:51 | time disparity of 1096319 minutes detected 
I'd like to avoid simply setting defaults on router to fix it, especially if that doesn't even work. It takes a good 1-2 hours to set it up again afterwards with 9 static IP addresses to make my rshaper rules and several custom port forward rules as well. So I need to figure out how to get block_baddies_undo.sh to function correctly.
User avatar
mysticalos
Experienced
Experienced
Posts: 237
Joined: Sun Feb 25, 2007 11:46 pm
Location: Georgia, USA
Contact:

Re: Can't disable force_dns

Post by mysticalos » Sun Mar 02, 2014 9:39 am

Bah, the bug is actually a typo on firmware-faq/features.html

I just realized proceeed had too many "e" in it, I didn't catch it because I faithfully copied and pasted from the features article. :P
User avatar
thechief
RouterTech Team
RouterTech Team
Posts: 12067
Joined: Wed Feb 01, 2006 10:22 pm
Location: England, the Centre of Africa
Contact:

Re: Can't disable force_dns

Post by thechief » Sun Mar 02, 2014 5:43 pm

A bug in the docs. That's a new one! :shock:
The Chief: :afro: Be sure to read the Firmware FAQ and do a Forum Search before posting!
No support via PM. Ask all questions on the open forum.
Post Reply