It was going well until I restart Fonera to acces to RedBoot (10 seg).
When I restart the WLAN LED doesn't swhich on, the POWER LED is on and the INTERNET ono blink sometimes.
I can't access it makin telnet, ssh, ping...
Is there a solution without open it and install a RS232 port?
Thank you very much.
you need to catch the fonera at 192.168.1.254 port 9000 with telnet.
config your network card to static ip and start a continuous ping to 192.168.1.254, plug in the fonera and when you see a response quickly telnet in with port 9000 and stop the fonera from booting
lazkano@debian:~$ ping 192.168.1.254
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
From 192.168.1.101 icmp_seq=2 Destination Host Unreachable
From 192.168.1.101 icmp_seq=3 Destination Host Unreachable
From 192.168.1.101 icmp_seq=4 Destination Host Unreachable
From 192.168.1.101 icmp_seq=6 Destination Host Unreachable
From 192.168.1.101 icmp_seq=7 Destination Host Unreachable
From 192.168.1.101 icmp_seq=8 Destination Host Unreachable
From 192.168.1.101 icmp_seq=10 Destination Host Unreachable
From 192.168.1.101 icmp_seq=11 Destination Host Unreachable
...
The POWER LED is on, and the INTERNET one starts blinking when I ping to 192.168.1.254
I need a RS232 cable?
Is there any solution?
Thanks again
you start the ping before you plug in the fonera right? also try putting a switch between your pc and the fonera sometimes the network card doesn't realise the cable is conncted before the redboot is already passed
you would host the firmware on your computer with a tftp server and then flash using redboot, you still need to hook the fonera up through a network cable
Posted: Thu Jun 30, 2011 8:54 Post subject: unbrick fonera 2100
Hi,
I got 2 foneras which are not working as they should. The bricking was done by others.
1. all three LEDs are on.
2. no WLAN
3. no Lan, even static on 169.254.255.1 nor 192.168.1
4. no reaction on pressing reset for 15-20 secs.
5. redboot accessible via serial
6. flashing dd-wrt or openwrt possible with ap51-flash-fonera-gui.
7. redboot answer to fis list:
Access RedBoot and ping the host. Does it work? Use crossover ethernet cable or connect a switch.
By serial access I have set the Redboot IP:
>fconfig bootp_my_ip 169.254.255.1<
So I can ping 169.254.255.1 successfully with a fixed IP within 169.254.255.x.
But I have no access to the webfrontend of the router.
Nor is it giving a WiFi signal.