Beware of dhcpcd-6.11.0

[are]

Killed my Wired Connection on the desktop computer and also the Wireless Connection on the laptop -- both against the same router though.
Interestingly I could make it work by using Android tethering via USB (dhcpd-6.11.0 got that one right), the Android phone could connect against this router as well as another Ubuntu Laptop ( ).

Masking 6.11.0 and reversing to 6.10.3 solved my problems on both machines.
Cheers

Could it be linked to http://roy.marples.name/projects/dhcpcd/tktview?name=3f10c9b871? ff so, then a patch seems to be available. Given that it breaks the ability to connect to the internet, it would be nice if that could be applied/pushed.[/url]

[steveL]

[are]

[NeddySeagoon]

are,

You will probably still have the distfiles and ebuild for the last release. If so, emerge can install a specific version for you.
If you run all ~arch, you need to use FEATURES="buildpkg" too, so you can use emerge -K to back out broken things.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[steveL]

[UberLord]

[UberLord]

As others have said, network management is a complex beast.
There have been very few dhcpcd releases where a new bug has not been created. Luckily, these bugs are generally with new features. Sometimes they are long standing issues only made more apparent by recent changes. Very rarely do they badly break anything current or well used.

Then consider that dhcpcd is supported by me on Linux, NetBSD, FreeBSD, OpenBSD and (and should work on derivative BSD's), compiles on QNX and is almost working on Solaris with the most feature rich setup system compared to anything else. Then consider the extremely small binary size for what it does (210k on NetBSD amd64 with all features enabled).

Given that I generally make a release about once a month and have done for almost 10 years of dhcpcd thats's about 120 releases (the dhcpcd timeline roughly agrees with me here, 109 releases since dhcpcd-4.0.0, i didn't tag prior releases for lower dhcpcd versions).

[are]

Ueber, you are doing a great job, nobody ever doubted that and actually I am one of your greatest fans for OPENRC alone.
And I never would like to criticize anyone for software failures. Also I am not aware where I did express myself in such a way.

I am running UNSTABLE for good and actually I am surprised how stable it is.

That said, my internet stopped working and it was just difficult to figure out what actually happened. There was at least another thread were a user was lost with that problem. Other people might have been affected still looking for a clue.

Now, all what I indeed have asked for -- considering the inconvenience and given that we are on UNSTABLE in any way -- was to push a fix asap,e specially as the cause was found already. I really do not need that, I have had solved it for myself already. Next time I just will be quiet.

[UberLord]

[charles17]

[are]

Thank you Charles, I appreciate the attempt.
Let me still offer you a polemic different perspective:

1) After an World-Update suddenly there is no internet (which happens not really often, to be fair)
2) The problem is a bit difficult to understand (and also difficult to research without internet)
3) Finally, when having identified the culprit, masking and reversing to the previous version does the trick

Really, I do not see where this How-to-apply-Patches document would have helped? I certainly won't remember that stuff after a day. I never needed it before. I could not have read it without internet either.
And finally masking/reversing solved the problem.

I do not need a patch. I have worked around. The only reason why I recommended to push a patch fast is the concern, that other users might struggle. No you can explain a 1000 users how to apply a patch by themselves -- or you simply just provide ONE patched version, especially when you are in UNSTABLE in anyway. What should go wrong? Breaking the broken version? Can't you guys imagine, that a lot of users out there simply will sync/update world after such an incident, hoping that the flaw might have been found and fixed already?

Please let this topic rest now, Admin please just delete this thread.

[krinn]

[UberLord]

BTW, there are other issues with 6.11.0 that are currently causing other people similar issues with connectivity.

I don't advise PPP users to use dhcpcd-6.11.0 unless explicitly disabling IPv4 on their PPP interface in dhcpcd.conf.
This has just been resovled in the dhcpcd trunk and just leaves one more issue to resolve before a new release.

I'll also note that IPv6 connectvity with dhcpcd-6.11.0 so far works fine.
_________________
Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool

[steveL]

[lasuit]

Uberlord, I see that dhcpcd-6.11.1 is now out and it fixed my problem with DHCPv4, although DHCPv6 worked, some websites didn't load well with that connection. Back to normal operation now. Thanks.

[UberLord]

Well, IPv6 is the new shiny which sites should really be using in this day and age!

BTW, you're welcome
_________________
Use dhcpcd for all your automated network configuration needs
Use dhcpcd-ui (GTK+/Qt) as your System Tray Network tool