RE: dchlient does not autostart anymore?

[M - Krasznai András]

Hi
I am on r315901 and still have the problem.  

I am using an aggregate interface lagg0 created from my Ethernet adapter and my 
WiFi; I use this configuration since a few months without any change and 
without problems. dhclient still does not start automatically for lagg0 since 
Thursday morning update.


Of course I can start dhclient manually after logging in, and get IP address.

best regards

András Krasznai


- Original Message-
From: owner-freebsd-curr...@freebsd.org 
[mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of Warner Losh
Sent: Friday, March 24, 2017 6:07 PM
To: Vladimir Zakharov
Cc: Jung-uk Kim; Kirill Ponomarev; FreeBSD Current
Subject: Re: dchlient does not autostart anymore?

On Fri, Mar 24, 2017 at 10:53 AM, Vladimir Zakharov <zakharov...@gmail.com> 
wrote:
> On Fri, Mar 24, 2017, Jung-uk Kim wrote:
>> On 03/24/2017 11:20, Kirill Ponomarev wrote:
>> > On 03/24, Vladimir Zakharov wrote:
>> >> Hello!
>> >>
>> >> 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.
>> >
>> > Same issues here with today CURRENT, r315896.
>>
>> FYI, r315901 fixed the issue for me.
>
> For me too. Thanks.

Yea, sorry about the brief breakage... I didn't notice until after I'd 
committed Ian's much improved version there'd been a problem. Stupid mistake on 
my part committing out of the wrong tree for the change that caused problems.

Warner
___
freebsd-current@freebsd.org mailing list 
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: dchlient does not autostart anymore?

[Warner Losh]

On Fri, Mar 24, 2017 at 10:53 AM, Vladimir Zakharov
 wrote:
> On Fri, Mar 24, 2017, Jung-uk Kim wrote:
>> On 03/24/2017 11:20, Kirill Ponomarev wrote:
>> > On 03/24, Vladimir Zakharov wrote:
>> >> Hello!
>> >>
>> >> 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.
>> >
>> > Same issues here with today CURRENT, r315896.
>>
>> FYI, r315901 fixed the issue for me.
>
> For me too. Thanks.

Yea, sorry about the brief breakage... I didn't notice until after I'd
committed Ian's much improved version there'd been a problem. Stupid
mistake on my part committing out of the wrong tree for the change
that caused problems.

Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: dchlient does not autostart anymore?

[Vladimir Zakharov]

On Fri, Mar 24, 2017, Jung-uk Kim wrote:
> On 03/24/2017 11:20, Kirill Ponomarev wrote:
> > On 03/24, Vladimir Zakharov wrote:
> >> Hello!
> >>
> >> 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.
> > 
> > Same issues here with today CURRENT, r315896.
> 
> FYI, r315901 fixed the issue for me.

For me too. Thanks.

-- 
Regards, | "In theory there is no difference between theory
  Vladimir Zakharov  | and practice. In practice there is."- Yogi Berra
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: dchlient does not autostart anymore?

[Kirill Ponomarev]

On 03/24, Vladimir Zakharov wrote:
> Hello!
> 
> 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.

Same issues here with today CURRENT, r315896.

K. 


signature.asc
Description: PGP signature

Re: dchlient does not autostart anymore?

[Jung-uk Kim]

On 03/24/2017 11:20, Kirill Ponomarev wrote:
> On 03/24, Vladimir Zakharov wrote:
>> Hello!
>>
>> 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.
> 
> Same issues here with today CURRENT, r315896.

FYI, r315901 fixed the issue for me.

Jung-uk Kim



signature.asc
Description: OpenPGP digital signature

Re: dchlient does not autostart anymore?

[Kirill Ponomarev]

On 03/24, Vladimir Zakharov wrote:
> Hello!
> 
> 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.

Same issues here with today CURRENT, r315896.

K.


signature.asc
Description: PGP signature

Re: dchlient does not autostart anymore?

[David Wolfskill]

On Fri, Mar 24, 2017 at 01:56:38AM -0700, Mark Millard wrote:
> 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.)
> 

Well, I just updated my (amd64) laptop from:

FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #293  
r315853M/315854:1200027: Thu Mar 23 06:41:30 PDT 2017 
r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY  amd64

to:

FreeBSD g1-252.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #294  
r315896M/315899:1200027: Fri Mar 24 06:36:28 PDT 2017 
r...@g1-252.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY  amd64

... and had no issues (with dhclient, mouse, or anything else).

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Who would have thought that a "hotelier" would be so ... unwelcoming?  Sad.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: dchlient does not autostart anymore?

[Ruslan Makhmatkhanov]

M - Krasznai András wrote on 03/24/2017 14:14:

It seems that usb mouse port has been changed from /dev/psm0 to /dev/ums0; 
loading ums.ko  with kldload and restarting the mouse with

moused -p /dev/ums0

makes the mouse work again (but now the touchpad is not working; I can survive 
that).

rgds

András Krasznai


I did kldload ums; service devd restart; dhclient wlan0 to solve both 
the problems. Btw, both mouse and touchpad are working. Thank you for 
the temporary solution!


--
Regards,
Ruslan

T.O.S. Of Reality
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: dchlient does not autostart anymore?

[Alexandr Krivulya]

+1
Need to manualy kldload ums.ko and start dhclient.

24.03.2017 12:38, Lev Serebryakov пишет:

On 24.03.2017 12:28, M - Krasznai András wrote:

  devd problems? Now dhclient and moused are started by devd.


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-curr...@freebsd.org 
[mailto:owner-freebsd-curr...@freebsd.org] Meghatalmazó Mark Millard
Küldve: 2017. március 24. 9:57
Címzett: zakharov...@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@freebsd.org mailing list 
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"






--
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: dchlient does not autostart anymore?

[M - Krasznai András]

It seems that usb mouse port has been changed from /dev/psm0 to /dev/ums0; 
loading ums.ko  with kldload and restarting the mouse with 

moused -p /dev/ums0 

makes the mouse work again (but now the touchpad is not working; I can survive 
that).

rgds

András Krasznai



-Eredeti üzenet-
Feladó: Ruslan Makhmatkhanov [mailto:r...@freebsd.org] 
Küldve: 2017. március 24. 12:04
Címzett: FreeBSD Current
Másolatot kap: M - Krasznai András
Tárgy: Re: dchlient does not autostart anymore?

The same for me (usb mouse + dhclient) on r315874. Touchpad is working.

-- 
Regards,
Ruslan

T.O.S. Of Reality
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: dchlient does not autostart anymore?

[Ruslan Makhmatkhanov]

The same for me (usb mouse + dhclient) on r315874. Touchpad is working.

--
Regards,
Ruslan

T.O.S. Of Reality
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: dchlient does not autostart anymore?

[Lev Serebryakov]

On 24.03.2017 12:28, M - Krasznai András wrote:

 devd problems? Now dhclient and moused are started by devd.

> 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-curr...@freebsd.org 
> [mailto:owner-freebsd-curr...@freebsd.org] Meghatalmazó Mark Millard
> Küldve: 2017. március 24. 9:57
> Címzett: zakharov...@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@freebsd.org mailing list 
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 


-- 
// Lev Serebryakov
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

RE: dchlient does not autostart anymore?

[M - Krasznai András]

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-curr...@freebsd.org 
[mailto:owner-freebsd-curr...@freebsd.org] Meghatalmazó Mark Millard
Küldve: 2017. március 24. 9:57
Címzett: zakharov...@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@freebsd.org mailing list 
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: dchlient does not autostart anymore?

[Mark Millard]

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@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

dchlient does not autostart anymore?

[Vladimir Zakharov]

Hello!

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.

-- 
Regards, | "In theory there is no difference between theory
  Vladimir Zakharov  | and practice. In practice there is."- Yogi Berra
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"