Re: n2100/redboot/tftp timeouts
- To: Jon Dowland <jon+debian-arm@alcopop.org>
- Cc: debian-arm@lists.debian.org
- Subject: Re: n2100/redboot/tftp timeouts
- From: Tobias Frost <tobi@coldtobi.de>
- Date: Wed, 19 Mar 2008 21:14:22 +0100
- Message-id: <1205957662.11620.0.camel@mordor>
- In-reply-to: <20080319194901.GA14029@konishi.dowland>
- References: <20080319194901.GA14029@konishi.dowland>
Did you specify the ip_address with
ip_address -h <host_ip>
ip_address -l <thecus_ip>
On Wed, 2008-03-19 at 19:49 +0000, Jon Dowland wrote:
> Hi folks,
>
> I finally got a serial console soldered on :) So now I try
> to use redboot's tftp to yank a kernel across the network.
>
> RedBoot> load -r ramdisk.arm -b 0x00800000
> Using default protocol (TFTP)
> timeout
>
> I cannot get the poor thing to grab kernels/ramdisks. I've
> tried two hosts for the tftpd server, and two tftpds on one
> host (atftpd and tftpd-hpa). I've also tried specifying the
> local IP in redboot so the packet src wasn't 0.0.0.0.
>
> I can tftpd between other hosts fine, so it isn't
> paths/permissions. wireshark shows the packets hitting the
> interface, but no attempt is made at responding. Is
> something throwing away the packets before they reach
> userland? It's not a firewall, maybe the IP stack's spoof
> protection?
>
> I notice the dest MAC is set as being the same as the
> source. Attached is a wireshark dump of two packets; there
> were no replies.
>
> RedBoot> version
>
> RedBoot(tm) bootstrap and debug environment [ROM]
> Red Hat certified release, version 1.93 - built
> 19:55:20, Aug 8 2006
>
> Platform: THECUS N2100 (IOP80219) Copyright (C)
> 2000, 2001, 2002, Red Hat, Inc.
>
> RAM: 0x00000000-0x20000000, 0x0004b648-0x1ffd1000
> available, total: 512 MB FLASH: 0xf0000000 -
> 0xf1000000, 128 blocks of 0x00020000 bytes each.
>
>
Reply to: