astlinux-devel — The AstLinux development environment, compilation, etc

[Astlinux-devel] Grrr I cant get Voicemail MWI status to refresh

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

We have built a separate Voicemail Portal but frankly I cant even get the standard Astlinux Voicemail Tab refreshing the status of MWI in any reasonable amount of time.
I don't know if its something funny in Asterisk 13.24.1 (Astlinux 1.3.5.2).

I have tried to use the AMI: VoicemailRefresh which does nothing and also setting pollmailboxes=yes and pollfreq=10 and still it does not change the MWI status on the phone for ages. I have also tried the UserEvent: FOP2RELOADVOICEMAIL and I still cant get that to work.

Any ideas where the problem could be or what I can try next?
The only thing that seems to work is a module reload chan_sip.so but I really dont want to be doing that every time someone uses my voicemail app.

Regards
Michael Knill

[Astlinux-devel] AstLinux Pre-Release: astlinux-1.3-4181-610913

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

Announcing Pre-Release Version: astlinux-1.3-4181-610913

The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.

-- Asterisk 11.x, no longer included, officially EOL 2017-10-25

-- Asterisk 13.23.1 (new '13se' version)
   Older than latest Asterisk 13.x version but more tested, built --without-pjproject

-- Asterisk 13.26.0 (version bump) and 16.3.0 (new version)
   Adds: res_mwi_devstate.so, MWI Device State Subscriptions

-- Linux Kernel 3.16.64, security and bug fixes.

-- busybox, *major* version bump to 1.30.1, security and bug fixes.

-- WireGuard VPN, version bump to 0.0.20190406

-- ne, new package, version 3.1.2, the nice editor, alternative to nano
   ne is easy to use for the beginner, but powerful and fully configurable for the wizard.
   Includes syntax checking for: asterisk, conf, ini, perl, sh
   More Info: http://ne.di.unimi.it/

-- Complete Pre-Release ChangeLog:
https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt


Updated Documentation Topics:
Asterisk LTS Series Version -
- https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version

The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ...

AstLinux Project -> Development
https://www.astlinux-project.org/dev.html

New "Development" tab feature for desktop browsers:
Guest VM x86-64bit ISO: Download Pre-Release Guest VM Install ISO (Video Console)


AstLinux Team

[Astlinux-devel] AstLinux Pre-Release: astlinux-1.3-4155-7d75e9

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

Announcing Pre-Release Version: astlinux-1.3-4155-7d75e9

The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.

-- Asterisk, version bump to 13.25.0 and added new LTS version 16.2.1 for testing.

-- Linux Kernel 3.16.64, security and bug fixes.

-- busybox, *major* version bump to 1.30.1, security and bug fixes.

-- ne, new package, version 3.1.2, the nice editor, alternative to nano
   ne is easy to use for the beginner, but powerful and fully configurable for the wizard.
   Includes syntax checking for: asterisk, conf, ini, perl, sh
   More Info: http://ne.di.unimi.it/

-- Complete Pre-Release ChangeLog:
https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt


Updated Documentation Topics:
Asterisk LTS Series Version -
- https://doc.astlinux-project.org/userdoc:tt_asterisk_upgrade_version

The "AstLinux Pre-Release ChangeLog" and "Pre-Release Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ...

AstLinux Project -> Development
https://www.astlinux-project.org/dev.html

New "Development" tab feature for desktop browsers:
Guest VM x86-64bit ISO: Download Pre-Release Guest VM Install ISO (Video Console)


AstLinux Team

Re: [Astlinux-devel] One of the Monit events is really annoying me

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

Whoops sorry you are right. This is the email that says it has gone below the threshold!
The email that says its over the threshold is 'Resource limit matched'

Both not very descriptive ☹
Would be better with something like:
> Resource limit exceeded
< Resource limit ok

Thanks as usual.

Regards
Michael Knill

On 19/3/19, 6:54 am, "Lonnie Abelbeck" <li...@lo...> wrote:

    Michael,
    
    Was this email preceded by a "Resource limit exceeded" ?
    
    What is your "loadavg (1min)" limit set to ? The measured 0.9 is normally below the limit which would imply "succeeded".
    
    Lonnie
    
    
    
    > On Mar 18, 2019, at 1:50 PM, Michael Knill <mic...@ip...> wrote:
    > 
    > See below:
    > Event should be Resource limit exceeded (not succeeded)
    > 
    > Is this a Monit thing or configuration?
    > 
    > Regards
    > Michael Knill
    > 
    > On 19/3/19, 2:09 am, "No Reply" <no...@ip...> wrote:
    > 
    >    Event:        Resource limit succeeded
    >    Service:      3024-DFK-CM1
    >    Date:         Tue, 19 Mar 2019 02:09:30
    >    Action:       alert
    >    Host:         3024-DFK-CM1
    >    Description:  loadavg(1min) check succeeded [current loadavg(1min) = 0.9]
    > 
    > 
    > 
    > _______________________________________________
    > Astlinux-devel mailing list
    > Ast...@li...
    > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    
    
    
    _______________________________________________
    Astlinux-devel mailing list
    Ast...@li...
    https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    

Re: [Astlinux-devel] One of the Monit events is really annoying me

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

Michael,

Was this email preceded by a "Resource limit exceeded" ?

What is your "loadavg (1min)" limit set to ? The measured 0.9 is normally below the limit which would imply "succeeded".

Lonnie



> On Mar 18, 2019, at 1:50 PM, Michael Knill <mic...@ip...> wrote:
> 
> See below:
> Event should be Resource limit exceeded (not succeeded)
> 
> Is this a Monit thing or configuration?
> 
> Regards
> Michael Knill
> 
> On 19/3/19, 2:09 am, "No Reply" <no...@ip...> wrote:
> 
>    Event:        Resource limit succeeded
>    Service:      3024-DFK-CM1
>    Date:         Tue, 19 Mar 2019 02:09:30
>    Action:       alert
>    Host:         3024-DFK-CM1
>    Description:  loadavg(1min) check succeeded [current loadavg(1min) = 0.9]
> 
> 
> 
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel

[Astlinux-devel] One of the Monit events is really annoying me

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

See below:
Event should be Resource limit exceeded (not succeeded)

Is this a Monit thing or configuration?

Regards
Michael Knill

On 19/3/19, 2:09 am, "No Reply" <no...@ip...> wrote:

    Event:        Resource limit succeeded
    Service:      3024-DFK-CM1
    Date:         Tue, 19 Mar 2019 02:09:30
    Action:       alert
    Host:         3024-DFK-CM1
    Description:  loadavg(1min) check succeeded [current loadavg(1min) = 0.9]
    

[Astlinux-devel] Announcing AstLinux Release: 1.3.5.2

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

Announcing AstLinux Release: 1.3.5.2
(1.3.5 and 1.3.5.1 were not released)

More Info: AstLinux Project
https://www.astlinux-project.org/

AstLinux 1.3.5.2 Highlights:
* Asterisk Versions: 11.25.3, 13.24.1
* Upgrade to Linux Kernel 3.16.61, including the RUNNIX bootloader, security and bug fixes
* wol-host, new command to send Wake-on-LAN packet to specified host, by IP or DNS name
* fossil, new feature to optionally send commit notifications via email while using "fossil-commit"
* WireGuard VPN, latest development snapshot during its incorporation into the mainline Linux Kernel
* Web Interface, WireGuard VPN sub-tab, add "Mobile Client Defaults" and "Mobile Client Credentials" sections
* Web Interface, Status tab, improve layout of "WireGuard VPN Status" section
* Package upgrades providing important security and bug fixes

Full ChangeLog:
https://raw.githubusercontent.com/astlinux-project/astlinux/1.3.5.2/docs/ChangeLog.txt

All users are encouraged to upgrade.

Special note:
Significant development on WireGuard VPN support, related to available macOS, iOS and Android WireGuard Apps
--
macOS Wireguard (macOS 10.14+)
https://itunes.apple.com/us/app/wireguard/id1451685025?ls=1&mt=12

iOS WireGuard (iOS 12+)
https://itunes.apple.com/us/app/wireguard/id1441195209?ls=1&mt=8

Android WireGuard
https://play.google.com/store/apps/details?id=com.wireguard.android
--
Please re-read first half of WireGuard VPN Configuration:
https://doc.astlinux-project.org/userdoc:tt_wireguard_vpn


AstLinux Team

Re: [Astlinux-devel] Traffic Shaping on backup connection

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

Michael,
  My scripts are below.  I put this in the firewall custom-rules script.

Now... if your WAN failover is a wireguard tunnel then be aware that if you
are stopping/starting wireguard then the rate limits will need to get setup
again... I do this in the wireguard.script file on "POST_UP" action.


#
=============================================================================
# Restore firewall marks on inbound/originating packets so that can be used
# elsewhere in the iptables firewall
echo "[CUSTOM RULE] rules to restore firewall marks"
ip4tables -t mangle -A PREROUTING -j CONNMARK --restore-mark
ip4tables -t mangle -A OUTPUT -j CONNMARK --restore-mark
ip6tables -t mangle -A PREROUTING -j CONNMARK --restore-mark
ip6tables -t mangle -A OUTPUT -j CONNMARK --restore-mark

