Re: [osol-discuss] [osol-code] OpenGrok Firefox toolbar
The OpenGrok Firefox toolbar extension is now up for download in the OpenGrok Files section: http://opensolaris.org/os/project/opengrok/files/ This is a fairly simple toolbar that is just a quick interface to searching cvs.opensolaris.org and bugs.opensolaris.org. Is there any update to this plugin that's compatible with Firefox 3.5? -- meem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] fw: [networking-discuss] project proposal: unifying NIC configuration via dladm
I assume that this project will be a provider to the NWAM project or is it expected that the functionality this project provides isn't expected to be exposed via the NWAM UI ? I think a lot of these details have yet to be worked out. However, one significant benefit we get by aligning the syntax and semantics of the more fiddly parts of NIC configuration is that higher-level administation tools like NWAM can configure those aspects without low-level knowledge of each and every device. -- meem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] re: [networking-discuss] Proposal for a new OpenSolaris project: Updated MIB support
Several new RFCs (4293, 4022, 4113) have been published that specifies updated MIBs for IP, ICMP, TCP and UDP. I propose a project to provide support for the new MIBs. Some of the issues that need to be addressed are: - Per interface IP statistics for both v4 and v6 (currently that is only done for v6) - Add missing counters and convert some of the existing counters to 64 bits - Update in.ndpd so that MIB agents can extract information from it Seconded. -- meem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] re: [networking-discuss] Re: Re: The 802.3ad link aggregationsupport onnetra 240 (bge broadcom) under solaris 8
but I am not very clear the meaning of By moving it into the networking stack, can I consider the way realize the 802.3ad features in sol 10 is just moving it from kernel to networking stack? The networking stack is in the kernel. With Sun Trunking, the feature is part of the drivers -- e.g., coded into the ce, qfe, and ge drivers (along with a related 'laggr' module). With the bundled support, the feature is part of the GLDv3 kernel networking framework. This means that any driver written to GLDv3 will support link aggregation. Further, as part of Clearview, we are developing a shim that will allow any driver to appear as a GLDv3 driver -- and thus allow link aggregation to work with any Ethernet driver. -- meem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] re: [networking-discuss] The 802.3ad link aggregation support on netra 240 (bge broadcom) under solaris 8
After checking some blog pages of open solaris, I knew that the old type drivers of NIC adapter (eg. qe,fqe,ge) was developed by DLPI or GLDv2, but the bge was developed by GLDv3. I guess sun trunking only support the former method. Sun Trunking is supported by some extensions coded directly into some of the existing monolithic DLPI drivers, such as ge or qfe. The approach has significant flexibility issues (e.g., you can't trunk across different drives), and thus we have moved away from it. Sun does provide a solution: migrate the platform to solaris 10 and use the built-in command dladm to realize the 802.3 link aggregation support. It's no sense to me, there are too many 3-party applications developed under solaris 8 in this project, it's impossible to migrate all of them to solaris 10 just because of the link aggregation problem. If you're stuck on Solaris 8, your options are limited. There are many reasons besides built-in link aggregation to move to Solaris 10, though. We also take our binary compatibility guarantee seriously, and would also be interested in knowing what problems you encounter with third-party software. If it is a matter of vendor support, we would also like to know what key products you need are not supported on Solaris 10. Any one knows which 3-party software can provide this kind of function: I'm not aware of one. However, I'd think you could get some Sun GigaSwift Ethernet (ce) cards, and use Sun Trunking to aggregate them. realize 802.3 support under solaris 8 by GLDv3 method, otherwise I have to study the solaris 10 code for link aggregation and port them to sol 8. I think that would be extremely difficult -- and you would of course end up with a completely unsupported solution. -- meem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] re: [networking-discuss] The 802.3ad link aggregation support on netra 240 (bge broadcom) under solaris 8
Sun Trunking is supported by some extensions coded directly into some of the existing monolithic DLPI drivers, such as ge or qfe. The approach has significant flexibility issues (e.g., you can't trunk across different drives), and thus we have moved away from it. That should read different drivers -- e.g., you can't create a trunk containing ce0 and ge0. -- meem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
[osol-discuss] re: [networking-discuss] Re: The 802.3ad link aggregation support onnetra 240 (bge broadcom) under solaris 8
Thanks for you guys' immediate answer, just like you mentioned, up to now it's an availabe way to plug the ce cards in the netra 240 boxes and use the sun trunking. ... and this is no longer an option? AFAIK, ce cards are still available and qualified for a Netra 240. It's worth pointing out that this issue is because a core OS feature (802.3ad support) was built into the driver rather than the networking stack. By moving it into the networking stack, we ensure this will not happen again. -- meem ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
