Hi, everybody.

I've got an RDC8610 Evaluation Board. This is in fact a development kit based on a RDC8610 chip. So it is very similar to the openwrt supported devices (Amit, ar525w etc).
I managed to build a ramdisk image of kamikaze (trunk @ r13499) with several packages included and to flash the device. It boots, i can execute commands over serial.

The problem is that ethernet networking doesn't work at all.
Alfer a reboot ifconfig says that 'br-lan' and 'eth0' interfaces are up and running with correct network config (ip,mask). But arping/ping to the host machine shows 100% packet loss. Wireshark on the host machine doesn't see any ARP packages from the device (while it sees ARPs from other network devices). It is also not possible to ping the device back. Physical connectivity is ok, since i can ping redboot during startup.

The device also has another interface eth1. It is down by default, but it is possible to 'ifconfig eth1 up' it with given network configuration. The same: arping/ping doesn't work, no ARP packets are captured on the host machine.

Any ideas?

Thank you in advance!

Some things to try:

Just doing "ifconfig eth1 up" is not enough--you want to add it to the LAN bridge along with eth0.
You can do this with:

uci set network.lan.ifname="eth0 eth1"
/etc/init.d/network restart
(if it does not break anything:)
uci commit network

Also, if it is really similar to the AR525W, it may have a ip175c switch chip onboard which needs some patches to be able to change its configuration, but depending on its defaults, you may need to add a vlan interface like eth0.1 or eth1.1

In fact i don't want to bridge an interface that doesn't work with a bridge that doesn't work neither :-)

All i want is one of the two interfaces up. And with one of the previous kamikaze revisions i was able make eth0 work with the following sequence of commands:

ifconfig br-lan down
ifconfig eth0 down
brctl delbr be-lan
ifconfig eth0 hw ether XX:XX:XX:XX:XX:XX
ifconfig eth0 up

But not with 13358 revision i've just downloaded.

root@OpenWrt:/# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:FC:02:03:04
          inet addr:192.168.1.252  Bcast:192.168.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:25 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:1050 (1.0 KiB)
          Interrupt:11

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:14 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1568 (1.5 KiB)  TX bytes:1568 (1.5 KiB)

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

--- 192.168.1.1 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss

(Last edited by outsourcer on 7 Dec 2008, 19:50)

This might be a side effect of changes I made to the Ethernet driver. Are you still having the issue?

...works fine with revision 17296