#
=============================================================================
## Function to block devices so that they cannot access network through a
given
## interface.  And/or block traffic to/from a specific tcp/udp port number.
## >>>Call this function only once per interface
## Parameters:
##  interface (e.g. eth2)
##  MacAddrs (list of mac addresses)
##  Ports (list of ports)
## The interface local IP addresses are whitelisted
block_ports_macaddrs()
{
  local IFS=' '
  local mac
  local interface="$1"
  local macs="${2//,/ }"  # if comma delimited convert to space delimited
  local ports="$(echo $3 | tr -s ' ' ',')" # make sure comma delimited
  local chain=$(echo "FORWARD_$interface" | tr [a-z] [A-Z])  # uppercase
interface name

  iptables -N $chain 2>/dev/null
  iptables -F $chain
  iptables -A FORWARD_CHAIN -o $interface -j $chain

  grep "$interface" /proc/net/dev >/dev/null
  if [ "$?" = "0" ]; then
    local ipv4=$(ip -4 addr show $interface | grep 'inet ' | awk -F' ' '{
print $2 }')
    local ipv6ula=$(ip -6 addr show $interface | grep 'inet6 fd' | awk -F'
' '{ print $2 }')
    if [ -n "$ipv4" ]; then
      ip4tables -A $chain -d "$ipv4" -j ACCEPT
    fi
    if [ -n "$ipv6ula" ]; then
      ip6tables -A $chain -d "$ipv6ula" -j ACCEPT
    fi
  fi
  for mac in $macs; do
    echo "[CUSTOM RULE] Block MAC address $mac on interface $interface"
    iptables -A $chain -m mac --mac-source $mac -j DROP
  done
  if [ -n "$ports" ]; then
    echo "[CUSTOM RULE] Block ports $ports on interface $interface"
    iptables -A $chain -p tcp -m multiport --dports $ports -j DROP
    iptables -A $chain -p tcp -m multiport --sports $ports -j DROP
    iptables -A $chain -p udp -m multiport --dports $ports -j DROP
    iptables -A $chain -p udp -m multiport --sports $ports -j DROP
  fi
}

#
=============================================================================
## Function to prepare for rate limiting for traffic between local net and
## the WAN failover wireguard net.  Actual packet selection for rate
## limiting will take place in iptables.  This function limits only
## internal interfaces or WAN failover, not default EXTIF.
prepare_rate_limits()
{
  local interface
  local IFS=' '
  for interface in $INT_IF $EXT2IF; do
    grep "$interface" /proc/net/dev >/dev/null
    if [ "$?" = "0" ]; then
      echo "[CUSTOM RULE] Prepare $interface for rate limiting"
      tc qdisc del dev $interface root 2>/dev/null
      tc qdisc add dev $interface root handle 1: htb
      tc class add dev $interface parent 1: classid 1:1 htb rate 256Kbit
      tc class add dev $interface parent 1: classid 1:2 htb rate 512Kbit
      tc class add dev $interface parent 1: classid 1:3 htb rate 1024Kbit
      tc qdisc add dev $interface parent 1:1 handle 2: sfq perturb 10
      tc qdisc add dev $interface parent 1:2 handle 3: sfq perturb 10
      tc qdisc add dev $interface parent 1:3 handle 4: sfq perturb 10
      tc filter add dev $interface protocol ip parent 1: prio 1 handle 1 fw
flowid 1:1
      tc filter add dev $interface protocol ip parent 1: prio 1 handle 2 fw
flowid 1:2
      tc filter add dev $interface protocol ip parent 1: prio 1 handle 3 fw
flowid 1:3
    fi
  done
}


## Function to Rate limit some devices so that they cannot drive up huge
data use.
## >>>Call this function only once per interface
## This uses kernel traffic control (tc) rules set on the net interface
## Parameters:
##  interface (e.g. eth2)
##  MacAddrs (list of mac addresses)
##  LimitMarks (list of limit-marks corresponding to each mac address)
##     Mark 1: 256 Kbps, 2: 512 Kbps, 3: 1 Mbps
## Inbound packets have the packet mark restored
## Outbound packets from selected devices are marked and the packet saved
## The interface local IP addresses are whitelisted
rate_limit_macaddrs()
{
  local IFS=' '
  local mac
  local interface="$1"
  local macs="${2//,/ }"  # if comma delimited convert to space delimited
  local rate_marks="${3//,/ }" # if comma delimited convert to space
delimited
  local chain=$(echo "FORWARD_$interface" | tr [a-z] [A-Z])  # uppercase
interface name

  iptables -N $chain -t mangle 2>/dev/null
  iptables -F $chain -t mangle
  iptables -A FORWARD -t mangle -o $interface -j $chain

  grep "$interface" /proc/net/dev >/dev/null
  if [ "$?" = "0" ]; then
    local ipv4=$(ip -4 addr show $interface | grep 'inet ' | awk -F' ' '{
print $2 }')
    local ipv6ula=$(ip -6 addr show $interface | grep 'inet6 fd' | awk -F'
' '{ print $2 }')
    if [ -n "$ipv4" ]; then
      ip4tables -A $chain -t mangle -d "$ipv4" -j ACCEPT
    fi
    if [ -n "$ipv6ula" ]; then
      ip6tables -A $chain -t mangle -d "$ipv6ula" -j ACCEPT
    fi
  fi
#  iptables -A $chain -t mangle -m mark ! --mark 0 -j ACCEPT
  for mac in $macs; do
    echo "[CUSTOM RULE] Rate limit MAC address $mac on interface $interface"
    mark=${rate_marks%% *}
    rate_marks=${rate_marks#* }
    iptables -A $chain -t mangle -m mac --mac-source $mac -j MARK
--set-xmark ${mark:-1}/0x03
  done
  iptables -A $chain -t mangle -j CONNMARK --save-mark
  iptables -A $chain -t mangle -j ACCEPT
}

#
=============================================================================
## Make the calls to block / rate limit
## During WAN (Comcast Xfinity) failure all traffic will be routed through
## a WAN_FAILOVER interface.  On this system that is configured as wg0...

prepare_rate_limits
rate_limit_macaddrs \
"${WIREGUARD_IF:-wg0}" \
"52:54:00:43:1c:6e 3c:2e:ff:4e:bd:8a 8c:85:90:05:da:42 b8:e8:56:a3:67:05
f0:99:b6:4b:8c:87 00:61:71:cd:00:10 e0:33:8e:38:44:03 98:01:a7:49:1e:1c" \
"3 1 1 2 1 1 1 2"
##^ TestVM, iPhone, MacBook, iPad, iPhone Xs Max, iPhone 6, iPhone Xs, iPad

block_ports_macaddrs \
"${WIREGUARD_IF:-wg0}" \
"00:08:9B:EE:D4:0E 00:08:9B:EE:D4:0F 00:08:9B:EF:30:68 52:54:00:43:1c:6e
08:66:98:92:00:55 52:54:00:43:1c:6e 3c:2e:ff:4e:bd:8a 8c:85:90:05:da:42
b8:e8:56:a3:67:05 f0:99:b6:4b:8c:87 00:61:71:cd:00:10 e0:33:8e:38:44:03
98:01:a7:49:1e:1c" \
"4242"
##^ QNAP, QNAP, QNAP, UbuntuVM, AppleTV
##^ 4242 = crashplan ports

#
=============================================================================






On Wed, Feb 20, 2019 at 5:18 PM Michael Knill <
mic...@ip...> wrote:

> Thanks David that would be great.
>
>
>
> Regards
>
> Michael Knill
>
>
>
> *From: *David Kerr <da...@ke...>
> *Reply-To: *AstLinux Developers Mailing List <
> ast...@li...>
> *Date: *Thursday, 21 February 2019 at 9:13 am
> *To: *AstLinux Developers Mailing List <
> ast...@li...>
> *Subject: *Re: [Astlinux-devel] Traffic Shaping on backup connection
>
>
>
> I created some custom firewall scripts to handle this.  Specifically I
> wanted to block or severely rate limit certain devices when going over the
> cellular connection.  Devices are identified by their MAC address.  If this
> is what you are trying to do then let me know and I will share with you the
> scripts.
>
>
>
> David
>
>
>
>
>
> On Wed, Feb 20, 2019 at 4:28 PM Lonnie Abelbeck <li...@lo...>
> wrote:
>
> Hi Michael,
>
> Currently only "$EXTIF" (Primary External) is used for traffic shaping via
> the AIF Traffic-Shaper plugin.
>
> You are correct, if shaping was to also apply to the Failover interface
> "$EXT2IF" then a complete different set of shaping parameters would be
> needed.
>
> Lonnie
>
>
>
> > On Feb 20, 2019, at 3:05 PM, Michael Knill <
> mic...@ip...> wrote:
> >
> > Hi Devs
> >
> > I assume that the Astlinux traffic shaping configuration applies to both
> the primary and secondary connections?
> > If so, then is there a way that you can separate them between the two
> connections as you usually don't have them at the same speeds?
> >
> > Thanks
> >
> > Regards
> > Michael Knill
> > _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>

Re: [Astlinux-devel] Traffic Shaping on backup connection

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

Thanks David that would be great.

Regards
Michael Knill

From: David Kerr <da...@ke...>
Reply-To: AstLinux Developers Mailing List <ast...@li...>
Date: Thursday, 21 February 2019 at 9:13 am
To: AstLinux Developers Mailing List <ast...@li...>
Subject: Re: [Astlinux-devel] Traffic Shaping on backup connection

I created some custom firewall scripts to handle this.  Specifically I wanted to block or severely rate limit certain devices when going over the cellular connection.  Devices are identified by their MAC address.  If this is what you are trying to do then let me know and I will share with you the scripts.

David


On Wed, Feb 20, 2019 at 4:28 PM Lonnie Abelbeck <li...@lo...<mailto:li...@lo...>> wrote:
Hi Michael,

Currently only "$EXTIF" (Primary External) is used for traffic shaping via the AIF Traffic-Shaper plugin.

You are correct, if shaping was to also apply to the Failover interface "$EXT2IF" then a complete different set of shaping parameters would be needed.

Lonnie



> On Feb 20, 2019, at 3:05 PM, Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote:
>
> Hi Devs
>
> I assume that the Astlinux traffic shaping configuration applies to both the primary and secondary connections?
> If so, then is there a way that you can separate them between the two connections as you usually don't have them at the same speeds?
>
> Thanks
>
> Regards
> Michael Knill
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...<mailto:Ast...@li...>
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel



_______________________________________________
Astlinux-devel mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-devel

Re: [Astlinux-devel] Traffic Shaping on backup connection

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

I created some custom firewall scripts to handle this.  Specifically I
wanted to block or severely rate limit certain devices when going over the
cellular connection.  Devices are identified by their MAC address.  If this
is what you are trying to do then let me know and I will share with you the
scripts.

David


On Wed, Feb 20, 2019 at 4:28 PM Lonnie Abelbeck <li...@lo...>
wrote:

> Hi Michael,
>
> Currently only "$EXTIF" (Primary External) is used for traffic shaping via
> the AIF Traffic-Shaper plugin.
>
> You are correct, if shaping was to also apply to the Failover interface
> "$EXT2IF" then a complete different set of shaping parameters would be
> needed.
>
> Lonnie
>
>
>
> > On Feb 20, 2019, at 3:05 PM, Michael Knill <
> mic...@ip...> wrote:
> >
> > Hi Devs
> >
> > I assume that the Astlinux traffic shaping configuration applies to both
> the primary and secondary connections?
> > If so, then is there a way that you can separate them between the two
> connections as you usually don't have them at the same speeds?
> >
> > Thanks
> >
> > Regards
> > Michael Knill
> > _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>

Re: [Astlinux-devel] Traffic Shaping on backup connection

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

Hi Michael,

Currently only "$EXTIF" (Primary External) is used for traffic shaping via the AIF Traffic-Shaper plugin.

You are correct, if shaping was to also apply to the Failover interface "$EXT2IF" then a complete different set of shaping parameters would be needed.

Lonnie



> On Feb 20, 2019, at 3:05 PM, Michael Knill <mic...@ip...> wrote:
> 
> Hi Devs 
>  
> I assume that the Astlinux traffic shaping configuration applies to both the primary and secondary connections?
> If so, then is there a way that you can separate them between the two connections as you usually don't have them at the same speeds?
>  
> Thanks
>  
> Regards
> Michael Knill
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel

[Astlinux-devel] Traffic Shaping on backup connection

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

Hi Devs

I assume that the Astlinux traffic shaping configuration applies to both the primary and secondary connections?
If so, then is there a way that you can separate them between the two connections as you usually don't have them at the same speeds?

Thanks

Regards
Michael Knill

[Astlinux-devel] AstLinux Pre-Release: astlinux-1.3-4073-68d8d5

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

Announcing Pre-Release Version: astlinux-1.3-4073-68d8d5
Provided no issues found, this will become AstLinux 1.3.5


Significant development on WireGuard VPN support, related to available iOS and Android WireGuard Apps
--
iOS WireGuard (iOS 12+)
https://itunes.apple.com/us/app/wireguard/id1441195209?ls=1&mt=8

Android WireGuard
https://play.google.com/store/apps/details?id=com.wireguard.android
--
Re-read first half of WireGuard VPN Configuration -- https://doc.astlinux-project.org/userdoc:tt_wireguard_vpn


The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.

-- Asterisk, version bump to 13.24.1 and pjsip 2.8

-- Linux Kernel 3.16.61, security and bug fixes.

-- WireGuard VPN, version bump to 0.0.20190123

-- WireGuard VPN, add wireguard-mobile-client script to manage mobile clients.  Also used by the web interface.

-- Web Interface, WireGuard VPN sub-tab, add "Mobile Client Defaults" and "Mobile Client Credentials" sections.

-- Web Interface, Status tab, improve layout of "WireGuard VPN Status" section.

-- arnofw (AIF), add WIREGUARD_ALLOW_OPENVPN rc.conf variable, Allow WireGuard tunnel to OpenVPN tunnel(s), disabled by default.

-- wol-host, new command to send Wake-on-LAN packet to specified host, by IP or DNS name.
 Example: wol-host --ping 192.168.101.13
 More info: wol-host --help

-- fossil, new feature to optionally send commit notifications via email while using 'fossil-commit'.
 New rc.conf variable FOSSIL_NOTIFY must be defined (via user.conf) as To: email address to enable.
 Additional new, optional rc.conf variables: FOSSIL_NOTIFY_FROM, FOSSIL_HOSTNAME

-- Complete Pre-Release ChangeLog:
 https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt


New Documentation Topics:
EdgeRouter-X VPN Endpoint -- https://doc.astlinux-project.org/userdoc:tt_edgerouter-x

Updated Documentation Topics:
WireGuard VPN Configuration -- https://doc.astlinux-project.org/userdoc:tt_wireguard_vpn

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
https://www.astlinux-project.org/dev.html

AstLinux Team

[Astlinux-devel] AstLinux Pre-Release: astlinux-1.3-4048-3bfd9f

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

Announcing Pre-Release Version: astlinux-1.3-4048-3bfd9f

Significant development on WireGuard VPN support, related to available iOS and Android WireGuard Apps
--
iOS WireGuard (iOS 12+)
https://itunes.apple.com/us/app/wireguard/id1441195209?ls=1&mt=8

Android WireGuard
https://play.google.com/store/apps/details?id=com.wireguard.android
--
Re-read first half of WireGuard VPN Configuration -- https://doc.astlinux-project.org/userdoc:tt_wireguard_vpn


The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.

-- Asterisk, version bump to 13.24.1 and pjsip 2.8

-- Linux Kernel 3.16.61, security and bug fixes.

-- WireGuard VPN, version bump to 0.0.20181218

-- WireGuard VPN, add wireguard-mobile-client script to manage mobile clients.  Also used by the web interface.

-- Web Interface, WireGuard VPN sub-tab, add "Mobile Client Defaults" and "Mobile Client Credentials" sections.

-- Web Interface, Status tab, improve layout of "WireGuard VPN Status" section.

-- arnofw (AIF), add WIREGUARD_ALLOW_OPENVPN rc.conf variable, Allow WireGuard tunnel to OpenVPN tunnel(s), disabled by default.

-- wol-host, new command to send Wake-on-LAN packet to specified host, by IP or DNS name.
  Example: wol-host --ping 192.168.101.13
  More info: wol-host --help

-- fossil, new feature to optionally send commit notifications via email while using 'fossil-commit'.
  New rc.conf variable FOSSIL_NOTIFY must be defined (via user.conf) as To: email address to enable.
  Additional new, optional rc.conf variables: FOSSIL_NOTIFY_FROM, FOSSIL_HOSTNAME

-- Complete Pre-Release ChangeLog:
  https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt


New Documentation Topics:
EdgeRouter-X VPN Endpoint -- https://doc.astlinux-project.org/userdoc:tt_edgerouter-x

Updated Documentation Topics:
WireGuard VPN Configuration -- https://doc.astlinux-project.org/userdoc:tt_wireguard_vpn

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
https://www.astlinux-project.org/dev.html

AstLinux Team

Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU

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

Hi thanks Lonnie

I think I will keep with the current preferred solution. Had to ask though!

Regards
Michael Knill

From: lists <li...@lo...>
Reply-To: AstLinux Developers Mailing List <ast...@li...>
Date: Friday, 28 December 2018 at 1:39 pm
To: AstLinux Developers Mailing List <ast...@li...>
Subject: Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU

Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session.  Not something I’m personally interested in digging through ATM.

Does this approach save much money ?  The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal.


BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed.

Lonnie


On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote:
I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case.
https://www.pcengines.ch/apu3c2.htm
https://pcengines.ch/howto.htm#3G

Working solutions using Voyage Linux and PFSense:
https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/
https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/

Would be awesome to get working.

Regards
Michael Knill

On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...<mailto:li...@lo...>> wrote:

   Hi Michael,


How hard would it be to add 4G support into Astlinux?

   For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require.

   Do you have a reference ?

   Lonnie




On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote:

Hi Devs

I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution.
Yes I can get separate devices but consider a pretty standard install:
   • 1 x VDSL Modem
   • 1 x Astlinux Appliance
   • 1 x WAP
   • 1 x 4G router

Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously).
I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality.

How hard would it be to add 4G support into Astlinux?

Regards
Michael Knill
_______________________________________________
Astlinux-devel mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-devel



   _______________________________________________
   Astlinux-devel mailing list
   Ast...@li...<mailto:Ast...@li...>
   https://lists.sourceforge.net/lists/listinfo/astlinux-devel



_______________________________________________
Astlinux-devel mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-devel

Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU

[lists <li...@lo...>]

Looks like they register as USB serial devices that require the old school AT command settings followed by a PPP session.  Not something I’m personally interested in digging through ATM.

Does this approach save much money ?  The Netgear LB1120 vs. a mini pcie card and antenna ... plus you have to locate the APU3 for good signal.

BTW, there appear a few of these modems register as usb ethernet devices, that would be far more straight-forward to support, not sure if any are mini-pcie or not ... of course cell carrier support is also needed.

Lonnie


> On Dec 27, 2018, at 8:06 PM, Michael Knill <mic...@ip...> wrote:
> 
> I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case.
> https://www.pcengines.ch/apu3c2.htm
> https://pcengines.ch/howto.htm#3G
> 
> Working solutions using Voyage Linux and PFSense:
> https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/
> https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/
> 
> Would be awesome to get working.
> 
> Regards
> Michael Knill
> 
> On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
> 
>    Hi Michael,
> 
>> How hard would it be to add 4G support into Astlinux?
> 
>    For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require.
> 
>    Do you have a reference ?
> 
>    Lonnie
> 
> 
> 
>> On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote:
>> 
>> Hi Devs
>> 
>> I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution.
>> Yes I can get separate devices but consider a pretty standard install:
>>    • 1 x VDSL Modem
>>    • 1 x Astlinux Appliance
>>    • 1 x WAP
>>    • 1 x 4G router
>> 
>> Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously).
>> I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality.
>> 
>> How hard would it be to add 4G support into Astlinux?
>> 
>> Regards
>> Michael Knill
>> _______________________________________________
>> Astlinux-devel mailing list
>> Ast...@li...
>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> 
> 
> 
>    _______________________________________________
>    Astlinux-devel mailing list
>    Ast...@li...
>    https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> 
> 
> 
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel

Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU

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

I suspect that the best option is the APU3 which is actually targeted for 3G/LTE support with dual SIM slots and antenna connections in the case.
https://www.pcengines.ch/apu3c2.htm
https://pcengines.ch/howto.htm#3G

Working solutions using Voyage Linux and PFSense:
https://txlab.wordpress.com/2017/05/19/two-lte-modems-with-pc-engines-apu3/
https://teklager.se/en/knowledge-base/apu-4g-lte-modem-configuration/

Would be awesome to get working.

Regards
Michael Knill

On 28/12/18, 12:19 pm, "Lonnie Abelbeck" <li...@lo...> wrote:

    Hi Michael,
    
    > How hard would it be to add 4G support into Astlinux?
    
    For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require.
    
    Do you have a reference ?
    
    Lonnie
    
    
    
    > On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote:
    > 
    > Hi Devs
    >  
    > I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution.
    > Yes I can get separate devices but consider a pretty standard install:
    > 	• 1 x VDSL Modem
    > 	• 1 x Astlinux Appliance
    > 	• 1 x WAP
    > 	• 1 x 4G router
    >  
    > Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously).
    > I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality.
    >  
    > How hard would it be to add 4G support into Astlinux?
    >  
    > Regards
    > Michael Knill
    > _______________________________________________
    > Astlinux-devel mailing list
    > Ast...@li...
    > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    
    
    
    _______________________________________________
    Astlinux-devel mailing list
    Ast...@li...
    https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    

