|
|
| Line 3: |
Line 3: |
| | Enabling telnet up to Firmware v2.3.3A | | Enabling telnet up to Firmware v2.3.3A |
| | -------------------------------------- | | -------------------------------------- |
| - | The telnet daemon can be legally enabled by the web frontend. The option to do so is *not* visible in the menu but the corresponding page ist existing. To get the page displayed log into you�¢ï¿½ï¿½re NAS device using the web frontend. Assuming that the device has the IP address 192.168.0.13 you can then call the telnet setup page. While logged on chance the URL to | + | The telnet daemon can be legally enabled by the web frontend. The option to do so is *not* visible in the menu but the corresponding page ist existing. To get the page displayed log into you������¢���¯���¿���½���¯���¿���½re NAS device using the web frontend. Assuming that the device has the IP address 192.168.0.13 you can then call the telnet setup page. While logged on chance the URL to |
| | | | |
| | http://Dual-NAS-IP/html/telnet/telnet.html | | http://Dual-NAS-IP/html/telnet/telnet.html |
| | | | |
| | The next display looks weird, but you if you check the checkbox and press the button telnet is enabled for you. Of course you can disable telnet here, too. | | The next display looks weird, but you if you check the checkbox and press the button telnet is enabled for you. Of course you can disable telnet here, too. |
| - |
| |
| - |
| |
| - |
| |
| - | Flash/Recover Firmware
| |
| - | ----------------------
| |
| - |
| |
| - | Here�s the step by step question/answer when you�re connected to the RedBoot.
| |
| - |
| |
| - | A last info, each time the redboot has completed a download (Waiting to receive file �.) he will disable the ethernet while flashing, so you will not see the dots progress (wait 1 to 5 min each time, ethernet is automaticaly reactivted by redboot after each flash-session). The ethernet is disable while flashing because of pins-sharing between Flash / IDE / EMAC / PCI / UART / GPIO (http://www.storlinksemi.com/an3316-04.htm). But now, let�s go baby :
| |
| - |
| |
| - | root@burg ~ #
| |
| - | root@burg ~ # arping -f 192.168.2.71 ; telnet 192.168.2.71 9000
| |
| - | ARPING 192.168.2.71 from 192.168.2.5 eth0
| |
| - | Unicast reply from 192.168.2.71 [7A:B3:F4:00:01:AC] 6.435ms
| |
| - | Sent 19 probes (19 broadcast(s))
| |
| - | Received 1 response(s)
| |
| - | Trying 192.168.2.71�
| |
| - | Connected to nas.home.fr (192.168.2.71).
| |
| - | Escape character is �^]�.
| |
| - | ==> enter Ctrl+C to abort booting within 2 seconds ��
| |
| - | ^C
| |
| - | Boot Menu
| |
| - | ====================================================================
| |
| - | 1: Start the Kernel Code
| |
| - | 2: List Image
| |
| - | 3: Delete Image
| |
| - | 4: Create New Image
| |
| - | 5: Set IP adderss
| |
| - | 6: Setting MAC address
| |
| - |
| |
| - | X:Upgrade Boot Y:Upgrade Kernel
| |
| - |
| |
| - | => Select: 2
| |
| - | 4
| |
| - | Name FLASH addr Mem addr Datalen Entry point
| |
| - | BOOT 0�70000000-7001FFFF 0�70000000 0�00020000 0�70000000
| |
| - | FIS directory 0�707F0000-707FFFFF 0�707F0000 0�00001400 0�00000000
| |
| - | Kern 0�70020000-7019FFFF 0�01600000 0�0016FDD4 0�01600000
| |
| - | Ramdisk 0�701A0000-7039FFFF 0�00800000 0�001D9FC6 0�00000000
| |
| - | Application 0�703A0000-707BFFFF 0�00000000 0�0041EB1F 0�00000000
| |
| - | CurConf 0�707D0000-707EFFFF 0�00000000 0�00020000 0�00000000
| |
| - | VCTL 0�707C0000-707CFFFF 0�00000000 0�00010000 0�00000000
| |
| - |
| |
| - | Boot Menu
| |
| - | ====================================================================
| |
| - | 1: Start the Kernel Code
| |
| - | 2: List Image
| |
| - | 3: Delete Image
| |
| - | 4: Create New Image
| |
| - | 5: Set IP adderss
| |
| - | 6: Setting MAC address
| |
| - |
| |
| - | X:Upgrade Boot Y:Upgrade Kernel
| |
| - |
| |
| - | => Select: 4
| |
| - |
| |
| - | Image Name: Kern
| |
| - | Flash Address: 0�70020000
| |
| - | Memory Address: 0�01600000
| |
| - | Entry Point: 0�01600000
| |
| - | An image named �Kern� exists - continue (y/n)? y
| |
| - | 1: Download by X-modem
| |
| - | 2: Download by TFTP
| |
| - | 2
| |
| - | TFTP Server IP Address: 192.168.2.5
| |
| - | Image Path and name(EX. /images/zImage): /zImage
| |
| - | Waiting to receive file �.
| |
| - | -
| |
| - | Raw file loaded 0�01000000-0�0116fdd3, assumed entry at 0�01000000
| |
| - | Erase flash �
| |
| - | � Erase from 0�70020000-0�70190000: �������..
| |
| - | OK!
| |
| - | � Program from 0�01000000-0�0116fdd4 at 0�70020000: �������..
| |
| - | OK!
| |
| - | Update FIS �
| |
| - | � Erase from 0�707f0000-0�70800000: .
| |
| - | � Program from 0�00400000-0�00410000 at 0�707f0000: .
| |
| - | OK!
| |
| - | Upload �Kern� code successfully!
| |
| - | Boot Menu
| |
| - | ====================================================================
| |
| - | 1: Start the Kernel Code
| |
| - | 2: List Image
| |
| - | 3: Delete Image
| |
| - | 4: Create New Image
| |
| - | 5: Set IP adderss
| |
| - | 6: Setting MAC address
| |
| - |
| |
| - | X:Upgrade Boot Y:Upgrade Kernel
| |
| - |
| |
| - | => Select: 4
| |
| - |
| |
| - | Image Name: Ramdisk
| |
| - | Flash Address: 0�701A0000
| |
| - | Memory Address: 0�00800000
| |
| - | Entry Point: 0�00800000
| |
| - | An image named �Ramdisk� exists - continue (y/n)? y
| |
| - | 1: Download by X-modem
| |
| - | 2: Download by TFTP
| |
| - | 2
| |
| - | TFTP Server IP Address: 192.168.2.5
| |
| - | Image Path and name(EX. /images/zImage): /rd.gz
| |
| - | Waiting to receive file �.
| |
| - | \\
| |
| - | Raw file loaded 0�01000000-0�011d9fc5, assumed entry at 0�01000000
| |
| - | Erase flash �
| |
| - | � Erase from 0�701a0000-0�70380000: ����������
| |
| - | OK!
| |
| - | � Program from 0�01000000-0�011d9fc6 at 0�701a0000: ����������
| |
| - | OK!
| |
| - | Update FIS �
| |
| - | � Erase from 0�707f0000-0�70800000: .
| |
| - | � Program from 0�00400000-0�00410000 at 0�707f0000: .
| |
| - | OK!
| |
| - | Upload �Ramdisk� code successfully!
| |
| - | Boot Menu
| |
| - | ====================================================================
| |
| - | 1: Start the Kernel Code
| |
| - | 2: List Image
| |
| - | 3: Delete Image
| |
| - | 4: Create New Image
| |
| - | 5: Set IP adderss
| |
| - | 6: Setting MAC address
| |
| - |
| |
| - | X:Upgrade Boot Y:Upgrade Kernel
| |
| - |
| |
| - | => Select: 4
| |
| - |
| |
| - | Image Name: Application
| |
| - | Flash Address: 0�703A0000
| |
| - | Memory Address: 0�00000000
| |
| - | Entry Point: 0�00000000
| |
| - | An image named �Application� exists - continue (y/n)? y
| |
| - | 1: Download by X-modem
| |
| - | 2: Download by TFTP
| |
| - | 2
| |
| - | TFTP Server IP Address: 192.168.2.5
| |
| - | Image Path and name(EX. /images/zImage): /hddapp.tgz
| |
| - | Waiting to receive file �.
| |
| - | -
| |
| - | Raw file loaded 0�01000000-0�0141eb1e, assumed entry at 0�01000000
| |
| - | Erase flash �
| |
| - | � Erase from 0�703a0000-0�707c0000: ����������������������
| |
| - | OK!
| |
| - | � Program from 0�01000000-0�0141eb1f at 0�703a0000: ����������������������
| |
| - | OK!
| |
| - | Update FIS �
| |
| - | � Erase from 0�707f0000-0�70800000: .
| |
| - | � Program from 0�00400000-0�00410000 at 0�707f0000: .
| |
| - | OK!
| |
| - | Upload �Application� code successfully!
| |
| - | Boot Menu
| |
| - | ====================================================================
| |
| - | 1: Start the Kernel Code
| |
| - | 2: List Image
| |
| - | 3: Delete Image
| |
| - | 4: Create New Image
| |
| - | 5: Set IP adderss
| |
| - | 6: Setting MAC address
| |
| - |
| |
| - | X:Upgrade Boot Y:Upgrade Kernel
| |
| - |
| |
| - | => Select: 1
| |
| - |
| |
| - | Wait 5 min � It�s done ! You nas is alive !
| |
| - |
| |
| - | Best regards, Samuel
| |
The telnet daemon can be legally enabled by the web frontend. The option to do so is *not* visible in the menu but the corresponding page ist existing. To get the page displayed log into you������¢���¯���¿���½���¯���¿���½re NAS device using the web frontend. Assuming that the device has the IP address 192.168.0.13 you can then call the telnet setup page. While logged on chance the URL to
The next display looks weird, but you if you check the checkbox and press the button telnet is enabled for you. Of course you can disable telnet here, too.
