astlinux-users — AstLinux Users Mailing List

[Astlinux-users] Redirecting all AstLinux logs to an external syslog server

[Bart T. <bar...@gm...>]

Hi,

I'm a bit of a novice but have been running Astlinux for some years. I'm OK
at the Asterisk part, but pretty lame at the Linux side, especially in a
minimalist environment that's flooded with optimizations to prevent or
contain permanent changes. I'm currently running astlinux-1.3.1 x86_64 -
Asterisk 13.17.2 on an APU2.

I'm wondering how to redirect all logs to an external syslog server. The
most obvious (and easiest) avenue was to look at the GUI for an option to
specify a remote syslog server but no such setting exists. The next step
was to look for syslogd.conf (or similar) to see if I could fiddle
that...but I couldn't find that either....

So the questions are:

1. Can you redirect/copy all logs to a remote syslog server?
2. And if so, how?

Cheers,
Bart.

Re: [Astlinux-users] LAN not able to reach remote network through Openvpn

[Lonnie A. <li...@lo...>]

Hi Gonzalo,

Great ! That makes sense since the 192.168.2.0/24 network would not be NAT'ed by tun0 anyway.

Thanks for reporting your results.

Lonnie


On Nov 11, 2017, at 1:54 PM, Gonzalo Ibáñez <gon...@ho...> wrote:

> Thanks Lonnie! 
> 
> It's working now; the key was this:
> 
> «the default OpenVPN Server "tun0" interface is treated as an internal LAN interface»
> 
> I only had to add the «Pass EXT->LAN» rules you mentioned to make it work, no need to disable NAT on tun0 interface as the Openvpn server had already remote networks routed and was not using NAT.
> 
> Thanks for your help as always.
> 
> Gonzalo.
> 
> 
> 
>> 
>> Message: 2
>> Date: Fri, 10 Nov 2017 22:39:11 -0600
>> From: Lonnie Abelbeck <li...@lo...>
>> To: AstLinux Users Mailing List <ast...@li...>
>> Subject: Re: [Astlinux-users] LAN not able to reach remote network
>> 	through Openvpn
>> Message-ID: <E9A...@lo...>
>> Content-Type: text/plain; charset=iso-8859-1
>> 
>> 
>> On Nov 10, 2017, at 7:35 PM, Gonzalo Ib??ez <gon...@ho...>
>> wrote:
>> 
>>> Hi all,
>>> 
>>> I've a problem that may be has been solved before but I can't find a
>> solution through documentation nor searching on this list archive.
>>> 
>>> My scenario is an Astlinux box with only an EXTINF (no LAN interface)
>> directly connected to my internet router through the local LAN
>> 192.168.1.0/24. I'm able to access Astlinux box from LAN through EXTINF
>> by adding a 'Pass EXT->Local' firewall rule.
>>> 
>>> The Astlinux server is running an Openvpn server with network
>> 10.0.0.0/24 and there's a remote location with LAN 192.168.2.0/24
>> permanently connected by vpn so that they can reach local LAN
>> 192.168.1.0/24 but the problem is I can't reach remote  192.168.2.0/24
>> from 192.168.1.0/24. 192.168.2.0/24 is reachable directly from Astlinux
>> box so I suspect the problem is related to NAT/Arno firewall
>> configuration. I've tried different iptables configurations without
>> success so far.
>>> 
>>> Any idea? 
>> 
>> I think I follow your setup ...
>> 
>> Remote 192.168.2.0/24 is routed to (OpenVPN) 10.0.0.0/24 within
>> AstLinux which is NAT'ed to EXT 192.168.1.0/24, and the return path
>> works via the NAT firewall state.
>> 
>> BTW, the default OpenVPN Server "tun0" interface is treated as an
>> internal LAN interface, which is NAT'ed to the external interface.
>> 
>> For your situation, it may be better if the tun0 interface is routed to
>> the EXT 192.168.1.0/24, but that is a little more complicated.
>> 
>> First, disable NAT for the tun0 interface (OpenVPN Server)
>> 
>> -- Add to /mnt/kd/rc.conf.d/user.conf --
>> NONAT="tun0"
>> --
>> 
>> Second, the 192.168.1.0/24 network must have firewall access to the
>> 192.168.2.0/24 network, that can be done by adding firewall rules for
>> TCP/UDP and ICMP ...
>> --
>> Pass EXT->LAN   Source: 192.168.1.0/24
>> Protocol: [TCP/UDP]  Destination: 192.168.2.0/24  Port: ___  (empty for
>> any port)
>> --
>> Pass EXT->LAN   Source: 192.168.1.0/24
>> Protocol: [ ICMP ]  Destination: 192.168.2.0/24
>> --
>> 
>> Now, restart the firewall via the web interface.
>> 
>> Finally, you need a static route telling your 192.168.1.0/24 network
>> that the 192.168.2.0/24 network is via 192.168.1.nn (the AstLinux box
>> external IP).  Note that this route is not for AstLinux, but rather for
>> the 192.168.1.0/24 router or a specific 192.168.1.0/24 device.
>> 
>> I may have missed something, not tested, but just might work :-)
>> 
>> Be sure to do a "ip r" on AstLinux to make sure all the routes exist
>> you expect.
>> 
>> Lonnie
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> ------------------------------
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> 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....

Re: [Astlinux-users] LAN not able to reach remote network through Openvpn

[Gonzalo I. <gon...@ho...>]

Thanks Lonnie! 

It's working now; the key was this:

«the default OpenVPN Server "tun0" interface is treated as an internal LAN interface»

I only had to add the «Pass EXT->LAN» rules you mentioned to make it work, no need to disable NAT on tun0 interface as the Openvpn server had already remote networks routed and was not using NAT.

Thanks for your help as always.

Gonzalo.



>
>Message: 2
>Date: Fri, 10 Nov 2017 22:39:11 -0600
>From: Lonnie Abelbeck <li...@lo...>
>To: AstLinux Users Mailing List <ast...@li...>
>Subject: Re: [Astlinux-users] LAN not able to reach remote network
>	through Openvpn
>Message-ID: <E9A...@lo...>
>Content-Type: text/plain; charset=iso-8859-1
>
>
>On Nov 10, 2017, at 7:35 PM, Gonzalo Ib??ez <gon...@ho...>
>wrote:
>
>> Hi all,
>> 
>> I've a problem that may be has been solved before but I can't find a
>solution through documentation nor searching on this list archive.
>> 
>> My scenario is an Astlinux box with only an EXTINF (no LAN interface)
>directly connected to my internet router through the local LAN
>192.168.1.0/24. I'm able to access Astlinux box from LAN through EXTINF
>by adding a 'Pass EXT->Local' firewall rule.
>> 
>> The Astlinux server is running an Openvpn server with network
>10.0.0.0/24 and there's a remote location with LAN 192.168.2.0/24
>permanently connected by vpn so that they can reach local LAN
>192.168.1.0/24 but the problem is I can't reach remote  192.168.2.0/24
>from 192.168.1.0/24. 192.168.2.0/24 is reachable directly from Astlinux
>box so I suspect the problem is related to NAT/Arno firewall
>configuration. I've tried different iptables configurations without
>success so far.
>> 
>> Any idea? 
>
>I think I follow your setup ...
>
>Remote 192.168.2.0/24 is routed to (OpenVPN) 10.0.0.0/24 within
>AstLinux which is NAT'ed to EXT 192.168.1.0/24, and the return path
>works via the NAT firewall state.
>
>BTW, the default OpenVPN Server "tun0" interface is treated as an
>internal LAN interface, which is NAT'ed to the external interface.
>
>For your situation, it may be better if the tun0 interface is routed to
>the EXT 192.168.1.0/24, but that is a little more complicated.
>
>First, disable NAT for the tun0 interface (OpenVPN Server)
>
>-- Add to /mnt/kd/rc.conf.d/user.conf --
>NONAT="tun0"
>--
>
>Second, the 192.168.1.0/24 network must have firewall access to the
>192.168.2.0/24 network, that can be done by adding firewall rules for
>TCP/UDP and ICMP ...
>--
>Pass EXT->LAN   Source: 192.168.1.0/24
>Protocol: [TCP/UDP]  Destination: 192.168.2.0/24  Port: ___  (empty for
>any port)
>--
>Pass EXT->LAN   Source: 192.168.1.0/24
>Protocol: [ ICMP ]  Destination: 192.168.2.0/24
>--
>
>Now, restart the firewall via the web interface.
>
>Finally, you need a static route telling your 192.168.1.0/24 network
>that the 192.168.2.0/24 network is via 192.168.1.nn (the AstLinux box
>external IP).  Note that this route is not for AstLinux, but rather for
>the 192.168.1.0/24 router or a specific 192.168.1.0/24 device.
>
>I may have missed something, not tested, but just might work :-)
>
>Be sure to do a "ip r" on AstLinux to make sure all the routes exist
>you expect.
>
>Lonnie
>
>
>
>
>
>
>
>------------------------------

Re: [Astlinux-users] LAN not able to reach remote network through Openvpn

[Lonnie A. <li...@lo...>]

On Nov 10, 2017, at 7:35 PM, Gonzalo Ibáñez <gon...@ho...> wrote:

> Hi all,
> 
> I've a problem that may be has been solved before but I can't find a solution through documentation nor searching on this list archive.
> 
> My scenario is an Astlinux box with only an EXTINF (no LAN interface) directly connected to my internet router through the local LAN 192.168.1.0/24. I'm able to access Astlinux box from LAN through EXTINF by adding a 'Pass EXT->Local' firewall rule.
> 
> The Astlinux server is running an Openvpn server with network 10.0.0.0/24 and there's a remote location with LAN 192.168.2.0/24 permanently connected by vpn so that they can reach local LAN 192.168.1.0/24 but the problem is I can't reach remote  192.168.2.0/24 from 192.168.1.0/24. 192.168.2.0/24 is reachable directly from Astlinux box so I suspect the problem is related to NAT/Arno firewall configuration. I've tried different iptables configurations without success so far.
> 
> Any idea? 

I think I follow your setup ...

Remote 192.168.2.0/24 is routed to (OpenVPN) 10.0.0.0/24 within AstLinux which is NAT'ed to EXT 192.168.1.0/24, and the return path works via the NAT firewall state.

BTW, the default OpenVPN Server "tun0" interface is treated as an internal LAN interface, which is NAT'ed to the external interface.

For your situation, it may be better if the tun0 interface is routed to the EXT 192.168.1.0/24, but that is a little more complicated.

First, disable NAT for the tun0 interface (OpenVPN Server)

-- Add to /mnt/kd/rc.conf.d/user.conf --
NONAT="tun0"
--

Second, the 192.168.1.0/24 network must have firewall access to the 192.168.2.0/24 network, that can be done by adding firewall rules for TCP/UDP and ICMP ...
--
Pass EXT->LAN   Source: 192.168.1.0/24
Protocol: [TCP/UDP]  Destination: 192.168.2.0/24  Port: ___  (empty for any port)
--
Pass EXT->LAN   Source: 192.168.1.0/24
Protocol: [ ICMP ]  Destination: 192.168.2.0/24
--

Now, restart the firewall via the web interface.

Finally, you need a static route telling your 192.168.1.0/24 network that the 192.168.2.0/24 network is via 192.168.1.nn (the AstLinux box external IP).  Note that this route is not for AstLinux, but rather for the 192.168.1.0/24 router or a specific 192.168.1.0/24 device.

I may have missed something, not tested, but just might work :-)

Be sure to do a "ip r" on AstLinux to make sure all the routes exist you expect.

Lonnie

[Astlinux-users] LAN not able to reach remote network through Openvpn

[Gonzalo I. <gon...@ho...>]

Hi all,

I've a problem that may be has been solved before but I can't find a solution through documentation nor searching on this list archive.

My scenario is an Astlinux box with only an EXTINF (no LAN interface) directly connected to my internet router through the local LAN 192.168.1.0/24<http://192.168.1.0/24>. I'm able to access Astlinux box from LAN through EXTINF by adding a 'Pass EXT->Local' firewall rule.

The Astlinux server is running an Openvpn server with network 10.0.0.0/24<http://10.0.0.0/24> and there's a remote location with LAN 192.168.2.0/24<http://192.168.2.0/24> permanently connected by vpn so that they can reach local LAN 192.168.1.0/24<http://192.168.1.0/24> but the problem is I can't reach remote 192.168.2.0/24<http://192.168.2.0/24> from 192.168.1.0/24<http://192.168.1.0/24>. 192.168.2.0/24<http://192.168.2.0/24> is reachable directly from Astlinux box so I suspect the problem is related to NAT/Arno firewall configuration. I've tried different iptables configurations without success so far.

Any idea?

Thanks for your support.

Re: [Astlinux-users] Busybox Ping

[Michael K. <mic...@ip...>]

Ah thanks Lonnie. I love mtr. Perfect! So glad I asked.

Regards
Michael Knill

-----Original Message-----
From: Lonnie Abelbeck <li...@lo...>
Reply-To: AstLinux List <ast...@li...>
Date: Friday, 10 November 2017 at 7:55 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Busybox Ping

Hi Michael,

I usually prefer to use "fping" (or "fping6") which is has a lot of features.

Even on the Busybox ping you can set the count option -c2 for two tries.

Also try "mtr host"

$ mtr 8.8.8.8

or for a -w or --report-wide

$ mtr -w 8.8.8.8

Give "mtr" a try.

Lonnie