Re: [Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU

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

Hi Michael,

> How hard would it be to add 4G support into Astlinux?

For the special case of the PC Engines APU2, I'm not sure what form of miniPCI express card works and what kernel support it would require.

Do you have a reference ?

Lonnie



> On Dec 27, 2018, at 7:20 PM, Michael Knill <mic...@ip...> wrote:
> 
> Hi Devs
>  
> I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution.
> Yes I can get separate devices but consider a pretty standard install:
> 	• 1 x VDSL Modem
> 	• 1 x Astlinux Appliance
> 	• 1 x WAP
> 	• 1 x 4G router
>  
> Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously).
> I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality.
>  
> How hard would it be to add 4G support into Astlinux?
>  
> Regards
> Michael Knill
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel

[Astlinux-devel] 4G/LTE support by Astlinux on PC Engines APU

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

Hi Devs

I know this has been sort of discussed before however I intend on pretty much providing 4G backup on all my new installs and would love an all in one Astlinux solution.
Yes I can get separate devices but consider a pretty standard install:

  *   1 x VDSL Modem
  *   1 x Astlinux Appliance
  *   1 x WAP
  *   1 x 4G router

Its all a bit overkill when you can buy a single device to do all the above (from a network perspective obviously).
I could maybe combine the 4G and WAP functionality on a single device if I could do something funky with VLAN’s to split the functionality.

