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: Lonnie A. <li...@lo...> - 2020-08-28 16:50:42
|
Hi DAHDI card users, For anyone out there that uses a DAHDI compatible card, please take note. DAHDI version 3+ removes support for a bunch of cards. Seemingly PCI (not PCIe) cards. Notable, these oldies: wctdm: Digium TDM400P: up to 4 analog ports wcfxo: X100P, similar and clones. A simple single-port FXO card and wctdm24xxp: Digium TDM800P/AEX800: up to 8 analog ports TDM410P/AEX410 up to 4 analog ports Complete list of changes here: https://github.com/asterisk/dahdi-linux/commit/f47c9bd9285d4c9d15f47a4cfbd2a00a5a1eaa13 Does anyone use removed card drivers ? ie, does anyone have a user.conf containing: DAHDIMODS="wctdm24xxp", or DAHDIMODS="wcfxo" or DAHDIMODS="wctdm" ? Granted PCI card slots are hard to come by today. Lonnie |
|
From: Lonnie A. <li...@lo...> - 2020-08-28 15:44:57
|
Announcing Pre-Release Version: astlinux-1.4-4801-574be0 The next AstLinux version will be 1.4.0, most notably switching to the Linux kernel 4.19.x LTS series. Much testing needs to be done, if you have a non-standard box (HP Thin Client, unique China box, etc.) we would encourage you to test. Be certain you have console access, using the CLI to upgrade to the pre-release version. Possibly type "dmesg -H" to view the logs and note anything weird, particularly Broadcom or Realtek NIC related. Revert back to your previous image with "upgrade-run-image revert" and "kernel-reboot" CLI commands. While we do not suggest this specific pre-release is production ready, some of the developers are using it in production. ** IMPORTANT NOTICE -- DAHDI is now version 3.1.0 to support the new kernel, as such previous DAHDI_HFCS and RHINO drivers are no longer supported. ** The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Linux Kernel 4.19.140 (major version bump) -- WireGuard VPN, module 1.0.20200729 (version bump), tools 1.0.20200820 (version bump) -- iproute2 (ip, tc, bridge, etc.) version bump to 4.20.0 -- iptables, version bump to 1.8.4 -- DAHDI, dahdi-linux 3.1.0 (version bump) and dahdi-tools 3.1.0 (version bump) -- Fossil, version bump to 2.10.2, security fixes -- Complete Pre-Release ChangeLog: https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html AstLinux Team |
|
From: Craig L. <cra...@gm...> - 2020-08-26 23:02:08
|
Thanks to all of those who responded. An out of band suggestion to use IP addresses in sip.conf seems to have resolved the issue. Which likely points to, I suppose, a DNS issue. But for now I have what I need. Thanks again. Craig On Wed, 26 Aug 2020 at 09:31, <ast...@li...> wrote: > Send Astlinux-users mailing list submissions to > ast...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/astlinux-users > or, via email, send a message with subject or body 'help' to > ast...@li... > > You can reach the person managing the list at > ast...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Astlinux-users digest..." > > > Today's Topics: > > 1. Re: Registration Timed Out (John Novack) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 25 Aug 2020 22:02:20 -0400 > From: John Novack <jn...@co...> > To: cra...@gm..., AstLinux Users Mailing List > <ast...@li...> > Subject: Re: [Astlinux-users] Registration Timed Out > Message-ID: <041...@co...> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > I have used voip.ms for several years, and support several others who do > also, both with plain vanilla Asterisk and AstLinux > > We all use the IAX protocol, and never have had such issues. All of ours > are in the U.S.? Doubtful it is voip.ms. > > One question though - Some time ago, you should have received notice to > change your configuration > > Toronto needs to be changed to toronto and a number. This was more than a > year ago, and they warned everyone there could be issues in the near future. > > You might want to do that first, and if problems then continue, contact > voip.ms They have always been very helpful, even with dumb user mistakes! > > John Novack > > > > > Craig Law wrote: > > Hi - first time posting and hopefully?this is the right place for this > type of question. > > > > I have a?fairly?simple setup for home use and have been running Astlinux > for many years. About 8 months ago I switched VOIP providers. Ever since > switching providers I continually get time outs to my provider. They > typically resolve themselves within a few minutes, but it has been a few > hours on another occasion. I'm trying to understand if this is a 'me' > problem (ie. my Astlinux/Asterisk setup) or a 'them' problem. > > > > Here's a snippet from?/var/log/messages (1234567 not my actual username) > : > > > > Aug 24 22:10:28 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE!? > Last qualify: 48 > > Aug 24 22:12:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #2) > > Aug 24 22:12:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #3) > > Aug 24 22:12:43 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #4) > > Aug 24 22:13:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #5) > > Aug 24 22:13:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #6) > > Aug 24 22:13:43 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #7) > > Aug 24 22:14:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #8) > > Aug 24 22:14:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #9) > > Aug 24 22:14:43 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #10) > > Aug 24 22:15:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #11) > > Aug 24 22:15:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #12) > > Aug 24 22:15:38 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now > Reachable. (24ms / 2500ms) > > Aug 25 10:45:08 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE!? > Last qualify: 19 > > Aug 25 10:45:18 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now > Reachable. (18ms / 2500ms) > > Aug 25 15:49:54 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE!? > Last qualify: 18 > > Aug 25 15:50:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #2) > > Aug 25 15:50:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #3) > > Aug 25 15:50:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #4) > > Aug 25 15:51:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #5) > > Aug 25 15:51:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #6) > > Aug 25 15:51:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #7) > > Aug 25 15:52:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #8) > > Aug 25 15:52:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #9) > > Aug 25 15:52:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #10) > > Aug 25 15:53:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #11) > > Aug 25 15:53:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #12) > > Aug 25 15:53:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #13) > > Aug 25 15:54:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:15981 in sip_reg_timeout: ? ?-- Registration for ' > 12...@to... <mailto:12...@to...>' timed out, > trying again (Attempt #15) > > Aug 25 15:54:39 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE!? > Last qualify: 4796 > > Aug 25 15:55:33 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now > Reachable. (47ms / 2500ms) > > Aug 25 16:41:41 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Lagged. > (4027ms / 2500ms) > > Aug 25 16:41:51 pbx local0.notice asterisk[1366]: NOTICE[1520]: > chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now > Reachable. (19ms / 2500ms) > > > > Any help, suggestions or comments welcome, > > Craig > > > > > > > > > > _______________________________________________ > > 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.... > > -- > Dog is my Co-Pilot > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > > ------------------------------ > > End of Astlinux-users Digest, Vol 168, Issue 6 > ********************************************** > |
|
From: John N. <jn...@co...> - 2020-08-26 02:02:32
|
I have used voip.ms for several years, and support several others who do also, both with plain vanilla Asterisk and AstLinux We all use the IAX protocol, and never have had such issues. All of ours are in the U.S. Doubtful it is voip.ms. One question though - Some time ago, you should have received notice to change your configuration Toronto needs to be changed to toronto and a number. This was more than a year ago, and they warned everyone there could be issues in the near future. You might want to do that first, and if problems then continue, contact voip.ms They have always been very helpful, even with dumb user mistakes! John Novack Craig Law wrote: > Hi - first time posting and hopefully this is the right place for this type of question. > > I have a fairly simple setup for home use and have been running Astlinux for many years. About 8 months ago I switched VOIP providers. Ever since switching providers I continually get time outs to my provider. They typically resolve themselves within a few minutes, but it has been a few hours on another occasion. I'm trying to understand if this is a 'me' problem (ie. my Astlinux/Asterisk setup) or a 'them' problem. > > Here's a snippet from /var/log/messages (1234567 not my actual username) : > > Aug 24 22:10:28 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE! Last qualify: 48 > Aug 24 22:12:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #2) > Aug 24 22:12:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #3) > Aug 24 22:12:43 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #4) > Aug 24 22:13:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #5) > Aug 24 22:13:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #6) > Aug 24 22:13:43 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #7) > Aug 24 22:14:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #8) > Aug 24 22:14:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #9) > Aug 24 22:14:43 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #10) > Aug 24 22:15:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #11) > Aug 24 22:15:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #12) > Aug 24 22:15:38 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Reachable. (24ms / 2500ms) > Aug 25 10:45:08 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE! Last qualify: 19 > Aug 25 10:45:18 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Reachable. (18ms / 2500ms) > Aug 25 15:49:54 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE! Last qualify: 18 > Aug 25 15:50:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #2) > Aug 25 15:50:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #3) > Aug 25 15:50:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #4) > Aug 25 15:51:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #5) > Aug 25 15:51:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #6) > Aug 25 15:51:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #7) > Aug 25 15:52:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #8) > Aug 25 15:52:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #9) > Aug 25 15:52:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #10) > Aug 25 15:53:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #11) > Aug 25 15:53:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #12) > Aug 25 15:53:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #13) > Aug 25 15:54:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to... <mailto:12...@to...>' timed out, trying again (Attempt #15) > Aug 25 15:54:39 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE! Last qualify: 4796 > Aug 25 15:55:33 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Reachable. (47ms / 2500ms) > Aug 25 16:41:41 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Lagged. (4027ms / 2500ms) > Aug 25 16:41:51 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Reachable. (19ms / 2500ms) > > Any help, suggestions or comments welcome, > Craig > > > > > _______________________________________________ > 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.... -- Dog is my Co-Pilot |
|
From: Michael K. <mic...@ip...> - 2020-08-26 01:22:36
|
It looks more like a network problem to me, especially if you are getting lags. I would try some continuous pings to toronto.voip.ms Regards Michael Knill From: Craig Law <cra...@gm...> Reply to: "cra...@gm..." <cra...@gm...>, AstLinux List <ast...@li...> Date: Wednesday, 26 August 2020 at 11:01 am To: AstLinux List <ast...@li...> Subject: [Astlinux-users] Registration Timed Out Hi - first time posting and hopefully this is the right place for this type of question. I have a fairly simple setup for home use and have been running Astlinux for many years. About 8 months ago I switched VOIP providers. Ever since switching providers I continually get time outs to my provider. They typically resolve themselves within a few minutes, but it has been a few hours on another occasion. I'm trying to understand if this is a 'me' problem (ie. my Astlinux/Asterisk setup) or a 'them' problem. Here's a snippet from /var/log/messages (1234567 not my actual username) : Aug 24 22:10:28 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE! Last qualify: 48 Aug 24 22:12:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #2) Aug 24 22:12:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #3) Aug 24 22:12:43 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #4) Aug 24 22:13:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #5) Aug 24 22:13:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #6) Aug 24 22:13:43 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #7) Aug 24 22:14:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #8) Aug 24 22:14:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #9) Aug 24 22:14:43 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #10) Aug 24 22:15:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #11) Aug 24 22:15:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #12) Aug 24 22:15:38 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Reachable. (24ms / 2500ms) Aug 25 10:45:08 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE! Last qualify: 19 Aug 25 10:45:18 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Reachable. (18ms / 2500ms) Aug 25 15:49:54 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE! Last qualify: 18 Aug 25 15:50:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #2) Aug 25 15:50:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #3) Aug 25 15:50:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #4) Aug 25 15:51:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #5) Aug 25 15:51:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #6) Aug 25 15:51:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #7) Aug 25 15:52:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #8) Aug 25 15:52:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #9) Aug 25 15:52:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #10) Aug 25 15:53:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #11) Aug 25 15:53:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #12) Aug 25 15:53:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #13) Aug 25 15:54:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for '12...@to...<mailto:12...@to...>' timed out, trying again (Attempt #15) Aug 25 15:54:39 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE! Last qualify: 4796 Aug 25 15:55:33 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Reachable. (47ms / 2500ms) Aug 25 16:41:41 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Lagged. (4027ms / 2500ms) Aug 25 16:41:51 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Reachable. (19ms / 2500ms) Any help, suggestions or comments welcome, Craig |
|
From: Craig L. <cra...@gm...> - 2020-08-26 01:01:35
|
Hi - first time posting and hopefully this is the right place for this type of question. I have a fairly simple setup for home use and have been running Astlinux for many years. About 8 months ago I switched VOIP providers. Ever since switching providers I continually get time outs to my provider. They typically resolve themselves within a few minutes, but it has been a few hours on another occasion. I'm trying to understand if this is a 'me' problem (ie. my Astlinux/Asterisk setup) or a 'them' problem. Here's a snippet from /var/log/messages (1234567 not my actual username) : Aug 24 22:10:28 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE! Last qualify: 48 Aug 24 22:12:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #2) Aug 24 22:12:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #3) Aug 24 22:12:43 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #4) Aug 24 22:13:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #5) Aug 24 22:13:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #6) Aug 24 22:13:43 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #7) Aug 24 22:14:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #8) Aug 24 22:14:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #9) Aug 24 22:14:43 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #10) Aug 24 22:15:03 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #11) Aug 24 22:15:23 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #12) Aug 24 22:15:38 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Reachable. (24ms / 2500ms) Aug 25 10:45:08 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE! Last qualify: 19 Aug 25 10:45:18 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Reachable. (18ms / 2500ms) Aug 25 15:49:54 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE! Last qualify: 18 Aug 25 15:50:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #2) Aug 25 15:50:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #3) Aug 25 15:50:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #4) Aug 25 15:51:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #5) Aug 25 15:51:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #6) Aug 25 15:51:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #7) Aug 25 15:52:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #8) Aug 25 15:52:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #9) Aug 25 15:52:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #10) Aug 25 15:53:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #11) Aug 25 15:53:36 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #12) Aug 25 15:53:56 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #13) Aug 25 15:54:16 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:15981 in sip_reg_timeout: -- Registration for ' 12...@to...' timed out, trying again (Attempt #15) Aug 25 15:54:39 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:30327 in sip_poke_noanswer: Peer 'voipms' is now UNREACHABLE! Last qualify: 4796 Aug 25 15:55:33 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Reachable. (47ms / 2500ms) Aug 25 16:41:41 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Lagged. (4027ms / 2500ms) Aug 25 16:41:51 pbx local0.notice asterisk[1366]: NOTICE[1520]: chan_sip.c:24777 in handle_response_peerpoke: Peer 'voipms' is now Reachable. (19ms / 2500ms) Any help, suggestions or comments welcome, Craig |
|
From: Michael K. <mic...@ip...> - 2020-08-24 06:58:11
|
Hi Group I have this box out in production and it seems to be working fine. This is arguably a better box for Astlinux than the Q190G4N-S07 as it does not have the Wifi holes/daughter board and is therefore a bit smaller and cheaper. Regards Michael Knill |
|
From: Michael K. <mic...@ip...> - 2020-08-23 23:18:58
|
Ah thanks Lonnie. I think I might have read it once but it didn't cross my mind.
I probably need to enable it somewhere too on the terminating device.
Regards
Michael Knill
On 24/8/20, 9:00 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Michael,
Remember if IPsec NAT traversal is enabled, UDP 4500 is used.
4500/udp - NAT traversal
Lonnie
> On Aug 23, 2020, at 5:20 PM, Michael Knill <mic...@ip...> wrote:
>
> Hi Group
>
> I don't think I'm doing this correctly and its not working. And yes I realise that Astlinux can terminate IPsec but this is easier (if it works) as the device is already configured.
> Here is what I am doing:
> NAT EXT->DMZ UDP 0/0 500 Dest: 192.168.200.2
> Pass EXT->DMZ ESP 0/0 Dest: 192.168.200.2
> Pass EXT->DMZ AH 0/0 Dest: 192.168.200.2
> Default Policy for DMZ to EXT: Pass DMZ->EXT
>
> Thanks so much.
>
> Regards
> Michael Knill
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2020-08-23 23:00:16
|
Michael, Remember if IPsec NAT traversal is enabled, UDP 4500 is used. 4500/udp - NAT traversal Lonnie > On Aug 23, 2020, at 5:20 PM, Michael Knill <mic...@ip...> wrote: > > Hi Group > > I don't think I'm doing this correctly and its not working. And yes I realise that Astlinux can terminate IPsec but this is easier (if it works) as the device is already configured. > Here is what I am doing: > NAT EXT->DMZ UDP 0/0 500 Dest: 192.168.200.2 > Pass EXT->DMZ ESP 0/0 Dest: 192.168.200.2 > Pass EXT->DMZ AH 0/0 Dest: 192.168.200.2 > Default Policy for DMZ to EXT: Pass DMZ->EXT > > Thanks so much. > > Regards > Michael Knill > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2020-08-23 22:50:03
|
Whoops just thinking about it, should it be NAT EXT->DMZ for all items. I will try. Regards Michael Knill From: Michael Knill <mic...@ip...> Reply to: AstLinux List <ast...@li...> Date: Monday, 24 August 2020 at 8:36 am To: AstLinux List <ast...@li...> Subject: [Astlinux-users] Forwarding IPsec traffic through Astlinux Hi Group I don't think I'm doing this correctly and its not working. And yes I realise that Astlinux can terminate IPsec but this is easier (if it works) as the device is already configured. Here is what I am doing: NAT EXT->DMZ UDP 0/0 500 Dest: 192.168.200.2 Pass EXT->DMZ ESP 0/0 Dest: 192.168.200.2 Pass EXT->DMZ AH 0/0 Dest: 192.168.200.2 Default Policy for DMZ to EXT: Pass DMZ->EXT Thanks so much. Regards Michael Knill |
|
From: Michael K. <mic...@ip...> - 2020-08-23 22:36:20
|
Hi Group I don't think I'm doing this correctly and its not working. And yes I realise that Astlinux can terminate IPsec but this is easier (if it works) as the device is already configured. Here is what I am doing: NAT EXT->DMZ UDP 0/0 500 Dest: 192.168.200.2 Pass EXT->DMZ ESP 0/0 Dest: 192.168.200.2 Pass EXT->DMZ AH 0/0 Dest: 192.168.200.2 Default Policy for DMZ to EXT: Pass DMZ->EXT Thanks so much. Regards Michael Knill |
|
From: Daryl R. <da...@is...> - 2020-08-20 16:24:04
|
Back in March of this year there was a request for a flashrom binary and Lonnie offered to provide the file. Is it possible to get that file please? -- Daryl Richards Isle Technical Services Inc. |
|
From: Dan R. <da...@ry...> - 2020-08-11 15:01:20
|
Brilliant! Thank you.Dan -------- Original message --------From: Lonnie Abelbeck <li...@lo...> Date: 8/11/20 9:47 AM (GMT-05:00) To: AstLinux Users Mailing List <ast...@li...> Subject: Re: [Astlinux-users] Announcing AstLinux Release: 1.3.10 Hi Dan,The /mnt/kd path is still read-write, as before.For those with a /dev/sda3 partition, the /mnt/kd path is a mountpoint to a read-write filesystem.For pre-existing systems without a /dev/sda3 partition a FUSE unionfs mount will support /mnt/kd as before. For future fresh installs, a /dev/sda3 partition will always be created where /mnt/kd is a mountpoint to a read-write filesystem.Let us know if you have any issues with the 1.3.10 upgrade.Dan, always great to hear from you.Lonnie> On Aug 11, 2020, at 7:52 AM, Dan Ryson <da...@ry...> wrote:> > Lonnie and All,> > The Highlights say, "To better secure the filesystem, now only '/etc' and '/stat' will be read-write over the read-only base firmware image."> > Does this mean that /mnt/kd will no longer be read-write? I have sngrep (as root) routinely saving pcaps in /mnt/kd/sngrep. Will I need to move this to /etc or /stat?> > As always, thanks for the ongoing development and guidance.> > Dan > > > On Sun, Jul 26, 2020 at 03:04 PM, Lonnie Abelbeck <li...@lo...> wrote:> Announcing AstLinux Release: 1.3.10> > More Info: AstLinux Project> https://www.astlinux-project.org/> > AstLinux 1.3.10 Highlights:> * Asterisk Versions: 13.29.2, 13.34.0, 16.11.1> * Upgrade to Linux Kernel 3.16.85, including the new x86_64 RUNNIX bootloader, security and bug fixes> Kernel config: Add NAMESPACES and CGROUPS for Linux Containers> * New toolchain: glibc 2.27, binutils 2.29.1, gcc 6.5.0, using crosstool-ng-1.24.0> * unionfs, move from old kernel unionfs to FUSE unionfs version 2.1> To better secure the filesystem, now only '/etc' and '/stat' will be read-write over the read-only base firmware image.> * lxc, new package, add support for guest Linux Containers. For example, run Pi-hole or the UniFi Controller.> * OpenSSL, version bump to 1.1.1g> * WireGuard VPN, version bump, module 1.0.20200712, tools 1.0.20200513> * OpenVPN, version bump to 2.4.9> * udev, now use eudev version 3.2.9> * zabbix, major version bump to 4.0.20, LTS series> * initial-setup, remove 'combined' partition format option, always use 'format separate'> * Asterisk '13se' (stable edition) version 13.29.2 is older than latest Asterisk 13.x version but more tested, built --without-pjproject> * Package upgrades providing important security and bug fixes> > Full ChangeLog:> https://raw.githubusercontent.com/astlinux-project/astlinux/1.3.10/docs/ChangeLog.txt> > All users are encouraged to upgrade.> > Previous Asterisk 11.x users are encouraged to switch to the new Asterisk '13se' (stable edition). Some configuration changes will be needed, though minimal.> > AstLinux Team> > _______________________________________________> Astlinux-users mailing list> Ast...@li...> https://lists.sourceforge.net/lists/listinfo/astlinux-users> > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr...._______________________________________________Astlinux-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/astlinux-usersDonations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2020-08-11 13:46:52
|
Hi Dan, The /mnt/kd path is still read-write, as before. For those with a /dev/sda3 partition, the /mnt/kd path is a mountpoint to a read-write filesystem. For pre-existing systems without a /dev/sda3 partition a FUSE unionfs mount will support /mnt/kd as before. For future fresh installs, a /dev/sda3 partition will always be created where /mnt/kd is a mountpoint to a read-write filesystem. Let us know if you have any issues with the 1.3.10 upgrade. Dan, always great to hear from you. Lonnie > On Aug 11, 2020, at 7:52 AM, Dan Ryson <da...@ry...> wrote: > > Lonnie and All, > > The Highlights say, "To better secure the filesystem, now only '/etc' and '/stat' will be read-write over the read-only base firmware image." > > Does this mean that /mnt/kd will no longer be read-write? I have sngrep (as root) routinely saving pcaps in /mnt/kd/sngrep. Will I need to move this to /etc or /stat? > > As always, thanks for the ongoing development and guidance. > > Dan > > > On Sun, Jul 26, 2020 at 03:04 PM, Lonnie Abelbeck <li...@lo...> wrote: > Announcing AstLinux Release: 1.3.10 > > More Info: AstLinux Project > https://www.astlinux-project.org/ > > AstLinux 1.3.10 Highlights: > * Asterisk Versions: 13.29.2, 13.34.0, 16.11.1 > * Upgrade to Linux Kernel 3.16.85, including the new x86_64 RUNNIX bootloader, security and bug fixes > Kernel config: Add NAMESPACES and CGROUPS for Linux Containers > * New toolchain: glibc 2.27, binutils 2.29.1, gcc 6.5.0, using crosstool-ng-1.24.0 > * unionfs, move from old kernel unionfs to FUSE unionfs version 2.1 > To better secure the filesystem, now only '/etc' and '/stat' will be read-write over the read-only base firmware image. > * lxc, new package, add support for guest Linux Containers. For example, run Pi-hole or the UniFi Controller. > * OpenSSL, version bump to 1.1.1g > * WireGuard VPN, version bump, module 1.0.20200712, tools 1.0.20200513 > * OpenVPN, version bump to 2.4.9 > * udev, now use eudev version 3.2.9 > * zabbix, major version bump to 4.0.20, LTS series > * initial-setup, remove 'combined' partition format option, always use 'format separate' > * Asterisk '13se' (stable edition) version 13.29.2 is older than latest Asterisk 13.x version but more tested, built --without-pjproject > * Package upgrades providing important security and bug fixes > > Full ChangeLog: > https://raw.githubusercontent.com/astlinux-project/astlinux/1.3.10/docs/ChangeLog.txt > > All users are encouraged to upgrade. > > Previous Asterisk 11.x users are encouraged to switch to the new Asterisk '13se' (stable edition). Some configuration changes will be needed, though minimal. > > AstLinux Team > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Dan R. <da...@ry...> - 2020-08-11 13:19:45
|
Lonnie and All, The Highlights say, "To better secure the filesystem, now only '/etc' and '/stat' will be read-write over the read-only base firmware image." Does this mean that /mnt/kd will no longer be read-write? I have sngrep (as root) routinely saving pcaps in /mnt/kd/sngrep. Will I need to move this to /etc or /stat? As always, thanks for the ongoing development and guidance. Dan On Sun, Jul 26, 2020 at 03:04 PM, Lonnie Abelbeck wrote: Announcing AstLinux Release: 1.3.10 More Info: AstLinux Project https://www.astlinux-project.org/ (https://www.astlinux-project.org/) AstLinux 1.3.10 Highlights: * Asterisk Versions: 13.29.2, 13.34.0, 16.11.1 * Upgrade to Linux Kernel 3.16.85, including the new x86_64 RUNNIX bootloader, security and bug fixes Kernel config: Add NAMESPACES and CGROUPS for Linux Containers * New toolchain: glibc 2.27, binutils 2.29.1, gcc 6.5.0, using crosstool-ng-1.24.0 * unionfs, move from old kernel unionfs to FUSE unionfs version 2.1 To better secure the filesystem, now only '/etc' and '/stat' will be read-write over the read-only base firmware image. * lxc, new package, add support for guest Linux Containers. For example, run Pi-hole or the UniFi Controller. * OpenSSL, version bump to 1.1.1g * WireGuard VPN, version bump, module 1.0.20200712, tools 1.0.20200513 * OpenVPN, version bump to 2.4.9 * udev, now use eudev version 3.2.9 * zabbix, major version bump to 4.0.20, LTS series * initial-setup, remove 'combined' partition format option, always use 'format separate' * Asterisk '13se' (stable edition) version 13.29.2 is older than latest Asterisk 13.x version but more tested, built --without-pjproject * Package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.3.10/docs/ChangeLog.txt (https://raw.githubusercontent.com/astlinux-project/astlinux/1.3.10/docs/ChangeLog.txt) All users are encouraged to upgrade. Previous Asterisk 11.x users are encouraged to switch to the new Asterisk '13se' (stable edition). Some configuration changes will be needed, though minimal. AstLinux Team |
|
From: Michael K. <mic...@ip...> - 2020-07-26 21:41:57
|
Thanks Lonnie
Yes to both questions.
Hmm that is all way too much custom config for me.
I think I am going to look for other providers and In the mean time I will just use the SNAT Plugin for port forwarding and use the dynamic address with dynamic DNS for access to the box.
Thanks so much for your help.
Regards
Michael Knill
On 26/7/20, 11:48 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
Hi Michael,
So the static /30 is routed via your dynamic PPPoE IPv4 address to your box ?
So anywhere internally you can hang your /30 ?
Off the top of my head, in /mnt/kd/rc.elocal, you could play with something like:
--
modprobe dummy numdummies=0
ip link add name ip4net type dummy
ip addr add 1.2.3.4/30 dev ip4net
ip link set dev ip4net up
--
where 1.2.3.4/30 is your assigned static subnet.
While this can be done in /mnt/kd/rc.elocal, the trick will be getting this new ip4net interface to be supported by the firewall. Services that bind to 0.0.0.0 should pass ip4net traffic if the firewall allows it.
Additionally you don't want ip4net traffic to be NAT'ed via ppp0 I suspect.
A couple /mnt/kd/arno-iptables-firewall/custom-rules should do the trick. Be careful since ip4net consists of publicly routable addresses via ppp0, no NAT isolation.
Hope this helps.
Lonnie
> On Jul 25, 2020, at 11:47 PM, Michael Knill <mic...@ip...> wrote:
>
> Ok I can confirm that PPPoE is only a single dynamic connection. The SNAT plugin seems to work fine.
>
> The problem I have is that I'm not sure how I can assign this address on the local box so I can ping it externally and use it for remote access. It needs to be an EXT interface somehow.
> Any ideas?
>
> Regards
> Michael Knill
>
> On 23/7/20, 12:22 pm, "Michael Knill" <mic...@ip...> wrote:
>
> Yep its certainly a bit strange.
> 1) Yes completely different although the /30 is actually 4 useable addresses as it's a PPP connection.
> 2) No I'm fairly certain that PPP can only allocate a single IP Address which is the dynamic one. I would need to add the additional addresses to ppp0 once its up.
> Note this is a routed range so I think it could be assigned to internal devices and/or Astlinux local interface with NAT used to determine the address that is source NAT'd for external traffic.
>
> Hmm may need to play with the SNAT plugin and let you know.
>
> Regards
> Michael Knill
>
> On 22/7/20, 11:31 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
>
>
>> On Jul 22, 2020, at 6:31 AM, Michael Knill <mic...@ip...> wrote:
>>
>> Hi Group
>>
>> I have moved to a carrier that only provides a dynamic PPPoE address and if you want a static address they add a /30 routed range.
>> Just wondering how I configure this in Astlinux? Do I use EXTIP_ALIAS? How do I use this address for outgoing Source NAT?
>
> Hi Michael,
>
> For all these years, I have not heard of such a PPPoE configuration. Are you sure you need a static IP :-)
>
> The EXTIP_ALIAS would not apply since that is for physical interfaces, not PPPoE.
>
> Questions:
> 1) Is the /30 route completely different from the assigned dynamic /32 IPv4 ?
>
> 2) Does the PPPoE connection, via the underlying PPP connection, automatically add the /30 as a route and associated with the ppp0 interface ? OR, is this a static route and address that needs to be manually added to ppp0 after the PPPoE connectioin is up ?
> --
> ip addr show dev ppp0
>
> ip route show dev ppp0
> --
> (sanitize any public IPs)
>
>
> AstLinux has a firewall Outbound SNAT plugin that will SNAT outbound traffic from select internal IPs/CIDRs, this may work for you.
>
> The added problem here is since PPPoE can destroy and create the ppp0 interface, any associated static routes and firewall rules will be lost on a PPPoE restart, so that needs to be kept in mind.
>
> Lonnie
>
>
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2020-07-26 19:04:25
|
Announcing AstLinux Release: 1.3.10 More Info: AstLinux Project https://www.astlinux-project.org/ AstLinux 1.3.10 Highlights: * Asterisk Versions: 13.29.2, 13.34.0, 16.11.1 * Upgrade to Linux Kernel 3.16.85, including the new x86_64 RUNNIX bootloader, security and bug fixes Kernel config: Add NAMESPACES and CGROUPS for Linux Containers * New toolchain: glibc 2.27, binutils 2.29.1, gcc 6.5.0, using crosstool-ng-1.24.0 * unionfs, move from old kernel unionfs to FUSE unionfs version 2.1 To better secure the filesystem, now only '/etc' and '/stat' will be read-write over the read-only base firmware image. * lxc, new package, add support for guest Linux Containers. For example, run Pi-hole or the UniFi Controller. * OpenSSL, version bump to 1.1.1g * WireGuard VPN, version bump, module 1.0.20200712, tools 1.0.20200513 * OpenVPN, version bump to 2.4.9 * udev, now use eudev version 3.2.9 * zabbix, major version bump to 4.0.20, LTS series * initial-setup, remove 'combined' partition format option, always use 'format separate' * Asterisk '13se' (stable edition) version 13.29.2 is older than latest Asterisk 13.x version but more tested, built --without-pjproject * Package upgrades providing important security and bug fixes Full ChangeLog: https://raw.githubusercontent.com/astlinux-project/astlinux/1.3.10/docs/ChangeLog.txt All users are encouraged to upgrade. Previous Asterisk 11.x users are encouraged to switch to the new Asterisk '13se' (stable edition). Some configuration changes will be needed, though minimal. AstLinux Team |
|
From: Lonnie A. <li...@lo...> - 2020-07-26 13:48:19
|
Hi Michael, So the static /30 is routed via your dynamic PPPoE IPv4 address to your box ? So anywhere internally you can hang your /30 ? Off the top of my head, in /mnt/kd/rc.elocal, you could play with something like: -- modprobe dummy numdummies=0 ip link add name ip4net type dummy ip addr add 1.2.3.4/30 dev ip4net ip link set dev ip4net up -- where 1.2.3.4/30 is your assigned static subnet. While this can be done in /mnt/kd/rc.elocal, the trick will be getting this new ip4net interface to be supported by the firewall. Services that bind to 0.0.0.0 should pass ip4net traffic if the firewall allows it. Additionally you don't want ip4net traffic to be NAT'ed via ppp0 I suspect. A couple /mnt/kd/arno-iptables-firewall/custom-rules should do the trick. Be careful since ip4net consists of publicly routable addresses via ppp0, no NAT isolation. Hope this helps. Lonnie > On Jul 25, 2020, at 11:47 PM, Michael Knill <mic...@ip...> wrote: > > Ok I can confirm that PPPoE is only a single dynamic connection. The SNAT plugin seems to work fine. > > The problem I have is that I'm not sure how I can assign this address on the local box so I can ping it externally and use it for remote access. It needs to be an EXT interface somehow. > Any ideas? > > Regards > Michael Knill > > On 23/7/20, 12:22 pm, "Michael Knill" <mic...@ip...> wrote: > > Yep its certainly a bit strange. > 1) Yes completely different although the /30 is actually 4 useable addresses as it's a PPP connection. > 2) No I'm fairly certain that PPP can only allocate a single IP Address which is the dynamic one. I would need to add the additional addresses to ppp0 once its up. > Note this is a routed range so I think it could be assigned to internal devices and/or Astlinux local interface with NAT used to determine the address that is source NAT'd for external traffic. > > Hmm may need to play with the SNAT plugin and let you know. > > Regards > Michael Knill > > On 22/7/20, 11:31 pm, "Lonnie Abelbeck" <li...@lo...> wrote: > > >> On Jul 22, 2020, at 6:31 AM, Michael Knill <mic...@ip...> wrote: >> >> Hi Group >> >> I have moved to a carrier that only provides a dynamic PPPoE address and if you want a static address they add a /30 routed range. >> Just wondering how I configure this in Astlinux? Do I use EXTIP_ALIAS? How do I use this address for outgoing Source NAT? > > Hi Michael, > > For all these years, I have not heard of such a PPPoE configuration. Are you sure you need a static IP :-) > > The EXTIP_ALIAS would not apply since that is for physical interfaces, not PPPoE. > > Questions: > 1) Is the /30 route completely different from the assigned dynamic /32 IPv4 ? > > 2) Does the PPPoE connection, via the underlying PPP connection, automatically add the /30 as a route and associated with the ppp0 interface ? OR, is this a static route and address that needs to be manually added to ppp0 after the PPPoE connectioin is up ? > -- > ip addr show dev ppp0 > > ip route show dev ppp0 > -- > (sanitize any public IPs) > > > AstLinux has a firewall Outbound SNAT plugin that will SNAT outbound traffic from select internal IPs/CIDRs, this may work for you. > > The added problem here is since PPPoE can destroy and create the ppp0 interface, any associated static routes and firewall rules will be lost on a PPPoE restart, so that needs to be kept in mind. > > Lonnie > > > > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2020-07-26 04:47:19
|
Ok I can confirm that PPPoE is only a single dynamic connection. The SNAT plugin seems to work fine.
The problem I have is that I'm not sure how I can assign this address on the local box so I can ping it externally and use it for remote access. It needs to be an EXT interface somehow.
Any ideas?
Regards
Michael Knill
On 23/7/20, 12:22 pm, "Michael Knill" <mic...@ip...> wrote:
Yep its certainly a bit strange.
1) Yes completely different although the /30 is actually 4 useable addresses as it's a PPP connection.
2) No I'm fairly certain that PPP can only allocate a single IP Address which is the dynamic one. I would need to add the additional addresses to ppp0 once its up.
Note this is a routed range so I think it could be assigned to internal devices and/or Astlinux local interface with NAT used to determine the address that is source NAT'd for external traffic.
Hmm may need to play with the SNAT plugin and let you know.
Regards
Michael Knill
On 22/7/20, 11:31 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
> On Jul 22, 2020, at 6:31 AM, Michael Knill <mic...@ip...> wrote:
>
> Hi Group
>
> I have moved to a carrier that only provides a dynamic PPPoE address and if you want a static address they add a /30 routed range.
> Just wondering how I configure this in Astlinux? Do I use EXTIP_ALIAS? How do I use this address for outgoing Source NAT?
Hi Michael,
For all these years, I have not heard of such a PPPoE configuration. Are you sure you need a static IP :-)
The EXTIP_ALIAS would not apply since that is for physical interfaces, not PPPoE.
Questions:
1) Is the /30 route completely different from the assigned dynamic /32 IPv4 ?
2) Does the PPPoE connection, via the underlying PPP connection, automatically add the /30 as a route and associated with the ppp0 interface ? OR, is this a static route and address that needs to be manually added to ppp0 after the PPPoE connectioin is up ?
--
ip addr show dev ppp0
ip route show dev ppp0
--
(sanitize any public IPs)
AstLinux has a firewall Outbound SNAT plugin that will SNAT outbound traffic from select internal IPs/CIDRs, this may work for you.
The added problem here is since PPPoE can destroy and create the ppp0 interface, any associated static routes and firewall rules will be lost on a PPPoE restart, so that needs to be kept in mind.
Lonnie
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Michael K. <mic...@ip...> - 2020-07-23 02:22:03
|
Yep its certainly a bit strange.
1) Yes completely different although the /30 is actually 4 useable addresses as it's a PPP connection.
2) No I'm fairly certain that PPP can only allocate a single IP Address which is the dynamic one. I would need to add the additional addresses to ppp0 once its up.
Note this is a routed range so I think it could be assigned to internal devices and/or Astlinux local interface with NAT used to determine the address that is source NAT'd for external traffic.
Hmm may need to play with the SNAT plugin and let you know.
Regards
Michael Knill
On 22/7/20, 11:31 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
> On Jul 22, 2020, at 6:31 AM, Michael Knill <mic...@ip...> wrote:
>
> Hi Group
>
> I have moved to a carrier that only provides a dynamic PPPoE address and if you want a static address they add a /30 routed range.
> Just wondering how I configure this in Astlinux? Do I use EXTIP_ALIAS? How do I use this address for outgoing Source NAT?
Hi Michael,
For all these years, I have not heard of such a PPPoE configuration. Are you sure you need a static IP :-)
The EXTIP_ALIAS would not apply since that is for physical interfaces, not PPPoE.
Questions:
1) Is the /30 route completely different from the assigned dynamic /32 IPv4 ?
2) Does the PPPoE connection, via the underlying PPP connection, automatically add the /30 as a route and associated with the ppp0 interface ? OR, is this a static route and address that needs to be manually added to ppp0 after the PPPoE connectioin is up ?
--
ip addr show dev ppp0
ip route show dev ppp0
--
(sanitize any public IPs)
AstLinux has a firewall Outbound SNAT plugin that will SNAT outbound traffic from select internal IPs/CIDRs, this may work for you.
The added problem here is since PPPoE can destroy and create the ppp0 interface, any associated static routes and firewall rules will be lost on a PPPoE restart, so that needs to be kept in mind.
Lonnie
_______________________________________________
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...> - 2020-07-22 13:31:26
|
> On Jul 22, 2020, at 6:31 AM, Michael Knill <mic...@ip...> wrote: > > Hi Group > > I have moved to a carrier that only provides a dynamic PPPoE address and if you want a static address they add a /30 routed range. > Just wondering how I configure this in Astlinux? Do I use EXTIP_ALIAS? How do I use this address for outgoing Source NAT? Hi Michael, For all these years, I have not heard of such a PPPoE configuration. Are you sure you need a static IP :-) The EXTIP_ALIAS would not apply since that is for physical interfaces, not PPPoE. Questions: 1) Is the /30 route completely different from the assigned dynamic /32 IPv4 ? 2) Does the PPPoE connection, via the underlying PPP connection, automatically add the /30 as a route and associated with the ppp0 interface ? OR, is this a static route and address that needs to be manually added to ppp0 after the PPPoE connectioin is up ? -- ip addr show dev ppp0 ip route show dev ppp0 -- (sanitize any public IPs) AstLinux has a firewall Outbound SNAT plugin that will SNAT outbound traffic from select internal IPs/CIDRs, this may work for you. The added problem here is since PPPoE can destroy and create the ppp0 interface, any associated static routes and firewall rules will be lost on a PPPoE restart, so that needs to be kept in mind. Lonnie |
|
From: Michael K. <mic...@ip...> - 2020-07-22 11:31:51
|
Hi Group I have moved to a carrier that only provides a dynamic PPPoE address and if you want a static address they add a /30 routed range. Just wondering how I configure this in Astlinux? Do I use EXTIP_ALIAS? How do I use this address for outgoing Source NAT? Thanks Regards Michael Knill |
|
From: Lonnie A. <li...@lo...> - 2020-07-21 21:47:37
|
Hi John, It depends how the CDR's are stored. If it is /mnt/kd/cdr-csv/Master.csv or /mnt/kd/cdr-custom/Master.csv files, then these are simple text files, one CDR per line. Use standard UNIX tools, like 'sed' to remove the lines you don't want anymore. You may want to stop asterisk while doing such things. If you are using SQL (ex. /mnt/kd/cdr-sqlite3/cdr-odbc.sqlite3) ... probably just leave them alone :-) or some SQL command via the 'sqlite3' CLI tool. Lonnie > On Jul 21, 2020, at 4:32 PM, John Novack SCII_U <jn...@co...> wrote: > > > I have a user who would like to remove older CDR records. No need to save or backup, he just seems uncomfortable to keep records from 3-4 years ago > > Any simple way to do that? > > John Novack > > -- > Dog is my Co-Pilot > > > > _______________________________________________ > 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: John N. S. <jn...@co...> - 2020-07-21 21:32:57
|
I have a user who would like to remove older CDR records. No need to save or backup, he just seems uncomfortable to keep records from 3-4 years ago Any simple way to do that? John Novack -- Dog is my Co-Pilot |
|
From: Lonnie A. <li...@lo...> - 2020-07-10 15:49:29
|
Release Candidate1 pre-1.3.10, please report any issues, ASAP. Many under-the-hood updates: New toolchain: glibc 2.27, binutils 2.29.1, gcc 6.5.0, using crosstool-ng-1.24.0 udev, now use eudev version 3.2.9 kmod, version 27, new package which replaces module-init-tools ** IMPORTANT NOTICE -- AstLinux now only supports 64-bit, x86_64 architectures. -- Current supported board types are: "genx86_64", "genx86_64-serial" and "genx86_64-vm" ** The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own. -- Linux Kernel 3.16.85 (version bump), security and bug fixes Kernel config: Add NAMESPACES and CGROUPS for Linux Containers -- lxc, new package, add support for guest Linux Containers. Running Pi-hole for example. New rc.conf variables: LXC_BRIDGE0, LXC_STOP_TIMEOUT More info: https://doc.astlinux-project.org/userdoc:guest_lxc_container_main -- unionfs, move from old kernel unionfs to FUSE unionfs version 2.1 To better secure the filesystem, now only '/etc' and '/stat' will be read-write over the read-only base firmware image. Previously '/' (everything) was overlaid. Additionally, mount ASTURW as /mnt/asturw instead of /oldroot/mnt/asturw . -- New rc.conf variable ASTERISK_RW_MODULES_DIR, give directory /usr/lib/asterisk/modules/ read/write permissions, "yes" or "no", defaults to "no". Example: If you had a codec_g729a.so module installed, you must define: ASTERISK_RW_MODULES_DIR="yes" Note: With AstLinux 1.3.8 and older this was implied to be "yes". -- Asterisk 13.29.2 ('13se' version bump) Older than latest Asterisk 13.x version but more tested, built --without-pjproject -- Asterisk 13.34.0 (version bump) and 16.11.1 (version bump) -- OpenSSL, version bump to 1.1.1g, security fix: CVE-2020-1967 -- WireGuard VPN, module 1.0.20200623 (version bump), tools 1.0.20200513 (version bump) -- OpenVPN, version bump to 2.4.9, security fix: CVE-2020-11810 -- zabbix, major version bump to 4.0.20, next LTS series -- Complete Pre-Release ChangeLog: https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt New Documentation Topics: -- AstLinux Hosted Linux Containers https://doc.astlinux-project.org/userdoc:guest_lxc_container_main -- Firewall Overview https://doc.astlinux-project.org/userdoc:tt_firewall_overview Updated Documentation Topics: -- DNS-TLS Proxy Server https://doc.astlinux-project.org/userdoc:tt_dns_tls_proxy The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ... AstLinux Project -> Development https://www.astlinux-project.org/dev.html AstLinux Team |
63 messages has been excluded from this view by a project administrator.
