Hi list, On re1 interface RTL8168H/8111H
re1: watchdog timeout re1: watchdog timeout re1: watchdog timeout ... kernel messages appeared from time to time when re1 working in DHCP client mode. Martin ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Monday, May 10, 2021 7:17 PM, Martin <[email protected]> wrote: > Hi, > > It seems a bug is still present in re(4) driver even in OpenBSD 6.9 > RTL8168H/8111H adapter. > > Freshly booted machine (address not assigned even during boot process) > without any cable disconnections or sleep/resume RTL8168H/8111H completely > ignores DHCP requests from any clients. > > Don't know how to deal with it. > > Martin > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > On Saturday, May 8, 2021 6:07 PM, George Koehler [email protected] wrote: > > > On Thu, 06 May 2021 16:58:40 +0000 > > Martin [email protected] wrote: > > > > > Small update: > > > The laptop has two integrated adapters: > > > re0 is: RTL8168EP/8111EP - dhcpd re0 -> dhcp server works and give IPs to > > > clients; > > > re1 is: RTL8168H/8111H - dhcpd re1 -> dhcpd server does not reply to > > > client's requests. > > > Martin > > > > I can't reproduce this problem with the re0 RTL8168H/8111H in my AMD > > B450 board. I guess that not every RTL8168H/8111H has problems; there > > was an earlier bug report about RTL8168H/8111H at > > https://marc.info/?l=openbsd-bugs&m=159403196706770&w=2 > > The rest of this mail only shows my dhcpd configuration, and might be > > useless, because you have a working dhcpd on another interface. > > I connected an Ethernet wire from "pehcehwahn" re0 to "maryland" gem0 > > and ran dhcpd re0. The wire was loose (ifconfig re0 said, "status: > > no carrier"), but it began to work after I fixed the wire. The link > > is 100baseTX because my gem(4) can't gigabit. --George > > re0 at pci4 dev 0 function 0 "Realtek 8168" rev 0x15: RTL8168H/8111H > > (0x5400), msi, address 00:d8:61:ca:7a:49 > > rgephy0 at re0 phy 7: RTL8251 PHY, rev. 0 > > pehcehwahn$ ifconfig re0 > > re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > > > > lladdr 00:d8:61:ca:7a:49 > > index 1 priority 0 llprio 3 > > media: Ethernet autoselect (100baseTX full-duplex) > > status: active > > inet 172.27.0.1 netmask 0xffffff00 broadcast 172.27.0.255 > > > > > > pehcehwahn$ cat /etc/hostname.re0 > > inet 172.27.0.1 255.255.255.0 > > pehcehwahn$ cat /etc/dhcpd.conf > > subnet 172.27.0.0 netmask 255.255.255.0 { > > option routers 172.27.0.1; > > option domain-name-servers 172.27.0.1; > > range 172.27.0.32 172.27.0.127; > > ... # other hosts > > host maryland { > > hardware ethernet 00:0a:95:89:5b:f2; > > fixed-address 172.27.0.5; > > option root-path "/home/maryland/root"; > > } > > } > > maryland$ ifconfig gem0 > > gem0: > > flags=248843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,AUTOCONF6TEMP,AUTOCONF6> > > mtu 1500 > > > > lladdr 00:0a:95:89:5b:f2 > > index 2 priority 0 llprio 3 > > groups: netboot egress > > media: Ethernet autoselect (100baseTX full-duplex) > > status: active > > inet6 fe80::20a:95ff:fe89:5bf2%gem0 prefixlen 64 scopeid 0x2 > > inet 172.27.0.5 netmask 0xffffff00 broadcast 172.27.0.255 > > > > > > maryland$ cat /etc/hostname.gem0 > > dhcp > > inet6 autoconf