On Nov 9, 2017, at 2:17 PM, Michael Knill <mic...@ip...> wrote:

> Hi Group
>  
> Im having what I believe are some upstream network issues with one of my providers and I really need to do some testing.
> Unfortunately the Busybox Ping is a bit limited in what it can do. Its also annoying that it does not show timeouts until you stop it, unlike most other Ping implementations (am I missing something here?).
>  
> Are there any other tools in Astlinux that can help with this?
>  
> Regards
> Michael Knill
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> 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....


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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....

Re: [Astlinux-users] Busybox Ping

[Lonnie A. <li...@lo...>]

Hi Michael,

I usually prefer to use "fping" (or "fping6") which is has a lot of features.

Even on the Busybox ping you can set the count option -c2 for two tries.

Also try "mtr host"

$ mtr 8.8.8.8

or for a -w or --report-wide

$ mtr -w 8.8.8.8

Give "mtr" a try.

Lonnie


On Nov 9, 2017, at 2:17 PM, Michael Knill <mic...@ip...> wrote:

> Hi Group
>  
> Im having what I believe are some upstream network issues with one of my providers and I really need to do some testing.
> Unfortunately the Busybox Ping is a bit limited in what it can do. Its also annoying that it does not show timeouts until you stop it, unlike most other Ping implementations (am I missing something here?).
>  
> Are there any other tools in Astlinux that can help with this?
>  
> Regards
> Michael Knill
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> 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] Busybox Ping

[Michael K. <mic...@ip...>]

Hi Group

Im having what I believe are some upstream network issues with one of my providers and I really need to do some testing.
Unfortunately the Busybox Ping is a bit limited in what it can do. Its also annoying that it does not show timeouts until you stop it, unlike most other Ping implementations (am I missing something here?).

Are there any other tools in Astlinux that can help with this?

Regards
Michael Knill

Re: [Astlinux-users] DNS Hosts

[Michael K. <mic...@ip...>]

Yes I was stupid after all. Thanks Michael

Regards
Michael Knill

-----Original Message-----
From: Michael Keuter <li...@mk...>
Reply-To: AstLinux List <ast...@li...>
Date: Wednesday, 8 November 2017 at 8:14 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] DNS Hosts


> Am 07.11.2017 um 22:09 schrieb Michael Knill <mic...@ip...>:
> 
> Forgive me if I am a bit stupid but how come you cant enter two hosts with the same IP Address?
>  
> Regards
> Michael Knill

Sure that works:

Hostname(s): "name1 name2 name3"
Without the quotes.

Michael

http://www.mksolutions.info




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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....

Re: [Astlinux-users] DNS Hosts

[Michael K. <li...@mk...>]

> Am 07.11.2017 um 22:09 schrieb Michael Knill <mic...@ip...>:
> 
> Forgive me if I am a bit stupid but how come you cant enter two hosts with the same IP Address?
>  
> Regards
> Michael Knill

Sure that works:

Hostname(s): "name1 name2 name3"
Without the quotes.

Michael

http://www.mksolutions.info

[Astlinux-users] DNS Hosts

[Michael K. <mic...@ip...>]

Forgive me if I am a bit stupid but how come you cant enter two hosts with the same IP Address?

Regards
Michael Knill

Re: [Astlinux-users] Qotom Q190G4N-S07

[Michael K. <mic...@ip...>]

Yeah but I feel a bit more comfortable with some name brand ones although I have had a problem with one of my Kingston SSD's
Maybe I am being a bit over cautious.

Regards
Michael Knill

-----Original Message-----
From: Lonnie Abelbeck <li...@lo...>
Reply-To: AstLinux List <ast...@li...>
Date: Thursday, 2 November 2017 at 9:47 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Qotom Q190G4N-S07

Some would say small mSATA are easer to find than M.2 stuff.

You can order via AliExpress, adding 4 GB RAM and 32 GB SSD adds $ 48 USD

PC Engines offers 16 GB mSATA for under $ 20 USD

Lonnie


On Nov 1, 2017, at 5:02 PM, Michael Knill <mic...@ip...> wrote:

> Actually one of my employees pointed out that it was still mSATA not M.2 which is a bit of an issue. Reasonably priced (small) mSATA is becoming hard to get now!
> 
> Regards
> Michael Knill
> 
> -----Original Message-----
> From: Lonnie Abelbeck <li...@lo...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Thursday, 2 November 2017 at 7:40 am
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] Qotom Q190G4N-S07
> 
> Hi Michael,
> 
> I purchased one back in April 23, 2017, here is the writeup: 
> 
> Qotom Q190G4N-S07 Celeron J1900 Fanless Appliance
> https://doc.astlinux-project.org/userdoc:board_qotom_q190g4n-s07
> 
> I initially used a Crucial SO-DIMM, but had rare lockups, I swapped it with a Samsung SO-DIMM and has been running perfectly ever since.  Could be I had a marginal RAM stick.
> 
> It has been running 24/7 .
> 
> A very professional looking box, customers will be impressed.
> 
> The only negative is no serial port, but enabling our "USB TTY Serial Login" feature easily allows serial CLI access *after* it has properly booted.  You need to use the VGA port for console access *during* boot and RUNNIX access.
> https://doc.astlinux-project.org/userdoc:usbtty_serial_login
> 
> Note: As with many boards, if the the VGA port is not connected to a monitor at boot you can't latter attach it and see the console, you must boot with the monitor attached to use the VGA port.  Not just a Qotom thing.
> 
> Here in the US the barebone price is $125 + $34 shipping on Amazon, slightly less expensive via AliExpress.  Given it is directly shipped from China, any sort of return would be mostly eaten in shipping costs so if you planned on 1 out of 10 might be a bad unit you could price that into the cost.
> 
> A good value IMHO.
> 
> Lonnie
> 
> 
> 
> On Nov 1, 2017, at 2:49 PM, Michael Knill <mic...@ip...> wrote:
> 
>> Hi group
>> 
>> Qotom has just completed their EMC compliance for this unit so I can install it now in Australia.
>> Anyone using these boxes?
>> 
>> Regards
>> Michael Knill
> 
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> 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....
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> 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....
> 
> 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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....

Re: [Astlinux-users] Qotom Q190G4N-S07

[Lonnie A. <li...@lo...>]

Some would say small mSATA are easer to find than M.2 stuff.

You can order via AliExpress, adding 4 GB RAM and 32 GB SSD adds $ 48 USD

PC Engines offers 16 GB mSATA for under $ 20 USD

Lonnie


On Nov 1, 2017, at 5:02 PM, Michael Knill <mic...@ip...> wrote:

