Many NICs can connect to the LaFonera directly with a normal cable, the LaFonera may have an autosensing auto-sensing port making a crossover cable unnecessary
Can anyone else verify this? If this is true, then it would make the flashing process that much easier!
Joined: 28 Jun 2006 Posts: 19 Location: Washington D.C.
Posted: Tue Mar 13, 2007 11:03 Post subject:
I haven't had any problems using a regular CAT5 cable into the Fonera... It's able to use both from my experience. You shouldn't have to get a crossover.
You may need a crossover network cable or two normal cables and a hub/switch/router to connect your PC to the LaFonera. If the network card you're using does not support auto-detection of connections (newer cards _usually_ do but not always) then you will need the cables and hub/switch.
Can someone please help me?
I did everything the video and wiki says. Everything went fine with no errors at all. But just after I type the last reset, it rebooted and bricked. I can access to redboot + ethernet cable. I tried to:
If you've managed to get partway through this guild and find the LaFonera doesn't seem to respond anymore, here are a few recovery tricks.
Set your computer's network card IP to 169.254.255.2 and the Subnet mask to 255.255.0.0. You may need to disconnect/disable all other network cards on that PC to ensure the proper route is used.
Connect your LaFonera to the network card via a network cable.
In a browser, try to connect to http://169.254.255.1:8080
If that fails, try to establish an SSH connection to 169.254.255.1
If that fails, try to establish a TELNET connection to 169.254.255.1 on the standard port (23), or port 9000.
Power on the LaFonera, and after 2 to 4 seconds, try to start the TELNET connection to catch the REDBOOT prompt.
If that fails, you may have to resort to a serial connection. Serial connect devices are listed in the #External_links section of this guide.
If the configuration is corrupted/incorrect, try resetting of the NVRAM. Power up the unit, and wait about 2 minutes, then hold down the Reset button for several seconds. You must do this while the firmware is loaded, hence waiting for a minute or two after powering it up.
If that fails, try these steps:
1. Reset the LaFonera and telnet into the Redboot prompt (see Step 5 above).
2. Enter the following command to erase the NVRAM partition.
fis erase -f 0xA83D0000 -l 0x00010000
3. Reboot the router by entering this command:
reset
Thank you for the reply.
I've tried that. After reset, both the power and internet light stay green. The Internet light sometimes blinks but it's random. I can access redboot on 192.168.1.254 on port 9000 all the time. It's not just on the first 10 seconds after I switch it ON. Isn't this weird?
I've downloaded original firmware from FON, dd the file so that I could untar it, uploaded to the router, made the rest of the procedure and so on. But after reboot, still no sognal at all. Netstumbler can't catch a single signal from it and I can access it (besides redboot).
It's driving me nuts. I've been all day around this.
Thank you
Looks like your redboot startup script got erased..
type fconfig -l
if startup empty enter :
fconfig and type statup script i.e next two lines:
fis load -l vmlinux.bin.l7
exec
now restart fonera...
RedBoot> fconfig -l
Run script at boot: true
Boot script:
.. fis load -l vmlinux.bin.l7
.. exec
Boot script timeout (1000ms resolution): 10
Use BOOTP for network configuration: false
Gateway IP address: 0.0.0.0
Local IP address: 192.168.1.254
Local IP address mask: 255.255.255.0
Default server IP address: 0.0.0.0
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false