To the interface itself I see successful pings. To the router (192.168.0.1) - no.
root@ls1012ardb:~# ping 192.168.0.51
PING 192.168.0.51 (192.168.0.51) 56(84) bytes of data.
64 bytes from 192.168.0.51: icmp_seq=1 ttl=64 time=0.089 ms
64 bytes from 192.168.0.51: icmp_seq=2 ttl=64 time=0.048 ms
...
root@ls1012ardb:~# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.50 icmp_seq=1 Destination Host Unreachable
From 192.168.0.50 icmp_seq=2 Destination Host Unreachable
...
By the way, for the purity of experiments, I mostly perform it at one interface at a time. Like this:
1. plug in only eth0
2. boot
3. try getting ip over DHCP using 'udhcpc -i eth0'
3a. if DHCP fails - set static IP with 'ip addr add, ip link set up'.
4. ping interface
5. ping router
6. repeat for eth1
So this way in my current configuration only eth1 gets IP from DHCP and able to ping both interface and router.
For eth0 both DHCP fails and static IP is not able to ping the router. Though able to ping interface.
New information. By try and error, I have found that after:
1. commenting out control write register in SERDES configuration somewhy helps to get DHCP
2. disabling phy_start() procedure
(diff is attached).
both eth0 and eth1 are working now. Acquiring IP from DHCP and able to ping the router.
I would have thought that if commenting out phy_start() helps this way that means the problem is in the generic PHY driver. But then why eth1 works from the start? Both PHYs are identical DP83867.
Any ideas?
Best regards,
Lavnikevich Dmitry
