Fonera WiFi client w/ transparent L2 - Fonera firmware Fixes

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page 1, 2, 3, 4  Next
Author Message
Barabba
DD-WRT Novice


Joined: 20 Dec 2019
Posts: 4

PostPosted: Sun May 31, 2020 0:05    Post subject: Fonera WiFi client w/ transparent L2 - Fonera firmware Fixes Reply with quote
Hi mates, I've lost some time trying to make it work, I have Fonera 2100 with latest DD-WRT v3.0-r40559 (08/06/19), as I understand I can use the Fonera's WiFi to connect to router and my PC to ethernet only if there are 2 different IP domains. I would like to use Fonera as a pure converter wifi to ethernet, I put both interface under the same bridge but I still no ping WiFi IPs and the Fonera IP too (reachable only by ethernet). How can I solve this? Thank you

Moderator Edit: Topic changed to include relevant content reference
Sponsor
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Sun May 31, 2020 1:11    Post subject: Reply with quote
https://duckduckgo.com/?q=Fonera+FON2100+dd-wrt

https://wiki.dd-wrt.com/wiki/index.php/Index:FAQ
(see "Where Do I Download Firmware", scroll to the bold red letters that say, "DO NOT USE THE ROUTER DATABASE")

Quote:
DISCLAIMER
This database may not have up-to-date information and may even recommend a build which might cause issues. As such, you should check the device specific forum (Broadcom, Atheros, MediaTek, etc.) first before flashing any build recommended in this database. There you will find build specific topics that discuss any issues with a particular build/release. For more up-to-date firmware files, please visit the firmware faq.

YOU HAVE BEEN GIVEN FRIENDLY AND FAIR NOTICE


https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2020/

New Build - 05/29/2020 - r43290

_________________
"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
arssant
DD-WRT User


Joined: 14 Aug 2013
Posts: 153

PostPosted: Sun May 31, 2020 14:22    Post subject: Re: How to use Fonera as a WiFi client with transparent Laye Reply with quote
Barabba wrote:
Hi mates, I've losidget some. time trying to make it work, I have Fonera 2100 with latest DD-WRT v3.0-r40559 (08/06/19), as I understand I can use the Fonera's WiFi to connect to router and my PC to ethernet only if there are 2 different IP domains. I would like to use Fonera as a pure converter wifi to ethernet, I put both interface under the same bridge but I still no ping WiFi IPs and the Fonera IP too (reachable only by ethernet). How can I solve this? Thank you



Hi.

Use the fon wireless settings as client bridge. By this way you don´t need 2 different IP domains.
Barabba
DD-WRT Novice


Joined: 20 Dec 2019
Posts: 4

PostPosted: Mon Jun 01, 2020 5:55    Post subject: Reply with quote
Thaak you for your kind and fast answer, as I see you are suggesting me to install latest r43290 but I?m not sure it's made fro Fonera 2100, actually this router has limited flash and RAM and I read in different articles it doesn't support everything, and I need to be careful.
actually I'm running Firmware: DD-WRT v3.0-r40559 (08/06/19) which doesn't look to be old, and I don't think in the last year DD-WRT introduced the transparent mode for ethernet.. I suppose there is already somewhere in router and I don't figure out how to enable it.

I've disabled WAN and add the WAN port to local switch, I placed the interfaces eth1 and ath1 under the same bridge
br0 no ath0 eth0
then what is still wrong? maybe I have problem on broadcast between the 2 interfaces? Maybe I can't arp MAC address on the other interface?
I've also tried to assign router a different IP address outside of the LAN subnet that I'm interested to..
Thank you
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Mon Jun 01, 2020 11:40    Post subject: Reply with quote
The problem is 40559 seems to be a problematic build in general, but do whatever you choose. It's not the latest firmware and doesn't have the latest patches. Since people do not report on any of the Fonera devices, I really do not know what to advise or recommend.
_________________
"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
arssant
DD-WRT User


Joined: 14 Aug 2013
Posts: 153

PostPosted: Mon Jun 01, 2020 15:15    Post subject: Reply with quote
Hi.