> Actually one of my employees pointed out that it was still mSATA not M.2 which is a bit of an issue. Reasonably priced (small) mSATA is becoming hard to get now!
> 
> Regards
> Michael Knill
> 
> -----Original Message-----
> From: Lonnie Abelbeck <li...@lo...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Thursday, 2 November 2017 at 7:40 am
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] Qotom Q190G4N-S07
> 
> Hi Michael,
> 
> I purchased one back in April 23, 2017, here is the writeup: 
> 
> Qotom Q190G4N-S07 Celeron J1900 Fanless Appliance
> https://doc.astlinux-project.org/userdoc:board_qotom_q190g4n-s07
> 
> I initially used a Crucial SO-DIMM, but had rare lockups, I swapped it with a Samsung SO-DIMM and has been running perfectly ever since.  Could be I had a marginal RAM stick.
> 
> It has been running 24/7 .
> 
> A very professional looking box, customers will be impressed.
> 
> The only negative is no serial port, but enabling our "USB TTY Serial Login" feature easily allows serial CLI access *after* it has properly booted.  You need to use the VGA port for console access *during* boot and RUNNIX access.
> https://doc.astlinux-project.org/userdoc:usbtty_serial_login
> 
> Note: As with many boards, if the the VGA port is not connected to a monitor at boot you can't latter attach it and see the console, you must boot with the monitor attached to use the VGA port.  Not just a Qotom thing.
> 
> Here in the US the barebone price is $125 + $34 shipping on Amazon, slightly less expensive via AliExpress.  Given it is directly shipped from China, any sort of return would be mostly eaten in shipping costs so if you planned on 1 out of 10 might be a bad unit you could price that into the cost.
> 
> A good value IMHO.
> 
> Lonnie
> 
> 
> 
> On Nov 1, 2017, at 2:49 PM, Michael Knill <mic...@ip...> wrote:
> 
>> Hi group
>> 
>> Qotom has just completed their EMC compliance for this unit so I can install it now in Australia.
>> Anyone using these boxes?
>> 
>> Regards
>> Michael Knill
> 
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> 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....
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> 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....
> 
> 

Re: [Astlinux-users] Qotom Q190G4N-S07

[Michael K. <mic...@ip...>]

Actually one of my employees pointed out that it was still mSATA not M.2 which is a bit of an issue. Reasonably priced (small) mSATA is becoming hard to get now!

Regards
Michael Knill

-----Original Message-----
From: Lonnie Abelbeck <li...@lo...>
Reply-To: AstLinux List <ast...@li...>
Date: Thursday, 2 November 2017 at 7:40 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Qotom Q190G4N-S07

Hi Michael,

I purchased one back in April 23, 2017, here is the writeup: 

Qotom Q190G4N-S07 Celeron J1900 Fanless Appliance
https://doc.astlinux-project.org/userdoc:board_qotom_q190g4n-s07

I initially used a Crucial SO-DIMM, but had rare lockups, I swapped it with a Samsung SO-DIMM and has been running perfectly ever since.  Could be I had a marginal RAM stick.

It has been running 24/7 .

A very professional looking box, customers will be impressed.

The only negative is no serial port, but enabling our "USB TTY Serial Login" feature easily allows serial CLI access *after* it has properly booted.  You need to use the VGA port for console access *during* boot and RUNNIX access.
https://doc.astlinux-project.org/userdoc:usbtty_serial_login

Note: As with many boards, if the the VGA port is not connected to a monitor at boot you can't latter attach it and see the console, you must boot with the monitor attached to use the VGA port.  Not just a Qotom thing.

Here in the US the barebone price is $125 + $34 shipping on Amazon, slightly less expensive via AliExpress.  Given it is directly shipped from China, any sort of return would be mostly eaten in shipping costs so if you planned on 1 out of 10 might be a bad unit you could price that into the cost.

A good value IMHO.

Lonnie



On Nov 1, 2017, at 2:49 PM, Michael Knill <mic...@ip...> wrote:

> Hi group
>  
> Qotom has just completed their EMC compliance for this unit so I can install it now in Australia.
> Anyone using these boxes?
>  
> Regards
> Michael Knill



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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....

Re: [Astlinux-users] Qotom Q190G4N-S07

[Michael K. <mic...@ip...>]

