RE: dchlient does not autostart anymore?

From: M&S - Krasznai András <Krasznai.Andras_at_mands.hu>
Date: Fri, 24 Mar 2017 09:28:05 +0000
Hi,

FreeBSD-current, r315895 also experiences the same problem. The problem started after updating my laptop yesterday morning. I can get an IP address after manually starting dhclient.

I have an additional anomaly: the USB mouse does not work (touchpad works) on a Lenovo T510 laptop. dmesg shows the correct vendor and type for the mouse.

rgds

András Krasznai



-----Eredeti üzenet-----
Feladó: owner-freebsd-current_at_freebsd.org [mailto:owner-freebsd-current_at_freebsd.org] Meghatalmazó Mark Millard
Küldve: 2017. március 24. 9:57
Címzett: zakharov.vv_at_gmail.com; FreeBSD Current
Tárgy: Re: dchlient does not autostart anymore?

Vladimir Zakharov zakharov.vv at gmail.com  wrote on Fri Mar 24 08:20:34 UTC 2017:

> After upgrading from r315544 to r315880 network interface doesn't get 
> IP address using DHCP on boot anymore.
> 
> $ grep re0 /etc/rc.conf | grep -v "^#"
> ifconfig_re0="DHCP"
> 
> "service netif restart" doesn't help either. Only manual dhclient 
> starting.

I have just updated two contexts to -r315870 just a bit ago and they both got that behavior as well:

A) An amd64 context (FreeBSD client in VirtualBox under macOS)
B) An arm64 context (pine64+ 2GB with -mcpu=cortex-a53 )

Later I'll be updating powerpc64, powerpc, and armv6 (with
-mcpu=cortex-a7 ) contexts but I'd expect they will all match the behavior.

(I started from earlier than -r315544 so your report provides a better lower bound -r315544. I ended earlier and so my report provides a better upper bound -r315870.)

===
Mark Millard
markmi at dsl-only.net

_______________________________________________
freebsd-current_at_freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
Received on Fri Mar 24 2017 - 08:29:21 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:10 UTC