For my fon 2201, I keep using :

Code:
 Fonera 2201
Firmware Version
DD-WRT v24-sp2 (12/07/11) std - build 17967


Reason: https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1181945&highlight=#1181945

Code:
v24 pre SP2 r14896
was more stable on high load traffic.

I have used them for years as wireless client or client bridge ( routed ). Even was used 2 of them as a 50+mts link connecting 2 houses.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Mon Jun 01, 2020 15:48    Post subject: Reply with quote
So, the premise is staying with an antique build with no security patches because nobody has tested more recent builds successfully (without reporting in the build threads or in the linked thread)? Can't fix anything if nobody reports and provides information...
_________________
"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
arssant
DD-WRT User


Joined: 14 Aug 2013
Posts: 153

PostPosted: Mon Jun 01, 2020 21:16    Post subject: Reply with quote
kernel-panic69 wrote:
So, the premise is staying with an antique build with no security patches because nobody has tested more recent builds successfully (without reporting in the build threads or in the linked thread)? Can't fix anything if nobody reports and provides information...


Hi.
Can be done.

Just pick any post build 17967. I will upgrade one of my fonera 2201. Just ask for any info needed ( boot log, network, etc ). Bricking it not an issue, I was able to recover one with my ch341a programmer, cheap Chinese one. I will post results here.
But basically, any post 17967, the issue is what I reported over my previous post.
Code:
eth0 not up
vlan0 not up
vlan1 not up


As result, no network connection working; wired: wan port , lan port or wireless. Serial rs232 connection still available.

Nvram erase same results, even a fresh upgrade from a fon firmware.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Mon Jun 01, 2020 21:24    Post subject: Reply with quote
I would start somewhere around 37961 and post all serial, dmesg, and syslog information. You may wish to try using one of the following command combinations in the startup script or via telnet / ssh to see if it fixes the issue:
Code:
swconfig dev switch0 set reset 1
swconfig dev switch0 set enable_vlan 1
swconfig dev switch0 set apply

Code:
swconfig dev eth0 set enable_vlan 1
swconfig dev eth0 set apply

Code:
(startup only)
LAN_IF="$(brctl showstp br0 | grep -Eom1 "^eth[0-9]")"
swconfig dev $LAN_IF set enable_vlan 1
swconfig dev $LAN_IF set apply

_________________
"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
arssant
DD-WRT User


Joined: 14 Aug 2013
Posts: 153

PostPosted: Mon Jun 01, 2020 22:42    Post subject: Reply with quote
Hi.

Will be done by tomorrow.
Right now some info for a working one:

Code:

