Obviously someone at Dell has to make decisions on things like this, and they will need to do so based on commercial pressures more than anything else, which is fair enough.
But the TUN/TAP interface is a standard Linux "thing", and OpenVPN is a pretty common and "standard" application to be run on servers. By making OMSA essentially incompatible with OpenVPN, Virtuozzo, OpenVZ and many other things, Dell is unintentionally creating severe problems for an awful lot of important customers. (In my experience Dell hardware seems to be used extensively in the hosting industry, and Virtuozzo is one of the most common virtualisation product for Linux-based VPSes within that industry). So hopefully this issue will be resolved sooner than we expect (crosses fingers). It is interesting that it works with TAP when it won't work with TUN though. Faris. > -----Original Message----- > From: [email protected] [mailto:linux- > [email protected]] On Behalf Of Jeremy Smith > Sent: 15 August 2009 17:58 > To: [email protected] > Subject: Re: OMSA yum upgrade to 6.1 broken > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jeremy Smith wrote: > | In hopes of Thomas's guess about the device names being the cause of > the > | issue, I was able to make openvpn create a tun device with the name > eth2 > | instead of tun0. Unfortunately, this did not solve the problem. > omreport > | still > | failed with: > | ... > > I spoke with Dell support on this. Apparently, they are aware of OMSA > having > trouble (not working) when TUN devices exist on the system. But they > told me > that since I was using unsupported free software (OpenVPN) that they > couldn't > officially support fixing the issue. I tried to explain that OpenVPN > simply > uses the TUN device interface via Linux kernel drivers and that I could > also > create a TUN devices with other software or even Linux itself, but they > failed > to grasp this. I had the tech talk to the OMSA development (at least he > told > me he did). He indicated that they are aware of the issue and at some > point > they expect to "implement support" for this. Clearly, he still didn't > understand that this issue was a failure of the OMSA software to work > with > Linux itself. > > However, I did discover that in my case I can use TAP devices instead > of TUN > devices with OpenVPN without OMSA crashing. While this is not exactly > what I > wanted, it will be a sufficient workaround for now. > > - -- > Jeremy Smith > Systems Administrator > eSilo, LLC. > [email protected] > > > > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkqG6SEACgkQgVS2ACgBQ6LiAACdEtMr7QOz1VAYWz0p/819xKk5 > 0v8An0zQsQNWdCyj8mkoa4QpY7A40kLk > =GXFj > -----END PGP SIGNATURE----- > > _______________________________________________ > Linux-PowerEdge mailing list > [email protected] > https://lists.us.dell.com/mailman/listinfo/linux-poweredge > Please read the FAQ at http://lists.us.dell.com/faq _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
