search for: notyetopenwrt

...;On Sat, Sep 05, 2015 at 09:55:45AM -0500, John via Syslinux wrote: > > At 03:21 PM 9/2/2015, Geert Stappers via Syslinux wrote: > > > > Still having trouble: > > (-: Welcome to real life :-) > > > > > cd /tmp > >Please confirm that it is done at the notyetOpenWRT device at 192.168.1.1. >Saying that the test is done from/at another computer is also fine. >(Bonuspoints for telling the IP-address) This is entered in the bash shell on the computer and not on the router. The bash shell prompt shows the directory is changed on the PC (server end). > &g...

On Sat, Sep 05, 2015 at 09:55:45AM -0500, John via Syslinux wrote: > At 03:21 PM 9/2/2015, Geert Stappers via Syslinux wrote: > > Still having trouble: (-: Welcome to real life :-) > > cd /tmp Please confirm that it is done at the notyetOpenWRT device at 192.168.1.1. Saying that the test is done from/at another computer is also fine. (Bonuspoints for telling the IP-address) > > ping -c 3 192.168.0.9 # check if TFTP server respons on ping New test request: ping -c 3 192.168.1.9 # check if TFTP server respons on ping &gt...

Still having trouble: >> cd /tmp >> ping -c 3 192.168.0.9 # check if TFTP server respons on ping >> tftp 192.168.0.9 # connect to TFTP server, you should get a new prompt OK to here using 192.168.1.9 for NIC eth(0) and tftpd server 192.168.1.9 New prompt is tftp> >> get aa This times out and returns to tftp> Unable to return to shell using exit

...r set to 192.168.1.9 on the PC and so is the NIC eth(0) Acknowledge <snip/> > >And you are doing fine. You are curious, you presist, > >you want to get it working. > > > > > >Your Ubuntu PC, the computer at 192.168.1.9, can you connect to it from the > >notyetOpenWRT device? These three tests will tell us more > > I don't know how to try this. > I'll write another e-mail. > > # all three might time-out, report if they do > > telnet 192.168.1.9 23 # a connection refused is expected > > telnet 192.168.1.9 22 # a...