root@d3faults:~# dmesg
<5>Linux version 2.6.24.111 (root@dd-wrt) (gcc version 4.1.1) #12583 Wed Dec 7 01:31:02 CET 2011
<6>mips devid = 86
<4>CPU revision is: 00019064
<0>mem setup
<4>Determined physical RAM map:
<4> memory: 01000000 @ 00000000 (usable)
<7>On node 0 totalpages: 4096
<7>  Normal zone: 32 pages used for memmap
<7>  Normal zone: 0 pages reserved
<7>  Normal zone: 4064 pages, LIFO batch:0
<7>  Movable zone: 0 pages used for memmap
<4>Built 1 zonelists in Zone order.  Total pages: 4064
<5>Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd
<4>Primary instruction cache 16kB, physically tagged, 4-way, linesize 16 bytes.
<4>Primary data cache 16kB, 4-way, linesize 16 bytes.
<6>Synthesized TLB refill handler (20 instructions).
<6>Synthesized TLB load handler fastpath (32 instructions).
<6>Synthesized TLB store handler fastpath (32 instructions).
<6>Synthesized TLB modify handler fastpath (31 instructions).
<4>PID hash table entries: 64 (order: 6, 256 bytes)
<4>Using 92.000 MHz high precision timer.
<6>console [ttyS0] enabled
<6>Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
<6>Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
<6>Memory: 12852k/16384k available (2298k kernel code, 3532k reserved, 305k data, 124k init, 0k highmem)
<7>Calibrating delay loop... 183.50 BogoMIPS (lpj=917504)
<4>Mount-cache hash table entries: 512
<6>NET: Registered protocol family 16
<4>scanning for board data at A87FF000 (FFFFFFFF)
<4>scanning for board data at A87FE000 (FFFFFFFF)
<4>scanning for board data at A87FD000 (FFFFFFFF)
<4>scanning for board data at A87FC000 (FFFFFFFF)
<4>scanning for board data at A87FB000 (FFFFFFFF)
<4>scanning for board data at A87FA000 (FFFFFFFF)
<4>scanning for board data at A87F9000 (FFFFFFFF)
<4>scanning for board data at A87F8000 (FFFFFFFF)
<4>scanning for board data at A87F7000 (FFFFFFFF)
<4>scanning for board data at A87F6000 (FFFFFFFF)
<4>scanning for board data at A87F5000 (FFFFFFFF)
<4>scanning for board data at A87F4000 (FFFFFFFF)
<4>scanning for board data at A87F3000 (FFFFFFFF)
<4>scanning for board data at A87F2000 (FFFFFFFF)
<4>scanning for board data at A87F1000 (FFFFFFFF)
<4>scanning for board data at A87F0000 (35333131)
<4>found 1
<4>Found board config at 0xa87f0000
<4>Radio config found at offset 0xf8(0x1f8) (a87f00f8)
<6>Generic PHY: Registered new driver
<6>Time: MIPS clocksource has been installed.
<6>NET: Registered protocol family 2
<6>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
<6>TCP established hash table entries: 512 (order: 0, 4096 bytes)
<6>TCP bind hash table entries: 512 (order: -1, 2048 bytes)
<6>TCP: Hash tables configured (established 512 bind 512)
<6>TCP reno registered
<5>gpio_proc: module loaded and /proc/gpio/ created
<6>devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
<6>devfs: boot_options: 0x1
<6>squashfs: version 3.0 (2006/03/15) Phillip Lougher
<6>io scheduler noop registered
<6>io scheduler deadline registered (default)
<6>Serial: 8250/16550 driver $Revision: 1.90 $ 1 ports, IRQ sharing disabled
<6>serial8250: ttyS0 at MMIO 0xb1100003 (irq = 37) is a 16550A
<3>serial8250 serial8250.0: unable to register port at index 0 (IO3f8 MEM0 IRQ4): -28
<3>serial8250 serial8250.0: unable to register port at index 1 (IO2f8 MEM0 IRQ3): -28
<3>serial8250 serial8250.0: unable to register port at index 2 (IO3e8 MEM0 IRQ4): -28
<3>serial8250 serial8250.0: unable to register port at index 3 (IO2e8 MEM0 IRQ3): -28
<6>Infineon ADM6996: Registered new driver
<6>Marvell 88E6060/88E6061: Registered new driver
<6>PPP generic driver version 2.4.2
<6>PPP Deflate Compression module registered
<6>PPP BSD Compression module registered
<6>MPPE/MPPC encryption/compression module registered
<6>NET: Registered protocol family 24
<6>tun: Universal TUN/TAP device driver, 1.6
<6>tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
<0>scanning for root partition
<0>
<4>found squashfs at 110000
<0>found RedBoot partition at [0xA8000000]
<0>found linux partition at [0xA8030000]
<5>Creating 8 MTD partitions on "spiflash":
<5>0x00000000-0x00030000 : "RedBoot"
<5>0x00030000-0x007d0000 : "linux"
<5>0x00110000-0x006f0000 : "rootfs"
<5>0x006f0000-0x007d0000 : "ddwrt"
<5>0x007d0000-0x007e0000 : "nvram"
<5>0x007e0000-0x007f0000 : "FIS directory"
<5>0x007f0000-0x00800000 : "board_config"
<5>0x00000000-0x00800000 : "fullflash"
<4>watchdog hb: 60  ISR: 0x20  IMR: 0x8  WD : 0xc266ac5c  WDC: 0x0
<4>ar2315_wdt_init using heartbeat 60 s cycles 2400000000
<4>watchdog hb: 60  ISR: 0x20  IMR: 0x88  WD : 0x8f0d00b8  WDC: 0x0
<4>u32 classifier
<4>    Actions configured
<4>Netfilter messages via NETLINK v0.30.
<4>nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
<4>ctnetlink v0.93: registering with nfnetlink.
<6>IPv4 over IPv4 tunneling driver
<6>GRE over IPv4 tunneling driver
<6>ip_tables: (C) 2000-2006 Netfilter Core Team
<5>ClusterIP Version 0.8 loaded successfully
<6>TCP bic registered
<6>TCP cubic registered
<6>TCP westwood registered
<6>TCP highspeed registered
<6>TCP hybla registered
<6>TCP htcp registered
<6>TCP vegas registered
<6>TCP scalable registered
<6>NET: Registered protocol family 1
<6>NET: Registered protocol family 17
<4>Welcome to PF_RING 3.2.1
<4>(C) 2004-06 L.Deri <deri@ntop.org>
<6>NET: Registered protocol family 27
<4>PF_RING: bucket length    128 bytes
<4>PF_RING: ring slots       4096
<4>PF_RING: sample rate      1 [1=no sampling]
<4>PF_RING: capture TX       No [RX only]
<4>PF_RING: transparent mode Yes
<4>PF_RING initialized correctly.
<4>PF_RING: registered /proc/net/pf_ring/
<6>802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
<6>All bugs added by David S. Miller <davem@redhat.com>
<0>decode 1f02
<4>VFS: Mounted root (squashfs filesystem) readonly.
<6>Mounted devfs on /dev
<6>Freeing unused kernel memory: 124k freed
<4>Algorithmics/MIPS FPU Emulator v1.5
<4>ar2315_wdt: starting watchdog w/timeout 60 seconds
<4>watchdog hb: 60  ISR: 0x20  IMR: 0x89  WD : 0x8f0b12a2  WDC: 0x0
<4>eth0: Atheros AR231x: 00:18:84:00:00:00, irq 4
<6>ar2313_eth_mii: probed
<4>eth0: Marvell 88E6060 PHY driver attached.
<6>eth0: attached PHY driver [Marvell 88E6060/88E6061] (mii_bus:phy_addr=0:1f)
<4>ath_hal: module license 'Proprietary' taints kernel.
<6>eth0: Configuring MAC for full duplex
<6>device eth0 entered promiscuous mode
<3>br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
<6>device br0 entered promiscuous mode
<6>br0: port 2(vlan1) entering learning state
<6>br0: port 1(vlan0) entering learning state
<6>device br0 left promiscuous mode
<6>device br0 entered promiscuous mode
<6>device br0 left promiscuous mode
<6>device br0 entered promiscuous mode
<6>br0: topology change detected, propagating
<6>br0: port 2(vlan1) entering forwarding state
<6>br0: topology change detected, propagating
<6>br0: port 1(vlan0) entering forwarding state
<6>etherip: Ethernet over IPv4 tunneling driver
root@d3faults:~#


