Nerd 2.0

Since there is already much zulesen the Fritz boxes on the Internet regarding firmware modding so I thought why did I not even try this time.

The first Problem was the Standert "starttelnet.image" image did not work. After a long search, much experimentation and frequent pulling plug on a post then I'm in the ip-phone-forum met. After much back and forth hats then folded up and I'm standing here now with my own small DNS server, but all times of the beginning.
How do I start a telnet to FritzBox 2030

1. The firmware can not be more topical 3/17/80, when the same is true can be continued with step 2.
   To get back to a previous firmware version, you must use the AVM Recover Tool. This one gets by you to contact the support of AVM. Now the update is to version .80, .73 still there 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 (unzip before) one. The box indicates an error "No error", the Internet is no longer responding and Infoled flashes constantly. All this is normal.
3. Her you can now log in via telnet to the box. But this also telnet after reboot you must first remains a TFTP server installed on a PC in your network, then you give the following command in the Fritzbox
   echo "mkdir / var / bin, / usr / bin / tftp-g-r bootup-l / usr / bin / bootup 192.168.0.2; chmod + x / usr / bin / bootup, / usr / 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 / usr / bin / telnetd 192.168.0.2;
   chmod + x / usr / bin / telnetd;
   / Usr / bin / telnetd-l / & sbin/ar7login
   (Applies to IP the same as in point 3)
5. This would all done on the box and you just have to put on a Telnet Binary euern TFTP server. These are available here .

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

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

1. Ye logged via telnet to the box and executes the following 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 dhcpend = 192.168.0.y; provide. 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 Fritz box using TFTP
   / Usr / bin / tftp-g-r-l ar7.cfg / var/flash/ar7.cfg 192.168.0.2;
4. Now type in "reboot" on the one Firtzbox to restart them.

So would the DHCP server and personalized, we can turn the DNS.

Feed with its own DNS name

1. Option 1 is of course easy for all PC's "automatic IP" to enable, for whom this enough, you can make statements.
2. Because I want to apply a variant not on every computer I / could I have just the entries in the DHCP server on the Fritzox faked. To do this you need to return to the Fritzbox
   / Usr / bin / tftp-g-r multid.leases-l / var / flash / multid.leases 192.168.0.2;
   perform
3. In the now present on the TFTP file server, the DHCP addresses are stored. Here you can enter as many others. All values ​​are in the form: "lease MAC IP NUMBER" NAME "01MAC" eg (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;
   Write back and restart the Fritzbox with "reboot".

That would be everything 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 changes are retained.

Mfg. BODY-Snatch