Menu
▾
▴
astlinux-users — AstLinux Users Mailing List
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(91) |
Feb
(111) |
Mar
(226) |
Apr
(65) |
May
(197) |
Jun
(202) |
Jul
(92) |
Aug
(87) |
Sep
(120) |
Oct
(133) |
Nov
(89) |
Dec
(155) |
| 2008 |
Jan
(251) |
Feb
(136) |
Mar
(174) |
Apr
(149) |
May
(56) |
Jun
(32) |
Jul
(36) |
Aug
(171) |
Sep
(245) |
Oct
(244) |
Nov
(218) |
Dec
(272) |
| 2009 |
Jan
(113) |
Feb
(119) |
Mar
(192) |
Apr
(117) |
May
(93) |
Jun
(46) |
Jul
(80) |
Aug
(54) |
Sep
(109) |
Oct
(70) |
Nov
(145) |
Dec
(110) |
| 2010 |
Jan
(137) |
Feb
(87) |
Mar
(45) |
Apr
(157) |
May
(58) |
Jun
(99) |
Jul
(188) |
Aug
(136) |
Sep
(101) |
Oct
(100) |
Nov
(61) |
Dec
(60) |
| 2011 |
Jan
(84) |
Feb
(43) |
Mar
(70) |
Apr
(17) |
May
(69) |
Jun
(28) |
Jul
(43) |
Aug
(21) |
Sep
(151) |
Oct
(120) |
Nov
(84) |
Dec
(101) |
| 2012 |
Jan
(119) |
Feb
(82) |
Mar
(70) |
Apr
(115) |
May
(66) |
Jun
(131) |
Jul
(70) |
Aug
(65) |
Sep
(66) |
Oct
(86) |
Nov
(197) |
Dec
(81) |
| 2013 |
Jan
(65) |
Feb
(48) |
Mar
(32) |
Apr
(68) |
May
(98) |
Jun
(59) |
Jul
(41) |
Aug
(52) |
Sep
(42) |
Oct
(37) |
Nov
(10) |
Dec
(27) |
| 2014 |
Jan
(61) |
Feb
(34) |
Mar
(30) |
Apr
(52) |
May
(45) |
Jun
(40) |
Jul
(28) |
Aug
(9) |
Sep
(39) |
Oct
(69) |
Nov
(55) |
Dec
(19) |
| 2015 |
Jan
(13) |
Feb
(21) |
Mar
(5) |
Apr
(14) |
May
(30) |
Jun
(51) |
Jul
(31) |
Aug
(12) |
Sep
(29) |
Oct
(15) |
Nov
(24) |
Dec
(16) |
| 2016 |
Jan
(62) |
Feb
(76) |
Mar
(30) |
Apr
(43) |
May
(46) |
Jun
(62) |
Jul
(21) |
Aug
(49) |
Sep
(67) |
Oct
(27) |
Nov
(26) |
Dec
(38) |
| 2017 |
Jan
(7) |
Feb
(12) |
Mar
(69) |
Apr
(59) |
May
(54) |
Jun
(40) |
Jul
(76) |
Aug
(82) |
Sep
(92) |
Oct
(51) |
Nov
(32) |
Dec
(30) |
| 2018 |
Jan
(22) |
Feb
(25) |
Mar
(34) |
Apr
(35) |
May
(37) |
Jun
(21) |
Jul
(69) |
Aug
(55) |
Sep
(17) |
Oct
(67) |
Nov
(9) |
Dec
(5) |
| 2019 |
Jan
(19) |
Feb
(12) |
Mar
(15) |
Apr
(19) |
May
|
Jun
(27) |
Jul
(27) |
Aug
(25) |
Sep
(25) |
Oct
(27) |
Nov
(10) |
Dec
(14) |
| 2020 |
Jan
(22) |
Feb
(20) |
Mar
(36) |
Apr
(40) |
May
(52) |
Jun
(35) |
Jul
(21) |
Aug
(32) |
Sep
(71) |
Oct
(27) |
Nov
(11) |
Dec
(16) |
| 2021 |
Jan
(16) |
Feb
(21) |
Mar
(21) |
Apr
(27) |
May
(17) |
Jun
|
Jul
(2) |
Aug
(22) |
Sep
(23) |
Oct
(7) |
Nov
(11) |
Dec
(28) |
| 2022 |
Jan
(23) |
Feb
(18) |
Mar
(9) |
Apr
(15) |
May
(15) |
Jun
(7) |
Jul
(8) |
Aug
(15) |
Sep
(1) |
Oct
|
Nov
(11) |
Dec
(10) |
| 2023 |
Jan
(14) |
Feb
(10) |
Mar
(11) |
Apr
(13) |
May
(2) |
Jun
(30) |
Jul
(1) |
Aug
(15) |
Sep
(13) |
Oct
(3) |
Nov
(25) |
Dec
(5) |
| 2024 |
Jan
(3) |
Feb
(10) |
Mar
(9) |
Apr
|
May
(1) |
Jun
(15) |
Jul
(7) |
Aug
(10) |
Sep
(3) |
Oct
(8) |
Nov
(6) |
Dec
(15) |
| 2025 |
Jan
(3) |
Feb
(1) |
Mar
(7) |
Apr
(5) |
May
(13) |
Jun
(16) |
Jul
(1) |
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Michael K. <mic...@ip...> - 2019-04-18 22:15:54
|
Well I have finally implemented ACME certs into my Lab and as you told me, its actually not as painful as I thought. I used Go Daddy because I am commercial and it seems to work fine. Note that I couldn't get it to work on acme version 2.7.2 (Astlinux 1.3.2) but it worked fine on acme 2.7.9 (Astlinux 1.3.4) As there are lots of cool domain suffix’s now available, I can now connect to the interface using <customer id>.myportal.tel. Nice! Thanks all for your help. Regards Michael Knill From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux List <ast...@li...> Date: Thursday, 11 April 2019 at 12:34 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] ACME (Let's Encrypt) Certificates Vs Wildcard SSL certificates Hi Michael, but the way I see it is that we could just purchase a Wildcard SSL certificate instead of using ACME which seems a bit of a hassle. Am I correct? IMO, using automatic ACME certs in AstLinux is the least-hassle approach ... after the initial setup. The hassle with a 1-2 year Wildcard SSL cert (other than the cost) is it needs to be deployed and updated to all the boxes, even if only every 1-2 years. You would need to create some sort of CRON script to do that, and probably with authentication. If you go through the trouble of creating a Wildcard SSL cert deploy/update system, you just as well mint your own Let's Encrypt Wildcard Certs at a central location, at no cost every two months. You need to weigh the pros/cons for your situation, I use Cloudflare for my ACME DNS validation, and after many renewals for many boxes using non-wildcard certs, it just works. Lonnie On Apr 10, 2019, at 5:34 AM, Michael Knill <mic...@ip...> wrote: Hi Group As I am looking to encourage the use of web portals that we have built into Astlinux, I am having to consider the use of non self signed certificates to stop the browser complaining. The web interface for all our systems is accessible with <customer id>.ibcaccess.net. Forgive me for my ignorance but I'm not that good with SSL certificates but the way I see it is that we could just purchase a Wildcard SSL certificate instead of using ACME which seems a bit of a hassle. Am I correct? Regards Michael Knill _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2019-04-18 22:05:50
|
Thanks Lonnie
As 1.3.2 is my current stable release, 13se should be good.
I do like the concept actually.
Regards
Michael Knill
On 19/4/19, 7:00 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Hi Michael,
The first 13se version will be Asterisk 13.23.1, same as AstLinux 1.3.4 used.
The current 13 version is 13.26.0 .
When there are security fixes we will apply them to the 13se version, and if you can identify any important fixes that are 13se worthy let us know. We have already included such a fix.
Currently both Asterisk 13 and 16 are changing at about the same pace, some of you will appreciate the 13se version which will not change as often.
Lonnie
> On Apr 18, 2019, at 3:25 PM, Michael Knill <mic...@ip...> wrote:
>
> Here are some dial plan changes I needed to make to move from Asterisk 11 to 13:
>
> - Unset JITTERBUFFER(adaptive)=default
> - CDR is completely different
> - ParkedCall application has changed
>
> Will the 13se version be the latest Asterisk 13 version? There were a few bugs with earlier Asterisk 13 versions!
> I do like the idea of no pjsip and the pain I had moving to 13, I wont be moving to 16 for quite a while.
>
> I like - stable edition __
>
> Regards
> Michael Knill
>
> On 19/4/19, 12:54 am, "Lonnie Abelbeck" <li...@lo...> wrote:
>
> Thanks for the survey responses, but publicly and privately.
>
> We have decided to no longer build Asterisk 11 in the future, but instead of Asterisk 11 we will be introducing a new 13se version, along with 13 and 16.
>
> The 13se version will have the same focus as Digium's Certified Asterisk, somewhat older, but more tested versions of Asterisk that don't change as often. In addition the first 13se versions will be built --without-pjproject so it will be smaller and not require a bunch of modules.conf noload's to keep the pjsip modules from loading. The 13se version will be the easiest transition for Asterisk 11 users. Alternatively if you want chan_pjsip, Asterisk 16 probably is the better choice.
>
> BTW, what does 'se' stand for: (whatever you like best)
> - stable edition
> - special edition
> - simple edition
>
> In the next week we will offer Pre-Releases including 13se to test.
>
> I personally was using Asterisk 11 and forced myself to move to the Asterisk 13se build.
>
> For later reference, here are the steps I took to migrate from 11 -> 13 ...
>
> 1) As always, the current Asterisk version's sample defaults are in: /stat/etc/asterisk/
>
> 2) extensions.conf mailbox's must include a @<context> now:
> -- example --
> exten => s,n,VoiceMail(1000@default,s)
> exten => 1000,n,VoiceMailMain(1000@default,s)
> --
>
> 3) Parking stuff has moved from features.conf to res_parking.conf
>
> 4) Add files:
> -- res_parking.conf
> -- hep.conf
> -- statsd.conf
> -- ari.conf
>
> 5) Update files:
> -- features.conf
> -- agents.conf
> -- asterisk.conf
> -- cdr.conf
> -- cel.conf
> -- confbridge.conf
> -- res_odbc.conf
> -- modules.conf
> == Add "noload=>res_phoneprov.so" if you don't already.
>
> More 11->13 upgrade details:
> http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=blob_plain;f=UPGRADE.txt;h=b3dcf0fb470f3772de6f3627b86f1ecf27c06a16;hb=refs/heads/13
>
>
> Lonnie
>
>
>
>> On Apr 13, 2019, at 7:43 AM, Lonnie Abelbeck <li...@lo...> wrote:
>>
>> Greetings,
>>
>> A quick survey, how may of you are still use using Asterisk 11 ?
>>
>> Officially, Asterisk 11.x was EOL 2017-10-25
>>
>> Asterisk Versions
>> https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions
>>
>>
>> AstLinux Team
>>
>>
>>
>> _______________________________________________
>> Astlinux-users mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>>
>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>>
>>
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2019-04-18 21:00:30
|
Hi Michael, The first 13se version will be Asterisk 13.23.1, same as AstLinux 1.3.4 used. The current 13 version is 13.26.0 . When there are security fixes we will apply them to the 13se version, and if you can identify any important fixes that are 13se worthy let us know. We have already included such a fix. Currently both Asterisk 13 and 16 are changing at about the same pace, some of you will appreciate the 13se version which will not change as often. Lonnie > On Apr 18, 2019, at 3:25 PM, Michael Knill <mic...@ip...> wrote: > > Here are some dial plan changes I needed to make to move from Asterisk 11 to 13: > > - Unset JITTERBUFFER(adaptive)=default > - CDR is completely different > - ParkedCall application has changed > > Will the 13se version be the latest Asterisk 13 version? There were a few bugs with earlier Asterisk 13 versions! > I do like the idea of no pjsip and the pain I had moving to 13, I wont be moving to 16 for quite a while. > > I like - stable edition __ > > Regards > Michael Knill > > On 19/4/19, 12:54 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Thanks for the survey responses, but publicly and privately. > > We have decided to no longer build Asterisk 11 in the future, but instead of Asterisk 11 we will be introducing a new 13se version, along with 13 and 16. > > The 13se version will have the same focus as Digium's Certified Asterisk, somewhat older, but more tested versions of Asterisk that don't change as often. In addition the first 13se versions will be built --without-pjproject so it will be smaller and not require a bunch of modules.conf noload's to keep the pjsip modules from loading. The 13se version will be the easiest transition for Asterisk 11 users. Alternatively if you want chan_pjsip, Asterisk 16 probably is the better choice. > > BTW, what does 'se' stand for: (whatever you like best) > - stable edition > - special edition > - simple edition > > In the next week we will offer Pre-Releases including 13se to test. > > I personally was using Asterisk 11 and forced myself to move to the Asterisk 13se build. > > For later reference, here are the steps I took to migrate from 11 -> 13 ... > > 1) As always, the current Asterisk version's sample defaults are in: /stat/etc/asterisk/ > > 2) extensions.conf mailbox's must include a @<context> now: > -- example -- > exten => s,n,VoiceMail(1000@default,s) > exten => 1000,n,VoiceMailMain(1000@default,s) > -- > > 3) Parking stuff has moved from features.conf to res_parking.conf > > 4) Add files: > -- res_parking.conf > -- hep.conf > -- statsd.conf > -- ari.conf > > 5) Update files: > -- features.conf > -- agents.conf > -- asterisk.conf > -- cdr.conf > -- cel.conf > -- confbridge.conf > -- res_odbc.conf > -- modules.conf > == Add "noload=>res_phoneprov.so" if you don't already. > > More 11->13 upgrade details: > http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=blob_plain;f=UPGRADE.txt;h=b3dcf0fb470f3772de6f3627b86f1ecf27c06a16;hb=refs/heads/13 > > > Lonnie > > > >> On Apr 13, 2019, at 7:43 AM, Lonnie Abelbeck <li...@lo...> wrote: >> >> Greetings, >> >> A quick survey, how may of you are still use using Asterisk 11 ? >> >> Officially, Asterisk 11.x was EOL 2017-10-25 >> >> Asterisk Versions >> https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions >> >> >> AstLinux Team >> >> >> >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... >> >> > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2019-04-18 20:25:49
|
Here are some dial plan changes I needed to make to move from Asterisk 11 to 13:
- Unset JITTERBUFFER(adaptive)=default
- CDR is completely different
- ParkedCall application has changed
Will the 13se version be the latest Asterisk 13 version? There were a few bugs with earlier Asterisk 13 versions!
I do like the idea of no pjsip and the pain I had moving to 13, I wont be moving to 16 for quite a while.
I like - stable edition __
Regards
Michael Knill
On 19/4/19, 12:54 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Thanks for the survey responses, but publicly and privately.
We have decided to no longer build Asterisk 11 in the future, but instead of Asterisk 11 we will be introducing a new 13se version, along with 13 and 16.
The 13se version will have the same focus as Digium's Certified Asterisk, somewhat older, but more tested versions of Asterisk that don't change as often. In addition the first 13se versions will be built --without-pjproject so it will be smaller and not require a bunch of modules.conf noload's to keep the pjsip modules from loading. The 13se version will be the easiest transition for Asterisk 11 users. Alternatively if you want chan_pjsip, Asterisk 16 probably is the better choice.
BTW, what does 'se' stand for: (whatever you like best)
- stable edition
- special edition
- simple edition
In the next week we will offer Pre-Releases including 13se to test.
I personally was using Asterisk 11 and forced myself to move to the Asterisk 13se build.
For later reference, here are the steps I took to migrate from 11 -> 13 ...
1) As always, the current Asterisk version's sample defaults are in: /stat/etc/asterisk/
2) extensions.conf mailbox's must include a @<context> now:
-- example --
exten => s,n,VoiceMail(1000@default,s)
exten => 1000,n,VoiceMailMain(1000@default,s)
--
3) Parking stuff has moved from features.conf to res_parking.conf
4) Add files:
-- res_parking.conf
-- hep.conf
-- statsd.conf
-- ari.conf
5) Update files:
-- features.conf
-- agents.conf
-- asterisk.conf
-- cdr.conf
-- cel.conf
-- confbridge.conf
-- res_odbc.conf
-- modules.conf
== Add "noload=>res_phoneprov.so" if you don't already.
More 11->13 upgrade details:
http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=blob_plain;f=UPGRADE.txt;h=b3dcf0fb470f3772de6f3627b86f1ecf27c06a16;hb=refs/heads/13
Lonnie
> On Apr 13, 2019, at 7:43 AM, Lonnie Abelbeck <li...@lo...> wrote:
>
> Greetings,
>
> A quick survey, how may of you are still use using Asterisk 11 ?
>
> Officially, Asterisk 11.x was EOL 2017-10-25
>
> Asterisk Versions
> https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions
>
>
> AstLinux Team
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2019-04-18 14:54:00
|
Thanks for the survey responses, but publicly and privately.
We have decided to no longer build Asterisk 11 in the future, but instead of Asterisk 11 we will be introducing a new 13se version, along with 13 and 16.
The 13se version will have the same focus as Digium's Certified Asterisk, somewhat older, but more tested versions of Asterisk that don't change as often. In addition the first 13se versions will be built --without-pjproject so it will be smaller and not require a bunch of modules.conf noload's to keep the pjsip modules from loading. The 13se version will be the easiest transition for Asterisk 11 users. Alternatively if you want chan_pjsip, Asterisk 16 probably is the better choice.
BTW, what does 'se' stand for: (whatever you like best)
- stable edition
- special edition
- simple edition
In the next week we will offer Pre-Releases including 13se to test.
I personally was using Asterisk 11 and forced myself to move to the Asterisk 13se build.
For later reference, here are the steps I took to migrate from 11 -> 13 ...
1) As always, the current Asterisk version's sample defaults are in: /stat/etc/asterisk/
2) extensions.conf mailbox's must include a @<context> now:
-- example --
exten => s,n,VoiceMail(1000@default,s)
exten => 1000,n,VoiceMailMain(1000@default,s)
--
3) Parking stuff has moved from features.conf to res_parking.conf
4) Add files:
-- res_parking.conf
-- hep.conf
-- statsd.conf
-- ari.conf
5) Update files:
-- features.conf
-- agents.conf
-- asterisk.conf
-- cdr.conf
-- cel.conf
-- confbridge.conf
-- res_odbc.conf
-- modules.conf
== Add "noload=>res_phoneprov.so" if you don't already.
More 11->13 upgrade details:
http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=blob_plain;f=UPGRADE.txt;h=b3dcf0fb470f3772de6f3627b86f1ecf27c06a16;hb=refs/heads/13
Lonnie
> On Apr 13, 2019, at 7:43 AM, Lonnie Abelbeck <li...@lo...> wrote:
>
> Greetings,
>
> A quick survey, how may of you are still use using Asterisk 11 ?
>
> Officially, Asterisk 11.x was EOL 2017-10-25
>
> Asterisk Versions
> https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions
>
>
> AstLinux Team
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>
|
|
From: Michael K. <mic...@ip...> - 2019-04-14 21:37:59
|
I'm still using it at one site due to a third party AMI based application but happy for you to remove Asterisk 11 support in the next release.
Regards
Michael Knill
On 13/4/19, 10:44 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
Greetings,
A quick survey, how may of you are still use using Asterisk 11 ?
Officially, Asterisk 11.x was EOL 2017-10-25
Asterisk Versions
https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions
AstLinux Team
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2019-04-13 12:43:50
|
Greetings, A quick survey, how may of you are still use using Asterisk 11 ? Officially, Asterisk 11.x was EOL 2017-10-25 Asterisk Versions https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2019-04-10 22:50:33
|
Hi List, As you know AstLinux's mail forwarder supports both TLS/STARTTLS (TCP 587) and SSL/SMTP (TCP 465). I ran across a very well written article that is worth sharing: SSL vs TLS vs STARTTLS https://www.fastmail.com/help/technical/ssltlsstarttls.html The current best practice is to use SMTP "implicit TLS" over port 465: https://tools.ietf.org/html/rfc8314#section-3 This seems like good advice since STARTTLS starts as cleartext and things can go wrong. Unfortunately, some email clients hide the STARTTLS option and don't automatically disable STARTTLS when port 465 is chosen, Mail in iOS 12 is one such example. At least with AstLinux, choosing "SSL/SMTP" (no STARTTLS) and port 465 works, and the current best practice. Lonnie |
|
From: Michael K. <mic...@ip...> - 2019-04-10 21:25:09
|
Thanks all. I might look into the LetsEncrypt wildcard certificates! Regards Michael Knill From: David Kerr <da...@ke...> Reply-To: AstLinux List <ast...@li...> Date: Thursday, 11 April 2019 at 1:06 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] ACME (Let's Encrypt) Certificates Vs Wildcard SSL certificates LetsEncrypt supports wildcard certificates and the acme client in AstLinux supports it too. There are limitations on which DNS providers it works with -- I had to implement it for FreeDNS. I don't think it will be that hard to use LetsEncrypt. David On Wed, Apr 10, 2019 at 6:34 AM Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote: Hi Group As I am looking to encourage the use of web portals that we have built into Astlinux, I am having to consider the use of non self signed certificates to stop the browser complaining. The web interface for all our systems is accessible with <customer id>.ibcaccess.net<http://ibcaccess.net>. Forgive me for my ignorance but I'm not that good with SSL certificates but the way I see it is that we could just purchase a Wildcard SSL certificate instead of using ACME which seems a bit of a hassle. Am I correct? Regards Michael Knill _______________________________________________ Astlinux-users mailing list Ast...@li...<mailto:Ast...@li...> https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...<mailto:pa...@kr...>. |
|
From: Michael K. <li...@mk...> - 2019-04-10 17:22:07
|
> Am 10.04.2019 um 16:36 schrieb David Kerr <da...@ke...>: > > LetsEncrypt supports wildcard certificates and the acme client in AstLinux supports it too. There are limitations on which DNS providers it works with -- I had to implement it for FreeDNS. I don't think it will be that hard to use LetsEncrypt. > > David In the latest acme version several more DNS providers are supported, we used 2.7.9 currently in AstLinux. https://github.com/Neilpang/acme.sh/releases https://github.com/Neilpang/acme.sh/wiki/dnsapi > On Wed, Apr 10, 2019 at 6:34 AM Michael Knill <mic...@ip...> wrote: > Hi Group > > As I am looking to encourage the use of web portals that we have built into Astlinux, I am having to consider the use of non self signed certificates to stop the browser complaining. > > The web interface for all our systems is accessible with <customer id>.ibcaccess.net. > > Forgive me for my ignorance but I'm not that good with SSL certificates but the way I see it is that we could just purchase a Wildcard SSL certificate instead of using ACME which seems a bit of a hassle. > > Am I correct? > > Regards > > Michael Knill Michael http://www.mksolutions.info |
|
From: David K. <da...@ke...> - 2019-04-10 15:06:37
|
LetsEncrypt supports wildcard certificates and the acme client in AstLinux supports it too. There are limitations on which DNS providers it works with -- I had to implement it for FreeDNS. I don't think it will be that hard to use LetsEncrypt. David On Wed, Apr 10, 2019 at 6:34 AM Michael Knill < mic...@ip...> wrote: > Hi Group > > > > As I am looking to encourage the use of web portals that we have built > into Astlinux, I am having to consider the use of non self signed > certificates to stop the browser complaining. > > The web interface for all our systems is accessible with <customer id>. > ibcaccess.net. > > Forgive me for my ignorance but I'm not that good with SSL certificates > but the way I see it is that we could just purchase a Wildcard SSL > certificate instead of using ACME which seems a bit of a hassle. > > Am I correct? > > > > Regards > > Michael Knill > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2019-04-10 14:53:29
|
Followup, One disadvantage of generating local ACME certificates (using DNS validation) is your DNS provider's credentials are needed on each AstLinux box. Lonnie > On Apr 10, 2019, at 9:30 AM, Lonnie Abelbeck <li...@lo...> wrote: > > Hi Michael, > >> but the way I see it is that we could just purchase a Wildcard SSL certificate instead of using ACME which seems a bit of a hassle. >> Am I correct? > > > IMO, using automatic ACME certs in AstLinux is the least-hassle approach ... after the initial setup. > > The hassle with a 1-2 year Wildcard SSL cert (other than the cost) is it needs to be deployed and updated to all the boxes, even if only every 1-2 years. You would need to create some sort of CRON script to do that, and probably with authentication. > > If you go through the trouble of creating a Wildcard SSL cert deploy/update system, you just as well mint your own Let's Encrypt Wildcard Certs at a central location, at no cost every two months. > > You need to weigh the pros/cons for your situation, I use Cloudflare for my ACME DNS validation, and after many renewals for many boxes using non-wildcard certs, it just works. > > Lonnie > > > > >> On Apr 10, 2019, at 5:34 AM, Michael Knill <mic...@ip...> wrote: >> >> Hi Group >> >> As I am looking to encourage the use of web portals that we have built into Astlinux, I am having to consider the use of non self signed certificates to stop the browser complaining. >> The web interface for all our systems is accessible with <customer id>.ibcaccess.net. >> Forgive me for my ignorance but I'm not that good with SSL certificates but the way I see it is that we could just purchase a Wildcard SSL certificate instead of using ACME which seems a bit of a hassle. >> Am I correct? >> >> Regards >> Michael Knill >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2019-04-10 14:34:07
|
<html><head></head><body dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="ApplePlainTextBody"><div dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="ApplePlainTextBody"><div class="ApplePlainTextBody">Hi Michael,<br><br><blockquote type="cite">but the way I see it is that we could just purchase a Wildcard SSL certificate instead of using ACME which seems a bit of a hassle.<br>Am I correct?<br></blockquote><br><br>IMO, using automatic ACME certs in AstLinux is the least-hassle approach ... after the initial setup.<br><br>The hassle with a 1-2 year Wildcard SSL cert (other than the cost) is it needs to be deployed and updated to all the boxes, even if only every 1-2 years. You would need to create some sort of CRON script to do that, and probably with authentication.<br><br>If you go through the trouble of creating a Wildcard SSL cert deploy/update system, you just as well mint your own Let's Encrypt Wildcard Certs at a central location, at no cost every two months.<br><br>You need to weigh the pros/cons for your situation, I use Cloudflare for my ACME DNS validation, and after many renewals for many boxes using non-wildcard certs, it just works.<br><br>Lonnie<br><br><br><br><br><blockquote type="cite">On Apr 10, 2019, at 5:34 AM, Michael Knill <mic...@ip...> wrote:<br><br>Hi Group<br><br>As I am looking to encourage the use of web portals that we have built into Astlinux, I am having to consider the use of non self signed certificates to stop the browser complaining.<br>The web interface for all our systems is accessible with <customer id>.ibcaccess.net.<br>Forgive me for my ignorance but I'm not that good with SSL certificates but the way I see it is that we could just purchase a Wildcard SSL certificate instead of using ACME which seems a bit of a hassle.<br>Am I correct? <br><br>Regards<br>Michael Knill<br>_______________________________________________<br>Astlinux-users mailing list<br>Ast...@li...<br>https://lists.sourceforge.net/lists/listinfo/astlinux-users<br><br>Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....<br></blockquote><br></div></div></body></html> |
|
From: Michael K. <mic...@ip...> - 2019-04-10 10:34:54
|
Hi Group As I am looking to encourage the use of web portals that we have built into Astlinux, I am having to consider the use of non self signed certificates to stop the browser complaining. The web interface for all our systems is accessible with <customer id>.ibcaccess.net. Forgive me for my ignorance but I'm not that good with SSL certificates but the way I see it is that we could just purchase a Wildcard SSL certificate instead of using ACME which seems a bit of a hassle. Am I correct? Regards Michael Knill |
|
From: Lonnie A. <li...@lo...> - 2019-04-02 14:26:42
|
Announcing Pre-Release Version: astlinux-1.3-4155-7d75e9 The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Asterisk, version bump to 13.25.0 and added new LTS version 16.2.1 for testing. -- Linux Kernel 3.16.64, security and bug fixes. -- busybox, *major* version bump to 1.30.1, security and bug fixes. -- ne, new package, version 3.1.2, the nice editor, alternative to nano ne is easy to use for the beginner, but powerful and fully configurable for the wizard. Includes syntax checking for: asterisk, conf, ini, perl, sh More Info: http://ne.di.unimi.it/ -- Complete Pre-Release ChangeLog: https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt Updated Documentation Topics: Asterisk LTS Series Version - - https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html New "Development" tab feature for desktop browsers: Guest VM x86-64bit ISO: Download Pre-Release Guest VM Install ISO (Video Console) AstLinux Team |
|
From: Michael K. <li...@mk...> - 2019-03-26 12:37:42
|
> Am 26.03.2019 um 01:59 schrieb Michael Knill <mic...@ip...>: > > Hi Group > > I have an annoying problem where the PPPoE Connection Status: on the Status Tab shows as no connection status available but PPPoE is working fine. > It needs a system reboot to fix the problem. > > Any ideas? > > Regards > Michael Knill Hi Michael, I had the same issue years ago as well (in those scenarios). This might be a timing issue in the PPPoE software (usr/sbin/pppoe-staus) after a manual/scripted PPPoE restart or when the ISP forced a reconnect and the line is not up again within a specific timeframe. Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2019-03-26 00:59:43
|
Hi Group I have an annoying problem where the PPPoE Connection Status: on the Status Tab shows as no connection status available but PPPoE is working fine. It needs a system reboot to fix the problem. Any ideas? Regards Michael Knill |
|
From: Dan R. <da...@ry...> - 2019-03-23 15:10:53
|
Good point. I had this problem on very similar Dell (R610) hardware. The easy fix was to add an Intel dual NIC dedicated to the AstLinux VM.Dan -------- Original message --------From: Lonnie Abelbeck <li...@lo...> Date: 3/22/19 7:21 PM (GMT-05:00) To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] Running Astlinux on a dedicated server Michael,Also...Those Dell's often use Broadcom NIC's, which we may or may not enable in the kernel.If the Dell's hardware requires kernel RAID drivers, that could be a problem.Lonnie> On Mar 22, 2019, at 5:43 PM, Lonnie Abelbeck <li...@lo...> wrote:> > Hi Michael,> > You covered the correct answers quite well :-)> > But, for the bare metal case...> The SAS drives might be a problem, not sure.> > The Dell BIOS must support "Legacy" (not UEFI) boot.> > Lonnie> > > >> On Mar 22, 2019, at 4:33 PM, Michael Knill <mic...@ip...> wrote:>> >> Hi All>> >> I'm looking at running Astlinux on a dedicated DC based blade server and wondering if there are any glaring reasons why it wont work before I go through the setup.>> I realise this has been discussed before and the outcome was to run it inside a VM on the server but I would rather avoid installing this if I don't need to.>> And I also realise that a VPS is cheaper and better as I can snapshot it regularly but for some of my high end use cases, there is nothing like a dedicated server for guaranteed performance and I am looking to build redundancy across Data Centres.>> >> The specs are:>> Dell PowerEdge M610 >> 4 Core Intel Xeon L5630 - 2.13Ghz>> 4G RAM>> 2 x 146G SAS in RAID1>> >> Thanks all.>> >> Regards>> Michael Knill>> _______________________________________________>> Astlinux-users mailing list>> Ast...@li...>> https://lists.sourceforge.net/lists/listinfo/astlinux-users>> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....> _______________________________________________Astlinux-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/astlinux-usersDonations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2019-03-23 03:41:48
|
Ok thanks guys. Looks like that's it then Regards Michael Knill From: darricklegacy <dha...@dj...> Reply-To: AstLinux List <ast...@li...> Date: Saturday, 23 March 2019 at 2:20 pm To: Lonnie Abelbeck <li...@lo...>, AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Running Astlinux on a dedicated server Hi Michael, I would just go for VMware. As Lonnie mention, ESXi Hypervisor is free and supported on that hardware. Makes it super flexible to move to different hardware in the future. AstLinux runs well on VMware. Darrick ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Saturday, March 23, 2019 12:30 AM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] Running Astlinux on a dedicated server Hi Michael, Personally, I would start with a VM hypervisor, the basic VMware ESXi is free isn't it ? You know that will work and gives you additional flexibility. The hardware is still dedicated. Others can chime in... Lonnie > On Mar 22, 2019, at 6:45 PM, Michael Knill <mic...@ip...> wrote: > > Hmm thanks Lonnie. Not looking good so far ☹ > Do you think I should give it a try and see how it goes or just go straight for VM? > > Regards > Michael Knill > > On 23/3/19, 10:21 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Michael, > > Also... > Those Dell's often use Broadcom NIC's, which we may or may not enable in the kernel. > > If the Dell's hardware requires kernel RAID drivers, that could be a problem. > > Lonnie > > >> On Mar 22, 2019, at 5:43 PM, Lonnie Abelbeck <li...@lo...> wrote: >> >> Hi Michael, >> >> You covered the correct answers quite well :-) >> >> But, for the bare metal case... >> The SAS drives might be a problem, not sure. >> >> The Dell BIOS must support "Legacy" (not UEFI) boot. >> >> Lonnie >> >> >> >>> On Mar 22, 2019, at 4:33 PM, Michael Knill <mic...@ip...> wrote: >>> >>> Hi All >>> >>> I'm looking at running Astlinux on a dedicated DC based blade server and wondering if there are any glaring reasons why it wont work before I go through the setup. >>> I realise this has been discussed before and the outcome was to run it inside a VM on the server but I would rather avoid installing this if I don't need to. >>> And I also realise that a VPS is cheaper and better as I can snapshot it regularly but for some of my high end use cases, there is nothing like a dedicated server for guaranteed performance and I am looking to build redundancy across Data Centres. >>> >>> The specs are: >>> Dell PowerEdge M610 >>> 4 Core Intel Xeon L5630 - 2.13Ghz >>> 4G RAM >>> 2 x 146G SAS in RAID1 >>> >>> Thanks all. >>> >>> Regards >>> Michael Knill >>> _______________________________________________ >>> Astlinux-users mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>> >>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... >> > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: darricklegacy <dha...@dj...> - 2019-03-23 03:20:01
|
Hi Michael, I would just go for VMware. As Lonnie mention, ESXi Hypervisor is free and supported on that hardware. Makes it super flexible to move to different hardware in the future. AstLinux runs well on VMware. Darrick ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Saturday, March 23, 2019 12:30 AM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] Running Astlinux on a dedicated server Hi Michael, Personally, I would start with a VM hypervisor, the basic VMware ESXi is free isn't it ? You know that will work and gives you additional flexibility. The hardware is still dedicated. Others can chime in... Lonnie > On Mar 22, 2019, at 6:45 PM, Michael Knill <mic...@ip...> wrote: > > Hmm thanks Lonnie. Not looking good so far ☹ > Do you think I should give it a try and see how it goes or just go straight for VM? > > Regards > Michael Knill > > On 23/3/19, 10:21 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Michael, > > Also... > Those Dell's often use Broadcom NIC's, which we may or may not enable in the kernel. > > If the Dell's hardware requires kernel RAID drivers, that could be a problem. > > Lonnie > > >> On Mar 22, 2019, at 5:43 PM, Lonnie Abelbeck <li...@lo...> wrote: >> >> Hi Michael, >> >> You covered the correct answers quite well :-) >> >> But, for the bare metal case... >> The SAS drives might be a problem, not sure. >> >> The Dell BIOS must support "Legacy" (not UEFI) boot. >> >> Lonnie >> >> >> >>> On Mar 22, 2019, at 4:33 PM, Michael Knill <mic...@ip...> wrote: >>> >>> Hi All >>> >>> I'm looking at running Astlinux on a dedicated DC based blade server and wondering if there are any glaring reasons why it wont work before I go through the setup. >>> I realise this has been discussed before and the outcome was to run it inside a VM on the server but I would rather avoid installing this if I don't need to. >>> And I also realise that a VPS is cheaper and better as I can snapshot it regularly but for some of my high end use cases, there is nothing like a dedicated server for guaranteed performance and I am looking to build redundancy across Data Centres. >>> >>> The specs are: >>> Dell PowerEdge M610 >>> 4 Core Intel Xeon L5630 - 2.13Ghz >>> 4G RAM >>> 2 x 146G SAS in RAID1 >>> >>> Thanks all. >>> >>> Regards >>> Michael Knill >>> _______________________________________________ >>> Astlinux-users mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>> >>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... >> > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2019-03-23 00:31:09
|
Hi Michael, Personally, I would start with a VM hypervisor, the basic VMware ESXi is free isn't it ? You know that will work and gives you additional flexibility. The hardware is still dedicated. Others can chime in... Lonnie > On Mar 22, 2019, at 6:45 PM, Michael Knill <mic...@ip...> wrote: > > Hmm thanks Lonnie. Not looking good so far ☹ > Do you think I should give it a try and see how it goes or just go straight for VM? > > Regards > Michael Knill > > On 23/3/19, 10:21 am, "Lonnie Abelbeck" <li...@lo...> wrote: > > Michael, > > Also... > Those Dell's often use Broadcom NIC's, which we may or may not enable in the kernel. > > If the Dell's hardware requires kernel RAID drivers, that could be a problem. > > Lonnie > > >> On Mar 22, 2019, at 5:43 PM, Lonnie Abelbeck <li...@lo...> wrote: >> >> Hi Michael, >> >> You covered the correct answers quite well :-) >> >> But, for the bare metal case... >> The SAS drives might be a problem, not sure. >> >> The Dell BIOS must support "Legacy" (not UEFI) boot. >> >> Lonnie >> >> >> >>> On Mar 22, 2019, at 4:33 PM, Michael Knill <mic...@ip...> wrote: >>> >>> Hi All >>> >>> I'm looking at running Astlinux on a dedicated DC based blade server and wondering if there are any glaring reasons why it wont work before I go through the setup. >>> I realise this has been discussed before and the outcome was to run it inside a VM on the server but I would rather avoid installing this if I don't need to. >>> And I also realise that a VPS is cheaper and better as I can snapshot it regularly but for some of my high end use cases, there is nothing like a dedicated server for guaranteed performance and I am looking to build redundancy across Data Centres. >>> >>> The specs are: >>> Dell PowerEdge M610 >>> 4 Core Intel Xeon L5630 - 2.13Ghz >>> 4G RAM >>> 2 x 146G SAS in RAID1 >>> >>> Thanks all. >>> >>> Regards >>> Michael Knill >>> _______________________________________________ >>> Astlinux-users mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>> >>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... >> > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2019-03-22 23:45:15
|
Hmm thanks Lonnie. Not looking good so far ☹
Do you think I should give it a try and see how it goes or just go straight for VM?
Regards
Michael Knill
On 23/3/19, 10:21 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Michael,
Also...
Those Dell's often use Broadcom NIC's, which we may or may not enable in the kernel.
If the Dell's hardware requires kernel RAID drivers, that could be a problem.
Lonnie
> On Mar 22, 2019, at 5:43 PM, Lonnie Abelbeck <li...@lo...> wrote:
>
> Hi Michael,
>
> You covered the correct answers quite well :-)
>
> But, for the bare metal case...
> The SAS drives might be a problem, not sure.
>
> The Dell BIOS must support "Legacy" (not UEFI) boot.
>
> Lonnie
>
>
>
>> On Mar 22, 2019, at 4:33 PM, Michael Knill <mic...@ip...> wrote:
>>
>> Hi All
>>
>> I'm looking at running Astlinux on a dedicated DC based blade server and wondering if there are any glaring reasons why it wont work before I go through the setup.
>> I realise this has been discussed before and the outcome was to run it inside a VM on the server but I would rather avoid installing this if I don't need to.
>> And I also realise that a VPS is cheaper and better as I can snapshot it regularly but for some of my high end use cases, there is nothing like a dedicated server for guaranteed performance and I am looking to build redundancy across Data Centres.
>>
>> The specs are:
>> Dell PowerEdge M610
>> 4 Core Intel Xeon L5630 - 2.13Ghz
>> 4G RAM
>> 2 x 146G SAS in RAID1
>>
>> Thanks all.
>>
>> Regards
>> Michael Knill
>> _______________________________________________
>> Astlinux-users mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>>
>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2019-03-22 23:21:17
|
Michael, Also... Those Dell's often use Broadcom NIC's, which we may or may not enable in the kernel. If the Dell's hardware requires kernel RAID drivers, that could be a problem. Lonnie > On Mar 22, 2019, at 5:43 PM, Lonnie Abelbeck <li...@lo...> wrote: > > Hi Michael, > > You covered the correct answers quite well :-) > > But, for the bare metal case... > The SAS drives might be a problem, not sure. > > The Dell BIOS must support "Legacy" (not UEFI) boot. > > Lonnie > > > >> On Mar 22, 2019, at 4:33 PM, Michael Knill <mic...@ip...> wrote: >> >> Hi All >> >> I'm looking at running Astlinux on a dedicated DC based blade server and wondering if there are any glaring reasons why it wont work before I go through the setup. >> I realise this has been discussed before and the outcome was to run it inside a VM on the server but I would rather avoid installing this if I don't need to. >> And I also realise that a VPS is cheaper and better as I can snapshot it regularly but for some of my high end use cases, there is nothing like a dedicated server for guaranteed performance and I am looking to build redundancy across Data Centres. >> >> The specs are: >> Dell PowerEdge M610 >> 4 Core Intel Xeon L5630 - 2.13Ghz >> 4G RAM >> 2 x 146G SAS in RAID1 >> >> Thanks all. >> >> Regards >> Michael Knill >> _______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > |
|
From: Lonnie A. <li...@lo...> - 2019-03-22 22:44:01
|
Hi Michael, You covered the correct answers quite well :-) But, for the bare metal case... The SAS drives might be a problem, not sure. The Dell BIOS must support "Legacy" (not UEFI) boot. Lonnie > On Mar 22, 2019, at 4:33 PM, Michael Knill <mic...@ip...> wrote: > > Hi All > > I'm looking at running Astlinux on a dedicated DC based blade server and wondering if there are any glaring reasons why it wont work before I go through the setup. > I realise this has been discussed before and the outcome was to run it inside a VM on the server but I would rather avoid installing this if I don't need to. > And I also realise that a VPS is cheaper and better as I can snapshot it regularly but for some of my high end use cases, there is nothing like a dedicated server for guaranteed performance and I am looking to build redundancy across Data Centres. > > The specs are: > Dell PowerEdge M610 > 4 Core Intel Xeon L5630 - 2.13Ghz > 4G RAM > 2 x 146G SAS in RAID1 > > Thanks all. > > Regards > Michael Knill > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2019-03-22 21:33:37
|
Hi All I'm looking at running Astlinux on a dedicated DC based blade server and wondering if there are any glaring reasons why it wont work before I go through the setup. I realise this has been discussed before and the outcome was to run it inside a VM on the server but I would rather avoid installing this if I don't need to. And I also realise that a VPS is cheaper and better as I can snapshot it regularly but for some of my high end use cases, there is nothing like a dedicated server for guaranteed performance and I am looking to build redundancy across Data Centres. The specs are: Dell PowerEdge M610 4 Core Intel Xeon L5630 - 2.13Ghz 4G RAM 2 x 146G SAS in RAID1 Thanks all. Regards Michael Knill |
63 messages has been excluded from this view by a project administrator.