Code:
 nvram show | grep vlan
vlan0_mtu=1500
vlan0ports=0 1 2 3 4 5*
vlan0_bridged=1
port5vlans=0 1 16
port3vlans=0
port1vlans=0
wl0_vlan_prio_mode=off
vlan1_bridged=1
lan_ifnames=vlan0 vlan1 ath0
vlan0_multicast=0
vlan0_nat=1
vlan1_mtu=1500
vlan1hwname=et0
vlan1ports=5
port4vlans=0
vlans=0
vlan_tagcount=0
port2vlans=0
port0vlans=1
size: 24203 bytes (41333 left)
dtag_vlan8=0
vlan0hwname=et0
vlan1_multicast=0
vlan1_nat=1
root@d3faults:~#



Code:
root@d3faults:~# nvram show | grep ath0
ath0_ff=0
ath0_wds6_enable=0
chilli_interface=ath0
ath0_wep=disabled
ath0_bias=0
ath0_minrate=0
ath0_br1_netmask=255.255.255.0
ath0_net_mode=mixed
ath0_br1_enable=0
ath0_txantenna=1
ath0_protmode=None
wl0_ifname=ath0
ath0_rts=0
ath0_wds1_enable=0
hotss_interface=ath0
ath0.3_ssid=
ath0_radius_ipaddr=
ath0_wds7_enable=0
ath0_key=1
ath0_txpwrdbm=20
ath0_xr=0
ath0.1_ssid=
ath0_diversity=0
ath0_antgain=0
wifi_display=ath0
size: 24203 bytes (41333 left)
ath0.1_bridged=1
ath0_▒ds2_enable=0
ath0_wds2_enable=0
ath0_inact=300
ath0_noise_immunity=4
ath0_wds8_enable=0
ath0_channelbw=20
ath0.1_ipaddr=0.0.0.0
ath0.1_netmask=0.0.0.0
ath0_intmit=-1
ath0_wpa_gtk_rekey=3600
ath0_hwaddr=00:18:84:00:00:00
ath0_ofdm_weak_det=1
ath0_mtikie=0
ath0_radius_port=1812
ath0_akm=psk psk2
ath0_netmas▒=0.0.0.0
ath0_br1_ipaddr=0.0.0.0
ath0_channel=0
ath0_authmode=open
ath0_wds3_enable=0
ath0_wds9_enable=0
ath0_radio=1
lan_ifnames=vlan0 vlan1 ath0
ath0_crypto=aes
ath0_wds10_enable=0
ath0_auth_mode=none
ath0_sifstime=16
ath0_rtsvalue=2346
ath0.2_ipaddr=0.0.0.0
ath0_preambletime=20
ath0_doth=0
ath0.2_bridged=1
ath0_rxantenna=1
ath0_multicast=0
ath0_ipaddr=0.0.0.0
ath0_wep_buf=:::::
ath0.2_netmask=0.0.0.0
ath0_maxassoc=256
ath0_wds4_enable=0
ath0_radius_key=
ath0_distance=2000
ath0.2_ssid=
ath0_chanshift=0
ath0.3_ipaddr=0.0.0.0
ath0_csma=1
ath0_wchannel=0
ath0_pollingmode=0
ath0_regdomain=my country
ath0.3_bridged=1
ath0_inact_tick=15
ath0_wds5_enable=0
ath0_preamble=0
ath0_8021xtype=peap
ath0_security_mode=psk psk2
ath0_bridged=1
ath0_mode=sta
ath0.1_netmas▒=0.0.0.0
ath0.3_netmask=0.0.0.0
ath0_nat=1
ath0_maxrate=0
ath0_outdoor=0
ath0_closed=0
ath0_regulatory=1
ath0_ssid=my network
ath0_lazywds=0
ath0_ap_isolate=0
ath0_netmask=0.0.0.0
ath0_wmm=0
ath0_scanlist=default
ath0_wpa_psk=my key
root@d3faults:~#


