Summary: | Baselayout does not assign IPv6 addresses and routes to wired interface upon boot (but works with wireless). | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Antek Grzymała (antoszka) <antoni> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED NEEDINFO | ||
Severity: | major | CC: | audun, glua, roy |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Screenshot of the system booting up with errors |
Description
Antek Grzymała (antoszka)
2008-12-01 17:06:28 UTC
Created attachment 173983 [details]
Screenshot of the system booting up with errors
Sorry to bug, but this seems quite a serious issue (I'm deploying production IPv6 on a number of systems these days). Can I help with debugging or anything? ICMP ECHO REQUEST If you want any help from me, you'll have to upgrade to OpenRC as I've tested that there and it works fine. Please upgrade to the latest version of openrc. If this is still an issue, please re-open this bug and let us know. Thanks, William Sorry to revive this bug, but this actually is a real issue, as there is no information whatsoever about OpenRC in the documentation on setting up an IPv6 router. There is no information that it even exists. Furthermore, OpenRC is masked; - sys-apps/openrc-9999 (masked by: missing keyword) - sys-apps/openrc-0.6.0 (masked by: ~amd64 keyword) Personally, I am not comfortable with unmasking too many packages on a production system. Finally, the introduction to OpenRC seems far from trivial, making the transition something not to take too lightly, especially on a production system. I suppose there might be unresolvable issues with the traditional rc scripts. In that case, this bug should be forwarded to the documentation team, as OpenRC probably needs mentioning (or more) in the main handbook, or the very least the IPv6 router guide. we arent backporting major things to baselayout-1. if openrc works, then use that. if you dont want to unmask it, then find some workaround for your system until it does stabilize. This works for me; how is IPv6 compiled? If it is a module, you may need it in modules.conf, or you may want to compile it into the kernel. Sorry to bring this one to the surface yet again, but I do have some new information. The problem seems to be whether or not the IPv6 system is built into the kernel or as a module. The problem still exist with openrc-0.6.1-r1 and baselayout-2.0.1, but goes away as soon as I build IPv6 into the kernel itself. As soon as I built IPv6 into the kernel, i.e. NOT as a module, everything works as it should. That would explain why it seemed to work on some of my servers, but not on the majority of them. Having automounter support built-in, I have never really thought much about module loading/unloading for a very long time. I still think this should be mentioned in either the Gentoo Handbook or the IPv6 how-to, but otherwise, this is resolved without need of further information... Well, I have somewhat contradicting news. I'm running baselayout-2.0.1/openrc-0.6.1-r1 and I don't have a problem with having v6 addresses/routes assigned at boot even though I have ipv6 built as a module. However, I have it listed in /etc/conf.d/modules -- so it probably gets loaded early enough for address/route assignment to work correctly. This may be a solution in your case, too. Since baselayout 1.x/non-openrc systems are pretty much dead for me I probably should close the bug. Yes, I suppose /etc/conf.d/modules would have done the trick for me as well, but I also had to upgrade from kernel 2.6.30-r4, so it was just as easy to compile it in. Anyway, the fact that there is no mention of a baselayout2 _anywhere_ in the installation docs, makes this problem hard to fix for someone new to Gentoo. Hell, I have been using Gentoo for 5-6 years, and the first I heard of it, was this bug report. I only set up baselayout2 today, and it was still not trivial, as the docs states I should move what I need from /etc/conf.d/rc to "appropriate" settings in /etc/rc.conf. The problem is, all those settings are not present in the new file. And the other files in /etc/conf.d also have a lot of changed variable names and values, so wouldn't it be better to start extensive testing on baselayout2 and openrc, making it the default when installing Gentoo? Should I open a new bug report for that, as we have now moved a bit away from the original bug? (In reply to comment #11) > Yes, I suppose /etc/conf.d/modules would have done the trick for me as well, > but I also had to upgrade from kernel 2.6.30-r4, so it was just as easy to > compile it in. Enough of BL1/IPv6 issues here. Everybody should just make sure IPv6 is loaded ahead of trying to use it. > Should I open a new bug report for that, as we have now moved a bit away from > the original bug? Look at the tracker bug for openrc/BL2. It's not quite ready yet, but it's getting there. Your observations above would be useful on the documentation parts of that bug. |