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...> - 2017-12-18 00:08:56
|
Hmm thanks Michael. I wonder if it is an Asterisk problem. I don't think so as I restarted Asterisk and it didn't fix it. Would it be more likely that its the PPPoE client or firewall? Regards Michael Knill -----Original Message----- From: Michael Keuter <li...@mk...> Reply-To: AstLinux List <ast...@li...> Date: Monday, 18 December 2017 at 10:43 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Problems with PPPoE and Asterisk > Am 17.12.2017 um 23:43 schrieb Michael Knill <mic...@ip...>: > > Hi Group > > I am still having issues with PPPoE and Asterisk connectivity. > > This happened over the weekend with one of my sites: > Dec 17 00:30:09 2005-Shaw_BG-CM1 local0.notice asterisk[1266]: NOTICE[1408]: chan_sip.c:30077 in sip_poke_noanswer: Peer 'cts_trunk' is now UNREACHABLE! Last qualify: 33 > Dec 17 00:30:33 2005-Shaw_BG-CM1 local0.notice asterisk[1266]: NOTICE[1408]: chan_sip.c:24558 in handle_response_peerpoke: Peer 'cts_trunk' is now Reachable. (34ms / 2000ms) > Dec 17 00:30:52 2005-Shaw_BG-CM1 daemon.info pppd[336]: LCP terminated by peer > Dec 17 00:30:52 2005-Shaw_BG-CM1 daemon.info pppd[336]: Connect time 568.6 minutes. > Dec 17 00:30:52 2005-Shaw_BG-CM1 daemon.info pppd[336]: Sent 1190012 bytes, received 1282467 bytes. > Dec 17 00:30:55 2005-Shaw_BG-CM1 daemon.notice pppd[336]: Connection terminated. > Dec 17 00:30:55 2005-Shaw_BG-CM1 daemon.notice pppd[336]: Modem hangup > Dec 17 00:31:03 2005-Shaw_BG-CM1 local0.warn asterisk[1266]: WARNING[1408]: acl.c:939 in ast_ouraddrfor: Cannot connect to 103.226.10.78: Network is unreachable > Dec 17 00:31:03 2005-Shaw_BG-CM1 local0.warn asterisk[1266]: WARNING[1408]: chan_sip.c:3785 in __sip_xmit: sip_xmit of 0x1ef58a0 (len 511) to 103.226.10.78:5060 returned -2: Network is unreachable > Dec 17 00:31:03 2005-Shaw_BG-CM1 local0.err asterisk[1266]: ERROR[1408]: chan_sip.c:4274 in __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data > Dec 17 00:31:07 2005-Shaw_BG-CM1 local0.notice asterisk[1266]: NOTICE[1408]: chan_sip.c:30077 in sip_poke_noanswer: Peer 'cts_trunk' is now UNREACHABLE! Last qualify: 34 > Dec 17 00:31:17 2005-Shaw_BG-CM1 local0.warn asterisk[1266]: WARNING[1408]: acl.c:939 in ast_ouraddrfor: Cannot connect to 103.226.10.78: Network is unreachable > Dec 17 00:31:17 2005-Shaw_BG-CM1 local0.warn asterisk[1266]: WARNING[1408]: chan_sip.c:3785 in __sip_xmit: sip_xmit of 0x1ef58a0 (len 511) to 103.226.10.78:5060 returned -2: Network is unreachable > Dec 17 00:31:17 2005-Shaw_BG-CM1 local0.err asterisk[1266]: ERROR[1408]: chan_sip.c:4274 in __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data > Dec 17 00:31:23 2005-Shaw_BG-CM1 user.info kernel: AIF:Dropped INPUT packet: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:02:60:40:02:01:41:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=146 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP SPT=5678 DPT=5678 LEN=126 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.info pppd[336]: PPP session is 3426 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.warn pppd[336]: Connected to e0:0e:da:4c:55:dd via interface eth0 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.info pppd[336]: Using interface ppp0 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: Connect: ppp0 <--> eth0 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: PAP authentication succeeded > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: peer from calling number E0:0E:DA:4C:55:DD authorized > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: local IP address 124.148.24.56 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: remote IP address 150.101.32.171 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: primary DNS address 203.0.178.191 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: secondary DNS address 203.215.29.191 > > > The PPPoE came back fine however the SIP Trunk did not come back. I tried an Asterisk reload an Asterisk restart and a firewall restart to no avail. > I actually needed to reboot the box before it came back up. This has happened before > > Im running Astlinux 1.2.10 with Asterisk 13. > > Any ideas? > > Regards > Michael Knill I have seen the same behaviour too with Asterisk 11. 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.... |
|
From: Michael K. <li...@mk...> - 2017-12-17 23:42:50
|
> Am 17.12.2017 um 23:43 schrieb Michael Knill <mic...@ip...>: > > Hi Group > > I am still having issues with PPPoE and Asterisk connectivity. > > This happened over the weekend with one of my sites: > Dec 17 00:30:09 2005-Shaw_BG-CM1 local0.notice asterisk[1266]: NOTICE[1408]: chan_sip.c:30077 in sip_poke_noanswer: Peer 'cts_trunk' is now UNREACHABLE! Last qualify: 33 > Dec 17 00:30:33 2005-Shaw_BG-CM1 local0.notice asterisk[1266]: NOTICE[1408]: chan_sip.c:24558 in handle_response_peerpoke: Peer 'cts_trunk' is now Reachable. (34ms / 2000ms) > Dec 17 00:30:52 2005-Shaw_BG-CM1 daemon.info pppd[336]: LCP terminated by peer > Dec 17 00:30:52 2005-Shaw_BG-CM1 daemon.info pppd[336]: Connect time 568.6 minutes. > Dec 17 00:30:52 2005-Shaw_BG-CM1 daemon.info pppd[336]: Sent 1190012 bytes, received 1282467 bytes. > Dec 17 00:30:55 2005-Shaw_BG-CM1 daemon.notice pppd[336]: Connection terminated. > Dec 17 00:30:55 2005-Shaw_BG-CM1 daemon.notice pppd[336]: Modem hangup > Dec 17 00:31:03 2005-Shaw_BG-CM1 local0.warn asterisk[1266]: WARNING[1408]: acl.c:939 in ast_ouraddrfor: Cannot connect to 103.226.10.78: Network is unreachable > Dec 17 00:31:03 2005-Shaw_BG-CM1 local0.warn asterisk[1266]: WARNING[1408]: chan_sip.c:3785 in __sip_xmit: sip_xmit of 0x1ef58a0 (len 511) to 103.226.10.78:5060 returned -2: Network is unreachable > Dec 17 00:31:03 2005-Shaw_BG-CM1 local0.err asterisk[1266]: ERROR[1408]: chan_sip.c:4274 in __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data > Dec 17 00:31:07 2005-Shaw_BG-CM1 local0.notice asterisk[1266]: NOTICE[1408]: chan_sip.c:30077 in sip_poke_noanswer: Peer 'cts_trunk' is now UNREACHABLE! Last qualify: 34 > Dec 17 00:31:17 2005-Shaw_BG-CM1 local0.warn asterisk[1266]: WARNING[1408]: acl.c:939 in ast_ouraddrfor: Cannot connect to 103.226.10.78: Network is unreachable > Dec 17 00:31:17 2005-Shaw_BG-CM1 local0.warn asterisk[1266]: WARNING[1408]: chan_sip.c:3785 in __sip_xmit: sip_xmit of 0x1ef58a0 (len 511) to 103.226.10.78:5060 returned -2: Network is unreachable > Dec 17 00:31:17 2005-Shaw_BG-CM1 local0.err asterisk[1266]: ERROR[1408]: chan_sip.c:4274 in __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data > Dec 17 00:31:23 2005-Shaw_BG-CM1 user.info kernel: AIF:Dropped INPUT packet: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:02:60:40:02:01:41:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=146 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP SPT=5678 DPT=5678 LEN=126 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.info pppd[336]: PPP session is 3426 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.warn pppd[336]: Connected to e0:0e:da:4c:55:dd via interface eth0 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.info pppd[336]: Using interface ppp0 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: Connect: ppp0 <--> eth0 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: PAP authentication succeeded > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: peer from calling number E0:0E:DA:4C:55:DD authorized > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: local IP address 124.148.24.56 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: remote IP address 150.101.32.171 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: primary DNS address 203.0.178.191 > Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: secondary DNS address 203.215.29.191 > > > The PPPoE came back fine however the SIP Trunk did not come back. I tried an Asterisk reload an Asterisk restart and a firewall restart to no avail. > I actually needed to reboot the box before it came back up. This has happened before > > Im running Astlinux 1.2.10 with Asterisk 13. > > Any ideas? > > Regards > Michael Knill I have seen the same behaviour too with Asterisk 11. Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2017-12-17 22:43:52
|
Hi Group I am still having issues with PPPoE and Asterisk connectivity. This happened over the weekend with one of my sites: Dec 17 00:30:09 2005-Shaw_BG-CM1 local0.notice asterisk[1266]: NOTICE[1408]: chan_sip.c:30077 in sip_poke_noanswer: Peer 'cts_trunk' is now UNREACHABLE! Last qualify: 33 Dec 17 00:30:33 2005-Shaw_BG-CM1 local0.notice asterisk[1266]: NOTICE[1408]: chan_sip.c:24558 in handle_response_peerpoke: Peer 'cts_trunk' is now Reachable. (34ms / 2000ms) Dec 17 00:30:52 2005-Shaw_BG-CM1 daemon.info pppd[336]: LCP terminated by peer Dec 17 00:30:52 2005-Shaw_BG-CM1 daemon.info pppd[336]: Connect time 568.6 minutes. Dec 17 00:30:52 2005-Shaw_BG-CM1 daemon.info pppd[336]: Sent 1190012 bytes, received 1282467 bytes. Dec 17 00:30:55 2005-Shaw_BG-CM1 daemon.notice pppd[336]: Connection terminated. Dec 17 00:30:55 2005-Shaw_BG-CM1 daemon.notice pppd[336]: Modem hangup Dec 17 00:31:03 2005-Shaw_BG-CM1 local0.warn asterisk[1266]: WARNING[1408]: acl.c:939 in ast_ouraddrfor: Cannot connect to 103.226.10.78: Network is unreachable Dec 17 00:31:03 2005-Shaw_BG-CM1 local0.warn asterisk[1266]: WARNING[1408]: chan_sip.c:3785 in __sip_xmit: sip_xmit of 0x1ef58a0 (len 511) to 103.226.10.78:5060 returned -2: Network is unreachable Dec 17 00:31:03 2005-Shaw_BG-CM1 local0.err asterisk[1266]: ERROR[1408]: chan_sip.c:4274 in __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data Dec 17 00:31:07 2005-Shaw_BG-CM1 local0.notice asterisk[1266]: NOTICE[1408]: chan_sip.c:30077 in sip_poke_noanswer: Peer 'cts_trunk' is now UNREACHABLE! Last qualify: 34 Dec 17 00:31:17 2005-Shaw_BG-CM1 local0.warn asterisk[1266]: WARNING[1408]: acl.c:939 in ast_ouraddrfor: Cannot connect to 103.226.10.78: Network is unreachable Dec 17 00:31:17 2005-Shaw_BG-CM1 local0.warn asterisk[1266]: WARNING[1408]: chan_sip.c:3785 in __sip_xmit: sip_xmit of 0x1ef58a0 (len 511) to 103.226.10.78:5060 returned -2: Network is unreachable Dec 17 00:31:17 2005-Shaw_BG-CM1 local0.err asterisk[1266]: ERROR[1408]: chan_sip.c:4274 in __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data Dec 17 00:31:23 2005-Shaw_BG-CM1 user.info kernel: AIF:Dropped INPUT packet: IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:02:60:40:02:01:41:08:00 SRC=0.0.0.0 DST=255.255.255.255 LEN=146 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP SPT=5678 DPT=5678 LEN=126 Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.info pppd[336]: PPP session is 3426 Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.warn pppd[336]: Connected to e0:0e:da:4c:55:dd via interface eth0 Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.info pppd[336]: Using interface ppp0 Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: Connect: ppp0 <--> eth0 Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: PAP authentication succeeded Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: peer from calling number E0:0E:DA:4C:55:DD authorized Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: local IP address 124.148.24.56 Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: remote IP address 150.101.32.171 Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: primary DNS address 203.0.178.191 Dec 17 00:31:25 2005-Shaw_BG-CM1 daemon.notice pppd[336]: secondary DNS address 203.215.29.191 The PPPoE came back fine however the SIP Trunk did not come back. I tried an Asterisk reload an Asterisk restart and a firewall restart to no avail. I actually needed to reboot the box before it came back up. This has happened before Im running Astlinux 1.2.10 with Asterisk 13. Any ideas? Regards Michael Knill |
|
From: David K. <da...@ke...> - 2017-12-04 16:24:09
|
I agree, for site-to-site Wireguard is perfect. With time more user friendly clients will emerge and a mechanism for managing IP addresses established to make that work easily as well. David. On Mon, Dec 4, 2017 at 11:05 AM, Lonnie Abelbeck <li...@lo...> wrote: > Hi David, > > Thanks for testing WireGuard, and you make good points. > > WireGuard and IPSec are similar in some ways, as the core code is in the > kernel and as such all addresses are manually assigned as you mention. > > IPSec has bolted on much "stuff" as time has gone on, Extended > Authentication (XAUTH) and Mode Configuration (MODE-CFG) to support dynamic > pools for client configuration via a user space daemon. > > I have tested a commercial VPN provider Mullvad.net which supports > WireGuard VPN "clients" where their "server" end automatically assigns a > 10.0.0.0/8 private /32 address for each client. A static one-time > configuration, works very nicely. > > Another approach would be to standardize on a IPv6 ULA "fd" address scheme > for the local client address, possibly generated from a hash of the > PublicKey. > > For site-to-site AstLinux constellations, there is no better VPN solution > than WireGuard, IMHO. > > It will take some time for Android, iOS, ChromeOS, etc. to provide > WireGuard solutions, but Android is almost there now, both user-space and > kernel implementations. > > Lonnie > > > On Dec 4, 2017, at 9:02 AM, David Kerr <Da...@Ke...> wrote: > > > Having played with Wireguard I think that it is very good underlying > technology to implement VPN. It seems to be very robust and tolerates > roaming (client's IP address changing) very well. But there are missing > pieces before it is ready for mainstream adoption. > > > > The biggest issue that I see is that client IP addresses (whether IPv4 > or IPv6) needed to be managed manually.... if you have a dozen clients > connecting in to the one server, each of these clients must have an IP > address manually assigned and configured at the client, and the server > needs to know what IP address was assigned and if there are any conflicts > (two clients use the same IP address) then I guess the results are > "undefined". Right now there is no way to have the server manage a pool of > IP addresses and push out to the client a IP address when it connects, > whether that IP is dynamically determined by the server or manually > configured for each client on the server. Wireguard could never be > deployed on a large scale without this. > > > > Managing IP addresses should not be a kernel task. So I suspect the raw > VPN technology will get embedded into the kernel and solving IP address > management will be left to some user space utility. I just don't know if > it will require some supporting capability in the kernel or not. > > > > David > > > > > > > > On Sun, Dec 3, 2017 at 3:44 PM, Michael Knill < > mic...@ip...> wrote: > > Great thanks Lonnie. Im looking forward to it. Very cool! > > > > Regards > > Michael Knill > > > > -----Original Message----- > > From: Lonnie Abelbeck <li...@lo...> > > Reply-To: AstLinux List <ast...@li...> > > Date: Monday, 4 December 2017 at 1:39 am > > To: AstLinux List <ast...@li...> > > Subject: Re: [Astlinux-users] AstLinux Pre-Release: > astlinux-1.3-3534-c5e366 > > > > Hi Michael, > > > > > Wow (WireGuard) looks super easy to set up. > > > > Indeed, the easiest VPN you ever have setup, particularly for > site-to-stie scenarios routing networks across the VPN. > > > > > > > So is it ready for production? > > > > I have had in production a remote AstLinux box (SIP / HTTPS) over > WireGuard for a few weeks now ... works perfectly, never missed a beat, > different ISP at each end. > > > > Officially, I would look for a 1.0.0 release and acceptance into the > mainline Linux kernel as milestones indicating WireGuard's > production-readyness ... should happen soon, but not yet. > > > > Definitely worth testing now. > > > > Lonnie > > > > > > > > On Dec 2, 2017, at 10:26 PM, Michael Knill <michael.knill@ipcsolutions. > com.au> wrote: > > > > > Wow looks super easy to set up. So is it ready for production? > > > > > > Regards > > > Michael Knill > > > > > > -----Original Message----- > > > From: Lonnie Abelbeck <li...@lo...> > > > Reply-To: AstLinux Developers Mailing List <astlinux-devel@lists. > sourceforge.net> > > > Date: Sunday, 3 December 2017 at 10:13 am > > > To: AstLinux List <ast...@li...> > > > Cc: AstLinux Developers Mailing List <astlinux-devel@lists. > sourceforge.net> > > > Subject: [Astlinux-devel] AstLinux Pre-Release: > astlinux-1.3-3534-c5e366 > > > > > > Announcing Pre-Release Version: astlinux-1.3-3534-c5e366 > > > > > > Particularly notable is the addition of the WireGuard VPN. > > > > > > The AstLinux Team is regularly upgrading packages containing security > and bug fixes as well as adding new features of our own. > > > > > > -- WireGuard VPN, new package; an extremely simple yet fast and modern > VPN that utilizes state-of-the-art cryptography. > > > http://doc.astlinux-project.org/userdoc:tt_wireguard_vpn > > > > > > -- Asterisk 13 version bump to 13.18.3 > > > > > > These pre-release images are for those who would like to take > advantage of the AstLinux development before the next official release, as > well as providing testing for the project. > > > > > > The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can > be found under the "Development" tab of the AstLinux Project web site ... > > > > > > AstLinux Project -> Development > > > http://www.astlinux-project.org/dev.html > > > > > > While these images are considered 'stable', the lack of testing will > not make these images suitable for critical production systems. > > > > > > If you should come across an issue, please report back here. > > > > > > AstLinux Team > > > > > > ------------------------------------------------------------ > ------------------ > > 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.... > > > ------------------------------------------------------------ > ------------------ > 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.... > |
|
From: David K. <da...@ke...> - 2017-12-04 16:21:21
|
Hi Michael, It looks like both Mullvad and azire are using essentially the same script (copyright claimed by same person) to do initial configuration... they request info from their servers using simple HTTS requests to obtain basic info from which they create the wireguard config files. This means that they are managing a pool of IP addresses at their servers when the customer does an initial configuration. Essentially assigning a static IP address that will be used every time a customer connects. The VPN IP address will be the same for every connection. If they allocate from the 10.x.x.x pool then this gives them approx 16 million IP addresses to work from. Which probably works fine for a small VPN provider. I suppose when they run out they can start revoking the access rights of the last used IP address by keeping track of who connects when, whomever connected longest time ago looses their VPN access. For IPv6 I doubt that there is any problem with running out of available addresses! It would be interesting to see the server-side scripts for this. David On Mon, Dec 4, 2017 at 10:32 AM, Michael Keuter <li...@mk...> wrote: > > > Am 04.12.2017 um 16:02 schrieb David Kerr <da...@ke...>: > > > > Having played with Wireguard I think that it is very good underlying > technology to implement VPN. It seems to be very robust and tolerates > roaming (client's IP address changing) very well. But there are missing > pieces before it is ready for mainstream adoption. > > > > The biggest issue that I see is that client IP addresses (whether IPv4 > or IPv6) needed to be managed manually.... if you have a dozen clients > connecting in to the one server, each of these clients must have an IP > address manually assigned and configured at the client, and the server > needs to know what IP address was assigned and if there are any conflicts > (two clients use the same IP address) then I guess the results are > "undefined". Right now there is no way to have the server manage a pool of > IP addresses and push out to the client a IP address when it connects, > whether that IP is dynamically determined by the server or manually > configured for each client on the server. Wireguard could never be > deployed on a large scale without this. > > Hi David, > > good point. It would be interesting in which way the commercial VPN > providers, who use WireGuard, are handling this issue. > Lonnie has tested Mullvad recently, maybe he can comment. > > https://www.azirevpn.com/wireguard > https://www.mullvad.net/guides/wireguard-and-mullvad-vpn/ > > > Managing IP addresses should not be a kernel task. So I suspect the raw > VPN technology will get embedded into the kernel and solving IP address > management will be left to some user space utility. I just don't know if > it will require some supporting capability in the kernel or not. > > > > David > > > > > > > > On Sun, Dec 3, 2017 at 3:44 PM, Michael Knill < > mic...@ip...> wrote: > > Great thanks Lonnie. Im looking forward to it. Very cool! > > > > Regards > > Michael Knill > > > > -----Original Message----- > > From: Lonnie Abelbeck <li...@lo...> > > Reply-To: AstLinux List <ast...@li...> > > Date: Monday, 4 December 2017 at 1:39 am > > To: AstLinux List <ast...@li...> > > Subject: Re: [Astlinux-users] AstLinux Pre-Release: > astlinux-1.3-3534-c5e366 > > > > Hi Michael, > > > > > Wow (WireGuard) looks super easy to set up. > > > > Indeed, the easiest VPN you ever have setup, particularly for > site-to-stie scenarios routing networks across the VPN. > > > > > > > So is it ready for production? > > > > I have had in production a remote AstLinux box (SIP / HTTPS) over > WireGuard for a few weeks now ... works perfectly, never missed a beat, > different ISP at each end. > > > > Officially, I would look for a 1.0.0 release and acceptance into the > mainline Linux kernel as milestones indicating WireGuard's > production-readyness ... should happen soon, but not yet. > > > > Definitely worth testing now. > > > > Lonnie > > > > > > > > On Dec 2, 2017, at 10:26 PM, Michael Knill <michael.knill@ipcsolutions. > com.au> wrote: > > > > > Wow looks super easy to set up. So is it ready for production? > > > > > > Regards > > > Michael Knill > > > > > > -----Original Message----- > > > From: Lonnie Abelbeck <li...@lo...> > > > Reply-To: AstLinux Developers Mailing List <astlinux-devel@lists. > sourceforge.net> > > > Date: Sunday, 3 December 2017 at 10:13 am > > > To: AstLinux List <ast...@li...> > > > Cc: AstLinux Developers Mailing List <astlinux-devel@lists. > sourceforge.net> > > > Subject: [Astlinux-devel] AstLinux Pre-Release: > astlinux-1.3-3534-c5e366 > > > > > > Announcing Pre-Release Version: astlinux-1.3-3534-c5e366 > > > > > > Particularly notable is the addition of the WireGuard VPN. > > > > > > The AstLinux Team is regularly upgrading packages containing security > and bug fixes as well as adding new features of our own. > > > > > > -- WireGuard VPN, new package; an extremely simple yet fast and modern > VPN that utilizes state-of-the-art cryptography. > > > http://doc.astlinux-project.org/userdoc:tt_wireguard_vpn > > > > > > -- Asterisk 13 version bump to 13.18.3 > > > > > > These pre-release images are for those who would like to take > advantage of the AstLinux development before the next official release, as > well as providing testing for the project. > > > > > > The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can > be found under the "Development" tab of the AstLinux Project web site ... > > > > > > AstLinux Project -> Development > > > http://www.astlinux-project.org/dev.html > > > > > > While these images are considered 'stable', the lack of testing will > not make these images suitable for critical production systems. > > > > > > If you should come across an issue, please report back here. > > > > > > AstLinux Team > > 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.... > |
|
From: Lonnie A. <li...@lo...> - 2017-12-04 16:05:52
|
Hi David, Thanks for testing WireGuard, and you make good points. WireGuard and IPSec are similar in some ways, as the core code is in the kernel and as such all addresses are manually assigned as you mention. IPSec has bolted on much "stuff" as time has gone on, Extended Authentication (XAUTH) and Mode Configuration (MODE-CFG) to support dynamic pools for client configuration via a user space daemon. I have tested a commercial VPN provider Mullvad.net which supports WireGuard VPN "clients" where their "server" end automatically assigns a 10.0.0.0/8 private /32 address for each client. A static one-time configuration, works very nicely. Another approach would be to standardize on a IPv6 ULA "fd" address scheme for the local client address, possibly generated from a hash of the PublicKey. For site-to-site AstLinux constellations, there is no better VPN solution than WireGuard, IMHO. It will take some time for Android, iOS, ChromeOS, etc. to provide WireGuard solutions, but Android is almost there now, both user-space and kernel implementations. Lonnie On Dec 4, 2017, at 9:02 AM, David Kerr <Da...@Ke...> wrote: > Having played with Wireguard I think that it is very good underlying technology to implement VPN. It seems to be very robust and tolerates roaming (client's IP address changing) very well. But there are missing pieces before it is ready for mainstream adoption. > > The biggest issue that I see is that client IP addresses (whether IPv4 or IPv6) needed to be managed manually.... if you have a dozen clients connecting in to the one server, each of these clients must have an IP address manually assigned and configured at the client, and the server needs to know what IP address was assigned and if there are any conflicts (two clients use the same IP address) then I guess the results are "undefined". Right now there is no way to have the server manage a pool of IP addresses and push out to the client a IP address when it connects, whether that IP is dynamically determined by the server or manually configured for each client on the server. Wireguard could never be deployed on a large scale without this. > > Managing IP addresses should not be a kernel task. So I suspect the raw VPN technology will get embedded into the kernel and solving IP address management will be left to some user space utility. I just don't know if it will require some supporting capability in the kernel or not. > > David > > > > On Sun, Dec 3, 2017 at 3:44 PM, Michael Knill <mic...@ip...> wrote: > Great thanks Lonnie. Im looking forward to it. Very cool! > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux List <ast...@li...> > Date: Monday, 4 December 2017 at 1:39 am > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] AstLinux Pre-Release: astlinux-1.3-3534-c5e366 > > Hi Michael, > > > Wow (WireGuard) looks super easy to set up. > > Indeed, the easiest VPN you ever have setup, particularly for site-to-stie scenarios routing networks across the VPN. > > > > So is it ready for production? > > I have had in production a remote AstLinux box (SIP / HTTPS) over WireGuard for a few weeks now ... works perfectly, never missed a beat, different ISP at each end. > > Officially, I would look for a 1.0.0 release and acceptance into the mainline Linux kernel as milestones indicating WireGuard's production-readyness ... should happen soon, but not yet. > > Definitely worth testing now. > > Lonnie > > > > On Dec 2, 2017, at 10:26 PM, Michael Knill <mic...@ip...> wrote: > > > Wow looks super easy to set up. So is it ready for production? > > > > Regards > > Michael Knill > > > > -----Original Message----- > > From: Lonnie Abelbeck <li...@lo...> > > Reply-To: AstLinux Developers Mailing List <ast...@li...> > > Date: Sunday, 3 December 2017 at 10:13 am > > To: AstLinux List <ast...@li...> > > Cc: AstLinux Developers Mailing List <ast...@li...> > > Subject: [Astlinux-devel] AstLinux Pre-Release: astlinux-1.3-3534-c5e366 > > > > Announcing Pre-Release Version: astlinux-1.3-3534-c5e366 > > > > Particularly notable is the addition of the WireGuard VPN. > > > > The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. > > > > -- WireGuard VPN, new package; an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography. > > http://doc.astlinux-project.org/userdoc:tt_wireguard_vpn > > > > -- Asterisk 13 version bump to 13.18.3 > > > > These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project. > > > > The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... > > > > AstLinux Project -> Development > > http://www.astlinux-project.org/dev.html > > > > While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems. > > > > If you should come across an issue, please report back here. > > > > AstLinux Team > > > ------------------------------------------------------------------------------ > 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.... |
|
From: Michael K. <li...@mk...> - 2017-12-04 15:32:45
|
> Am 04.12.2017 um 16:02 schrieb David Kerr <da...@ke...>: > > Having played with Wireguard I think that it is very good underlying technology to implement VPN. It seems to be very robust and tolerates roaming (client's IP address changing) very well. But there are missing pieces before it is ready for mainstream adoption. > > The biggest issue that I see is that client IP addresses (whether IPv4 or IPv6) needed to be managed manually.... if you have a dozen clients connecting in to the one server, each of these clients must have an IP address manually assigned and configured at the client, and the server needs to know what IP address was assigned and if there are any conflicts (two clients use the same IP address) then I guess the results are "undefined". Right now there is no way to have the server manage a pool of IP addresses and push out to the client a IP address when it connects, whether that IP is dynamically determined by the server or manually configured for each client on the server. Wireguard could never be deployed on a large scale without this. Hi David, good point. It would be interesting in which way the commercial VPN providers, who use WireGuard, are handling this issue. Lonnie has tested Mullvad recently, maybe he can comment. https://www.azirevpn.com/wireguard https://www.mullvad.net/guides/wireguard-and-mullvad-vpn/ > Managing IP addresses should not be a kernel task. So I suspect the raw VPN technology will get embedded into the kernel and solving IP address management will be left to some user space utility. I just don't know if it will require some supporting capability in the kernel or not. > > David > > > > On Sun, Dec 3, 2017 at 3:44 PM, Michael Knill <mic...@ip...> wrote: > Great thanks Lonnie. Im looking forward to it. Very cool! > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux List <ast...@li...> > Date: Monday, 4 December 2017 at 1:39 am > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] AstLinux Pre-Release: astlinux-1.3-3534-c5e366 > > Hi Michael, > > > Wow (WireGuard) looks super easy to set up. > > Indeed, the easiest VPN you ever have setup, particularly for site-to-stie scenarios routing networks across the VPN. > > > > So is it ready for production? > > I have had in production a remote AstLinux box (SIP / HTTPS) over WireGuard for a few weeks now ... works perfectly, never missed a beat, different ISP at each end. > > Officially, I would look for a 1.0.0 release and acceptance into the mainline Linux kernel as milestones indicating WireGuard's production-readyness ... should happen soon, but not yet. > > Definitely worth testing now. > > Lonnie > > > > On Dec 2, 2017, at 10:26 PM, Michael Knill <mic...@ip...> wrote: > > > Wow looks super easy to set up. So is it ready for production? > > > > Regards > > Michael Knill > > > > -----Original Message----- > > From: Lonnie Abelbeck <li...@lo...> > > Reply-To: AstLinux Developers Mailing List <ast...@li...> > > Date: Sunday, 3 December 2017 at 10:13 am > > To: AstLinux List <ast...@li...> > > Cc: AstLinux Developers Mailing List <ast...@li...> > > Subject: [Astlinux-devel] AstLinux Pre-Release: astlinux-1.3-3534-c5e366 > > > > Announcing Pre-Release Version: astlinux-1.3-3534-c5e366 > > > > Particularly notable is the addition of the WireGuard VPN. > > > > The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. > > > > -- WireGuard VPN, new package; an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography. > > http://doc.astlinux-project.org/userdoc:tt_wireguard_vpn > > > > -- Asterisk 13 version bump to 13.18.3 > > > > These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project. > > > > The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... > > > > AstLinux Project -> Development > > http://www.astlinux-project.org/dev.html > > > > While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems. > > > > If you should come across an issue, please report back here. > > > > AstLinux Team Michael http://www.mksolutions.info |
|
From: David K. <da...@ke...> - 2017-12-04 15:03:08
|
Having played with Wireguard I think that it is very good underlying technology to implement VPN. It seems to be very robust and tolerates roaming (client's IP address changing) very well. But there are missing pieces before it is ready for mainstream adoption. The biggest issue that I see is that client IP addresses (whether IPv4 or IPv6) needed to be managed manually.... if you have a dozen clients connecting in to the one server, each of these clients must have an IP address manually assigned and configured at the client, and the server needs to know what IP address was assigned and if there are any conflicts (two clients use the same IP address) then I guess the results are "undefined". Right now there is no way to have the server manage a pool of IP addresses and push out to the client a IP address when it connects, whether that IP is dynamically determined by the server or manually configured for each client on the server. Wireguard could never be deployed on a large scale without this. Managing IP addresses should not be a kernel task. So I suspect the raw VPN technology will get embedded into the kernel and solving IP address management will be left to some user space utility. I just don't know if it will require some supporting capability in the kernel or not. David On Sun, Dec 3, 2017 at 3:44 PM, Michael Knill < mic...@ip...> wrote: > Great thanks Lonnie. Im looking forward to it. Very cool! > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux List <ast...@li...> > Date: Monday, 4 December 2017 at 1:39 am > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] AstLinux Pre-Release: > astlinux-1.3-3534-c5e366 > > Hi Michael, > > > Wow (WireGuard) looks super easy to set up. > > Indeed, the easiest VPN you ever have setup, particularly for site-to-stie > scenarios routing networks across the VPN. > > > > So is it ready for production? > > I have had in production a remote AstLinux box (SIP / HTTPS) over > WireGuard for a few weeks now ... works perfectly, never missed a beat, > different ISP at each end. > > Officially, I would look for a 1.0.0 release and acceptance into the > mainline Linux kernel as milestones indicating WireGuard's > production-readyness ... should happen soon, but not yet. > > Definitely worth testing now. > > Lonnie > > > > On Dec 2, 2017, at 10:26 PM, Michael Knill <michael.knill@ipcsolutions. > com.au> wrote: > > > Wow looks super easy to set up. So is it ready for production? > > > > Regards > > Michael Knill > > > > -----Original Message----- > > From: Lonnie Abelbeck <li...@lo...> > > Reply-To: AstLinux Developers Mailing List <astlinux-devel@lists. > sourceforge.net> > > Date: Sunday, 3 December 2017 at 10:13 am > > To: AstLinux List <ast...@li...> > > Cc: AstLinux Developers Mailing List <astlinux-devel@lists. > sourceforge.net> > > Subject: [Astlinux-devel] AstLinux Pre-Release: astlinux-1.3-3534-c5e366 > > > > Announcing Pre-Release Version: astlinux-1.3-3534-c5e366 > > > > Particularly notable is the addition of the WireGuard VPN. > > > > The AstLinux Team is regularly upgrading packages containing security > and bug fixes as well as adding new features of our own. > > > > -- WireGuard VPN, new package; an extremely simple yet fast and modern > VPN that utilizes state-of-the-art cryptography. > > http://doc.astlinux-project.org/userdoc:tt_wireguard_vpn > > > > -- Asterisk 13 version bump to 13.18.3 > > > > These pre-release images are for those who would like to take advantage > of the AstLinux development before the next official release, as well as > providing testing for the project. > > > > The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be > found under the "Development" tab of the AstLinux Project web site ... > > > > AstLinux Project -> Development > > http://www.astlinux-project.org/dev.html > > > > While these images are considered 'stable', the lack of testing will not > make these images suitable for critical production systems. > > > > If you should come across an issue, please report back here. > > > > AstLinux Team > > > ------------------------------------------------------------ > ------------------ > 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.... > |
|
From: Michael K. <mic...@ip...> - 2017-12-03 20:45:07
|
Great thanks Lonnie. Im looking forward to it. Very cool! Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux List <ast...@li...> Date: Monday, 4 December 2017 at 1:39 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] AstLinux Pre-Release: astlinux-1.3-3534-c5e366 Hi Michael, > Wow (WireGuard) looks super easy to set up. Indeed, the easiest VPN you ever have setup, particularly for site-to-stie scenarios routing networks across the VPN. > So is it ready for production? I have had in production a remote AstLinux box (SIP / HTTPS) over WireGuard for a few weeks now ... works perfectly, never missed a beat, different ISP at each end. Officially, I would look for a 1.0.0 release and acceptance into the mainline Linux kernel as milestones indicating WireGuard's production-readyness ... should happen soon, but not yet. Definitely worth testing now. Lonnie On Dec 2, 2017, at 10:26 PM, Michael Knill <mic...@ip...> wrote: > Wow looks super easy to set up. So is it ready for production? > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux Developers Mailing List <ast...@li...> > Date: Sunday, 3 December 2017 at 10:13 am > To: AstLinux List <ast...@li...> > Cc: AstLinux Developers Mailing List <ast...@li...> > Subject: [Astlinux-devel] AstLinux Pre-Release: astlinux-1.3-3534-c5e366 > > Announcing Pre-Release Version: astlinux-1.3-3534-c5e366 > > Particularly notable is the addition of the WireGuard VPN. > > The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. > > -- WireGuard VPN, new package; an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography. > http://doc.astlinux-project.org/userdoc:tt_wireguard_vpn > > -- Asterisk 13 version bump to 13.18.3 > > These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project. > > The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... > > AstLinux Project -> Development > http://www.astlinux-project.org/dev.html > > While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems. > > If you should come across an issue, please report back here. > > AstLinux Team ------------------------------------------------------------------------------ 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.... |
|
From: Lonnie A. <li...@lo...> - 2017-12-03 14:39:23
|
Hi Michael, > Wow (WireGuard) looks super easy to set up. Indeed, the easiest VPN you ever have setup, particularly for site-to-stie scenarios routing networks across the VPN. > So is it ready for production? I have had in production a remote AstLinux box (SIP / HTTPS) over WireGuard for a few weeks now ... works perfectly, never missed a beat, different ISP at each end. Officially, I would look for a 1.0.0 release and acceptance into the mainline Linux kernel as milestones indicating WireGuard's production-readyness ... should happen soon, but not yet. Definitely worth testing now. Lonnie On Dec 2, 2017, at 10:26 PM, Michael Knill <mic...@ip...> wrote: > Wow looks super easy to set up. So is it ready for production? > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux Developers Mailing List <ast...@li...> > Date: Sunday, 3 December 2017 at 10:13 am > To: AstLinux List <ast...@li...> > Cc: AstLinux Developers Mailing List <ast...@li...> > Subject: [Astlinux-devel] AstLinux Pre-Release: astlinux-1.3-3534-c5e366 > > Announcing Pre-Release Version: astlinux-1.3-3534-c5e366 > > Particularly notable is the addition of the WireGuard VPN. > > The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. > > -- WireGuard VPN, new package; an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography. > http://doc.astlinux-project.org/userdoc:tt_wireguard_vpn > > -- Asterisk 13 version bump to 13.18.3 > > These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project. > > The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... > > AstLinux Project -> Development > http://www.astlinux-project.org/dev.html > > While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems. > > If you should come across an issue, please report back here. > > AstLinux Team |
|
From: Michael K. <mic...@ip...> - 2017-12-03 04:26:29
|
Wow looks super easy to set up. So is it ready for production? Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux Developers Mailing List <ast...@li...> Date: Sunday, 3 December 2017 at 10:13 am To: AstLinux List <ast...@li...> Cc: AstLinux Developers Mailing List <ast...@li...> Subject: [Astlinux-devel] AstLinux Pre-Release: astlinux-1.3-3534-c5e366 Announcing Pre-Release Version: astlinux-1.3-3534-c5e366 Particularly notable is the addition of the WireGuard VPN. The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- WireGuard VPN, new package; an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography. http://doc.astlinux-project.org/userdoc:tt_wireguard_vpn -- Asterisk 13 version bump to 13.18.3 These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project. The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development http://www.astlinux-project.org/dev.html While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems. If you should come across an issue, please report back here. AstLinux Team ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2017-12-02 23:13:11
|
Announcing Pre-Release Version: astlinux-1.3-3534-c5e366 Particularly notable is the addition of the WireGuard VPN. The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- WireGuard VPN, new package; an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography. http://doc.astlinux-project.org/userdoc:tt_wireguard_vpn -- Asterisk 13 version bump to 13.18.3 These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project. The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development http://www.astlinux-project.org/dev.html While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems. If you should come across an issue, please report back here. AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2017-11-20 14:36:49
|
Stefan, A Virtual Machine is you friend. :-) Spin-up your favorite general distro, minimal as you like, and do gcc/g++ work there. If you want to create custom binaries for AstLinux, follow our development instructions: https://doc.astlinux-project.org/devdoc:documentation or, if you are careful, you can copy over glibc binaries built elsewhere in some cases. For a simple example where you can include a local .c file and compile, it, take a look at the Buildroot "makedevs" package: https://github.com/astlinux-project/astlinux/tree/master/package/makedevs AstLinux is an appliance, not a development environment. Just as a point of reference the total uncompressed AstLinux image is around 100MB, the gcc/g++ x86_64 toolchain used to create it is over 150MB. Lonnie On Nov 20, 2017, at 7:46 AM, Stefan Ulm <s....@di...> wrote: > Hello all, > > is there any possibility to install gcc/g++ in astlinux to run it on the machine. I would like to develop and run directly on running astinux device. > > > > Best regards > > Stefan Ulm > Technical Department | Research & Development > ste...@di... > > > > <image001.png> > > DIVUS Headquarters Pillhof 51 . I-39057 Eppan (Südtirol) . Tel. +39 0471 633 662 . Fax. +39 0471 631 829 > DIVUS Showroom Deutschland Leinfelder Str. 64 . D-70771 Leinfelden-Echterdingen . Tel. +49(0)711 5087 5923 > www.divus.eu . Privacy: http://www.divus.eu/media/DivusPrivacy.pdf |
|
From: Stefan U. <s....@di...> - 2017-11-20 14:01:29
|
Hello all,
is there any possibility to install gcc/g++ in astlinux to run it on the machine. I would like to develop and run directly on running astinux device.
Best regards
Stefan Ulm
Technical Department | Research & Development
ste...@di...<mailto:mo...@di...>
[cid:image001.png@01D3620E.6638D0A0]
DIVUS Headquarters Pillhof 51 . I-39057 Eppan (Südtirol) . Tel. +39 0471 633 662 . Fax. +39 0471 631 829
DIVUS Showroom Deutschland Leinfelder Str. 64 . D-70771 Leinfelden-Echterdingen . Tel. +49(0)711 5087 5923
www.divus.eu<http://www.divus.eu/> . Privacy: http://www.divus.eu/media/DivusPrivacy.pdf
|
|
From: Michael K. <mic...@ip...> - 2017-11-16 22:48:11
|
Yes like object groups in Cisco ASA where you can group hosts into a single rule. That would be nice. Regards Michael Knill -----Original Message----- From: Michael Keuter <li...@mk...> Reply-To: AstLinux List <ast...@li...> Date: Friday, 17 November 2017 at 9:18 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Multiple hosts into firewall > Am 16.11.2017 um 22:46 schrieb Lonnie Abelbeck <li...@lo...>: > > Michael, > > The Firewall tab, Source: and Destination: fields should contain a single IP address or CIDR, or 0/0 for Any Host. > > If you can group a range of IP addresses into a single CIDR, that would be ideal. > > Lonnie Other firewalls use new entities where they group stuff together, and then use those entity name in the rules (for e.g. naming multiple ports to "sip-ports", I know we could use multiple ports, as below). > On Nov 16, 2017, at 3:33 PM, Michael Knill <mic...@ip...> wrote: > >> Hi sorry a dumb question. >> I know you can put multiple hosts into the firewall tab e.g. p1,p2,p3-p4 but I assume you cant put in multiple IP addresses and/or ranges? You meant "ports" instead of "hosts" right? >> Regards >> Michael Knill 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.... |
|
From: Michael K. <li...@mk...> - 2017-11-16 22:17:58
|
> Am 16.11.2017 um 22:46 schrieb Lonnie Abelbeck <li...@lo...>: > > Michael, > > The Firewall tab, Source: and Destination: fields should contain a single IP address or CIDR, or 0/0 for Any Host. > > If you can group a range of IP addresses into a single CIDR, that would be ideal. > > Lonnie Other firewalls use new entities where they group stuff together, and then use those entity name in the rules (for e.g. naming multiple ports to "sip-ports", I know we could use multiple ports, as below). > On Nov 16, 2017, at 3:33 PM, Michael Knill <mic...@ip...> wrote: > >> Hi sorry a dumb question. >> I know you can put multiple hosts into the firewall tab e.g. p1,p2,p3-p4 but I assume you cant put in multiple IP addresses and/or ranges? You meant "ports" instead of "hosts" right? >> Regards >> Michael Knill Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2017-11-16 21:54:08
|
Thanks Lonnie I suspected so. Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux List <ast...@li...> Date: Friday, 17 November 2017 at 8:46 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Multiple hosts into firewall Michael, The Firewall tab, Source: and Destination: fields should contain a single IP address or CIDR, or 0/0 for Any Host. If you can group a range of IP addresses into a single CIDR, that would be ideal. Lonnie On Nov 16, 2017, at 3:33 PM, Michael Knill <mic...@ip...> wrote: > Hi sorry a dumb question. > I know you can put multiple hosts into the firewall tab e.g. p1,p2,p3-p4 but I assume you cant put in multiple IP addresses and/or ranges? > > 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.... |
|
From: Lonnie A. <li...@lo...> - 2017-11-16 21:46:20
|
Michael, The Firewall tab, Source: and Destination: fields should contain a single IP address or CIDR, or 0/0 for Any Host. If you can group a range of IP addresses into a single CIDR, that would be ideal. Lonnie On Nov 16, 2017, at 3:33 PM, Michael Knill <mic...@ip...> wrote: > Hi sorry a dumb question. > I know you can put multiple hosts into the firewall tab e.g. p1,p2,p3-p4 but I assume you cant put in multiple IP addresses and/or ranges? > > 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.... |
|
From: Michael K. <mic...@ip...> - 2017-11-16 21:34:04
|
Hi sorry a dumb question. I know you can put multiple hosts into the firewall tab e.g. p1,p2,p3-p4 but I assume you cant put in multiple IP addresses and/or ranges? Regards Michael Knill |
|
From: Michael K. <mic...@ip...> - 2017-11-16 20:43:40
|
Hi Group Gosh I have had some issues with Asterisk 13. Just found another bug affecting me; ASTERISK-25676. This was causing one way voice for calls to some numbers. Fixed in 13.17 so I highly recommend that you don't use 13.15 which is in 1.2.10. Im trying to find a workaround so I don't need to upgrade all my sites AGAIN! Unfortunately I have one site I cant upgrade as my queue crash bug is not fixed yet. Looks like I wont be going to the next LTS release until its practically EoL ☹ Regards Michael Knill |
|
From: Lonnie A. <li...@lo...> - 2017-11-14 15:13:38
|
Announcing Pre-Release Version: astlinux-1.3-3510-3ca6e3 Particularly notable is the addition of the WireGuard VPN. WireGuard is relatively new, but its efficiency and simple configuration make it a perfect match for AstLinux and distributed SIP voice networks. While WireGuard is still considered "experimental" an official release should be coming soon, and fully usable for testing now. Many Linux projects support WireGuard. It would make sense for SIP trunk providers to offer there services over WireGuard ... seems like a great solution to securely encrypt SIP, work around NAT, and keep external SIP ports from being exposed. Currently there is little support for WireGuard other than for Linux, since it was first implemented as a Linux kernel module. But several user-space implementations are actively being worked on. A special thanks to Michael Keuter for suggesting WireGuard and testing. The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- WireGuard VPN, new package; an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography. http://doc.astlinux-project.org/userdoc:tt_wireguard_vpn -- Asterisk 13 version bump to 13.18.2 If you need a VM ISO, privately email me, or install the 1.3.1 ISO and upgrade to astlinux-1.3-3510-3ca6e3 . These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project. The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development http://www.astlinux-project.org/dev.html While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems. If you should come across an issue, please report back here. AstLinux Team |
|
From: Darrick H. <dha...@dj...> - 2017-11-12 13:06:48
|
Bart, Yes, if both /mnt/kd/rc.conf and the series of files under /mnt/kd/rc.conf.d/ both exist, the series of files under /mnt/kd/rc.conf.d/ take precedence and the /mnt/kd/rc.conf file is ignored. Darrick ________________________________ From: Bart Teekman [bar...@gm...] Sent: Saturday, November 11, 2017 3:16 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] Redirecting all AstLinux logs to an external syslog server Hi, Brilliant! I found the rc.conf file in /mnt/kd and added my syslog server: ## Remote Syslog Config ## The machine below will receive all logging messages from this machine via ## syslog's remote logging features. SYSLOGHOST="192.168.1.10" I tried it with, and without, quotes. Rebooting between attempts. But nothing is reaching the syslog server. Then I got your update, and edited the user.conf file via the GUI. It must be the right one because the system says: File opened for editing: /mnt/kd/rc.conf.d/user.conf I added the line: ### user.conf - start ### ### ### Advanced Configuration: User System Variables ### ### Define variables here that are not otherwise set in the Network tab. ### ### Variables defined here will override any value set elsewhere. ### ### SYSLOGHOST="192.168.1.10" ### user.conf - end ### Then I restarted syslogd which all went without a hitch: Nov 12 10:06:16 ASTERISK auth.info<http://auth.info> login[733]: root login on 'pts/0' Nov 12 10:06:56 ASTERISK syslog.info<http://syslog.info> syslogd exiting Nov 12 10:06:57 ASTERISK syslog.info<http://syslog.info> syslogd started: BusyBox v1.19.4 Still nothing on the remote syslog server. So I tried a reboot (just to be sure). And then she kicked into life! Thank you so much!! Kind regards, Bart. On 12 November 2017 at 09:57, Lonnie Abelbeck <li...@lo...<mailto:li...@lo...>> wrote: Bart, Just to be clear, add SYSLOGHOST="10.1.2.3" to your /mnt/kd/rc.conf.d/user.conf file. service netsyslogd stop gen-rc-conf service netsyslogd init Lonnie On Nov 11, 2017, at 2:33 PM, Lonnie Abelbeck <li...@lo...<mailto:li...@lo...>> wrote: > Hi Bart, > > The place to discover hidden features is in the /stat/etc/rc.conf file, or using the web interface ... > > System tab -> View System Files: [ Default System Variables ] click { View Selected File } > -- > ## Remote Syslog Config > ## The machine below will receive all logging messages from this machine via > ## syslog's remote logging features. > #SYSLOGHOST="" > -- > > I can't say I have ever used it, and keep in mind the syslog stream is not encrypted. > > Lonnie > > > > On Nov 11, 2017, at 2:06 PM, Bart Teekman <bar...@gm...<mailto:bar...@gm...>> wrote: > >> 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. > > > > ------------------------------------------------------------------------------ > 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...<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...>. > > ------------------------------------------------------------------------------ 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...<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: Bart T. <bar...@gm...> - 2017-11-11 21:16:33
|
Hi,
Brilliant!
I found the rc.conf file in /mnt/kd and added my syslog server:
## Remote Syslog Config
## The machine below will receive all logging messages from this machine via
## syslog's remote logging features.
SYSLOGHOST="192.168.1.10"
I tried it with, and without, quotes. Rebooting between attempts. But
nothing is reaching the syslog server.
Then I got your update, and edited the user.conf file via the GUI. It must
be the right one because the system says: File opened for editing:
/mnt/kd/rc.conf.d/user.conf
I added the line:
### user.conf - start ###
###
### Advanced Configuration: User System Variables
###
### Define variables here that are not otherwise set in the Network tab.
###
### Variables defined here will override any value set elsewhere.
###
###
SYSLOGHOST="192.168.1.10"
### user.conf - end ###
Then I restarted syslogd which all went without a hitch:
Nov 12 10:06:16 ASTERISK auth.info login[733]: root login on 'pts/0'
Nov 12 10:06:56 ASTERISK syslog.info syslogd exiting
Nov 12 10:06:57 ASTERISK syslog.info syslogd started: BusyBox v1.19.4
Still nothing on the remote syslog server. So I tried a reboot (just to be
sure).
And then she kicked into life!
Thank you so much!!
Kind regards,
Bart.
On 12 November 2017 at 09:57, Lonnie Abelbeck <li...@lo...>
wrote:
> Bart,
>
> Just to be clear, add
>
> SYSLOGHOST="10.1.2.3"
>
> to your /mnt/kd/rc.conf.d/user.conf file.
>
> service netsyslogd stop
> gen-rc-conf
> service netsyslogd init
>
>
> Lonnie
>
>
> On Nov 11, 2017, at 2:33 PM, Lonnie Abelbeck <li...@lo...>
> wrote:
>
> > Hi Bart,
> >
> > The place to discover hidden features is in the /stat/etc/rc.conf file,
> or using the web interface ...
> >
> > System tab -> View System Files: [ Default System Variables ] click {
> View Selected File }
> > --
> > ## Remote Syslog Config
> > ## The machine below will receive all logging messages from this machine
> via
> > ## syslog's remote logging features.
> > #SYSLOGHOST=""
> > --
> >
> > I can't say I have ever used it, and keep in mind the syslog stream is
> not encrypted.
> >
> > Lonnie
> >
> >
> >
> > On Nov 11, 2017, at 2:06 PM, Bart Teekman <bar...@gm...>
> wrote:
> >
> >> 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.
> >
> >
> >
> > ------------------------------------------------------------
> ------------------
> > 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....
>
|
|
From: Lonnie A. <li...@lo...> - 2017-11-11 20:57:14
|
Bart,
Just to be clear, add
SYSLOGHOST="10.1.2.3"
to your /mnt/kd/rc.conf.d/user.conf file.
service netsyslogd stop
gen-rc-conf
service netsyslogd init
Lonnie
On Nov 11, 2017, at 2:33 PM, Lonnie Abelbeck <li...@lo...> wrote:
> Hi Bart,
>
> The place to discover hidden features is in the /stat/etc/rc.conf file, or using the web interface ...
>
> System tab -> View System Files: [ Default System Variables ] click { View Selected File }
> --
> ## Remote Syslog Config
> ## The machine below will receive all logging messages from this machine via
> ## syslog's remote logging features.
> #SYSLOGHOST=""
> --
>
> I can't say I have ever used it, and keep in mind the syslog stream is not encrypted.
>
> Lonnie
>
>
>
> On Nov 11, 2017, at 2:06 PM, Bart Teekman <bar...@gm...> wrote:
>
>> 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.
>
>
>
> ------------------------------------------------------------------------------
> 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....
>
>
|
|
From: Lonnie A. <li...@lo...> - 2017-11-11 20:33:43
|
Hi Bart,
The place to discover hidden features is in the /stat/etc/rc.conf file, or using the web interface ...
System tab -> View System Files: [ Default System Variables ] click { View Selected File }
--
## Remote Syslog Config
## The machine below will receive all logging messages from this machine via
## syslog's remote logging features.
#SYSLOGHOST=""
--
I can't say I have ever used it, and keep in mind the syslog stream is not encrypted.
Lonnie
On Nov 11, 2017, at 2:06 PM, Bart Teekman <bar...@gm...> wrote:
> 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.
|
63 messages has been excluded from this view by a project administrator.