Fonera 2201
Firmware Version
DD-WRT v24-sp2 (12/07/11) std - build 17967

wireless mode: client

vlan0 is lan, and I use wan port as a 2 lan port.
Code:
vlan0ports=0 1 2 3 4 5*
lan_ifnames=vlan0 vlan1 ath0


vlan1 is wan.

The atheros switch, port 0 is the physical wan port on the fonera, 5 is cpu. In my case I disable the switch port 0 for vlan1.

Code:
vlan1ports=5


Just for reference: build 17967
Code:
root@d3faults:~# swconfig
-sh: swconfig: not found
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Mon Jun 01, 2020 23:23    Post subject: Reply with quote
Ok. Thanks for the info. I don't have a whole lot of background on these, so not sure if the swconfig utility was ever introduced to them. I would suggest not doing any resets to your nvram or configuration when you upgrade so we can see what effects, if any it has. I would copy your entire nvram show to a text file from the working build for reference in you do reset in the process of troubleshooting.
_________________
"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
arssant
DD-WRT User


Joined: 14 Aug 2013
Posts: 153

PostPosted: Mon Jun 01, 2020 23:58    Post subject: Reply with quote
Hi.

Thanx for your time, I really appreciate that.
Another thing, upgrade via gui, is not, and never worked for me since 1st time I got these foneras, from v. 14896.
I not sure why, don´t remember, upload error or after upload completed the fon freeze on redboot.

