Modify

Opened 10 years ago

Closed 10 years ago

#2410 closed defect (fixed)

Only one Ethernet detected on Fonera+ and it is unusable

Reported by: l.dardini@… Owned by: developers
Priority: high Milestone:
Component: packages Version:
Keywords: Cc:

Description

Using lastest svn kamikaze version, revision 8848, only one Ethernet is detected and it is not usable: it cannot send or receive packets. This is not a cable or network problem. Using RedBoot you can send and receive from the net. It is not a firewall issue, there is no firewall active and even the arp fail.

Here a simple session, hint, look at the arp table!

root@OpenWrt:/# ifconfig
br-lan    Link encap:Ethernet  HWaddr 00:18:84:A0:CD:04  
          inet addr:172.16.2.201  Bcast:172.16.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:823 (823.0 B)

eth0      Link encap:Ethernet  HWaddr 00:18:84:A0:CD:04  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:1866 (1.8 KiB)
          Interrupt:4 Base address:0x1000 

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

root@OpenWrt:/# ping 172.16.1.49
PING 172.16.1.49 (172.16.1.49): 56 data bytes

--- 172.16.1.49 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
root@OpenWrt:/# ifconfig
br-lan    Link encap:Ethernet  HWaddr 00:18:84:A0:CD:04  
          inet addr:172.16.2.201  Bcast:172.16.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:1075 (1.0 KiB)

eth0      Link encap:Ethernet  HWaddr 00:18:84:A0:CD:04  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:2118 (2.0 KiB)
          Interrupt:4 Base address:0x1000 

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

root@OpenWrt:/# arp -n
IP address       HW type     Flags       HW address            Mask     Device
172.16.1.49      0x1         0x0         00:00:00:00:00:00     *        br-lan
root@OpenWrt:/# 

Attachments (0)

Change History (8)

comment:1 Changed 10 years ago by xkennyx at seznam.cz

Hi, maybe it is the same problem like me (ticket #2387, #2386)
I try the command "arp -n" too and we will see.

comment:2 follow-ups: Changed 10 years ago by nbd

support for the switch hasn't been merged yet. the code still needs some cleanup

comment:3 in reply to: ↑ 2 Changed 10 years ago by Mike Barnes <mike@…>

Replying to nbd:

support for the switch hasn't been merged yet. the code still needs some cleanup

Is this going to happen in the near future?

comment:4 in reply to: ↑ 2 Changed 10 years ago by Andrey Nepomnyaschih <nas@…>

Replying to nbd:

support for the switch hasn't been merged yet. the code still needs some cleanup

I also have the same question as Mike Barnes has.

Additionally is there something a person without decent programming skills can do to speed up the merge of the code?

comment:5 Changed 10 years ago by arkanoid

any update on this? it's been a while now an i think most people are waiting for this to be fixed before buying a fonera+.

comment:6 Changed 10 years ago by anonymous

If switch is MARVELL 88e6060(DDWRT HW SITE), bring up can be done hw by use of pullup/down.
If all is done properly the input port is replicated on the RJ connector.
and you're done.
The privileged ports that work this way are P0 (pin 4 5 7 8) and P1 (pin 9 10 12 13)
if other ports have been used, explicit setting has to be done.
so can be used a eeprom uwire93c66 or eventually a spi interface using spare
i/o.
I don't have fonera schematics nor data sheets of atheros, so basic reverse enginering is not worth...
Do you have detailed informations of marvell?
Regards
Manuel

comment:7 Changed 10 years ago by davide_lenza

Any news on this? I can reflash openwrt kamikaze 7.09 on Fonera+ but then I am not able to access the Fonera+ after the "fis load -l vmlinux.bin.l7" + "exec": only Redboot remain available after a reboot.

Does someone has a functional also if not perfect version? Only to understand if this is the source of my problem with the flashing of Fonera+.

Thanks

comment:8 Changed 10 years ago by nbd

  • Resolution set to fixed
  • Status changed from new to closed

finished in [10877]

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.