FS#18015 - [dhclient] broken
Attached to Project:
Arch Linux
Opened by Michal (broch) - Tuesday, 26 January 2010, 13:46 GMT
Last edited by Isenmann Daniel (ise) - Wednesday, 30 June 2010, 17:56 GMT
Opened by Michal (broch) - Tuesday, 26 January 2010, 13:46 GMT
Last edited by Isenmann Daniel (ise) - Wednesday, 30 June 2010, 17:56 GMT
|
Details
Description:
1) latest dhclient version 4.1.0.p1-2 does not handle basic commands anymore: for example IP release does not work: sudo dhclient -r eth0 $ ifconfig eth0 Link encap:Ethernet HWaddr inet addr:10.xxx.xxx.xxx Bcast:10.xxx.xxx.xxx Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2352 errors:0 dropped:0 overruns:0 frame:0 TX packets:717 errors:0 dropped:0 overruns:0 carrier:0 collisions:156 txqueuelen:1000 RX bytes:514048 (502.0 Kb) TX bytes:81227 (79.3 Kb) so after issuing "release" command IP is still assigned. 2) dhclient moved from /sbin/dhclient to /usr/dhclient Additional info: * package version(s) 4.1.0.p1-2 * config and/or log files etc. arch linux i686 up to date Steps to reproduce: simply upgrade to the latest dhclient and try command liste above. I downgraded to dhclient 3.0.6-2 and this is how release IP address works now: sudo dhclient -r eth0 There is already a pid file /var/run/dhclient.pid with pid 5071 killed old client process, removed PID file Internet Systems Consortium DHCP Client V3.0.6 Copyright 2004-2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ Listening on LPF/eth0/xx:xx:xx:xx:xx:xx Sending on LPF/eth0/xx:xx:xx:xx:xx:xx Sending on Socket/fallback DHCPRELEASE on eth0 to 10.2.25.25 port 67 It looks like recent dhclient version 4.1.0.p1-2 is real mess: 1) failing script commands (e.g. IP release) - reported here 2) dhclient 4.1.0.p1-2 moved from /sbin/dhclient to /usr/sbin/dhclient without warning which brakes loading dhclient from /etc/rc.d/network script 3) problems mentioned in 4) problems mentioned in a lot of problems arised with single update of dhclient. |
This task depends upon
Closed by Isenmann Daniel (ise)
Wednesday, 30 June 2010, 17:56 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in newest package 4.1.1-P1 in [extra]
Wednesday, 30 June 2010, 17:56 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in newest package 4.1.1-P1 in [extra]
both dhclient 3.0.6-2 and dhclient 3.2.1-1 work but only dhcpcd 3.2.1-1 should be used because dhclient 3.0.6-2 suffers from Stack Buffer Overflow Vulnerability (http://www.securityfocus.com/bid/35668)
Three points you mentioned above are totally unnecessary.
Answers to your points:
1) Yeah, that's maybe really a bug, maybe in dhclient itself and has maybe nothing to do with the Arch package
2) This was discussed in other bug reports already and will be fixed with the next package release and has nothing to do with your initial bug report
3) and 4) see 2)
title of this bug report: dhclient broken (see ad1, ad2, ad3, ad4)
My explanation:
ad1) reported here. I don't accuse dhclient maintainer of introducing specific bug. I am reporting a bug.
ad2) regarding moving location from /sbin/dhclient to /usr/sbin/dhclient (in addition to dhclient-script)
I did mention this in http://bugs.archlinux.org/task/17885 but because in the above thread is a lot of disscussion in general, I was not sure if person responsible for dhclient maintenance will see this.
again, I just reported a bug
ad3) and ad4) this is my comment in general to the fact that single update introduced not one but several problems.
I am not accusing anyone. I am surprised that so many problems popped out in one update. In addition dhcp networking is quite broken in 2.6.32 kernel release (not arch fault). Add this to the fact that dhcpcd client is also quite broken for a long time (not arch fault). So whole dhcp networking is failing.
I am a little bit frustrated.
I do think though that before releasing new version of dhclient, it should be tested.
If my comments offended you, then I am sorry.
The main problem about testing is, that if I put it in [testing] repo, then I don't get any response (this is my personal view, same with wicd, put it in testing and only get 2 positive feedbacks. Moved it to [extra] and I got a lot of bug reports about broken wicd and what a crappy package,etc.)
About your bug report, I will have a look into point 1), the other points are already reported and will be discussed there. I have posted my solution already there.
You don't offended me, but reading bug reports sometimes are really annoying. I hope you can understand me a little bit.
My network setups:
home wireless wpa2
work 1) wired
work 2) cisco vpn wireless
Personally, I would not mind testing part of the software I have installed, but activating [testing] automatically updates (offers option to) update all installed packages.
Is there a way to open [testing] and set it only for selected packages (same way as ignore=) eg update= list packages from testing that I want to try out (and report testing bugs)?
thanks
I didn't have the time yet to investigate it further, but I haven't forget it.
I understand. I will wait. Currently using dhclient 3.1.2p1-3
thank you very much