ALT Linux sysadmins discussion
 help / color / mirror / Atom feed
From: Vladimir Elizarov <xengelpublicx@gmail.com>
To: ALT Linux sysadmin discuss <sysadmins@lists.altlinux.org>
Subject: Re: [Sysadmins] openwrt и asus wl-320ge
Date: Wed, 28 Jan 2009 11:54:54 +0300
Message-ID: <49801D5E.40205@gmail.com> (raw)
In-Reply-To: <20090128081203.GA22474@snowwhite.immo>

Pavlov Konstantin wrote:
> On Wed, Jan 28, 2009 at 10:59:38AM +0300, Vladimir Elizarov wrote:
>   
>> Пытаюсь залить прошивку через tftp. Делаю всё как написано в 
>> документации. Сделал hard-reset до асусвской прошивки (1.9.8.6)
>>
>> Выключил девайc
>> сделал:
>>
>> atftp --trace --option "timeout 1" --option "mode octet" --put --local-file openwrt-brcm-2.4-squashfs.trx 192.168.1.1
>>
>> и включил девайс
>>
>> показывает следующие:
>> Trace mode on.
>> Option timeout = 1
>> Option mode = octet
>> sent WRQ <file: openwrt-brcm-2.4-squashfs.trx, mode: octet <timeout: 1>>
>> source port mismatch, check bypassedtimeout: retrying...
>> sent WRQ <file: openwrt-brcm-2.4-squashfs.trx, mode: octet <timeout: 1>>
>> source port mismatch, check bypassedtimeout: retrying...
>> sent WRQ <file: openwrt-brcm-2.4-squashfs.trx, mode: octet <timeout: 1>>
>> source port mismatch, check byassedtimeout: retrying...
>> sent WRQ <file: openwrt-brcm-2.4-squashfs.trx, mode: octet <timeout: 1>>
>> source port mismatch, check bypassedtimeout: retrying...
>> sent WRQ <file: openwrt-brcm-2.4-squashfs.trx, mode: octet <timeout: 1>>
>> source port mismatch, check bypassedtimeout: retrying...
>> sent WRQ <file: openwrt-brcm-2.4-squashfs.trx, mode: octet <timeout: 1>>
>> source port mismatch, check bypassedtimeout: retrying...
>>
>>
>> связь между точкой и компом есть. Похоже на то что tftp не включен, на
>> странице wl-320ge про особое включение tftp ничего не написано. Как его всё-таки включить?
>>     
>
> В diag mode надо.
>
> В моем wl500gp это так:
>
> To install OpenWrt using TFTP or the ASUS firmware restoration tool you have to
> put the router in diag mode. To put the router in the diag mode, do this:
>
> * Unplug the router's power cord.
>
> * Confirm your PC is configured to request an address via DHCP.
>
> * Connect the router's LAN1 port directly to your PC.
>
> * Push the black RESTORE button using a pen or such, and keep the button pushed
> down.
>
> * Plug the power on while keeping the RESTORE button pushed for few
> seconds.
>
> * When you see a slowly blinking power light, you are in diag mode.
>
> * Now the router should accept an image via TFTP or via the ASUS firmware
> restoration tool. 
>
> In diag mode, the router takes address 192.168.1.1. It responds to ping, so you
> can confirm that it is in diag mode and ready for the tftp by using "ping
> 192.168.1.1".
>
> Note: I used the Asus tool to reflash the orginal asus firmware over kamikaze
> 7.09. In diag mode the asus kept the IP address assigned to it in kamikaze,
> which was not 192.168.1.1. The asus firmware restoration tool worked even
> though the asus in diag mode did not assign my PC an IP via DHCP and even
> though I could not ping the asus at 192.168.1.1. I had to use
> ethereal/wireshark to monitor traffic on LAN1 to figure out what I had set the
> IP address to. Then, using the proper IP address I could access the stock Asus
> web pages to use the "Reset to Factory Default" function and restore all
> settings to factory state. 
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Sysadmins mailing list
> Sysadmins@lists.altlinux.org
> https://lists.altlinux.org/mailman/listinfo/sysadmins
>   
Да. действительно в Diag mode всё получилось. Спасибо.



      reply	other threads:[~2009-01-28  8:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28  7:59 Vladimir Elizarov
2009-01-28  8:12 ` Pavlov Konstantin
2009-01-28  8:54   ` Vladimir Elizarov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49801D5E.40205@gmail.com \
    --to=xengelpublicx@gmail.com \
    --cc=sysadmins@lists.altlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux sysadmins discussion

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/sysadmins/0 sysadmins/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 sysadmins sysadmins/ http://lore.altlinux.org/sysadmins \
		sysadmins@lists.altlinux.org sysadmins@lists.altlinux.ru sysadmins@lists.altlinux.com
	public-inbox-index sysadmins

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.sysadmins


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git