The only way was and is by TFTP via redboot.

Code:
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-0x80662fff, assumed entry at 0x80041000
RedBoot> fis create linux
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14125
Location: Texas, USA

PostPosted: Tue Jun 02, 2020 0:36    Post subject: Reply with quote
Correct. The only other way I know of is using fon_flash from the Gargoyle downloads page. Seeing your boot logs and seeing what is publicly visible in the code repository makes me scratch my head. How can you have vlans when the .config doesn't have a "Y" next to that line. Interesting. Worst case scenario is I have to ping BrainSlayer for anything that is broken and/or open a ticket.

EDIT: Delayed answer to the OP regarding his last post. Use the Client bridge wiki linked in this one:

https://wiki.dd-wrt.com/wiki/index.php/Linking_Routers

_________________
"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
arssant
DD-WRT User


Joined: 14 Aug 2013
Posts: 153

PostPosted: Tue Jun 02, 2020 13:26    Post subject: Reply with quote
Hi

As requested. Logs, nvram, boot info, ifconfig, etc, as attachment.
Just ignore my previous post, for logs and nvram, I used a fresh fon2201. Updated from build 17967 to 37961. All settings were maintained, no reset no nvram erase.

fon working : build 17967
fon not working : build 37961
arssant
DD-WRT User


Joined: 14 Aug 2013
Posts: 153

PostPosted: Tue Jun 02, 2020 21:19    Post subject: Reply with quote
Some new development.
I was playing with ifconfig commands, and got some weird results:

Code:
root@DD-WRT:~# ifconfig
ath0      Link encap:Ethernet  HWaddr 00:18:84:A2:D5:95
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:20 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:496 (496.0 B)  TX bytes:492 (492.0 B)

br0       Link encap:Ethernet  HWaddr 00:18:84:A2:D5:94
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:2 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:496 (496.0 B)  TX bytes:840 (840.0 B)


lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING MULTICAST  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


wifi0     Link encap:UNSPEC  HWaddr 00-18-84-A2-D5-95-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:295
          RX bytes:3069 (2.9 KiB)  TX bytes:1696 (1.6 KiB)
          Interrupt:3 Memory:b0000000-b000ffff


after this one:



Code:
root@DD-WRT:~# ifconfig eth0 up

[   52.220000] device eth0 entered promiscuous mode

<6>[   19.670000] device vlan1 entered promiscuous mode
<1>[   20.010000] fast-classifier: starting up
<1>[   20.020000] fast-classifier: registered
<6>[   25.510000] device vlan1 left promiscuous mode
<6>[   52.220000] device eth0 entered promiscuous mode
<6>[  571.680000] device eth0 entered promiscuous mode

root@DD-WRT:~# ifconfig
ath0      Link encap:Ethernet  HWaddr 00:18:84:A2:D5:95
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:20 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:496 (496.0 B)  TX bytes:492 (492.0 B)

br0       Link encap:Ethernet  HWaddr 00:18:84:A2:D5:94
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:6 errors:0 dropped:2 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:496 (496.0 B)  TX bytes:840 (840.0 B)

eth0      Link encap:Ethernet  HWaddr 00:18:84:A2:D5:94
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:4 Base address:0x1000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING MULTICAST  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vlan0     Link encap:Ethernet  HWaddr 00:18:84:A2:D5:94
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vlan1     Link encap:Ethernet  HWaddr 00:18:84:A2:D5:95
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wifi0     Link encap:UNSPEC  HWaddr 00-18-84-A2-D5-95-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:19 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:295
          RX bytes:3069 (2.9 KiB)  TX bytes:1696 (1.6 KiB)
          Interrupt:3 Memory:b0000000-b000ffff

after a -20 mns

