TFTP WITH WRV210

Hi
I have a WRV210 Router. I am unable to access the web interface but the DHCP Server for the router is operational. I have tried to reset to defaults but this does not work. I have also tried to upgrade the firmware and restore a configuration file via tftp but it times out. Please advise if there is another way to recover this router.

Yes I did all this already. I can ping the gateway ip address of 192.168.1.1 but i cannot tftp the backup image file for the router nor the firmware upgrade.

Similar Messages

TFTP with timestamp

Hi
We got C2960 switch. May I know how to use kron autobackup by using TFTP with timestamp?
Hugo

How to change the timestamp format, I got error as follow?
2960G#sh archive
The next archive file will be named tftp://192.168.1.1/2960G-Feb-24-10:33:34-cfg-1
Archive # Name
0
1 :Error - Bad file number
Timestamp config:
service timestamps debug datetime localtime
service timestamps log datetime localtime

How do I correctly configure TFTP?

Hi again!
Now that I'm talking to my serial device, I need to provide it with a TFTP server (on an Ethernet) from which it can install its firmware. OS X, being UNIX, should be perfectly capable of running such a server. So, I looked around, found the xinetd and xinetd.conf man pages, set 'enable = yes' in /private/etc/xinetd.d/tftp, verified that /usr/libexec/tftpd exists, put the files to be served in /private/tftpboot, poked a hole in my firewall for port 69, and rebooted.
No joy. Using the Console utility to view the system.log, I do see xinetd starting tftpd in response to requests from my device's IP-address -- so it appears that the requests are getting through the firewall and are recognized by xinetd, and it is starting tftpd. However, the client on the device is claiming that the connection is timing out (in its cryptic way -- it is saying ' T'), and it is retrying every 5 seconds.
I can't see a way to get any more detailed information from tftpd about the problem. Has anyone successfully set up the stock OS X xinetd/tftpd ? Is there some step I'm obviously missing? Does anyone know how to get details of errors tftpd encounters?
Thanks!

