[Bug 279384] dwc: all incoming packages rejected because of bad checksums

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=279384

            Bug ID: 279384
           Summary: dwc: all incoming packages rejected because of bad
                    checksums
           Product: Base System
           Version: CURRENT
          Hardware: arm
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: arm
          Assignee: freebsd-arm@FreeBSD.org
          Reporter: helmut.schlattl@web.de

kernel version: FreeBSD 14.1-STABLE stable/14-n267765-5dced4143910
system: Lemaker BananaPI Pro (SOC: A20)

Overview: 
No LAN-connection possible. Apparently there is some problems with the
checksums:

Steps to Reproduce: 
dhclient -d dwc0

Actual result:
DHCPDISCOVER on dwc0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on dwc0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on dwc0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on dwc0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on dwc0 to 255.255.255.255 port 67 interval 10
5 bad IP checksums seen in 5 packets
DHCPDISCOVER on dwc0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on dwc0 to 255.255.255.255 port 67 interval 5
No DHCPOFFERS received.
No working leases in persistent database - sleeping.

At the DHCP server the DHCP requests and replies are visible (tcpdump ... port
bootps):
19:20:50.773224 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
02:0c:05:81:21:8c (oui Unknown), length 300
19:20:54.118494 IP asus.67 > 192.168.6.100.68: BOOTP/DHCP, Reply, length 308
19:20:57.162472 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
02:0c:05:81:21:8c (oui Unknown), length 300
19:20:57.163067 IP asus.67 > 192.168.6.100.68: BOOTP/DHCP, Reply, length 308
19:21:04.298389 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
02:0c:05:81:21:8c (oui Unknown), length 300
19:21:04.299397 IP asus.67 > 192.168.6.100.68: BOOTP/DHCP, Reply, length 308
19:21:16.365076 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
02:0c:05:81:21:8c (oui Unknown), length 300
19:21:16.365619 IP asus.67 > 192.168.6.100.68: BOOTP/DHCP, Reply, length 308
19:21:28.500666 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
02:0c:05:81:21:8c (oui Unknown), length 300
19:21:31.582031 IP asus.67 > 192.168.6.100.68: BOOTP/DHCP, Reply, length 308
19:21:38.636503 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
02:0c:05:81:21:8c (oui Unknown), length 300
19:21:38.636877 IP asus.67 > 192.168.6.100.68: BOOTP/DHCP, Reply, length 308
19:21:46.684215 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from
02:0c:05:81:21:8c (oui Unknown), length 300
19:21:46.684607 IP asus.67 > 192.168.6.100.68: BOOTP/DHCP, Reply, length 308

Expected result: 
DHCP address is accepted.

Further information:

Also tried setting the IP address manually, but there is then also no usable
LAN-connection.
E.g. ping 192.168.6.50
Result:
PING 192.168.6.50 (192.168.6.50): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down

But 192.168.6.50 is pingable from other hosts on the same network.

On kernel releng/14.0-n265380-f9716eee8ab4-dirty everything worked fine.

-- 
You are receiving this mail because:
You are the assignee for the bug.