Yes I need 20mm x 60mm (
Oh well underneath it goes!

Regards
Michael Knill

-----Original Message-----
From: Lonnie Abelbeck <li...@lo...>
Reply-To: AstLinux List <ast...@li...>
Date: Thursday, 2 November 2017 at 8:22 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Qotom Q190G4N-S07

Michael,

> Not sure where I am going to put my IPC Solutions sticker though (. I don't think it will fit above the power button.

You could squeeze a 10 mm x 35 mm sticker (max) above the power button, with careful placement.

The underside has a lot of free smooth area for a sticker.

Lonnie


On Nov 1, 2017, at 4:08 PM, Michael Knill <mic...@ip...> wrote:

> Thanks Lonnie. When you posted this I approached the manufacturer for a EMC Compliance tests which they have now just completed. 
> I think the serial will be a minor annoyance only. I like the nice big heatsink!
> Not sure where I am going to put my IPC Solutions sticker though (. I don't think it will fit above the power button.
> 
> I will buy one to play with. Goody more toys.
> 
> Regards
> Michael Knill
> 
> -----Original Message-----
> From: Lonnie Abelbeck <li...@lo...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Thursday, 2 November 2017 at 7:40 am
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] Qotom Q190G4N-S07
> 
> Hi Michael,
> 
> I purchased one back in April 23, 2017, here is the writeup: 
> 
> Qotom Q190G4N-S07 Celeron J1900 Fanless Appliance
> https://doc.astlinux-project.org/userdoc:board_qotom_q190g4n-s07
> 
> I initially used a Crucial SO-DIMM, but had rare lockups, I swapped it with a Samsung SO-DIMM and has been running perfectly ever since.  Could be I had a marginal RAM stick.
> 
> It has been running 24/7 .
> 
> A very professional looking box, customers will be impressed.
> 
> The only negative is no serial port, but enabling our "USB TTY Serial Login" feature easily allows serial CLI access *after* it has properly booted.  You need to use the VGA port for console access *during* boot and RUNNIX access.
> https://doc.astlinux-project.org/userdoc:usbtty_serial_login
> 
> Note: As with many boards, if the the VGA port is not connected to a monitor at boot you can't latter attach it and see the console, you must boot with the monitor attached to use the VGA port.  Not just a Qotom thing.
> 
> Here in the US the barebone price is $125 + $34 shipping on Amazon, slightly less expensive via AliExpress.  Given it is directly shipped from China, any sort of return would be mostly eaten in shipping costs so if you planned on 1 out of 10 might be a bad unit you could price that into the cost.
> 
> A good value IMHO.
> 
> Lonnie
> 
> 
> 
> On Nov 1, 2017, at 2:49 PM, Michael Knill <mic...@ip...> wrote:
> 
>> Hi group
>> 
>> Qotom has just completed their EMC compliance for this unit so I can install it now in Australia.
>> Anyone using these boxes?
>> 
>> Regards
>> Michael Knill
> 
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> 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....
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> 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....
> 
> 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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....

Re: [Astlinux-users] Qotom Q190G4N-S07

[Lonnie A. <li...@lo...>]

Michael,

> Not sure where I am going to put my IPC Solutions sticker though (. I don't think it will fit above the power button.

You could squeeze a 10 mm x 35 mm sticker (max) above the power button, with careful placement.

The underside has a lot of free smooth area for a sticker.

Lonnie


On Nov 1, 2017, at 4:08 PM, Michael Knill <mic...@ip...> wrote:

> Thanks Lonnie. When you posted this I approached the manufacturer for a EMC Compliance tests which they have now just completed. 
> I think the serial will be a minor annoyance only. I like the nice big heatsink!
> Not sure where I am going to put my IPC Solutions sticker though (. I don't think it will fit above the power button.
> 
> I will buy one to play with. Goody more toys.
> 
> Regards
> Michael Knill
> 
> -----Original Message-----
> From: Lonnie Abelbeck <li...@lo...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Thursday, 2 November 2017 at 7:40 am
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] Qotom Q190G4N-S07
> 
> Hi Michael,
> 
> I purchased one back in April 23, 2017, here is the writeup: 
> 
> Qotom Q190G4N-S07 Celeron J1900 Fanless Appliance
> https://doc.astlinux-project.org/userdoc:board_qotom_q190g4n-s07
> 
> I initially used a Crucial SO-DIMM, but had rare lockups, I swapped it with a Samsung SO-DIMM and has been running perfectly ever since.  Could be I had a marginal RAM stick.
> 
> It has been running 24/7 .
> 
> A very professional looking box, customers will be impressed.
> 
> The only negative is no serial port, but enabling our "USB TTY Serial Login" feature easily allows serial CLI access *after* it has properly booted.  You need to use the VGA port for console access *during* boot and RUNNIX access.
> https://doc.astlinux-project.org/userdoc:usbtty_serial_login
> 
> Note: As with many boards, if the the VGA port is not connected to a monitor at boot you can't latter attach it and see the console, you must boot with the monitor attached to use the VGA port.  Not just a Qotom thing.
> 
> Here in the US the barebone price is $125 + $34 shipping on Amazon, slightly less expensive via AliExpress.  Given it is directly shipped from China, any sort of return would be mostly eaten in shipping costs so if you planned on 1 out of 10 might be a bad unit you could price that into the cost.
> 
> A good value IMHO.
> 
> Lonnie
> 
> 
> 
> On Nov 1, 2017, at 2:49 PM, Michael Knill <mic...@ip...> wrote:
> 
>> Hi group
>> 
>> Qotom has just completed their EMC compliance for this unit so I can install it now in Australia.
>> Anyone using these boxes?
>> 
>> Regards
>> Michael Knill
> 
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> 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....
> 
> 
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> 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....
> 
> 

Re: [Astlinux-users] Qotom Q190G4N-S07

[Michael K. <mic...@ip...>]

Thanks Lonnie. When you posted this I approached the manufacturer for a EMC Compliance tests which they have now just completed. 
I think the serial will be a minor annoyance only. I like the nice big heatsink!
Not sure where I am going to put my IPC Solutions sticker though (. I don't think it will fit above the power button.

I will buy one to play with. Goody more toys.

Regards
Michael Knill

-----Original Message-----
From: Lonnie Abelbeck <li...@lo...>
Reply-To: AstLinux List <ast...@li...>
Date: Thursday, 2 November 2017 at 7:40 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Qotom Q190G4N-S07

Hi Michael,

I purchased one back in April 23, 2017, here is the writeup: 

Qotom Q190G4N-S07 Celeron J1900 Fanless Appliance
https://doc.astlinux-project.org/userdoc:board_qotom_q190g4n-s07

I initially used a Crucial SO-DIMM, but had rare lockups, I swapped it with a Samsung SO-DIMM and has been running perfectly ever since.  Could be I had a marginal RAM stick.

It has been running 24/7 .

A very professional looking box, customers will be impressed.

The only negative is no serial port, but enabling our "USB TTY Serial Login" feature easily allows serial CLI access *after* it has properly booted.  You need to use the VGA port for console access *during* boot and RUNNIX access.
https://doc.astlinux-project.org/userdoc:usbtty_serial_login

Note: As with many boards, if the the VGA port is not connected to a monitor at boot you can't latter attach it and see the console, you must boot with the monitor attached to use the VGA port.  Not just a Qotom thing.

Here in the US the barebone price is $125 + $34 shipping on Amazon, slightly less expensive via AliExpress.  Given it is directly shipped from China, any sort of return would be mostly eaten in shipping costs so if you planned on 1 out of 10 might be a bad unit you could price that into the cost.

A good value IMHO.

Lonnie



On Nov 1, 2017, at 2:49 PM, Michael Knill <mic...@ip...> wrote:

> Hi group
>  
> Qotom has just completed their EMC compliance for this unit so I can install it now in Australia.
> Anyone using these boxes?
>  
> Regards
> Michael Knill



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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....

Re: [Astlinux-users] Qotom Q190G4N-S07

[Lonnie A. <li...@lo...>]

Hi Michael,

I purchased one back in April 23, 2017, here is the writeup: 

Qotom Q190G4N-S07 Celeron J1900 Fanless Appliance
https://doc.astlinux-project.org/userdoc:board_qotom_q190g4n-s07

I initially used a Crucial SO-DIMM, but had rare lockups, I swapped it with a Samsung SO-DIMM and has been running perfectly ever since.  Could be I had a marginal RAM stick.

It has been running 24/7 .

A very professional looking box, customers will be impressed.

The only negative is no serial port, but enabling our "USB TTY Serial Login" feature easily allows serial CLI access *after* it has properly booted.  You need to use the VGA port for console access *during* boot and RUNNIX access.
https://doc.astlinux-project.org/userdoc:usbtty_serial_login

Note: As with many boards, if the the VGA port is not connected to a monitor at boot you can't latter attach it and see the console, you must boot with the monitor attached to use the VGA port.  Not just a Qotom thing.

Here in the US the barebone price is $125 + $34 shipping on Amazon, slightly less expensive via AliExpress.  Given it is directly shipped from China, any sort of return would be mostly eaten in shipping costs so if you planned on 1 out of 10 might be a bad unit you could price that into the cost.

A good value IMHO.

Lonnie



On Nov 1, 2017, at 2:49 PM, Michael Knill <mic...@ip...> wrote:

> Hi group
>  
> Qotom has just completed their EMC compliance for this unit so I can install it now in Australia.
> Anyone using these boxes?
>  
> Regards
> Michael Knill

[Astlinux-users] Qotom Q190G4N-S07

[Michael K. <mic...@ip...>]

Hi group

Qotom has just completed their EMC compliance for this unit so I can install it now in Australia.
Anyone using these boxes?

Regards
Michael Knill

Re: [Astlinux-users] [asterisk-dev] Asterisk 11 EOL Announcement

[Michael K. <li...@mk...>]

> Am 29.10.2017 um 15:55 schrieb David Kerr <da...@ke...>:
> 
> Michael,
>   I have put the dialplan to implement voicemail call screening here...
> https://github.com/dkerr64/astlinux/blob/develop/package/asterisk/examples/voicemail-monitor.conf
> And remember that it does require either Asterisk 15 or a custom build of Asterisk 13 with this patch...
> https://github.com/dkerr64/astlinux/blob/develop/package/asterisk/asterisk-13-app-originate.patch
> 
> Your request prompted me to do further testing and so some cleanup and commenting of the code. Hopefully it is clear enough as to what it does and why/how it works.  If you have any questions just ask.
> 
> If you like this then lobby Lonnie to include the patch into Astlinux default build.  It extends the function of
> Asterisk app_originate() to match that in Asterisk 15.
> 
> David

Hi David,

thanks a lot for documenting this.
At first glance it seems to me, that it was quite some work to implement that stuff, wow.

I need some spare time to review it fully, and since my SIP-peer are more complicated than "SIP/${EXTEN}", I need to adjust it to my needs.
So it will take a while.

But never the less your patch seem to be very useful. No problem for me though, since I do my own builds too.

> On Thu, Oct 26, 2017 at 11:33 PM, David Kerr <da...@ke...> wrote:
> Michael,
>   If you could give me until the weekend please when I will have more time to get my dialplan for you.  In the meantime you would need a custom build with this patch...
> https://github.com/dkerr64/astlinux/blob/develop/package/asterisk/asterisk-13-app-originate.patch
> It is not in the mainline astlinux builds, that would be up to Lonnie to decide if to include or not.  Wiki instructions would make sense only if that patch was included, but I will certainly share details here in a few days.
> 
> David
> 
> On Thu, Oct 26, 2017 at 12:06 PM, Michael Keuter <li...@mk...> wrote:
> 
> > Am 26.10.2017 um 17:32 schrieb David Kerr <da...@ke...>:
> >
> > So, little plug here... one tiny part of the lots of new code in 15 is an enhancement to app Originate() that I proposed and was accepted...
> > https://issues.asterisk.org/jira/browse/ASTERISK-26587
> >
> > Cool feature enabled by this is call screening.  Remember the old days where you could let your answerphone pick up the call and you could hear the caller leave a message... and pick up the phone if you decided you do want to talk to them after all.  Well with the above you can do the same with Asterisk voicemail, if you have a phone that will auto-answer.  While the caller leaves a voicemail you can hear it and if you want to intercept and talk to the person you can do so.
> >
> > Requires some clever dialplan logic.  If anyone is interested I'd be happy to share what I have in my dialplan for this, and the patch to make it work on Asterisk 13.
> >
> > David
> 
> Hi David,
> 
> that sounds like a great addition!
> 
> I (and one of my customers) would be very interested in that feature.
> Maybe something for our Wiki …
> 
> Michael

Michael

http://www.mksolutions.info

Re: [Astlinux-users] [asterisk-dev] Asterisk 11 EOL Announcement

[David K. <da...@ke...>]

Michael,
  I have put the dialplan to implement voicemail call screening here...
https://github.com/dkerr64/astlinux/blob/develop/package/asterisk/examples/voicemail-monitor.conf
And remember that it does require either Asterisk 15 or a custom build of
Asterisk 13 with this patch...
https://github.com/dkerr64/astlinux/blob/develop/package/asterisk/asterisk-13-app-originate.patch

Your request prompted me to do further testing and so some cleanup and
commenting of the code. Hopefully it is clear enough as to what it does and
why/how it works.  If you have any questions just ask.

If you like this then lobby Lonnie to include the patch into Astlinux
default build.  It extends the function of
Asterisk app_originate() to match that in Asterisk 15.

David



On Thu, Oct 26, 2017 at 11:33 PM, David Kerr <da...@ke...> wrote:

> Michael,
>   If you could give me until the weekend please when I will have more time
> to get my dialplan for you.  In the meantime you would need a custom build
> with this patch...
> https://github.com/dkerr64/astlinux/blob/develop/package/
> asterisk/asterisk-13-app-originate.patch
> It is not in the mainline astlinux builds, that would be up to Lonnie to
> decide if to include or not.  Wiki instructions would make sense only if
> that patch was included, but I will certainly share details here in a few
> days.
>
> David
>
> On Thu, Oct 26, 2017 at 12:06 PM, Michael Keuter <li...@mk...>
> wrote:
>
>>
>> > Am 26.10.2017 um 17:32 schrieb David Kerr <da...@ke...>:
>> >
>> > So, little plug here... one tiny part of the lots of new code in 15 is
>> an enhancement to app Originate() that I proposed and was accepted...
>> > https://issues.asterisk.org/jira/browse/ASTERISK-26587
>> >
>> > Cool feature enabled by this is call screening.  Remember the old days
>> where you could let your answerphone pick up the call and you could hear
>> the caller leave a message... and pick up the phone if you decided you do
>> want to talk to them after all.  Well with the above you can do the same
>> with Asterisk voicemail, if you have a phone that will auto-answer.  While
>> the caller leaves a voicemail you can hear it and if you want to intercept
>> and talk to the person you can do so.
>> >
>> > Requires some clever dialplan logic.  If anyone is interested I'd be
>> happy to share what I have in my dialplan for this, and the patch to make
>> it work on Asterisk 13.
>> >
>> > David
>>
>> Hi David,
>>
>> that sounds like a great addition!
>>
>> I (and one of my customers) would be very interested in that feature.
>> Maybe something for our Wiki …
>>
>> > On Wed, Oct 25, 2017 at 12:31 PM, The Cadillac Kid via Astlinux-users <
>> ast...@li...> wrote:
>> > theres a lot of asterisk 11 production systems out there in the real
>> world..  i know I have a few hundred myself.. its been one of the good
>> ones!! 11.20  has been a good build of asterisk for me..  ive got systems
>> with > 500 day uptimes..
>> >
>> > I was glad to see asterisk 13 get a longer stay..  as its proving
>> itself to be a good one (im still using chan_sip in my 13's), PJ has goiven
>> me some grief but that will get better,.
>> >
>> > my cloud runs on 13.
>> >
>> > 14 is worthless (skip over this one)
>> > 15 isnt yet ready for prime time..  though it will be used in my test
>> labs to test since theres a **LOT** of new code in it..  but Ill not use it
>> in production.
>> >
>> > -Christopher
>> >
>> >
>> > On Wednesday, October 25, 2017, 11:21:45 AM EDT, Lonnie Abelbeck <
>> li...@lo...> wrote:
>> >
>> >
>> > AstLinux users, don't worry, we will be building Asterisk 11 for some
>> time to come.
>> >
>> > Lonnie
>> >
>> >
>> > On Oct 25, 2017, at 10:07 AM, Michael Keuter <li...@mk...>
>> wrote:
>> >
>> > >
>> > >> From: Matt Fredrickson <cr...@di...>
>> > >> Subject: [asterisk-dev] Asterisk 11 EOL Announcement
>> > >> Date: 25. Oktober 2017 16:44:55 MESZ
>> > >> To: Asterisk Developers Mailing List <ast...@li...>
>> > >> Antwort an: Asterisk Developers Mailing List <
>> ast...@li...>
>> > >>
>> > >> Dearly Beloved,
>> > >>
>> > >> We have gathered here today to mourn the passing of a deeply regarded
>> > >> branch of Asterisk - Asterisk 11.  As of today, it has officially
>> > >> reached its end of life.  It was a good branch, having served 5 years
>> > >> faithfully in the service of its users.  As far as history goes,
>> > >> 11.0.0 was born on November 28th 2012.  It had 1458 commits in its 5
>> > >> year life, and some will try to use it even after its useful end of
>> > >> life.  Now, mostly due to the fact that it is no longer with us,
>> > >> Asterisk 11 will become one of the “great” releases of Asterisk,
>> > >> joining the ranks of all the other “great” branches such as 1.0, 1.2,
>> > >> 1.4, 1.6, 1.8, and 10.  Please join with me now for a moment of
>> > >> silence for it, as it passes to the great beyond.
>> > >>
>> > >> In all seriousness, if you didn’t get the humor in the above message,
>> > >> today is the day that Asterisk 11 officially goes end of life.  For
>> > >> the last year, Asterisk 11 has been in security fix only mode,
>> meaning
>> > >> it stopped receive regular bug fixes a year ago, and has only
>> received
>> > >> security related fixes.  Today that all ends and not even security
>> > >> fixes will going into that branch.  If you haven’t gotten off of it
>> > >> yet, there is no better time than the present.
>> > >>
>> > >> If you’re curious about the dates and times associated with life
>> > >> cycles transitions on Asterisk branches, you can read more at
>> > >> https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions
>> > >>
>> > >> Last of all, thanks to all of you who contribute to the Asterisk
>> > >> project, whether it be bug reports, bug fixes, new feature
>> > >> development, or helping other users by answering questions on the
>> > >> mailing lists, forums, and other venues.  At the end of the day, it’s
>> > >> the quality of the user and development community that make Asterisk
>> > >> such a great project.
>> > >>
>> > >> Best wishes.
>> > >>
>> > >> --
>> > >> Matthew Fredrickson
>> > >> Digium, Inc. | Engineering Manager
>> > >> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
>> > >
>> > > Michael
>> > >
>> > > http://www.mksolutions.info
>>
>> Michael
>>
>> http://www.mksolutions.info
>>
>>
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> 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....
>
>
>

Re: [Astlinux-users] Lots of chronyd logs at a particular site

[Michael K. <mic...@ip...>]

Yes thanks Lonnie. Interesting you mention random packet loss as I think I am getting some.
Do you think setting a list of servers in a persistent chrony.conf is ok? 
Or should I just mask the logs?

Regards
Michael Knill

-----Original Message-----
From: Lonnie Abelbeck <li...@lo...>
Reply-To: AstLinux List <ast...@li...>
Date: Sunday, 29 October 2017 at 8:03 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Lots of chronyd logs at a particular site

Michael,

I agree unusual, but not excessive for a 24 hour period.

Possibly all the sources are very similar (same stratum and similar offset) so it is a constant "horse race" who wins.  If your upstream ISP had a lot of random packet loss might be a cause as well, not sure.

My local time server is consistent because of a local GPS server ...
--
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^* time-gps...             1  10   377   997   +215us[ +250us] +/- 1467us
^- ntp...                      2  10   377   760  -1718us[-1718us] +/-   25ms
^- tock...                    1  10   377   531    -13ms[  -13ms] +/-   24ms
--
so it almost never changes sources.

Lonnie



On Oct 28, 2017, at 3:41 PM, Michael Knill <mic...@ip...> wrote:

> Oct 28 04:26:28 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 04:45:22 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 05:35:25 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 06:08:19 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 07:01:34 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 08:39:19 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 12:45:30 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 13:19:57 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 14:20:22 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 116.66.161.4
> Oct 28 14:23:35 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 15:38:01 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 17:04:21 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 17:21:30 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 19:14:42 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 19:39:36 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 20:20:28 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 20:48:11 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 116.66.161.4
> Oct 28 21:52:06 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 22:05:01 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 22:37:22 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 23:29:07 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 23:45:29 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 29 01:13:49 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 29 01:21:22 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 29 02:59:31 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 116.66.161.4
> Oct 29 03:21:05 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
>  
> I don't recall getting this many logs at other sites? Any ideas?
>  
> Regards
> Michael Knill
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> 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....


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
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....

Re: [Astlinux-users] Lots of chronyd logs at a particular site

[Lonnie A. <li...@lo...>]

Michael,

I agree unusual, but not excessive for a 24 hour period.

Possibly all the sources are very similar (same stratum and similar offset) so it is a constant "horse race" who wins.  If your upstream ISP had a lot of random packet loss might be a cause as well, not sure.

My local time server is consistent because of a local GPS server ...
--
MS Name/IP address         Stratum Poll Reach LastRx Last sample
===============================================================================
^* time-gps...             1  10   377   997   +215us[ +250us] +/- 1467us
^- ntp...                      2  10   377   760  -1718us[-1718us] +/-   25ms
^- tock...                    1  10   377   531    -13ms[  -13ms] +/-   24ms
--
so it almost never changes sources.

Lonnie



On Oct 28, 2017, at 3:41 PM, Michael Knill <mic...@ip...> wrote:

> Oct 28 04:26:28 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 04:45:22 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 05:35:25 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 06:08:19 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 07:01:34 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 08:39:19 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 12:45:30 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 13:19:57 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 14:20:22 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 116.66.161.4
> Oct 28 14:23:35 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 15:38:01 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 17:04:21 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 17:21:30 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 19:14:42 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 19:39:36 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 20:20:28 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 20:48:11 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 116.66.161.4
> Oct 28 21:52:06 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 22:05:01 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 22:37:22 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 28 23:29:07 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 28 23:45:29 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
> Oct 29 01:13:49 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 29 01:21:22 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
> Oct 29 02:59:31 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 116.66.161.4
> Oct 29 03:21:05 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
>  
> I don't recall getting this many logs at other sites? Any ideas?
>  
> Regards
> Michael Knill
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> 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] Lots of chronyd logs at a particular site

[Michael K. <mic...@ip...>]

Oct 28 04:26:28 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
Oct 28 04:45:22 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
Oct 28 05:35:25 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
Oct 28 06:08:19 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
Oct 28 07:01:34 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
Oct 28 08:39:19 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
Oct 28 12:45:30 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
Oct 28 13:19:57 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
Oct 28 14:20:22 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 116.66.161.4
Oct 28 14:23:35 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
Oct 28 15:38:01 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
Oct 28 17:04:21 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
Oct 28 17:21:30 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
Oct 28 19:14:42 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
Oct 28 19:39:36 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
Oct 28 20:20:28 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
Oct 28 20:48:11 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 116.66.161.4
Oct 28 21:52:06 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
Oct 28 22:05:01 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
Oct 28 22:37:22 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
Oct 28 23:29:07 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
Oct 28 23:45:29 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 144.48.166.166
Oct 29 01:13:49 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
Oct 29 01:21:22 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33
Oct 29 02:59:31 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 116.66.161.4
Oct 29 03:21:05 3040-RJSC-CM1 daemon.info chronyd[1039]: Selected source 192.189.54.33

I don't recall getting this many logs at other sites? Any ideas?

Regards
Michael Knill

Re: [Astlinux-users] [asterisk-dev] Asterisk 11 EOL Announcement

[David K. <da...@ke...>]

Michael,
  If you could give me until the weekend please when I will have more time
to get my dialplan for you.  In the meantime you would need a custom build
with this patch...
https://github.com/dkerr64/astlinux/blob/develop/package/asterisk/asterisk-13-app-originate.patch
It is not in the mainline astlinux builds, that would be up to Lonnie to
decide if to include or not.  Wiki instructions would make sense only if
that patch was included, but I will certainly share details here in a few
days.

David

On Thu, Oct 26, 2017 at 12:06 PM, Michael Keuter <li...@mk...>
wrote:

>
> > Am 26.10.2017 um 17:32 schrieb David Kerr <da...@ke...>:
> >
> > So, little plug here... one tiny part of the lots of new code in 15 is
> an enhancement to app Originate() that I proposed and was accepted...
> > https://issues.asterisk.org/jira/browse/ASTERISK-26587
> >
> > Cool feature enabled by this is call screening.  Remember the old days
> where you could let your answerphone pick up the call and you could hear
> the caller leave a message... and pick up the phone if you decided you do
> want to talk to them after all.  Well with the above you can do the same
> with Asterisk voicemail, if you have a phone that will auto-answer.  While
> the caller leaves a voicemail you can hear it and if you want to intercept
> and talk to the person you can do so.
> >
> > Requires some clever dialplan logic.  If anyone is interested I'd be
> happy to share what I have in my dialplan for this, and the patch to make
> it work on Asterisk 13.
> >
> > David
>
> Hi David,
>
> that sounds like a great addition!
>
> I (and one of my customers) would be very interested in that feature.
> Maybe something for our Wiki …
>
> > On Wed, Oct 25, 2017 at 12:31 PM, The Cadillac Kid via Astlinux-users <
> ast...@li...> wrote:
> > theres a lot of asterisk 11 production systems out there in the real
> world..  i know I have a few hundred myself.. its been one of the good
> ones!! 11.20  has been a good build of asterisk for me..  ive got systems
> with > 500 day uptimes..
> >
> > I was glad to see asterisk 13 get a longer stay..  as its proving itself
> to be a good one (im still using chan_sip in my 13's), PJ has goiven me
> some grief but that will get better,.
> >
> > my cloud runs on 13.
> >
> > 14 is worthless (skip over this one)
> > 15 isnt yet ready for prime time..  though it will be used in my test
> labs to test since theres a **LOT** of new code in it..  but Ill not use it
> in production.
> >
> > -Christopher
> >
> >
> > On Wednesday, October 25, 2017, 11:21:45 AM EDT, Lonnie Abelbeck <
> li...@lo...> wrote:
> >
> >
> > AstLinux users, don't worry, we will be building Asterisk 11 for some
> time to come.
> >
> > Lonnie
> >
> >
> > On Oct 25, 2017, at 10:07 AM, Michael Keuter <li...@mk...>
> wrote:
> >
> > >
> > >> From: Matt Fredrickson <cr...@di...>
> > >> Subject: [asterisk-dev] Asterisk 11 EOL Announcement
> > >> Date: 25. Oktober 2017 16:44:55 MESZ
> > >> To: Asterisk Developers Mailing List <ast...@li...>
> > >> Antwort an: Asterisk Developers Mailing List <
> ast...@li...>
> > >>
> > >> Dearly Beloved,
> > >>
> > >> We have gathered here today to mourn the passing of a deeply regarded
> > >> branch of Asterisk - Asterisk 11.  As of today, it has officially
> > >> reached its end of life.  It was a good branch, having served 5 years
> > >> faithfully in the service of its users.  As far as history goes,
> > >> 11.0.0 was born on November 28th 2012.  It had 1458 commits in its 5
> > >> year life, and some will try to use it even after its useful end of
> > >> life.  Now, mostly due to the fact that it is no longer with us,
> > >> Asterisk 11 will become one of the “great” releases of Asterisk,
> > >> joining the ranks of all the other “great” branches such as 1.0, 1.2,
> > >> 1.4, 1.6, 1.8, and 10.  Please join with me now for a moment of
> > >> silence for it, as it passes to the great beyond.
> > >>
> > >> In all seriousness, if you didn’t get the humor in the above message,
> > >> today is the day that Asterisk 11 officially goes end of life.  For
> > >> the last year, Asterisk 11 has been in security fix only mode, meaning
> > >> it stopped receive regular bug fixes a year ago, and has only received
> > >> security related fixes.  Today that all ends and not even security
> > >> fixes will going into that branch.  If you haven’t gotten off of it
> > >> yet, there is no better time than the present.
> > >>
> > >> If you’re curious about the dates and times associated with life
> > >> cycles transitions on Asterisk branches, you can read more at
> > >> https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions
> > >>
> > >> Last of all, thanks to all of you who contribute to the Asterisk
> > >> project, whether it be bug reports, bug fixes, new feature
> > >> development, or helping other users by answering questions on the
> > >> mailing lists, forums, and other venues.  At the end of the day, it’s
> > >> the quality of the user and development community that make Asterisk
> > >> such a great project.
> > >>
> > >> Best wishes.
> > >>
> > >> --
> > >> Matthew Fredrickson
> > >> Digium, Inc. | Engineering Manager
> > >> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
> > >
> > > Michael
> > >
> > > http://www.mksolutions.info
>
> Michael
>
> http://www.mksolutions.info
>
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> 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....