Posted: Wed Jun 16, 2021 13:51 Post subject: Fon 2100: Default Settings / NAT
Hello,
I was trying to repurposed and old Fon 2100 for a low speed/range situation and I was able to flash it with r29218. Unfortunately it doesn't seem to behave like other DD-WRT capable routers I own. After a factory reset I got this default settings:
WAN is disabled by default. On the "dd-wrt" wifi network I was unable to access the router GUI and somehow I was provided with an IP address from my main router 172.16.x.x instead of something like 192.168.1.x. Why? After I manually changed my IP to static under the 192.168 range I was able to access the GUI.
Why doesn't it have WAN in DHCPd like any other router and why isn't it doing NAT? Is there any specific config that comes with these routers that needs to be changed?
Indeed, however if I enable it and set it as DHCPd I get an IP from the router on the 192.168.1.x range however I can't ping the router, open the page, or access anything else. _________________ 1x Netgear R7800 (latest); 3x Netgear R7000 (latest); 2x Asus RT-N16 (v3.0-r47656); 2x Fonera 2100 (v3.0-r45454).
Update, after reading the links you provided I decided to try r17967 and everything works as expected. I was able to enable the WAN port and have NAT working.
I read that were some workarounds for newer builds however it wasn't clear to me how to proceed. _________________ 1x Netgear R7800 (latest); 3x Netgear R7000 (latest); 2x Asus RT-N16 (v3.0-r47656); 2x Fonera 2100 (v3.0-r45454).
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Thu Jun 17, 2021 2:28 Post subject:
The build you initially mentioned may be questionable. If you read the entire thread (first link), you should be able to upgrade to a much more recent build successfully. These devices are tedious to flash and update, as best I understand it. I don't have one, personally, but BrainSlayer dug out one of his to fix the issues flashing newer firmwares, etc. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
The build you initially mentioned may be questionable. If you read the entire thread (first link), you should be able to upgrade to a much more recent build successfully. These devices are tedious to flash and update, as best I understand it. I don't have one, personally, but BrainSlayer dug out one of his to fix the issues flashing newer firmwares, etc.
Yeah you're right, I managed to flash one of my fon routers to r43516 as recommended.
I did it using telnet and tftpd64 (no serial cable) and it now works properly.
Here is the log for future reference (tftp server running at 192.168.1.105):
Code:
RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
RedBoot 0xA8000000 0xA8000000 0x00030000 0x00000000
rootfs 0xA8030000 0xA8030000 0x006E0000 0x00000000
vmlinux.bin.l7 0xA8710000 0x80041000 0x000D0000 0x80041000
FIS directory 0xA87E0000 0xA87E0000 0x0000F000 0x00000000
RedBoot config 0xA87EF000 0xA87EF000 0x00001000 0x00000000
RedBoot> fis init
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot> load -r -b 0x80041000 linux.bin
Using default protocol (TFTP)
Raw file loaded 0x80041000-0x805a73ef, assumed entry at 0x80041000
RedBoot> fis create linux
( Took a long time, telnet didn't disconnect and then showed all the output at once! )
... Erase from 0xa8030000-0xa85963f0: .......................................................................................
... Program from 0x80041000-0x805a73f0 at 0xa8030000: .......................................................................................
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot> reset
After this it didn't boot, as documented in one of the links I had to enter RedBoot again and change the boot script:
Code:
RedBoot> fconfig
Run script at boot: true
Boot script:
.. fis load -l vmlinux.bin.l7
.. exec
Enter script, terminate with empty line
>> fis load -l linux
>> exec
>>
Boot script timeout (1000ms resolution): 10
Use BOOTP for network configuration: false
Gateway IP address:
Local IP address: 192.168.1.254
Local IP address mask: 255.255.255.0
Default server IP address: 192.168.1.105
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration - continue (y/n)? y
... Erase from 0xa87e0000-0xa87f0000: .
... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
RedBoot> reset
After this it boot just fine! About the WAN port, I just decided to add it to the switch and then used an IP for the FON that matched my main router. This way I'm able to access it from it's wifi network and from the rest of my network.
Main Router: 172.21.1.1
Main Router DHCPd Range: 172.21.1.100-200
FON WAN Port: Disabled
FON Add WAN Port to Switch: True
FON DHCP Server: Disabled (along with DNSMasq etc)
FON Static IP: 172.21.1.2
FON Gateway: 172.21.1.1
FON Wifi Mode: AP
FON Setup > Advanced Routing > Operating Mode > Router
FON SPI Firewall: Disabled
This why my clients on the FON get an IP from my main router, can connect to the internet and everything works just fine. I still can't get the WAN port to work like other DD-WRT routers with NAT but I don't need it right now.
My Internet connection is 100/100Mbps, while connected to the FON I'm getting around this:
It's low, but well it fits my needs. What else can I except from something that has 100Mhz?
Now I'm the the process of trying to flash another FON that also seems bricked. Unfortunately after entering RedBoot I send the ^C command it it disconnects me... Or it's just ignoring the command. Maybe it has some protection?
Thank you for all your tips. _________________ 1x Netgear R7800 (latest); 3x Netgear R7000 (latest); 2x Asus RT-N16 (v3.0-r47656); 2x Fonera 2100 (v3.0-r45454).
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Thu Jun 17, 2021 14:49 Post subject:
You may want to venture into upgrading to builds from this year at some point, but that is entirely at your own discretion. Not sure what (other) issues may have been fixed since that release for the FON 2xxx devices. The default config on these is weird, it seems. Shouldn't take much to figure it out, though? _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
You may want to venture into upgrading to builds from this year at some point, but that is entirely at your own discretion. Not sure what (other) issues may have been fixed since that release for the FON 2xxx devices. The default config on these is weird, it seems. Shouldn't take much to figure it out, though?
I'll venture into newer builds as soon as I'm able to recover the other bricked device.
It enters RedBoot, however I send the ^C command it it disconnects me... Or it's just ignoring the command. Any tips?
Joined: 08 May 2018 Posts: 14125 Location: Texas, USA
Posted: Thu Jun 17, 2021 17:49 Post subject:
I personally don't have one of these, but it is definitely a timing issue, I am sure. It may take several attempts. Serial console is likely much easier, since less change of disconnecting; but it is also a timing thing. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
I personally don't have one of these, but it is definitely a timing issue, I am sure. It may take several attempts. Serial console is likely much easier, since less change of disconnecting; but it is also a timing thing.
Oh yeah, it was a timing issue. I was searching around and found the following:
Quote:
I recommend using putty.
All the defaults are correct, and upon connecting it will type a ^C so you do not have to worry about this
Tried it putty and it worked right away! Flashed successfully at the first try.
Now I'm about to test the latest firmware. _________________ 1x Netgear R7800 (latest); 3x Netgear R7000 (latest); 2x Asus RT-N16 (v3.0-r47656); 2x Fonera 2100 (v3.0-r45454).