Nerd 2.0

Since there is a lot to them during use the Fritz boxes on the Internet regarding firmware modding was so I thought why I try not even once.

The first Problem was the Standert "starttelnet.image" image did not work. After a long search, much trial and error and frequent Steckerziehen I went to a post in the ip-phone-forum encountered. After much back and forth hats then worked and I am standing here now with my own small DNS server, but all times of the beginning.
How to start telnet on a FritzBox 2030

1. The firmware must not be more topical 17.03.80, if it does can be immediately proceed with step 2.
   To get back to a previous firmware version, you must use the AVM Recover Tool. This one gets by you contact us for support by AVM. Now the update is to version .80, as .73 still in the LAN-B connection was broken because of an error. This version can be found again directly from AVM .
2. Now you play this file " enable_telnet.tar "as a firmware image (not previously extract a). The box reports as an error "No error", the Internet will not respond anymore and the Infoled flashes constantly. All this is normal.
3. Her you can now log in via telnet to the box. But this also telnet after restarting it will remain active you must first one TFTP server on a PC install in your network, then you give the command in the Fritzbox
   echo "mkdir / var / bin, / usr bin / tftp-g-r bootup-l / var / bin / bootup 192.168.0.2; chmod + x / var / bin / bootup, / var / bin / bootup &"> var / flash / debug.cfg
   192.168.0.2 stands for the address of the computer on which the TFTP server is running.
   
4. Now it puts a file with the name "bootup" on the server. In it should show:
   / Usr / bin / tftp-g-r Linux / router / telnetd-l / var / bin / telnetd 192.168.0.2;
   chmod + x / var / bin / telnetd;
   / Var / bin / telnetd-l / & sbin/ar7login
   (Applies to IP the same as in point 3)
5. This was all done on the box and you have to just put a Telnet Binary upon your TFTP server. This exists here .

Thus it would be done and it runs first telnet to the box.

Next I will take care of the change in the address range of the DHCP server as the assigned IP from .20 to not quite fit into my network.
DHCP address range change

1. Ye log a telnet to the box and executes the command:
   / Usr / bin / tftp-p-r-l ar7.cfg / var/flash/ar7.cfg 192.168.0.2;
2. Now you edited the now lying on your server ar7.cfg. You need to "brinterfaces (name =" lan ";" dhcpstart = on 192.168.0.x, and provide dhcpend = 192.168.0.y;. Then the DHCP server assigns addresses from x to y, where x is greater than one course should be.
3. Now it writes the file back to the Fritzbox via TFTP
   / Usr / bin / tftp-g-r-l ar7.cfg / var/flash/ar7.cfg 192.168.0.2;
4. Now pay "reboot" on the one Firtzbox to restart it.

This would personalize the DHCP server and we can turn to the DNS.

DNS fed with its own name

1. Option 1 is obviously easy for all PC's "Automatic IP Allocating turn on who the last that can make this connection.
2. Since I want to apply a variant not in any computer by me / I could have just the entries of the DHCP server on the Fritzox faked. Therefore you back on the Fritzbox and
   / Usr / bin / tftp-g-r multid.leases-l / var / flash / multid.leases 192.168.0.2;
   perform
3. In the now on the TFTP server this file, the DHCP addresses are stored. Here you can enter as many others. All values are in the form of "lease MAC IP NUMBER" NAME "01MAC" for example (lease 00:0 F: 3D F0: 1D: 192.168.0.2 C 8 862 468 "Cube" 01000f3df01dc8)
4. Jetz simply return the file with
   / Usr / bin / tftp-p-r multid.leases-l / var / flash / multid.leases 192.168.0.2;
   restore and restart the Fritzbox with "reboot".

That would be all I've done so with me. But watch the end when you upgrade to version 92 is the telnet function is lost. DNS and DHCP will be change.

Mfg BODY SNATCH