Aktueller Inhalt von stefanoIT

The solution I found was to insert the following lines in debug.cfg /usr/bin/ctlmgr_ctl w forwardrules settings/rule0/activated 1 (/bin/sleep 30; /sbin/ifconfig lan:1 192.168.178.19) & My firmware has debug.cfg working and I created a forward rule to IP 192.168.178.19 using web interface. I had...

What I am searching for is a way to do that using command line because ar7.cfg is overwritten at avery change in FB configuration.

Hello, my FB is a 7360 SL with a modified firmware 6.30 with telnet enabled (and debug.cfg too) I'm searching a way to create a portforwarding in debug.cfg because it is impossible create a porforwarding to 192.168.178.1 using web interface and the changes to ar7.cfg are lost if I change...

Hello, I have telnet access on my FB. Is it possibile to set a portforwarding using command line? Thanks s

Thank you for your reply. I solved the problem adding the following line to rc.tail.sh and repacking. ########################################################################################## ## user rc file...

There is a way to restore the execution of debug.cfg on boot in 7490 with firmware 6.30? I mean adding or changing a file under /etc/init.d and repacking the firmware with freetz? Thanks.

Hello, I'm trying to make my 7362SL multilingual with 6.30. I used freetz and my script to realize that: The script copy some file from 7360v2 international firmware to 7362SL firmware. #!/bin/bash WORKDIR="$1" SCNDSRC="$2" SRC=$SCNDSRC/original/filesystem...

I fixed the issue by executing my script under fakeroot too.

I unpacked the original firmware from sratch. STEP 1: UNPACK unpacking firmware image Skipping 0 Bytes garbage...unpacking update image Reading a different endian SQUASHFS filesystem on ../FRITZ.Box_7362_SL.131.06.30.image.mod/original/firmware/var/tmp/filesystem.image Filesystem...

Thanks for your help I did many attempts to find out what is the problem with that. I done this test: 1) unpacking the firmware 2) copy the original to modified with cp -a 3) touch file .modified 4) packing The result is that the devices are disappeared from the packed firmware and turned...

My process is: 1) unpacking the firmware 2) do patching (using script) 3) repacking firmware As you suggest the script create a copy of original folder (cp -r original modified) then create the .modified file. During the packing the /dev/* should be ignored and all 86 devices should be...

I found the devices under /dev are not properly created during packing. I can't fix this because it's a fwmod behavior

The files added by the copy and not removed during packing are the files in /dev (86 files in filesystem_core and 87 files in filesystem). I don't know if I have to remove them by hand to avoid the stucking during the boot. In my opinion the devices are not created properly during paking.

Hi @PeterPawn, something is wrong copyng original directory by hands as you suggested. Unpacking the original firmware this is the result STEP 1: UNPACK unpacking firmware image Skipping 0 Bytes garbage...unpacking update image Reading a different endian SQUASHFS filesystem on...

Just for the records. The device never restarts. It remains blocked on trying /sbin/init for ever. In your opinion, the numer of files present in filesystem_code is important? Thanks.