LAN doesn't work in 19.07.2 custom build

epiniguin · April 30, 2020, 10:17pm

In the moment I have not a crossover cable. Tomorrow I will make it.
But I guess that if it works normally without a crossover cable on 18.06 it has to work on 19.07.

psherman · April 30, 2020, 10:19pm

I'm just throwing out a few ideas... I don't think it will solve the problem, but worth testing.

Another thought -- if you remove eth1 from the LAN (bridge), that would put the LAN only on eth0.1 (switch) and the radio. I wonder if that could help.

epiniguin · April 30, 2020, 10:20pm

It was initial config and it did not work also.

epiniguin · April 30, 2020, 10:25pm

Now I switched off WLAN, removed a bridge, but it does not work

root@OpenWrt:/# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:22:B0:BA:50:1F
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:1043 (1.0 KiB)
          Interrupt:4

eth0.1    Link encap:Ethernet  HWaddr 00:22:B0:BA:50:1F
          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: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)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:32 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2636 (2.5 KiB)  TX bytes:2636 (2.5 KiB)

psherman · April 30, 2020, 10:28pm

I'm assuming that the ethernet configuration on the laptop is correct and functioning.

Otherwise, I'm out of ideas for now.

I will say that this may not really worth the effort -- maybe just roll back to 18.06.x or invest in a new (more capable) device.

epiniguin · April 30, 2020, 10:37pm

I have modern capable devices but I wanted(like a hobby) to force to work this DIR615-C1 with new firmware. By the way it works without problem on 18.06 and I don't see any reason to throwing it away.
I guess that there are some misconfigurations or bugs in drivers for this device in 19.07.

epiniguin · April 30, 2020, 10:41pm

It is from wireshark.
If I understand right, packets from D-link reach the laptop.
But packets from the laptop do not reach D-link.

44	13.940690	D-Link_ba:50:1f	Broadcast	ARP	60	Who has 192.168.1.2? Tell 192.168.1.1
45	13.940706	Dell_23:0f:12	D-Link_ba:50:1f	ARP	42	192.168.1.2 is at a4:bb:6d:23:0f:12
46	14.960433	D-Link_ba:50:1f	Broadcast	ARP	60	Who has 192.168.1.2? Tell 192.168.1.1
47	14.960444	Dell_23:0f:12	D-Link_ba:50:1f	ARP	42	192.168.1.2 is at a4:bb:6d:23:0f:12

retiredtab · July 19, 2020, 10:44pm

@epiniguin, I'm able to replicate your problem.

I know my 615c1 works fine with 17.01, but when building with imagebuilder and 19.07, the 615 fails to respond to a simple ping, just as you found.

I don't have an serial port to connect to the 615, but when a simple ping fails, something is definitely wrong.

Your output from ifconfig

Your stats show that eth0 sent 10 packets, but received none. You can see that in RX packets:0
and RX bytes:0.

root@OpenWrt:/# ifconfig
br-lan Link encap:Ethernet HWaddr 00:22:B0:BA:50:1F
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:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:378 (378.0 B)

eth0 Link encap:Ethernet HWaddr 00:22:B0:BA:50:1F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1475 (1.4 KiB)
Interrupt:4

eth0.1 Link encap:Ethernet HWaddr 00:22:B0:BA:50:1F
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:378 (378.0 B)

Wireshark trace

In your wireshark trace, packets are leaving the 615 and reaching the laptop. The laptop is properly responding to pings.

Suggestions

See if the router has an arp entry for your laptop using the command

ip neigh

Start pinging the router on your laptop. See if ethernet packets are making it into the router with

cat /proc/net/dev

and see if the command ifconfig shows the RX bytes and RX packets are still 0.

The 615 uses "AR8216 6-port switch" according to

https://openwrt.org/toh/d-link/dir-615#tab__revisions_c1c2

At github

github.com

openwrt/openwrt/blob/master/target/linux/generic/files/drivers/net/phy/ar8216.c

/*
 * ar8216.c: AR8216 switch driver
 *
 * Copyright (C) 2009 Felix Fietkau <nbd@nbd.name>
 * Copyright (C) 2011-2012 Gabor Juhos <juhosg@openwrt.org>
 *
 * This program is free software; you can redistribute it and/or
 * modify it under the terms of the GNU General Public License
 * as published by the Free Software Foundation; either version 2
 * of the License, or (at your option) any later version.
 *
 * This program is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.
 */

#include <linux/if.h>
#include <linux/module.h>
#include <linux/init.h>

This file has been truncated. show original

shows changes that might have broken something?

Commits are below.

If you are compiling directly from source and not image builder, maybe try an older version of ar8216.c and ar8216.h to see if the older versions work? If an older version works, then you can apply one patch at a time to see which patch breaks the funtionality?

If the bug is in ar8216.c, then I suspect other devices using the AR8216 switch would same problem.

My search openwrt.org/toh were inconclusive if AR8216 is widely used or not. The parameter search doesn't allow for ethernet switch.

If you can opkg install ethtool or compile ethtool into your build, check to see if speed and duplex are correct with your laptop.

ethtool eth0

Sometimes wierd problems happen if both parties don't negotiate ethernet properly. One side might be 100 full duplex and the other might be 10 half duplex.

Comment on 11.0

PS. RFC6761 defines which address are for private home use (section 6.1)

https://tools.ietf.org/html/rfc6761

Using 11.0 for testing purposes, however, has no affect on whether the 615 responds to pings or not in your simple test.

retiredtab · July 22, 2020, 10:12pm

I was correct. 615c1 works fine with four 18.06.8 files

/target/linux/generic/files/drivers/net/phy

ar8216.c, ar8216.h, ar8327.c and ar8327.h

Changes were made in 19.07.1 to the above and it breaks the functionality.

I did a snapshot build today, July 22, 2020 and if I keep the 18.06.8 files in my build, it works correctly.

OpenWrt SNAPSHOT, r13911-b057862e24

root@LEDE:~# uname -a
Linux LEDE 4.14.187 #0 Wed Jul 22 16:59:44 2020 mips GNU/Linux

retiredtab · July 23, 2020, 10:20pm

I opened a bug report.

https://bugs.openwrt.org/index.php?do=details&task_id=3246

epiniguin · July 27, 2020, 8:26am

Thanks!
I was sure that it is a bug.

WaldoX · September 29, 2023, 11:25pm

hi i have a dlink 615 c1, do you have a link where i can get a copy of the latest version 18.06.8 upgrade for this router?

thanks in advance

RuralRoots · September 29, 2023, 11:32pm

not recommended

WaldoX · September 29, 2023, 11:46pm

i believe the build is not on the public servers, as its his own custom build
thanks for the link, but i didnt see the build there

RuralRoots · September 30, 2023, 6:16am

Sorry. Didn’t look at the device. This is a 4/32 device that stopped being supported after 17.01.7.

Based on your response I see this was a custom build for 18.06.8. Unless you’re skilled in building a minimal build, you’re sol. Frankly, I wouldn’t let it loose in the wild.