How hard would it be to add 4G support into Astlinux?

Regards
Michael Knill

[Astlinux-devel] AstLinux Pre-Release: astlinux-1.3-4025-663f0b

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

Announcing Pre-Release Version: astlinux-1.3-4025-663f0b

Asterisk 13.x version bump.

Significant development on WireGuard VPN support, related to available iOS and Android WireGuard Apps
--
iOS WireGuard beta (iOS 12+)
https://testflight.apple.com/join/63I19SDT

Android WireGuard
https://play.google.com/store/apps/details?id=com.wireguard.android
--
Re-read first half of WireGuard VPN Configuration
https://doc.astlinux-project.org/userdoc:tt_wireguard_vpn


The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.

-- Asterisk, version bump to 13.24.0 and pjsip 2.8

-- Linux Kernel 3.16.61, security and bug fixes.

-- WireGuard VPN, version bump to 0.0.20181119

-- WireGuard VPN, add wireguard-mobile-client script to manage mobile clients.  Also used by the web interface.

-- Web Interface, WireGuard VPN sub-tab, add "Mobile Client Defaults" and "Mobile Client Credentials" sections.

-- Web Interface, Status tab, improve layout of "WireGuard VPN Status" section.

-- arnofw (AIF), add WIREGUARD_ALLOW_OPENVPN rc.conf variable, Allow WireGuard tunnel to OpenVPN tunnel(s), disabled by default.

-- alert, on boot create a /etc/motd MOTD (Message of the Day) file containing system information.
  The MOTD is displayed at post-login by ssh, console and web interface CLI tab login.
  New rc.conf variable ENABLE_MOTD, display MOTD at post-login, "yes" or "no", defaults to "yes"

-- wol-host, new command to send Wake-on-LAN packet to specified host, by IP or DNS name.
 Example: wol-host --ping 192.168.101.13
 More info: wol-host --help

-- fossil, new feature to optionally send commit notifications via email while using 'fossil-commit'.
 New rc.conf variable FOSSIL_NOTIFY must be defined (via user.conf) as To: email address to enable.
 Additional new, optional rc.conf variables: FOSSIL_NOTIFY_FROM, FOSSIL_HOSTNAME

-- Complete Pre-Release ChangeLog:
 https://s3.amazonaws.com/beta.astlinux-project/astlinux-changelog/ChangeLog.txt


New Documentation Topics:
(none)

Updated Documentation Topics:
WireGuard VPN Configuration -- https://doc.astlinux-project.org/userdoc:tt_wireguard_vpn

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
https://www.astlinux-project.org/dev.html

AstLinux Team

Re: [Astlinux-devel] Dual PPPoE

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

Yes that's true but at one of my sites, I wanted to use one network connection for voice and the other for data with failover to each.
I will just use a nice Ubiquiti router instead!

Regards
Michael Knill

On 14/12/18, 7:31 am, "Lonnie Abelbeck" <li...@lo...> wrote:

    > Yes I can put the PPPoE credentials in the modem to turn it into a router but most of the DSL modems don't make good routers in my opinion.
    
    But if all the failover traffic is over WireGuard (or OpenVPN) a basic NAT router will work just fine, yielding a no-NAT VPN tunnel.
    
    Lonnie
    
    
    
    > On Dec 13, 2018, at 2:19 PM, Michael Knill <mic...@ip...> wrote:
    > 
    > Thanks Lonnie
    > 
    > Yes I suspected so but thought I better put it out there.
    > Yes I can put the PPPoE credentials in the modem to turn it into a router but most of the DSL modems don't make good routers in my opinion.
    > And yes I agree that 4G/LTE is a better option but I have some customers where I need two fixed network connections.
    > 
    > I will work something out.
    > 
    > Thanks.
    > 
    > Regards
    > Michael Knill
    > 
    > On 13/12/18, 9:40 am, "Lonnie Abelbeck" <li...@lo...> wrote:
    > 
    > 
    >> On Dec 12, 2018, at 3:59 PM, Michael Knill <mic...@ip...> wrote:
    >> 
    >> Hi Devs
    >> 
    >> Is there any option for dual PPPoE connections for Astlinux?
    >> Im setting up more and more WAN failover and it would be very handy to not have to install another router.
    >> 
    >> Regards
    >> Michael Knill
    > 
    >    Hi Michael,
    > 
    >    There is only support of a single PPPoE connection in Astlinux.  Though a person could hack in a 2nd PPPoE connection manually via rc.elocal, not recommended.
    > 
    >    Just as an aside, wouldn't a 4G/LTE failover for a PPPoE primary be better than a PPPoE failover for a PPPoE primary ?  Seems two PPPoE would have a lot in common.
    > 
    >    Also, if you don't mind if the failover PPPoE connection is behind NAT for failover, you could put your PPPoE credentials in the failover PPPoE modem.
    > 
    >    Lonnie
    > 
    >    PS, Michael, you asked about adding some WireGuard features in the past, some/most have been added in the current Pre-Release for testing.
    >    https://doc.astlinux-project.org/userdoc:tt_wireguard_vpn
    > 
    > 
    > 
    >    _______________________________________________
    >    Astlinux-devel mailing list
    >    Ast...@li...
    >    https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    > 
    > 
    > 
    > _______________________________________________
    > Astlinux-devel mailing list
    > Ast...@li...
    > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    
    
    
    _______________________________________________
    Astlinux-devel mailing list
    Ast...@li...
    https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    

Re: [Astlinux-devel] Dual PPPoE

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

> Yes I can put the PPPoE credentials in the modem to turn it into a router but most of the DSL modems don't make good routers in my opinion.

But if all the failover traffic is over WireGuard (or OpenVPN) a basic NAT router will work just fine, yielding a no-NAT VPN tunnel.

Lonnie



> On Dec 13, 2018, at 2:19 PM, Michael Knill <mic...@ip...> wrote:
> 
> Thanks Lonnie
> 
> Yes I suspected so but thought I better put it out there.
> Yes I can put the PPPoE credentials in the modem to turn it into a router but most of the DSL modems don't make good routers in my opinion.
> And yes I agree that 4G/LTE is a better option but I have some customers where I need two fixed network connections.
> 
> I will work something out.
> 
> Thanks.
> 
> Regards
> Michael Knill
> 
> On 13/12/18, 9:40 am, "Lonnie Abelbeck" <li...@lo...> wrote:
> 
> 
>> On Dec 12, 2018, at 3:59 PM, Michael Knill <mic...@ip...> wrote:
>> 
>> Hi Devs
>> 
>> Is there any option for dual PPPoE connections for Astlinux?
>> Im setting up more and more WAN failover and it would be very handy to not have to install another router.
>> 
>> Regards
>> Michael Knill
> 
>    Hi Michael,
> 
>    There is only support of a single PPPoE connection in Astlinux.  Though a person could hack in a 2nd PPPoE connection manually via rc.elocal, not recommended.
> 
>    Just as an aside, wouldn't a 4G/LTE failover for a PPPoE primary be better than a PPPoE failover for a PPPoE primary ?  Seems two PPPoE would have a lot in common.
> 
>    Also, if you don't mind if the failover PPPoE connection is behind NAT for failover, you could put your PPPoE credentials in the failover PPPoE modem.
> 
>    Lonnie
> 
>    PS, Michael, you asked about adding some WireGuard features in the past, some/most have been added in the current Pre-Release for testing.
>    https://doc.astlinux-project.org/userdoc:tt_wireguard_vpn
> 
> 
> 
>    _______________________________________________
>    Astlinux-devel mailing list
>    Ast...@li...
>    https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> 
> 
> 
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel

Re: [Astlinux-devel] Dual PPPoE

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

Oh and thanks for adding the new Wireguard features.

Regards
Michael Knill

On 13/12/18, 9:40 am, "Lonnie Abelbeck" <li...@lo...> wrote:

    
    > On Dec 12, 2018, at 3:59 PM, Michael Knill <mic...@ip...> wrote:
    > 
    > Hi Devs
    >  
    > Is there any option for dual PPPoE connections for Astlinux?
    > Im setting up more and more WAN failover and it would be very handy to not have to install another router.
    >  
    > Regards
    > Michael Knill
    
    Hi Michael,
    
    There is only support of a single PPPoE connection in Astlinux.  Though a person could hack in a 2nd PPPoE connection manually via rc.elocal, not recommended.
    
    Just as an aside, wouldn't a 4G/LTE failover for a PPPoE primary be better than a PPPoE failover for a PPPoE primary ?  Seems two PPPoE would have a lot in common.
    
    Also, if you don't mind if the failover PPPoE connection is behind NAT for failover, you could put your PPPoE credentials in the failover PPPoE modem.
    
    Lonnie
    
    PS, Michael, you asked about adding some WireGuard features in the past, some/most have been added in the current Pre-Release for testing.
    https://doc.astlinux-project.org/userdoc:tt_wireguard_vpn
    
    
    
    _______________________________________________
    Astlinux-devel mailing list
    Ast...@li...
    https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    

Re: [Astlinux-devel] Dual PPPoE

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

Thanks Lonnie

Yes I suspected so but thought I better put it out there.
Yes I can put the PPPoE credentials in the modem to turn it into a router but most of the DSL modems don't make good routers in my opinion.
And yes I agree that 4G/LTE is a better option but I have some customers where I need two fixed network connections.

I will work something out.

Thanks.

Regards
Michael Knill

On 13/12/18, 9:40 am, "Lonnie Abelbeck" <li...@lo...> wrote:

    
    > On Dec 12, 2018, at 3:59 PM, Michael Knill <mic...@ip...> wrote:
    > 
    > Hi Devs
    >  
    > Is there any option for dual PPPoE connections for Astlinux?
    > Im setting up more and more WAN failover and it would be very handy to not have to install another router.
    >  
    > Regards
    > Michael Knill
    
    Hi Michael,
    
    There is only support of a single PPPoE connection in Astlinux.  Though a person could hack in a 2nd PPPoE connection manually via rc.elocal, not recommended.
    
    Just as an aside, wouldn't a 4G/LTE failover for a PPPoE primary be better than a PPPoE failover for a PPPoE primary ?  Seems two PPPoE would have a lot in common.
    
    Also, if you don't mind if the failover PPPoE connection is behind NAT for failover, you could put your PPPoE credentials in the failover PPPoE modem.
    
    Lonnie
    
    PS, Michael, you asked about adding some WireGuard features in the past, some/most have been added in the current Pre-Release for testing.
    https://doc.astlinux-project.org/userdoc:tt_wireguard_vpn
    
    
    
    _______________________________________________
    Astlinux-devel mailing list
    Ast...@li...
    https://lists.sourceforge.net/lists/listinfo/astlinux-devel
    

Re: [Astlinux-devel] Dual PPPoE

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

> On Dec 12, 2018, at 3:59 PM, Michael Knill <mic...@ip...> wrote:
> 
> Hi Devs
>  
> Is there any option for dual PPPoE connections for Astlinux?
> Im setting up more and more WAN failover and it would be very handy to not have to install another router.
>  
> Regards
> Michael Knill

Hi Michael,

There is only support of a single PPPoE connection in Astlinux.  Though a person could hack in a 2nd PPPoE connection manually via rc.elocal, not recommended.

Just as an aside, wouldn't a 4G/LTE failover for a PPPoE primary be better than a PPPoE failover for a PPPoE primary ?  Seems two PPPoE would have a lot in common.

Also, if you don't mind if the failover PPPoE connection is behind NAT for failover, you could put your PPPoE credentials in the failover PPPoE modem.

Lonnie

PS, Michael, you asked about adding some WireGuard features in the past, some/most have been added in the current Pre-Release for testing.
https://doc.astlinux-project.org/userdoc:tt_wireguard_vpn