Obviously my dump is showing 7 packets capt, 7 rec by filt, 0 pkts dropped by kernel. But we knew it was working. Just a cross check. On system pref pane, I did new, with port 69, tftp with check on. Now when I did this last night and this am(it wouldn't stay after sleep) I originally typed on the new(under firewall) tftpd because without the d it wouldn't let me ok it. So I did with d, ok'd it, and it now, and last night shows 2 entries of port 69(one w/tftpd & one w/tftp). I don't know why it took that way, but it does and works. And my xinetd is like your directions. My bs.txt in /private/tftpboot are 400(rrr) owned by me, and /private/tftpboot is root w/rwxr-xr-x. And(forget the structure of disable = no, for it still works and isn't worth the change).
service tftp
cps = 200 5
disable = no
socket_type = dgram
wait = yes
user = nobody
server = /usr/libexec/tftpd
server_args = /private/tftpboot
groups = yes
flags = REUSE
}

Wip310: problema con tftp ringtone

intento enviar un tono vía tftp con la siguiente
sintaxis:
http://10.100.40.123/ringtone1?tftp://10.100.40.2/tonos/alarma1.mid
y obtengo el resultado "failed":
Las rutas de origen y destino son correctas.
He probado a poner en EXT1 Line enable "NO" para hacer el tftp
El firmware es 5.0.13(04261322)

I translate the problem........
I try to send a ringtone via tftp with the following syntax:
1st Image
and get the result "failed"
2nd Image
the paths are correct.
I tried to put in EXT1 -> LINE ENABLE "no" to make the tftp.
The firmware is 5.0.13 (04261322)

Bulk Phone Resets and TFTP Performance

I have approximately 1500 7941/61 phones in Callmanager 4.1(3)SR2 that are to be upgraded with the 8.0(3) phone load. I plan to reset the devices via device search (not device pool) and we want to know the estimated system impact and overall time to process all of the requests. We have a cluster of 3 7845 Callmanagers, all enabled for TFTP, with priority to sub2, sub1, Pub.

Thanks! This is the info I needed.
We actually ran the update last week with catastrophic results. Although we have three TFTP servers, they were set to the default of 200. Approximately 400 of the phones hung on the reboot, stopped dead and not registering to Callmanager, with no way to reset. We opened a P1 with TAC. They said the multiple TFTP servers should have handled the requests just fine (we're using three 7845s). Recommendation was to shut/no shut switchport interfaces to hopefully reboot the phones - no luck. Even reloading the switches didn't do it, because apparently there is still some power provided to the ethernet interface somehow. The ONLY sure fix was to unplug and reconnect each IP phone ... all 400 of them. In a college campus of 60-70 buildings and multiple IDFs per building let's just say is was a real long night. We're still not sure if this was a TFTP performance issue or an issue with the 7.0(2) to 8.0(3) phone loads.
Thanks again for your help.

Resetting PIX 515E 'enable' password and/or Factory Reset

                   We have a PIX Firewall where the last user of the device had not changed the 'enable' password and username so we are locked out of the device. I did some research and found a password reset tool that was supposed to clear the 'enable' password on the device. I set up a TFTP with the 'np61.bin' file needed. I went into 'monitor>' mode, set the interface, address and server address and it pings with success. I pointed it at the file and sent the 'tftp' command. I saw it downloading and booting off the binary file and after letting it go for a little bit (I walked away for a little while and came back to my telnet prompt) I noticed it was stuck in a loop:
No bootable image in flash. Please download an image from a network server in the monitor mode
Failed to find an image to boot
Rebooting......
                    I downloaded a copy of the latest firmware, 'pix804-28.bin', and repeated the process used for the password reset file. After loading, I am greeted with my familiar prompt:
XXXX-XXX-Xx-Xx0-XX>
XXXX-XXX-Xx-Xx0-XX>enable
Username: pix
Password: pix
Username: pix
Password:
Username: cisco
Password: cisco
Access denied.
XXXX-XXX-Xx-Xx0-XX>
                    I then did a hard reset, and was stuck back in the loop I was in before, asking me to reflash a boot image. I now need to somehow load the IOS back onto the router (As it seems to just be booting from the TFTP server), and then after that still remove the enable password or somehow default the entire firewall to Factory Defaults. If anyone knows how to solve my issue or has any ideas for me to try, you help would be greatly appreciated, thanks!

Still having trouble with this, has no one encountered this problem before?

I can't get rid of firmware for WRT54RS flashed on WRT54GL router

Today I tried (unsuccesfull) to reset my router back to factory default.
Unfortunately I found that the IP address did not reset to factory default.
But I still can ping the device.
So I checked the firmware by logging into the device.
B.t.w the admin account credentials changed back to factory default.
First I checked the model of the router and compared that with the firmware within the device.
Then I found the mismatch, the device specs say it's a WRT54GL and the installed firmware says it's WRT54GS.
This seem to be some custom made firmware of some kind.
In the administration section, I found that the firmware update tab is missing.
I then googled for some methods trying to flash the device with the appropriate firmware.
At first I tried the 30/30/30 reset procedure, after reboot still the same settings, so no luck here.
Next I tried tftp with the appropriate firmware version.
After specifying the location of firmware, entering the device password (which happen to be the default due to earlier reset), I then hit the start button.
Some leds start to flicker, then after about 20 seconds the error text occur "unable to get a response from the server".
So I can't get rid of this mismatch firmware here.
What do I do next?
How about jtag?
Assumption is the cause of all misery

Hi wrtlinksys-user, you can try to do a funny reset on the router. To do it, just press and hold the reset button on the device for 30 seconds and when you reach 20 seconds while counting, simply unplug and replug the power adapter of the router. Update us if this will help you.

Cisco ACE key.pem import error

Hi
after extracting the Cert.pem and Key.pem from the PXF file.
i am get the following error trying to import the Key.pem file to the ACE
ENG-CTN-ACE01/Admin# crypto import tftp 10.3.31.249 key5.pem key5
Trying to connect to tftp server......
TFTP get operation was successful
3294 bytes copied
Successfully imported file from remote server.
Error: File not of supported key or certificate type - RSA, import failed.
ENG-CTN-ACE01/Admin#
* i have decrypted the key.pem and tried adding the key manually with crypto import terminal command but still getting the same error.
can you please assist as want am i doing wrong.
the cert has been uploaded successfully.
Filename                                 File File    Expor      Key/
                                         Size Type    table      Cert
cisco-sample-cert                        1082 PEM     Yes        CERT
cisco-sample-key                         887   PEM     Yes         KEY
wildcard-20140102.cer                    1459 DER     Yes        CERT
Thanks
rayyaan

HI Rayyaan,
This is a key which you cannot share so that i can try here on my and see what is going on so i would suggested contacting your CA vendor and ask them to provide the key and cert in PEM format. Once you have that try it again. That's all i guess we can do here or you can open a TAC case and see what is going on. If the key is in PEM format ACE shouldn't have any problem in accepting it.
From user guide:
Importing Certificate and Key Pair Files
The ACE supports the importation of PEM-encoded key pairs and certificates (including wildcard certificates) signed by keys. The ACE allows a maximum public key size of 4096 bits. The maximum private key size is 2048 bits.
You can import a certificate or key pair file to the ACE from a remote server by using the crypto import command in Exec mode. You can import either individual certificates and keys or multiple certificates and keys. Because a network device uses its certificate and corresponding public key together to prove its identity during the SSL handshake, be sure to import both the certificate file and its corresponding key pair file.
The ACE supports the importation of PEM-encoded SSL certificates and keys with a maximum line width of 130 characters using the terminal. If an SSL certificate or key is not wrapped or it exceeds 130 characters per line, use a text editor such as the visual (vi) editor or Notepad to manually wrap the certificate or key to less than 130 characters per line. Alternatively, you can import the certificate or key by using SFTP, FTP, or TFTP with no regard to line width
Regards,
Kanwal

SG300-10MP Firmware Upgrade Fails

Trying to upgrade a SG300-10MP from firmware revision 1.10.68 to 1.3.5.58 when I try to upgrade I keep getting an error that says
"Error Message: Copy: Illegal software format"
I have tried using the HTTP copy as well as TFTP with the same results. I have tried upgrading to a few other older releses and get the same error.
Any thoughts?

Looks like Cisco small business products dont support the cisco network assistant. I have tried the web console with both Internet Explorer and Firefox.

Can you use the result of a "zone copy" to restore

If I'm doing major changes to zones/zonesets I always do a
zone copy vsan xxx active-zoneset bootflash:/backup/zoneset-vsanxxx
I have a script that will take this file and re-create the the whole zoneset from scratch. I was told that there is a direct way to accomplish this - somehow copy the bootflash:/backup/zoneset-vsanxxx -> vsan xxx active-zoneset ?
I know the phoney command I just dreamed up does not appear to exist but is there a way to do that via cli ?

Hello Bruce,
There is other way,
Assuming your zone file on tftp with file name zonetest
you need to modify the file and add "conf t" on the first line, then add "member" before any line with "pwwn"
put back the file to booflash, then run:
mds1# runscript bootflash:zonetest
This will put back the zones
There is no other CLI way

Softphone Handsets (not Headsets)

Does anyone know if any USB handset such as Sogatel - Skype compatible USB desktop speaker desk phone - LCD screen would work with BT Softphone, I'm tired of using headsets.

first you need configure ephone and dn on ccme site b
then
you can reconfigure your cipc with tftp address of site b (same ip address of ccme)
your cipc get configuration trough tftp
tftp-server flash:..... is for firmware and locale upgrade
while the xml config is stored in ram
you can view all file binding by tftp with this command
show telephony-service tftp-bindings

Linksys SRW224G4 FIRMWARE UPDATE

Hi, i want to update firmware to a Linksys SRW224G4 switch.
My switch model and version are:
Serial Number
Model Name
SRW224G4
Hardware Version
00.03.00
Boot Version
1.0.2
Firmware Version
1.2.1b
I try update firmware via http, but nothing occurs. I download firmware version 1.2.3 (latest)
I try TFTP with the same result.
I get no messages, no error, no logs, nothing.
I`m using VLAN, and trying update from a notebook conected to a managed port.
I try reboot, turn it off and on, but firmware don`t update.
What I`m doing wrong?
Where can I found a manual step by step to update Linksys Switch?
I have three of them and I want to be most update possible.

Can some one please help....
I have exactly same problem
We have a SRW224G4 V1.1 Switch.
Serial Number
Model Name
SRW224G4
Hardware Version
00.03.00
Boot Version
1.0.2
Firmware Version
1.2.1b
On the Front of the Switch it say SRW224G4 v1.1
Is it possible to upgrade to Firmware version 1.3.2.0. ... because I can't get it to load this firmware.
I'm doing it via HTTP upgrade and when it restarts after upgrading, it returns to the current Version 1.2.1.b again.
Have I misunderstood something???
Firmware file is 1.3.2.0.ros
And I have done like discribed i the following link:
http://www.cisco.com/en/US/products/ps9967/products_qanda_item09186a0080a36480.shtml
Release Notes attached as PDF File and user guide
Is it possible to contact Cisco direct by mail about this????

Config file from tftp at startup (6509 with Sup720)

Hi together
I will download the config file for my 6509 with Sup720 from a TFTP Server.
I have configerd the GigabitEthernet 5/2, so I can ping the tftp-server. Also I'm able to down&upload files to the tftp-server.
The configuration looks like:
hostname Testrouter
boot host tftp run 192.168.88.250
boot network tftp run 192.168.88.250
interface GigabitEthernet5/2
switchport
no ip address
media-type rj45
interface Vlan1
ip address 192.168.88.9 255.255.255.0
The service config command is also set!
The big problem is, the router comes up normaly and do not access the tftp-server in any way :-(
Have anyone a idea?
Thanks a lot in advance
Cheers Ralph

I have done it now in this way, but without any improvement! :-(
Here is my config:
(I found the ip tftp ? command!)
hostname Router
boot host tftp://192.168.88.250/run
boot network tftp://192.168.88.250/run
no aaa new-model
ip subnet-zero
ip tftp source-interface GigabitEthernet5/2
ip tftp boot-interface GigabitEthernet5/2
interface GigabitEthernet5/2
ip address 192.168.88.9 255.255.255.0
media-type rj45
ip default-gateway 192.168.88.250
I'm able to ping the TFTP Server...
Router#ping 192.168.88.250
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.88.250, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
Router#
Have anyone any idea??
Cheers Ralph

[SOLVED] Netbooting with PXE, TFTP and NFS / Numerous errors

Greetings all, hope you can help me out.
Been given a task by my company of making a network bootable ICA client (with X and Firefox, with the Citrix ICA client installed) as small as possible to minimize network traffic (as 440 workstations would be downloading the end-product simultaneously, so it'd beat ten bells of proverbial out of the core and edge switches for a little while). I discovered two options. One being to integrate everything in side a cloop image directly inside the INITRD. I have stacks of working INITRDs with their matched kernels yet being my first dabble in to extracting the INITRD, my faffing with CPIO has resulted in me nuking my base layout (Thank god for snapshotting in VMware Workstation!) 4 times, and either getting "Premature end of file" or a copius amount of lines stating "cpio: Malformed Number: <strange characters>" finally ending with "Premature end of file". As a result I went in search of another option, which would be booting off an NFS share. I followed the guide:
http://wiki.archlinux.org/index.php/Dis … t_NFS_root
...in order to set up a network booted install of Arch and hit a few snags along the way, probably a result of using multiple operating systems for the TFTP and NFS server as opposed to using what the guide recommends, but I'm not sure as these seem solvable, although I don't know how right now.
The set up:
DHCP is provided by a Microsoft Windows Server 2003 VM (AD Integrated) on 172.16.10.17 on a box called "Rex".
TFTP is provided by another Windows Server 2003 VM by "TFTPd32" which is a free download. This is located on 172.16.10.158 on a box called "Terra".
The NFS store is provided by OpenFiler 2.3 which is a specialized version of rPath Linux designed specifically for turning boxes in to dedicated NAS stores. This is located on 172.16.10.6, and is called "frcnet-nas-1".
The problem:
DHCP is correctly configured with a Boot Host Name (Which is 172.16.10.158) and a boot file name of "pxelinux.0". This is confirmed as working.
Client gets the kernel and INITRD from TFTP and boots up fine until it hits "Waiting for devices to settle..." by which point it echos out "Root device /dev/nfs doesn't exist, attempting to create it...", which it seems to do so fine. It then passes control over to kinit and echos "INIT: version 2.86 booting" and the archlinux header, and immediately after that it prints:
mount: only root can do that
mount: only root can do that
mount: only root can do that
/bin/mknod: '/dev/null': File exists
/bin/mknod: '/dev/zero': File exists
/bin/mknod: '/dev/console': File exists
/bin/mkdir: cannot create directory '/dev/pts': File exists
/bin/mkdir: cannot create directory '/dev/shm': File exists
/bin/grep: /proc/cmdline: No such file or directory
/etc/rc.sysinit: line 72: /proc/sys/kernel/hotplug: No such file or directory
:: Using static /dev filesystem [DONE]
:: Mounting Root Read-only [FAIL]
:: Checking Filesystems [BUSY]
/bin/grep: /proc/cmdline: No such file or directory
:: Mounting Local Filesystems
mount: only root can do that
mount: only root can do that
mount: only root can do that
[DONE]
:: Activating Swap [DONE]
:: Configuring System Clock [DONE]
:: Removing Leftover Files [DONE]
:: Setting Hostname: myhost [DONE]
:: Updating Module Dependencies [DONE]
:: Setting Locale: en_US.utf8 [DONE]
:: Setting Consoles to UTF-8 mode[BUSY]
/etc/rc.sysinit: line 362: /dev/vc/0: No such file or directory
/etc/rc.sysinit: line 363: /dev/vc/0: No such file or directory
/etc/rc.sysinit: line 362: /dev/vc/1: No such file or directory
/etc/rc.sysinit: line 363: /dev/vc/1: No such file or directory
... all the way down to vc/63 ...
:: Loading Keyboard Map: us [DONE]
INIT: Entering runlevel: 3
:: Starting Syslog-NG [DONE]
Error opening file for reading; filename='/proc/kmsg', error='No such file or directory (2)'
Error initializing source driver; source='src'
:: Starting Network...
Warning: cannot open /proc/net/dev (No such file or directory). Limited output.
eth0: dhcpcd 4.0.3 starting
eth0: broadcasting inform for 172.16.10.154
eth0: received approval for 172.16.10.154
eth0: write_lease: Permission denied
:: Mounting Network Filesystems
mount: only root can do that
[FAIL]
:: Starting Cron Daemon [DONE]
...and, nothing after that, it just stops. Kernel doesn't panic, and hitting ctrl+alt+delete does what you'd expect, a clean shutdown minus a few errors about filesystems not being mounted. It seems /proc isn't getting mounted because init apparently doesn't have the appropriate permissions, and /proc not being mounted causes a whole string of other issues. Thing is, proc gets created at boot time as it contains kernel specific information about the system and the kernel's capabilities, right? Why can't it create it? How come init doesn't have the same privileges as root as it usually would, and how would I go about fixing it?
I admit, while I'm fairly competent in Linux, this one has me stumped. Anyone have any ideas?
Last edited by PinkFloydYoshi (2008-11-22 12:29:01)

The idea behind the Windows DHCP and TFTP is that we'd be using an existing server and a NetApp box with NFS license to serve everything off. I would have loved to make a new server which is completely Linux, but my boss, nor the other technician have ever used Linux so if I left for any reason, they'd be stuck if ever they ran in to trouble, which is why I've struggled to get Linux to penetrate our all Windows infrastructure.
During my hunting around on Google I found a lot of information on making my own initrd, and a lot of it using all manner of switches. I can make them fine, but I figure that I would need to look at extracting the current working one first, adding X, Firefox and the ICA client to it, then compressing it again. Cloop came about when I was looking at DSL's internals. The smaller the initrd, the better, so utilizing this could possibly be a plus too.
The reason I'm doing this with Archlinux is that I know Arch's internals quite well (and pacman is just wonderous, which is more than I can say for yum), so if I run in to a small problem I'm more likely to fix it without consulting Google. Fair enough though, the NFS booting method is giving me issues I never thought were possible. Ahh, sods law strikes again.
Addendum: I've noticed something which struck me as odd. Files in the NFS share are somehow owned by 96:scanner instead of root:root. Upon attempting changing, it's telling me "Operation Not Permitted". Further prodding has led me to believe it's an Openfiler thing where GID/UID 96 on the OpenFiler box is "ofgroup"/"ofguest". Chowning / to root:root puts NFS boot right ahead and gives me a prompt, however I cannot log in as root. I've also discovered that chrooting in to the base from my Arch workstation and creating a directory makes the directory owned by ofgroup:ofguest again, so it's an Openfiler thing after all this time. Prodding further.
Addendum two: For anyone using Openfiler out there, when you allow guest access to the NFS share, be sure to set the Anonymous GID and Anonymous UID to 0. By default it's 96 and as a result when trying to boot you get the errors I experienced. This is insecure and you should use some sort of network/host/ip range restriction. Because the root filesystem has 96:96 as the owner of everything after you install the base layout using pacman (and any changes you make afterward) init and root no longer have the appropriate permissions, user 96:96 (which is "scanner" in Archlinux) has the permissions instead and init, in order to complete boot would need to be "scanner" in order to boot completely.
Solution is to set Anon GID and Anon UID to 0, chown the entire diskless root filesystem to root, then use a linux desktop to mount the diskless root filesystem, mount /proc, /sys and mount bind /dev, then chroot in to the diskless root filesystem. At this point to clear up any problems with bad passwords, use passwd to change your password. Exit the chroot environment then unmount the diskless proc, sys and dev. Boot up via the network and use your chosen password to log in as root. At this point, start clearing up permissions from the en masse filesystem chown and you should then have a usable diskless root.
I'll experiment further and clear up some of the remaining permission errors that occured during boot and report on my progress in fixing it. Didn't like the idea of chowning the entire share as root. :S
Last edited by PinkFloydYoshi (2008-11-21 19:28:15)

Cisco 8945 PC Port not workign with Alternate TFTP ON

I have a Cisco 8945 at home (Internet provided via Cable modem), and it had been working just fine. I have now found that the PC port on the phone will not pass data to my PC with Alternate TFTP on. I know the cabling is all correct, I can actually go into the Cisco phone and DISABLE the alternate TFTP servers on the phone. When I do that the phone no longer works, but the pass through to the PC network port works and my PC connects to the Internet fine.
Enable the alternate TFTP servers again so my phone works, and my PC LAN adapter now thinks there is no longer a cable plugged into it.
What about the TFTP server being enabled (which is required to get my phone to work of the corporate VOIP switch up in Boston), kills the PC port connectivity on the phone?

I have a Cisco 8945 at home (Internet provided via Cable modem), and it had been working just fine. I have now found that the PC port on the phone will not pass data to my PC with Alternate TFTP on. I know the cabling is all correct, I can actually go into the Cisco phone and DISABLE the alternate TFTP servers on the phone. When I do that the phone no longer works, but the pass through to the PC network port works and my PC connects to the Internet fine.
Enable the alternate TFTP servers again so my phone works, and my PC LAN adapter now thinks there is no longer a cable plugged into it.
What about the TFTP server being enabled (which is required to get my phone to work of the corporate VOIP switch up in Boston), kills the PC port connectivity on the phone?

TFTP WITH WRV210

Similar Messages

Maybe you are looking for