<6>[  612.870000] eth0: Link Down
<6>[  613.370000] eth0: Link Down
and so on


vlan1 is the physical lan port, some TX packets but no RX ( even trying ping from my windows box )

And for the weirdest, wifi, is working, kind of. I was able to connect to the fon with the correct wpa2 key, and my windows box got a valid ip address from the fon dhcp range. But no pings, no GUI access to the fon.

running wireshark, I got this over wireless: Connected with ethernet, ( even with static ip on my windows box ) nothing not a single packet.


Code:
Frame 69: 42 bytes on wire (336 bits), 42 bytes captured (336 bits) on interface \Device\NPF_{F4A98FE1-2B75-4A30-8BB4-AAAA9319AFE5}, id 0
    Interface id: 0 (\Device\NPF_{F4A98FE1-2B75-4A30-8BB4-AAAA9319AFE5})
        Interface name: \Device\NPF_{F4A98FE1-2B75-4A30-8BB4-AAAA9319AFE5}
        Interface description: Wireless Network Connection
    Encapsulation type: Ethernet (1)
    Arrival Time: Jun  2, 2020 18:24:22.018416000 GMT Daylight Time
    [Time shift for this packet: 0.000000000 seconds]
    Epoch Time: 1591118662.018416000 seconds
    [Time delta from previous captured frame: 0.009016000 seconds]
    [Time delta from previous displayed frame: 0.009016000 seconds]
    [Time since reference or first frame: 16.951778000 seconds]
    Frame Number: 69
    Frame Length: 42 bytes (336 bits)
    Capture Length: 42 bytes (336 bits)
    [Frame is marked: False]
    [Frame is ignored: False]
    [Protocols in frame: eth:ethertype:arp]
    [Coloring Rule Name: ARP]
    [Coloring Rule String: arp]

Ethernet II, Src: FonTechn_a2:d5:94 (00:18:84:a2:d5:94), Dst: HonHaiPr_ce:38:9f (90:00:4e:ce:38:9f)
    Destination: HonHaiPr_ce:38:9f (90:00:4e:ce:38:9f)
        Address: HonHaiPr_ce:38:9f (90:00:4e:ce:38:9f)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Source: FonTechn_a2:d5:94 (00:18:84:a2:d5:94)
        Address: FonTechn_a2:d5:94 (00:18:84:a2:d5:94)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Type: ARP (0x0806)



Address Resolution Protocol (reply)
    Hardware type: Ethernet (1)
    Protocol type: IPv4 (0x0800)
    Hardware size: 6
    Protocol size: 4
    Opcode: reply (2)
    Sender MAC address: FonTechn_a2:d5:94 (00:18:84:a2:d5:94)
    Sender IP address: 192.168.1.1
    Target MAC address: HonHaiPr_ce:38:9f (90:00:4e:ce:38:9f)
    Target IP address: 192.168.1.127


--------------------------------------------

ping to fon

Ethernet II, Src: HonHaiPr_ce:38:9f (90:00:4e:ce:38:9f), Dst: FonTechn_a2:d5:94 (00:18:84:a2:d5:94)
    Destination: FonTechn_a2:d5:94 (00:18:84:a2:d5:94)
        Address: FonTechn_a2:d5:94 (00:18:84:a2:d5:94)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Source: HonHaiPr_ce:38:9f (90:00:4e:ce:38:9f)
        Address: HonHaiPr_ce:38:9f (90:00:4e:ce:38:9f)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Type: IPv4 (0x0800)


Internet Control Message Protocol
    Type: 8 (Echo (ping) request)
    Code: 0
    Checksum: 0x4bc6 [correct]
    [Checksum Status: Good]
    Identifier (BE): 1 (0x0001)
    Identifier (LE): 256 (0x0100)
    Sequence number (BE): 405 (0x0195)
    Sequence number (LE): 38145 (0x9501)
    [No response seen]
        [Expert Info (Warning/Sequence): No response seen to ICMP request]
    Data (32 bytes)
Goto page 1, 2, 3, 4  Next Display posts from previous:    Page 1 of 4
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum