Re: Strange issue with dhcpd and laster kernel upgrade?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Since it works fine with the previous kernel, and not with the new kernel, that 
would seem to pointing to the kernel versus the other devices.

With the wired devices it is a trendnet router that I've had for many years.
With the wireless, it is a blink wireless router.

In both cases, it worked before the upgrade, and rebooting to the previous 
kernel makes it work again. Just after midnight here, so will have to look into 
the things tomorrow. Have a sunrise ride, and then a funeral escort, so will 
have to wait. I'm still using Fedora 27, so perhaps it is a difference between 
the fedora 27 and Fedora 28.  Will have to see if there is some kind of failure 
message.


On 1 Jun 2018 at 21:38, Ed Greshko wrote:

From:	Ed Greshko <ed.greshko@xxxxxxxxxxx>
Subject:	Re: Strange issue with dhcpd and laster kernel upgrade?
To:	users@xxxxxxxxxxxxxxxxxxxxxxx
Date sent:	Fri, 1 Jun 2018 21:38:27 +0800
Send reply to:	Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx>

> On 06/01/18 20:57, Michael D. Setzer II wrote:
> > Have just had an issue with the dhcp ip addresses no longer working with the 
> > latest kernels on my Fedora 27 machines.
> >
> > Have 4 machines at my house, 2 have fixed IP addresses, so had no 
> > problems, but the other 2 machines stopped getting IPs. Didn't think anything 
> > of it, and just assigned them fixed IP addresses.
> >
> > Have an old notebook that I had just been using, and did the updates. Then 
> > rebooted, and it also would no longer get a connection with the 4.16.12 
> > kernel. Rebooted to the 4.16.11, and it connected with no problem??
> >
> > Rebooted again with the 4.16.12, and it just shows connecting, but no 
> > connection. 
> >
> > Changed the setup to hard code an IP address on the wifi routers range, and 
> > then it connects to the wifi just fine.
> >
> > So Wifi and dhcp connection works fine with 4.16.11, but fails with 4.16.12??
> > Works with the IP address hard coded, so is this a kernel issue or what?
> 
> 
> You've not indicated what system is acting as the dhcp server.
> 
> My system is running F28 and 4.16.12-300.fc28 kernel.  It has one wired interface
> with a fixed IP and a WiFi interface that gets its IP address via DHCP from a
> router.  No issues.
> 
> Not much thought put into this....  But I did "journalctl -b | grep dhcp4 and this is
> the exchange.
> 
> Jun 01 21:36:10 meimei.greshko.com NetworkManager[1017]: <info>  [1527860170.5524]
> dhcp4 (wlp0s29u1u2): activation: beginning transaction (timeout in 45 seconds)
> Jun 01 21:36:10 meimei.greshko.com NetworkManager[1017]: <info>  [1527860170.5554]
> dhcp4 (wlp0s29u1u2): dhclient started with pid 31750
> Jun 01 21:36:10 meimei.greshko.com NetworkManager[1017]: <info>  [1527860170.5924]
> dhcp4 (wlp0s29u1u2):   address 192.168.2.190
> Jun 01 21:36:10 meimei.greshko.com NetworkManager[1017]: <info>  [1527860170.5925]
> dhcp4 (wlp0s29u1u2):   plen 24 (255.255.255.0)
> Jun 01 21:36:10 meimei.greshko.com NetworkManager[1017]: <info>  [1527860170.5925]
> dhcp4 (wlp0s29u1u2):   gateway 192.168.2.5
> Jun 01 21:36:10 meimei.greshko.com NetworkManager[1017]: <info>  [1527860170.5925]
> dhcp4 (wlp0s29u1u2):   lease time 86400
> Jun 01 21:36:10 meimei.greshko.com NetworkManager[1017]: <info>  [1527860170.5925]
> dhcp4 (wlp0s29u1u2):   hostname 'meimei'
> Jun 01 21:36:10 meimei.greshko.com NetworkManager[1017]: <info>  [1527860170.5926]
> dhcp4 (wlp0s29u1u2):   nameserver '192.168.2.5'
> Jun 01 21:36:10 meimei.greshko.com NetworkManager[1017]: <info>  [1527860170.5926]
> dhcp4 (wlp0s29u1u2):   domain name 'greshko.com'
> Jun 01 21:36:10 meimei.greshko.com NetworkManager[1017]: <info>  [1527860170.5926]
> dhcp4 (wlp0s29u1u2): state changed unknown -> bound
> 
> -- 
> Conjecture is just a conclusion based on incomplete information. It isn't a fact.
> 
> 


+------------------------------------------------------------+
 Michael D. Setzer II - Computer Science Instructor (Retired)     
 mailto:mikes@xxxxxxxx                            
 mailto:msetzerii@xxxxxxxxx
 Guam - Where America's Day Begins                        
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
+------------------------------------------------------------+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS

ROSETTA      65562597.392201 | ABC          16613838.513356
SETI        109375858.605587 | EINSTEIN    141132520.999240
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/RURNVKP6V63PAYNXTSISGBI4WN5KZDDC/



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux