Archive | Imprint | Privacy
15th May 2010
Nerd 2.0

7270 FritzBox soon with IPv6 for each

After it the first time a test firmware CeBit 2009 with IPv6 was introduced for the FritzBox 7270, the successor to IPv4, is now in the latest "preview on the official firmware" migrating, so it should in the near future, via firmware update hike on each box. So now missing only the ISPs and IPv6 can come. (1 & 1 provides in any case, no address)

Interestingly, however, what will change when migrating to the Internet population to v6 everything. Will my surfing behavior on the basis of my static block is stored (data adé)? Can I bypass an IP ban simply by listing the addresses in my block change or is it a lock for the entire block? How much will the new address for Web servers or do I get there and blocks?

Is certainly interesting.

Update: Even I am in the 1 & 1 Blog on this post hit on the topic, very interesting :-)

26th February 2009
Nerd 2.0

New FritzBox 7270 without IPv6

Today it seems semi-officially a new firmware for the Fritz box 7270 to be published.

She carries the version number 54.04.70 and there are changes in the telephony and Internet access via UMTS / HSPA has been inserted. (Complete changelog below)

The latest update is apparently not yet been officially released, since neither of the AVM - page nor the AVM - FTP , information can be found to check and update the FritzBox also has its flaws.

FritzBox 7270 Updateprüfung – Fehler

Find the latest firmware is available at:
ftp://update.avm.de/updtest/FRITZ.Box_Fon_WLAN_7270.54.04.70.image

The integration of IPv6 into the firmware (more info at Heise and Klaus Alrutz ) has not happened yet unfortunately.

Learn more »

23rd November 2006
Nerd 2.0

Tip for the solution for firmware problem with AVM

Since June is on the AVM FTP next to the current firmware also always make a recovery image to the older version of the firmware again.

Just have to open the folder with the name of the Fritz box patched, and there appear to be two subfolders. Firmware in the folder is the folder in the current firmware and the x-misc recovery image is.

So I recommend now to consider not only the latest firmware and set aside but also the suitable recovery image, who knows when we need it again. ;-)

Mfg. BODY Snatch.

2nd February 2006
Nerd 2.0

DLink 360-T: Router, HTTP server and DHCP in a

From current events, I would now like to summarize again all about the DLink 360-T.

The data for the telnet login, user "root" and password "admin". You should change this but as soon as possible via the web interface.

Modem as a router

  1. Ye log into a web interface of the modem and provides a data connection with the pppoe connection. To give one your connection and removes the Hacken at "On Demand" (not going to the modem).
  2. Now on Status> Connection Status and dial.
  3. Now you log onto via telnet, and give
    route default netmask 0.0.0.0 dev ppp0
    one.
  4. Now it would take more than just the gateway IP of the DSL modem and the DNS server of your provider.

Port shares one can now easily perform using "iptables". Here the example of eMule ports:

TCP | 4661
TCP | 4662
UDP | 4665
UDP | 4672
Zielrechner bei mir war 192.168.1.2
iptables -t nat -A PREROUTING -j DNAT -p tcp -s 0/0 –-dport 4661 –-to-destination 192.168.1.2 -i ppp0
iptables -t nat -A PREROUTING -j DNAT -p tcp -s 0/0 –-dport 4662 –-to-destination 192.168.1.2 -i ppp0
iptables -t nat -A PREROUTING -j DNAT -p udp -s 0/0 –-dport 4665 –-to-destination 192.168.1.2 -i ppp0
iptables -t nat -A PREROUTING -j DNAT -p udp -s 0/0 –-dport 4672 –-to-destination 192.168.1.2 -i ppp0

DHCP server

  1. Ye logged via telnet to the modem
  2. Go to the directory / var / tmp and have here is the file where all records relating to the DHCP server udhcpd.conf be made.
  3. To change the configuration it just puts a udhcpd.conf from the network and then brings them to you via wget on the modem.

Here is my example:
start 192.168.0.3
end 192.168.0.254
inflease_time 604800
interface br0
opt router 192.168.0.1
opt dns 192.168.0.1
opt subnet 255.255.255.0
opt lease 3600
conflict_time 60
lease_file /var/tmp/udhcpd.leases

own HTTP server

  1. Is it any wonder again just log in via Telnet.
  2. Now enter "ps" and the "thttpd" services seek out and kill by fire.
  3. Now you create a new directory (mkdir "/ var / tmp / www /") and starts the server with
    /usr/sbin/thttpd -g -d /var/tmp/www -u root -p 80
    again.
  4. Now you can store it in the directory / var / tmp / www / your HTML files.

To have a way to perform all changes automatically on start up now I've found yet, unfortunately.

Sample page on the modem: body-snatcher.ath.cx

Mfg. BODY-Snatch

PS: If you did not understand something, only the and the by then still read and post here.

31st January 2006
Nerd 2.0

Fritz Box 2030 Telnet

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 this connection.
  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

6th June 2005
Nerd 2.0

New DSL modem

So I have my old modem to the swapped from my buddy and had the first configuration, therefore gabs no recent updates. The modem is a DLink DSL-360T with the latest Fireware. In the beginning, only the bridge function worked really make sense, but in the course of the time I discovered more and more features and is now my Inet sohalb again, but start at the beginning.

The DHCP server of the modem is totally bugged. He is only normal IPs from the specified range, but once you get to the Internetconnectet its Internet IP, that is no longer a connection with other computers in the network. So first DHCP.

When can browse the Internet, I realized then that you connect to the modem via telnet and then tried to configure Sun

On the 360T is a Linux-based operating system, which with a little Linux knowledge and a little adjustment period is actually quite handy.

Respect the modem has a READ-ONLY FILE SYSTEM

My current configuration looks like this.
In the webadmin connection data set for PPPOE connection (note, not anhacken "On Demand", otherwise is not the Internet;)). (As on Demand works I try desperately to find even just out.)
Then click Status -> Connection Status and dial.
Now log in via Telnet and "route default netmask 0.0.0.0 dev ppp0" command.
Now you can the "iptables" ports still further conduct, etc. (just as with NEM ROUTER Linux;)).

The Windows client now simply as:
IP 192.168.1 .*
Netmask: 255.255.255.0
Gateway: 192.168.1.1 (router)

and DNS of your provider.
(Available also under Status -> System Log -> primary DNS address *.*.*.*
secondary DNS address *.*.*.*)

The problem until now is still the only one stop every time you connect to "route" and the minute you enter must. once every 24 hours in the Webadmin need to connect to reboot.

For more tips I'd be very grateful.

And as an idea, how versatile is the modem looks you look at the page:
http://www.webalice.it/andrea.usenet/dsl-302t.htm

Maybe the FAQ, so soon to find on Google and I can help some desperate users.

Mfg. BODY-Snatch