astlinux-users — AstLinux Users Mailing List

Re: [Astlinux-users] Hardware question

[John N. <jn...@co...>]

Our collectors network ( of obsolete telephone equipment ) has quite a few users of AstLinux with both 4 port analog cards ( TDM400/410 ) as well as T1 cards and channel bank. Older HP thin clients with expansion frames that support 1 PCI card are in use. FXS modules require 12VDC, so the units that are powered off 12VDC ( up to T5720 ) are more suitable. The SE version of AstLinux has to be used, as these are 32 bit.

Certainly not a "bleeding edge" application, but it works well.

As to PSTN connections, in North America, IMO the best choice is voip.ms. They support both SIP and IAX into Asterisk/AstLinux. I have used them with IAX for 10 years, with hardly a burp on their end!

YMMV

John Novack


Lonnie Abelbeck wrote:
>
>> On Feb 14, 2021, at 5:32 PM, Doron Keller <dor...@gm...> wrote:
>>
>> Hello,
>>
>> I'm not sure this is the place to ask this so I'd appreciate pointing me to the right place if not.
>>
>> I would like to build or buy an embedded system with fxo, fxs and ethernet interfaces and a processor that can run astlinux.
>>
>> Are you aware of such over the shelf hardware?
>>
>> Thank you.
> Hi Doron,
>
> Not knowing your technical background makes it difficult to define a specific answer, but maybe a little info.
>
> Short answer, I'm not aware of an x86_64 box with FXO/FXS ports.
>
> Though a plain x86_64 box should work with a SIP voice network, we have some examples in the docs:
>
> Generic 64-bit, x86_64 Boards and Appliances
> https://doc.astlinux-project.org/userdoc:documentation#generic_64-bit_x86_64_boards_and_appliances
>
> Getting AstLinux running and functioning as a router/firewall/vpn is fairly straightforward.
>
> On the other hand, getting the PBX (asterisk) configured from scratch takes some effort.  We have tools to help configure phones and such, but getting the first phone and upstream SIP provider configured takes time and research.
>
> While PCIe cards that support FXO, FXS exist, some sort of SIP telephony gateway device will also get you FXO/FXS with less trouble and more hardware options.
>
> An alternative to physical FXO, open an account with an internet SIP provider and obtain a phone number and billing by the minute.  Do the math, but is it usually not expensive.
>
> 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....
>
-- 
Dog is my Co-Pilot

Re: [Astlinux-users] Hardware question

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

> On Feb 14, 2021, at 5:32 PM, Doron Keller <dor...@gm...> wrote:
> 
> Hello,
> 
> I'm not sure this is the place to ask this so I'd appreciate pointing me to the right place if not.
> 
> I would like to build or buy an embedded system with fxo, fxs and ethernet interfaces and a processor that can run astlinux. 
> 
> Are you aware of such over the shelf hardware? 
> 
> Thank you.

Hi Doron,

Not knowing your technical background makes it difficult to define a specific answer, but maybe a little info.

Short answer, I'm not aware of an x86_64 box with FXO/FXS ports.

Though a plain x86_64 box should work with a SIP voice network, we have some examples in the docs:

Generic 64-bit, x86_64 Boards and Appliances
https://doc.astlinux-project.org/userdoc:documentation#generic_64-bit_x86_64_boards_and_appliances

Getting AstLinux running and functioning as a router/firewall/vpn is fairly straightforward.

On the other hand, getting the PBX (asterisk) configured from scratch takes some effort.  We have tools to help configure phones and such, but getting the first phone and upstream SIP provider configured takes time and research.

While PCIe cards that support FXO, FXS exist, some sort of SIP telephony gateway device will also get you FXO/FXS with less trouble and more hardware options.

An alternative to physical FXO, open an account with an internet SIP provider and obtain a phone number and billing by the minute.  Do the math, but is it usually not expensive.

Lonnie

Re: [Astlinux-users] Hardware question

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

I am not aware of any but would suggest that it is probably far cheaper and
more flexible to separate the FXO/FXS ports into a separate VoIP adapter.
I think it quite rare to need to convert to an outgoing POTS port
now-a-days an the only real use of analog on an inside network is to
support FAX machines (and they have their own set of VoIP issues).  You can
get a FXO/FXS devices with built-in router, but I do not think they are x86
based.  For the best range of commercial devices check out voipsupply.com.

David.

On Sun, Feb 14, 2021 at 6:32 PM Doron Keller <dor...@gm...> wrote:

> Hello,
>
> I'm not sure this is the place to ask this so I'd appreciate pointing me
> to the right place if not.
>
> I would like to build or buy an embedded system with fxo, fxs and ethernet
> interfaces and a processor that can run astlinux.
>
> Are you aware of such over the shelf hardware?
>
> Thank you.
> _______________________________________________
> 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] Hardware question

[Doron K. <dor...@gm...>]

Hello,

I'm not sure this is the place to ask this so I'd appreciate pointing me to
the right place if not.

I would like to build or buy an embedded system with fxo, fxs and ethernet
interfaces and a processor that can run astlinux.

Are you aware of such over the shelf hardware?

Thank you.

[Astlinux-users] AstLinux Pre-Release: astlinux-1.4-5042-8873c9

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

Announcing AstLinux Pre-Release: astlinux-1.4-5042-8873c9

** IMPORTANT NOTICE

-- The ipsec-tools (racoon) support in AstLinux has been removed. The development of ipsec-tools has been ABANDONED.
	The Network tab -> VPN Type: "IPsec Peers" and "IPsec Mobile" in the web interface has been removed.
	The AstLinux Team suggests using either WireGuard or OpenVPN for your VPN needs, but if IPsec is required for
	compatibility reasons the Network tab -> VPN Type: "IPsec strongSwan" should be able to do what you want,
	albeit in a less than ideal text based configuration.
	More info: https://doc.astlinux-project.org/userdoc:tt_ipsec_vpn_strongswan

** 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.175 (version bump), security and bug fixes

-- ipsec-tools (racoon) package has been removed.
	More info: https://doc.astlinux-project.org/userdoc:tt_ipsec_vpn_strongswan

-- OpenVPN, version bump to 2.4.10

-- unbound, version bump to 1.13.1

-- zabbix, version bump to 4.0.28

-- vnStat, new package, version 2.6, interface counter history is saved to /mnt/kd/vnstat/vnstat.db every hour.
	Enabled by default to keep a log of network traffic for external interface(s). No sniffing of traffic is performed.
	New rc.conf variable VNSTAT_ENABLE can be set to "no" to disable.

-- Web Interface, added vnStat tab, available to "admin/staff" users.  Hidden by default in Prefs tab.

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

-- Asterisk 13.38.1 (no change) and 16.16.0 (version bump)

-- 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

Re: [Astlinux-users] Cisco 7942 use

[John N. <jn...@co...>]

Great

Just be cautious of any unwanted tag-a-longs from any unknown source

JN


Ionel Chila wrote:
> Your Firmware here —> http://www.firewall.cx/downloads/cisco-tools-a-applications/cisco-ip-phone-a-ata-firmware-downloads/133-7942-a-7962-ip-phone-sccp-a-sip.html
>
>
> Load the latest SIP firmware and you’re good to go.  I have the 7945 version which is perfect. I have 4 of these in my home.  How to below:
>
> Recently I needed to change the firmware on some Cisco 7965 phones from SCCP to SIP. By far the simplest method is loading the COP file on UCM and letting the phone upgrade on its own.  In my case, this upgrade was being done without using UCM.  The Cisco read-me doc for the SIP firmware covers the COP upgrade procedure only.  It tells you that you may unzip the files on a TFTP server but there is no procedure which explains what else you must do to load the SIP firmware.
>
> In this example I am upgrading Cisco 7965 phones to SIP firmware 8.5.  Once you have downloaded the zipped version of the SIP firmware from CCO place the unzipped files in your TFTP servers root directory.  Modify your XMLDefaults.cnf.xml file so the load information matches your firmware.
>
> <loadInformation8 model=”Cisco 7965″>SIP45.8-5-3TH1</loadInformation8>
>
> You should connect your IP phone to LAN where DHCP provides the IP, subnet, and TFTP server IP.  Make sure your phone has DHCP enabled = YES. Your DHCP server needs to support DHCP Options.  TFTP option 66 is required for Cisco phones running SIP. Option 66 can be used to provide an IP address (recommended) but can also support a DNS names (assuming you are also providing at least one DNS server IP via DHCP).  Option 150 only supports IP addresses and is required for SCCP firmware.  You can safely configure your DHCP to issue both TFTP options.
>
> Next pull the power from your phone and plug it back in.  Hold down # until the line keys start to blink and press 123456789*0# and your phone should reset.  Your phone should display “Upgrading” on the screen.  If you are using a Unix based tftp server you can execute tcpdump port 69 and you should see your phone requesting the files.  Your phone should display the progress of the SIP firmware upgrade and eventually reboot.  After it reboots you can press Settings > Model Information and scroll down until you see the Call Control Protocol = SIP.
>
> If you performed a factory reset and did not have DHCP enabled then your phone is most likely stuck at the Upgrading screen. Pressing keys on the phone will not change the status. At this point you should pull the power, plug it back in, hold # and then enter the keys 3491672850*# to factory reset the phone. This allows the phone to clear its flash and still download new firmware.  Your screen is going to be totally black and it will appear as if your phone is not functional, but the phone is really sending a DHCP request and waiting for an IP, subnet, and TFTP IP assignment before proceeding to download the firmware. All of this is happening while the phone’s screen is black. If you want to read the official word on this, Cisco has a field notice on their web site.  Monitoring tcpdump on the TFTP server is useful in this case because you know the phone is doing something.  Also, you can view the DHCP bindings to verify your phone successfully acquired an IP address.
>
>
>
> Then setup the XML config file with your Mac address in /tftpboot in the Astlinux box and make sure your DHCP server know where to pass the tftp IP.   After SEP put your Cisco phone MAC address. I have SEP00235EB65698.cnf.xml
>
> HOME-PBX tftpboot # cat SEP00235EB65698.cnf.xml
> <!-- FIXME: Change to your own phone number (or another unique ID) -->
> <device xsi:type="axl:XIPPhone" ctiid="7134542795">
> <deviceProtocol>SIP</deviceProtocol>
> <sshUserId>cisco</sshUserId>
> <sshPassword>cisco</sshPassword>
> <sshAccess>0</sshAccess>
> <sshPort>22</sshPort>
> <devicePool>
>  <dateTimeSetting>
>   <!-- FIXME: Set your preferred date format and timezone here -->
>   <dateTemplate>M/D/Ya</dateTemplate>
>   <timeZone>Central Standard/Daylight Time</timeZone>
>   <ntps>
>       <!-- NTP might not actually work, but the phone can set the
>             date/time from the SIP response headers -->
>       <ntp>
>           <name>pool.ntp.org <http://pool.ntp.org></name>
>           <ntpMode>Unicast</ntpMode>
>       </ntp>
>   </ntps>
>  </dateTimeSetting>
>
>  <!-- This section probably does not do anything useful. -->
>  <callManagerGroup>
>   <members>
>     <member priority="0">
>         <callManager>
>           <ports>
> <ethernetPhonePort>2000</ethernetPhonePort>
>               <sipPort>5060</sipPort>
> <securedSipPort>5061</securedSipPort>
>           </ports>
> <processNodeName>192.168.0.15</processNodeName>
>         </callManager>
>     </member>
>   </members>
>  </callManagerGroup>
> </devicePool>
> <sipProfile>
>  <sipProxies>
> <registerWithProxy>true</registerWithProxy>
>  </sipProxies>
>  <sipCallFeatures>
>   <cnfJoinEnabled>true</cnfJoinEnabled>
> <callForwardURI>x--serviceuri-cfwdall</callForwardURI>
> <callPickupURI>x-cisco-serviceuri-pickup</callPickupURI>
> <callPickupListURI>x-cisco-serviceuri-opickup</callPickupListURI>
> <callPickupGroupURI>x-cisco-serviceuri-gpickup</callPickupGroupURI>
> <meetMeServiceURI>x-cisco-serviceuri-meetme</meetMeServiceURI>
> <abbreviatedDialURI>x-cisco-serviceuri-abbrdial</abbreviatedDialURI>
>   <rfc2543Hold>false</rfc2543Hold>
>   <callHoldRingback>2</callHoldRingback>
>   <localCfwdEnable>true</localCfwdEnable>
> <semiAttendedTransfer>true</semiAttendedTransfer>
> <anonymousCallBlock>2</anonymousCallBlock>
>   <callerIdBlocking>2</callerIdBlocking>
>   <dndControl>0</dndControl>
>   <remoteCcEnable>true</remoteCcEnable>
>  </sipCallFeatures>
>  <sipStack>
>   <sipInviteRetx>6</sipInviteRetx>
>   <sipRetx>10</sipRetx>
> <timerInviteExpires>180</timerInviteExpires>
>   <!-- Force short registration timeout to keep NAT connection alive -->
> <timerRegisterExpires>180</timerRegisterExpires>
> <timerRegisterDelta>5</timerRegisterDelta>
> <timerKeepAliveExpires>120</timerKeepAliveExpires>
> <timerSubscribeExpires>120</timerSubscribeExpires>
> <timerSubscribeDelta>5</timerSubscribeDelta>
>   <timerT1>500</timerT1>
>   <timerT2>4000</timerT2>
>   <maxRedirects>70</maxRedirects>
>   <remotePartyID>false</remotePartyID>
>   <userInfo>None</userInfo>
>  </sipStack>
>  <autoAnswerTimer>1</autoAnswerTimer>
>  <autoAnswerAltBehavior>false</autoAnswerAltBehavior>
>  <autoAnswerOverride>true</autoAnswerOverride>
>  <transferOnhookEnabled>false</transferOnhookEnabled>
>  <enableVad>false</enableVad>
>  <preferredCodec>g711ulaw</preferredCodec>
>  <dtmfAvtPayload>101</dtmfAvtPayload>
>  <dtmfDbLevel>3</dtmfDbLevel>
>  <dtmfOutofBand>avt</dtmfOutofBand>
>  <alwaysUsePrimeLine>false</alwaysUsePrimeLine>
>  <alwaysUsePrimeLineVoiceMail>false</alwaysUsePrimeLineVoiceMail>
>  <kpml>3</kpml>
>  <natEnabled>false</natEnabled>
>  <natAddress>1</natAddress>
>  <!-- FIXME: This will appear in the upper right corner of the display -->
>  <phoneLabel>Yenos Budros</phoneLabel>
>  <stutterMsgWaiting>1</stutterMsgWaiting>
>  <callStats>false</callStats>
>  <silentPeriodBetweenCallWaitingBursts>10</silentPeriodBetweenCallWaitingBursts>
>  <disableLocalSpeedDialConfig>false</disableLocalSpeedDialConfig>
>  <startMediaPort>16384</startMediaPort>
>  <stopMediaPort>16391</stopMediaPort>
>  <sipLines>
>   <line button="1">
>     <featureID>9</featureID>
>     <!-- FIXME: Text to display next to line button #1 -->
>     <featureLabel>Home Office Line</featureLabel>
>     <!-- FIXME: FQDN or IP of your SIP proxy -->
>     <proxy>USECALLMANAGER</proxy>
>     <port>5060</port>
>     <!-- FIXME: SIP username -->
>     <name>200</name>
>     <!-- FIXME: Name to display on outbound caller ID -->
>     <displayName>Yenos Budros</displayName>
>     <autoAnswer>
> <autoAnswerEnabled>2</autoAnswerEnabled>
>     </autoAnswer>
>     <callWaiting>1</callWaiting>
>     <!-- FIXME: SIP authorization name (often matches username) -->
>     <authName>200</authName>
>     <!-- FIXME: SIP authorization password -->
> <authPassword>ciscocisco</authPassword>
>     <sharedLine>true</sharedLine>
> <messageWaitingLampPolicy>1</messageWaitingLampPolicy>
>     <!-- FIXME: "Messages" key will autodial this number -->
>     <messagesNumber>*97</messagesNumber>
>     <ringSettingIdle>4</ringSettingIdle>
> <ringSettingActive>5</ringSettingActive>
>     <contact></contact>
>     <forwardCallInfoDisplay>
>         <callerName>true</callerName>
>         <callerNumber>false</callerNumber>
> <redirectedNumber>false</redirectedNumber>
>         <dialedNumber>true</dialedNumber>
>     </forwardCallInfoDisplay>
>   </line>
>   <line button="2">
>     <featureID>2</featureID>
>     <featureLabel>CVX Conference</featureLabel>
> <speedDialNumber>18773444239</speedDialNumber>
>   </line>
>   <line button="3">
>       <featureID>2</featureID>
>       <featureLabel>Teresa Cell</featureLabel>
> <speedDialNumber>18333547560</speedDialNumber>
>   </line>
>   <line button="4">
>       <featureID>2</featureID>
>       <featureLabel>Yenos Cell</featureLabel>
> <speedDialNumber>17134222795</speedDialNumber>
>   </line>
>   <line button="6">
>       <featureID>2</featureID>
>       <featureLabel>KIDS EMERGENCY 911</featureLabel>
> <speedDialNumber>911</speedDialNumber>
>   </line>
> </sipLines>
>  <voipControlPort>5060</voipControlPort>
>  <dscpForAudio>184</dscpForAudio>
>  <ringSettingBusyStationPolicy>0</ringSettingBusyStationPolicy>
>  <dialTemplate>dialplan.xml</dialTemplate>
> </sipProfile>
> <commonProfile>
>  <phonePassword></phonePassword>
>  <backgroundImageAccess>true</backgroundImageAccess>
>  <callLogBlfEnabled>2</callLogBlfEnabled>
> </commonProfile>
> <!-- FIXME: Change this to upgrade the firmware -->
> <loadInformation>SIP45.9-3-1SR3-1S</loadInformation>
> <vendorConfig>
>  <disableSpeaker>false</disableSpeaker>
>  <disableSpeakerAndHeadset>false</disableSpeakerAndHeadset>
>  <pcPort>0</pcPort>
>  <settingsAccess>1</settingsAccess>
>  <garp>0</garp>
>  <voiceVlanAccess>1</voiceVlanAccess>
>  <videoCapability>0</videoCapability>
>  <autoSelectLineEnable>0</autoSelectLineEnable>
>  <webAccess>0</webAccess>
>  <!-- For Sunday (1) and Saturday (7):
> <daysDisplayNotActive>1,2,3,4,5,6,7</daysDisplayNotActive>
> Current default is to enable the display 24/7.
>  -->
>  <daysDisplayNotActive>1,2,3,4,5,6,7</daysDisplayNotActive>
>  <displayOnTime>06:30</displayOnTime>
>  <displayOnDuration>12:00</displayOnDuration>
>  <displayIdleTimeout>00:01</displayIdleTimeout>
>  <spanToPCPort>1</spanToPCPort>
>  <loggingDisplay>1</loggingDisplay>
>  <loadServer></loadServer>
> </vendorConfig>
> <versionStamp></versionStamp>
> <userLocale>
>  <name>English_United_States</name>
> <uid>1</uid>
>  <langCode>en_US</langCode>
> <version>1.0.0.0-1</version>
>  <winCharSet>iso-8859-1</winCharSet>
> </userLocale>
> <networkLocale>United_States</networkLocale>
> <networkLocaleInfo>
>  <name>United_States</name>
> <uid>64</uid>
>  <version>1.0.0.0-1</version>
> </networkLocaleInfo>
> <deviceSecurityMode>0</deviceSecurityMode>
> <!--
> <authenticationURL>http://yourwebserver/authenticate.php</authenticationURL>
> <directoryURL>http://yourwebserver/directory.xml</directoryURL>
> -->
> <authenticationURL></authenticationURL>
> <directoryURL></directoryURL>
> <idleURL></idleURL>
> <informationURL></informationURL>
> <messagesURL></messagesURL>
> <proxyServerURL></proxyServerURL>
> <!--
> <servicesURL>http://phone-xml.berbee.com/menu.xml</servicesURL>
> -->
> <dscpForSCCPPhoneConfig>96</dscpForSCCPPhoneConfig>
> <dscpForSCCPPhoneServices>0</dscpForSCCPPhoneServices>
> <dscpForCm2Dvce>96</dscpForCm2Dvce>
> <transportLayerProtocol>2</transportLayerProtocol>
> <capfAuthMode>0</capfAuthMode>
> <capfList>
>  <capf>
>   <phonePort>3804</phonePort>
>  </capf>
> </capfList>
> <certHash></certHash>
> <encrConfig>false</encrConfig>
> </device
>
>
>
>
>> On Feb 12, 2021, at 4:10 PM, John Novack SCII_U <jn...@co... <mailto:jn...@co...>> wrote:
>>
>> Does the phone have the SIP firmware load?
>> I believe the 7940/7960 series can have more than one type of firmware, Sip, one for the Cisco Call Manager, and possibly one other
>> You would need the SIP firmware, and if it was used with Call Manager, probably doesn't have it
>> Not sure you can obtain it if you aren't hooked up with Cisco.
>> Aren't these phones now EOL, or nearly so?
>>
>> John Novack
>>
>>
>> Jerry Gartner wrote:
>>> I want to use some Cisco 7942's from a retired Cisco system. Being of newb, what are best practices for this? Are there provision templates available for these phones? Should they be factory reset? Etcetera, etcetera.
>>>
>>> -- 
>>> Kind Regards,
>>> Jerry Gartner
>>
>> -- 
>> Dog is my Co-Pilot
>> _______________________________________________
>> Astlinux-users mailing list
>> Ast...@li... <mailto:Ast...@li...>
>> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>>
>> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
>
-- 
Dog is my Co-Pilot

Re: [Astlinux-users] Cisco 7942 use

[John N. S. <jn...@co...>]

You will need to find a way to load SIP firmware then
And I believe you need several versions, and step through them to get to the latest
It will have to come through someone with Cisco connections, AFAIK the firmware is not publicly available
John Novack


Jerry Gartner wrote:
> I see SCCP firmware but no SIP firmware. They were EOL as of Jan. 31st.
>
> --
> Kind Regards,
>
> Jerry Gartner
> 920-547-4407
>
>
> On Fri, Feb 12, 2021 at 4:11 PM John Novack SCII_U <jn...@co... <mailto:jn...@co...>> wrote:
>
>     Does the phone have the SIP firmware load?
>     I believe the 7940/7960 series can have more than one type of firmware, Sip, one for the Cisco Call Manager, and possibly one other
>     You would need the SIP firmware, and if it was used with Call Manager, probably doesn't have it
>     Not sure you can obtain it if you aren't hooked up with Cisco.
>     Aren't these phones now EOL, or nearly so?
>
>     John Novack
>
>
>     Jerry Gartner wrote:
>>     I want to use some Cisco 7942's from a retired Cisco system. Being of newb, what are best practices for this? Are there provision templates available for these phones?
>>     Should they be factory reset? Etcetera, etcetera.
>>
>>     -- 
>>     Kind Regards,
>>     Jerry Gartner
>
>     -- 
>     Dog is my Co-Pilot
>

-- 
Dog is my Co-Pilot

Re: [Astlinux-users] Cisco 7942 use

[John N. S. <jn...@co...>]

Does the phone have the SIP firmware load?
I believe the 7940/7960 series can have more than one type of firmware, Sip, one for the Cisco Call Manager, and possibly one other
You would need the SIP firmware, and if it was used with Call Manager, probably doesn't have it
Not sure you can obtain it if you aren't hooked up with Cisco.
Aren't these phones now EOL, or nearly so?

John Novack


Jerry Gartner wrote:
> I want to use some Cisco 7942's from a retired Cisco system. Being of newb, what are best practices for this? Are there provision templates available for these phones? Should 
> they be factory reset? Etcetera, etcetera.
>
> -- 
> Kind Regards,
> Jerry Gartner

-- 
Dog is my Co-Pilot

[Astlinux-users] Cisco 7942 use

[Jerry G. <jer...@gm...>]

I want to use some Cisco 7942's from a retired Cisco system. Being of newb,
what are best practices for this? Are there provision templates
available for these phones? Should they be factory reset? Etcetera,
etcetera.

--
Kind Regards,
Jerry Gartner

Re: [Astlinux-users] python on astlinux

[Doron K. <dor...@gm...>]

Awesome! Thank you so much. I will look into all proposals.

Doron

On Thu, Feb 4, 2021, 5:25 AM David Kerr <da...@ke...> wrote:

> Hi Doron, thanks for your interest in astlinux.  The subject of a package
> manager has come up before and the decision has always been no.  So to add
> python you would need to build your own custom astlinux.  Before you
> run away, building astlinux is not that hard, many users choose to do that
> so they can add specific packages they need, instructions are on the
> website.  As for python, I just gave it a go and was able to build it so
> long as I did not add in the optional packages.  The version of python in
> astlinux's package probably needs to be brought up-to-date (it is 2.7.1
> whereas buildroot is at 2.7.18) and we would need to figure out why some of
> the optional packages fail to build if there are any you need.
>
> If you are familiar with building linux / buildroot then do give it a go
> and let us know.  If you need help don't hesitate to ask over on the
> astlinux developers mailing list.
>
> Thanks
> David
>
> On Thu, Feb 4, 2021 at 12:47 AM Doron Keller <dor...@gm...>
> wrote:
>
>> Hello and please excuse the newby question, I stumbled on this project
>> accidentally and it seems to be everything I was looking for.
>>
>> Is it possible to get python and/or a package manager on the system? I
>> saw there is perl but python could save me much development time.
>>
>> Thanks!
>> _______________________________________________
>> 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....

Re: [Astlinux-users] python on astlinux

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

Hi Doron, thanks for your interest in astlinux.  The subject of a package
manager has come up before and the decision has always been no.  So to add
python you would need to build your own custom astlinux.  Before you
run away, building astlinux is not that hard, many users choose to do that
so they can add specific packages they need, instructions are on the
website.  As for python, I just gave it a go and was able to build it so
long as I did not add in the optional packages.  The version of python in
astlinux's package probably needs to be brought up-to-date (it is 2.7.1
whereas buildroot is at 2.7.18) and we would need to figure out why some of
the optional packages fail to build if there are any you need.

If you are familiar with building linux / buildroot then do give it a go
and let us know.  If you need help don't hesitate to ask over on the
astlinux developers mailing list.

Thanks
David

On Thu, Feb 4, 2021 at 12:47 AM Doron Keller <dor...@gm...> wrote:

> Hello and please excuse the newby question, I stumbled on this project
> accidentally and it seems to be everything I was looking for.
>
> Is it possible to get python and/or a package manager on the system? I saw
> there is perl but python could save me much development time.
>
> Thanks!
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....

Re: [Astlinux-users] python on astlinux

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

> On Feb 3, 2021, at 11:47 PM, Doron Keller <dor...@gm...> wrote:
> 
> Hello and please excuse the newby question, I stumbled on this project accidentally and it seems to be everything I was looking for.
> 
> Is it possible to get python and/or a package manager on the system? I saw there is perl but python could save me much development time.

Hi Doron,

Thanks for reaching out.

AstLinux does not natively support python in our efficient 60 MB compressed image.

We do offer: bash, php, perl (limited modules), lua (version 5.1)

Alternatively, AstLinux does support LXC containers:

https://doc.astlinux-project.org/userdoc:guest_lxc_container_main

As such, you could create a Debian LXC, and install python.  Not sure what you are trying to do, but if network communication to your python LXC work for you, that may be a possible solution.

Lonnie

[Astlinux-users] python on astlinux

[Doron K. <dor...@gm...>]

Hello and please excuse the newby question, I stumbled on this project
accidentally and it seems to be everything I was looking for.

Is it possible to get python and/or a package manager on the system? I saw
there is perl but python could save me much development time.

Thanks!

[Astlinux-users] Announcing AstLinux Release: 1.4.1

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

Announcing AstLinux Release: 1.4.1

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

AstLinux 1.4.1 Highlights:
* Asterisk Versions: 13.29.2, 13.38.1, 16.15.1
* Linux Kernel 4.19.167, security and bug fixes
* RUNNIX, version bump to runnix-0.6.3, with Linux Kernel 4.19.167, kexec 2.0.21
* OpenSSL, version bump to 1.1.1i, security fix
* WireGuard VPN, module 1.0.20210124 (version bump), tools 1.0.20200827 (no change)
* dnsmasq, version bump to 2.84, important security fixes
* getdns/stubby, remove package, replace getdns/stubby with unbound for DNS-over-TLS
* unbound, version bump to 1.13.0
* PPPoE client, reimplement using the latest pppd 2.4.9 pppoe kernel driver and our custom scripts
* rng-tools, jitterentropy version bump to 3.0.1 (2x improved performance on APU systems)
* sudo, critical security fix
* sngrep, version bump to 1.4.8
* zabbix, version bump to 4.0.27
* Package upgrades providing important security and bug fixes

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

All users are encouraged to upgrade.

AstLinux Team

Re: [Astlinux-users] Ddclient update

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

Thanks Gonzalo for the info.

When we gat a chance we will take a look at it.

Lonnie



> On Feb 1, 2021, at 12:14 PM, Gonzalo Ibáñez <gon...@ho...> wrote:
> 
> Hi,
> 
> Thanks, I try to explain full details:
> 
> I have 2 free DDNS providers: Changeip (configured from GUI) and Afraid.org (configured in a custom script executed after boot from /mnt/kd/rc.local).
> 
> Apparently both are working fine and everytime there's an IP address change both domains are updated, but while there's no IP change after each check the first one is flooding logs with error messages showing it tries to update domain with a void IP field:
> 
> "Feb  1 18:27:42 astlinux daemon.notice ddclient[2135]: WARNING:  SENT:    http://nic.changeip.com/nic/update/nic/update?hostname=domain.changeip.org&ip=
> Feb  1 18:27:42 astlinux daemon.notice ddclient[2135]: WARNING:  REPLIED: 506 Invalid IP address submitted.  Check syntax.
> Feb  1 18:27:42 astlinux daemon.notice ddclient[2135]: FAILED:   updating domain.changeip.org: Invalid reply."
> 
> (*) Note the first log line in which the IP field sent at the end of the URL is void
> 
> 
> If I look at the file /var/db/ddclient.cache generated by first ddclient daemon, the IP field is missing:
> 
> "## ddclient-3.8.3-07
> ## last updated at Mon Feb  1 18:32:42 2021 (1612200762)
> atime=1612200762,host=domain.changeip.org,mtime=0,status=failed,status-ipv6=,warned-min-error-interval=0,warned-min-interval=0,wtime=0 domain.changeip.org"
> 
> And if I look at the file /var/db/ddclient_2.cache generated by the second ddclient daemon the IP field is present:
> 
> "## ddclient-3.8.3-07
> ## last updated at Sun Jan 31 15:41:32 2021 (1612104092)
> atime=0,host=domain.privatedns.org,ip=XXX.XXX.XXX.XXX,mtime=1612103790,status=good,status-ipv6=,warned-min-error-interval=0,warned-min-interval=0,wtime=30 domain.privatedns.org"
> 
> 
> I'm not sure if the problem is exactly the same but I found this link reporting very similar behaviour which seems solved in latest ddclient versions:
> 
> https://github.com/linuxserver/docker-ddclient/issues/11
> 
> 
> Regards.
> ------------------
> 
> > On Jan 31, 2021, at 9:14 AM, Gonzalo Ib??ez <gon...@ho...> wrote:
> > 
> > Hi,
> > 
> > Any chance of getting ddclient updated (v3.9.1 is the latest) on next astlinux release?
> > 
> > I'm getting some errors with some domain providers (ex. Changeip) because of ddclient sending a void IP address when trying to perform domain updates and I've read there've been some changes on APIs which should be included on latest version.
> 
> Hi Gonzalo,
> 
> Can you describe your errors in more detail.
> 
> We don't use the original ddclient, but rather a fork that uses curl:
> 
> https://github.com/astlinux-project/ddclient-curl
> 
> If you find the fix in the original ddclient we can look at back-porting it to ours.
> 
> Lonnie
> 
> 
> 
> 
> ------------------------------
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> 
> ------------------------------
> 
> End of Astlinux-users Digest, Vol 174, Issue 1
> **********************************************
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
> 
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....

Re: [Astlinux-users] Astlinux-users Digest, Vol 174, Issue 1

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

Hi,

Thanks, I try to explain full details:

I have 2 free DDNS providers: Changeip (configured from GUI) and Afraid.org (configured in a custom script executed after boot from /mnt/kd/rc.local).

Apparently both are working fine and everytime there's an IP address change both domains are updated, but while there's no IP change after each check the first one is flooding logs with error messages showing it tries to update domain with a void IP field:

"Feb  1 18:27:42 astlinux daemon.notice ddclient[2135]: WARNING:  SENT:    http://nic.changeip.com/nic/update/nic/update?hostname=domain.changeip.org&ip=
Feb  1 18:27:42 astlinux daemon.notice ddclient[2135]: WARNING:  REPLIED: 506 Invalid IP address submitted.  Check syntax.
Feb  1 18:27:42 astlinux daemon.notice ddclient[2135]: FAILED:   updating domain.changeip.org: Invalid reply."

(*) Note the first log line in which the IP field sent at the end of the URL is void


If I look at the file /var/db/ddclient.cache generated by first ddclient daemon, the IP field is missing:

"## ddclient-3.8.3-07
## last updated at Mon Feb  1 18:32:42 2021 (1612200762)
atime=1612200762,host=domain.changeip.org,mtime=0,status=failed,status-ipv6=,warned-min-error-interval=0,warned-min-interval=0,wtime=0 domain.changeip.org"

And if I look at the file /var/db/ddclient_2.cache generated by the second ddclient daemon the IP field is present:

"## ddclient-3.8.3-07
## last updated at Sun Jan 31 15:41:32 2021 (1612104092)
atime=0,host=domain.privatedns.org,ip=XXX.XXX.XXX.XXX,mtime=1612103790,status=good,status-ipv6=,warned-min-error-interval=0,warned-min-interval=0,wtime=30 domain.privatedns.org"


I'm not sure if the problem is exactly the same but I found this link reporting very similar behaviour which seems solved in latest ddclient versions:

https://github.com/linuxserver/docker-ddclient/issues/11


Regards.
------------------

> On Jan 31, 2021, at 9:14 AM, Gonzalo Ib??ez <gon...@ho...> wrote:
>
> Hi,
>
> Any chance of getting ddclient updated (v3.9.1 is the latest) on next astlinux release?
>
> I'm getting some errors with some domain providers (ex. Changeip) because of ddclient sending a void IP address when trying to perform domain updates and I've read there've been some changes on APIs which should be included on latest version.

Hi Gonzalo,

Can you describe your errors in more detail.

We don't use the original ddclient, but rather a fork that uses curl:

https://github.com/astlinux-project/ddclient-curl

If you find the fix in the original ddclient we can look at back-porting it to ours.

Lonnie




------------------------------



------------------------------

Subject: Digest Footer

_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users


------------------------------

End of Astlinux-users Digest, Vol 174, Issue 1
**********************************************

Re: [Astlinux-users] Ddclient update

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

> On Jan 31, 2021, at 9:14 AM, Gonzalo Ibáñez <gon...@ho...> wrote:
> 
> Hi,
> 
> Any chance of getting ddclient updated (v3.9.1 is the latest) on next astlinux release?
> 
> I'm getting some errors with some domain providers (ex. Changeip) because of ddclient sending a void IP address when trying to perform domain updates and I've read there've been some changes on APIs which should be included on latest version.

Hi Gonzalo,

Can you describe your errors in more detail.

We don't use the original ddclient, but rather a fork that uses curl:

https://github.com/astlinux-project/ddclient-curl

If you find the fix in the original ddclient we can look at back-porting it to ours.

Lonnie

[Astlinux-users] Ddclient update

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

Hi,

Any chance of getting ddclient updated (v3.9.1 is the latest) on next astlinux release?

I'm getting some errors with some domain providers (ex. Changeip) because of ddclient sending a void IP address when trying to perform domain updates and I've read there've been some changes on APIs which should be included on latest version.

Regards.

Re: [Astlinux-users] Metering all traffic

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

> Am 27.01.2021 um 08:34 schrieb Michael Keuter <li...@mk...>:
> 
> Yes, vnStat looks very promising.
> 
> Sent from a mobile device.
> 
> Michael Keuter

BTW: This looks quite nice:

https://humdi.net/vnstat/cgidemo/

>> Am 27.01.2021 um 05:27 schrieb David Kerr <da...@ke...>:
>> 
>> 
>> Lonnie,
>>   That is very interesting, I would love to have that as part of astlinux.  We may be missing some dependencies, it says it needs libgd for the graphs.  But I would find the data it collects and shows more useful than what we have with Netstat/darkstat today.
>> 
>> David.
>> 
>> On Tue, Jan 26, 2021 at 9:56 PM Lonnie Abelbeck <li...@lo...> wrote:
>> Hi David,
>> 
>> In upstream Buildroot there is a "vnStat" package.
>> 
>> Seems like exactly what you are after, uses sqlite for storage.
>> 
>> https://humdi.net/vnstat/
>> 
>> Might be a good addition to AstLinux.
>> 
>> Lonnie
>> 
>> 
>> 
>> > On Jan 26, 2021, at 4:26 PM, David Kerr <da...@ke...> wrote:
>> > 
>> > Here is what I have done so far. In the network init script I have added the following...
>> > 
>> > echo $(date +%s.%3N; cat /sys/class/net/$EXTIF/statistics/rx_bytes; cat /sys/class/net/$EXTIF/statistics/tx_bytes) "stop" >> /var/log/$EXTIF-meter.txt
>> > 
>> > right before the ip link set dev $EXTIF down.  I did the same for EXT2IF and a "start" log immediately after every place the EXTIF/EXT2IF is brought up.
>> > 
>> > Then I added the following to crontabs...
>> > 
>> > 59 * * * * echo $(date +%s.%3N; cat /sys/class/net/eth0/statistics/rx_bytes; cat /sys/class/net/eth0/statistics/tx_bytes) "cron" >> /var/log/eth0-meter.txt
>> > 59 * * * * echo $(date +%s.%3N; cat /sys/class/net/eth2/statistics/rx_bytes; cat /sys/class/net/eth2/statistics/tx_bytes) "cron" >> /var/log/eth2-meter.txt
>> > 
>> > Is there a way to get $EXTxx variables in crontabs?
>> > 
>> > After rebooting and waiting for the big hand to point at the number 12, here is my eth0 log...
>> > 
>> > pbx kd # cat log/eth0-meter.txt
>> > 1611696594.726 41916587023 8211080131 stop
>> > 1611696625.644 0 0 start
>> > 1611698340.940 832008278 51755144 cron
>> > 
>> > So now I think I can just gather all the data and I should be able to create a script to read and sum things up... last hour, last day, last week, last month, whatever.  Could probably import to excel for fancy graphs.  But patience required, will have to wait a while before I have enough data to play with.
>> > 
>> > I suppose I could do this for INTIF's as well.
>> > 
>> > David
>> > 
>> > 
>> > On Tue, Jan 26, 2021 at 12:42 PM Lonnie Abelbeck <li...@lo...> wrote:
>> > David,
>> > 
>> > If you are happy with Netstat/darkstat there is a way to save and reload that data to persistent storage.  Years ago this caused issues, but may work today, and with a rc.conf variable option to enable it.
>> > 
>> > Without looking, basically the darkstat.init needs to be tweaked.
>> > 
>> > Lonnie
>> > 
>> > 
>> > 
>> > 
>> > > On Jan 26, 2021, at 10:45 AM, David Kerr <da...@ke...> wrote:
>> > > 
>> > > ifconfig/ip -s probably reports closest to what the ISP is metering.
>> > > And I assume that is what Netstat/darkstat is measuring.  But the data
>> > > on that tab is reset every reboot. I assume the interface RX/TX bytes
>> > > are reset to zero on boot (and/or on taking the interface down/up).  I
>> > > would need to make sure to capture the values on shutdown... and maybe
>> > > at regular intervals.  Any suggestions on how to capture final values
>> > > as an interface is shutdown?
>> > > 
>> > > Measuring in iptables might provide more granularity, but may not map
>> > > as closely to the raw data comcast measure.
>> > > 
>> > > David
>> > > 
>> > > On Tue, Jan 26, 2021 at 10:57 AM Lonnie Abelbeck
>> > > <li...@lo...> wrote:
>> > >> 
>> > >> 
>> > >> 
>> > >>> On Jan 26, 2021, at 8:29 AM, Michael Keuter <li...@mk...> wrote:
>> > >>> 
>> > >>> 
>> > >>> 
>> > >>>> Am 26.01.2021 um 15:08 schrieb David Kerr <da...@ke...>:
>> > >>>> 
>> > >>>> As some of you may be aware, Comcast / Xfinity are starting to impose
>> > >>>> monthly data caps on internet usage.  Where I live it is 1.2TB a
>> > >>>> month.  So I just received the dreaded "You have used 75% of your
>> > >>>> allowance" email.  Fortunately only 5 days from the end of the month,
>> > >>>> but looking back there are months that I have exceeded the cap.
>> > >>>> 
>> > >>>> Can I do anything in Astlinux to meter usage myself?  I would want to
>> > >>>> monitor raw traffic in and out on eth0, the totals would need to
>> > >>>> survive reboot, I would want to reset on the first of each month and
>> > >>>> maintain a history.  For extra credit... be able to identify high
>> > >>>> users on my internal network(s).
>> > >>>> 
>> > >>>> Any ideas?  Have any other gateways (like OpenWRT) tackled this?
>> > >>>> 
>> > >>>> Thanks
>> > >>>> David
>> > >>> 
>> > >>> Hi David,
>> > >>> 
>> > >>> most applications that I know use RRDtool (a Round-Robin-database to store data/measurements) as its basis, like Munin, Cacti, MRTG etc.
>> > >>> 
>> > >>> https://en.wikipedia.org/wiki/RRDtool
>> > >>> 
>> > >>> It is also available in BR2.
>> > >>> Years ago I had hacked myself a Munin node (client) for AstLinux, so data could fetched from a Munin server on Debian in my network from my AstLinux boxes. But it does not work anymore or I forgot about it. But it created nice progress graphicss for some parameters (CPU load, traffic, Asterisk calls, etc.).
>> > >>> 
>> > >>> Now since we're using SSDs instead CF cards it would be nice to have such application.
>> > >>> My 2 cts.
>> > >>> 
>> > >>> Michael
>> > >> 
>> > >> If we are mostly interesting in network info:
>> > >> 
>> > >> ip -s link show dev eth0
>> > >> --or--
>> > >> ifconfig eth0
>> > >> 
>> > >> provides network interface usage.  On shutdown and/or regular cron this info would need to be saved to persistent storage along with the sample date.
>> > >> 
>> > >> Though corner cases when the eth0 link goes down or a PPPoE ppp0 interface comes and goes can make pure interface monitoring less accurate.
>> > >> 
>> > >> An AIF plugin could be added to do something similar, which would be required if forwarded LAN -> WAN traffic was to be recorded.  Though the matching WAN -> LAN traffic might be a little tricky.
>> > >> 
>> > >> Then the little matter of what the ISP says the data is vs. your actual data.
>> > >> 
>> > >> 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....
>> 
>> 
>> 
>> _______________________________________________
>> 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....


Michael

http://www.mksolutions.info

Re: [Astlinux-users] Metering all traffic

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

Yes, vnStat looks very promising.

Sent from a mobile device.

Michael Keuter

> Am 27.01.2021 um 05:27 schrieb David Kerr <da...@ke...>:
> 
> 
> Lonnie,
>   That is very interesting, I would love to have that as part of astlinux.  We may be missing some dependencies, it says it needs libgd for the graphs.  But I would find the data it collects and shows more useful than what we have with Netstat/darkstat today.
> 
> David.
> 
>> On Tue, Jan 26, 2021 at 9:56 PM Lonnie Abelbeck <li...@lo...> wrote:
>> Hi David,
>> 
>> In upstream Buildroot there is a "vnStat" package.
>> 
>> Seems like exactly what you are after, uses sqlite for storage.
>> 
>> https://humdi.net/vnstat/
>> 
>> Might be a good addition to AstLinux.
>> 
>> Lonnie
>> 
>> 
>> 
>> > On Jan 26, 2021, at 4:26 PM, David Kerr <da...@ke...> wrote:
>> > 
>> > Here is what I have done so far. In the network init script I have added the following...
>> > 
>> > echo $(date +%s.%3N; cat /sys/class/net/$EXTIF/statistics/rx_bytes; cat /sys/class/net/$EXTIF/statistics/tx_bytes) "stop" >> /var/log/$EXTIF-meter.txt
>> > 
>> > right before the ip link set dev $EXTIF down.  I did the same for EXT2IF and a "start" log immediately after every place the EXTIF/EXT2IF is brought up.
>> > 
>> > Then I added the following to crontabs...
>> > 
>> > 59 * * * * echo $(date +%s.%3N; cat /sys/class/net/eth0/statistics/rx_bytes; cat /sys/class/net/eth0/statistics/tx_bytes) "cron" >> /var/log/eth0-meter.txt
>> > 59 * * * * echo $(date +%s.%3N; cat /sys/class/net/eth2/statistics/rx_bytes; cat /sys/class/net/eth2/statistics/tx_bytes) "cron" >> /var/log/eth2-meter.txt
>> > 
>> > Is there a way to get $EXTxx variables in crontabs?
>> > 
>> > After rebooting and waiting for the big hand to point at the number 12, here is my eth0 log...
>> > 
>> > pbx kd # cat log/eth0-meter.txt
>> > 1611696594.726 41916587023 8211080131 stop
>> > 1611696625.644 0 0 start
>> > 1611698340.940 832008278 51755144 cron
>> > 
>> > So now I think I can just gather all the data and I should be able to create a script to read and sum things up... last hour, last day, last week, last month, whatever.  Could probably import to excel for fancy graphs.  But patience required, will have to wait a while before I have enough data to play with.
>> > 
>> > I suppose I could do this for INTIF's as well.
>> > 
>> > David
>> > 
>> > 
>> > On Tue, Jan 26, 2021 at 12:42 PM Lonnie Abelbeck <li...@lo...> wrote:
>> > David,
>> > 
>> > If you are happy with Netstat/darkstat there is a way to save and reload that data to persistent storage.  Years ago this caused issues, but may work today, and with a rc.conf variable option to enable it.
>> > 
>> > Without looking, basically the darkstat.init needs to be tweaked.
>> > 
>> > Lonnie
>> > 
>> > 
>> > 
>> > 
>> > > On Jan 26, 2021, at 10:45 AM, David Kerr <da...@ke...> wrote:
>> > > 
>> > > ifconfig/ip -s probably reports closest to what the ISP is metering.
>> > > And I assume that is what Netstat/darkstat is measuring.  But the data
>> > > on that tab is reset every reboot. I assume the interface RX/TX bytes
>> > > are reset to zero on boot (and/or on taking the interface down/up).  I
>> > > would need to make sure to capture the values on shutdown... and maybe
>> > > at regular intervals.  Any suggestions on how to capture final values
>> > > as an interface is shutdown?
>> > > 
>> > > Measuring in iptables might provide more granularity, but may not map
>> > > as closely to the raw data comcast measure.
>> > > 
>> > > David
>> > > 
>> > > On Tue, Jan 26, 2021 at 10:57 AM Lonnie Abelbeck
>> > > <li...@lo...> wrote:
>> > >> 
>> > >> 
>> > >> 
>> > >>> On Jan 26, 2021, at 8:29 AM, Michael Keuter <li...@mk...> wrote:
>> > >>> 
>> > >>> 
>> > >>> 
>> > >>>> Am 26.01.2021 um 15:08 schrieb David Kerr <da...@ke...>:
>> > >>>> 
>> > >>>> As some of you may be aware, Comcast / Xfinity are starting to impose
>> > >>>> monthly data caps on internet usage.  Where I live it is 1.2TB a
>> > >>>> month.  So I just received the dreaded "You have used 75% of your
>> > >>>> allowance" email.  Fortunately only 5 days from the end of the month,
>> > >>>> but looking back there are months that I have exceeded the cap.
>> > >>>> 
>> > >>>> Can I do anything in Astlinux to meter usage myself?  I would want to
>> > >>>> monitor raw traffic in and out on eth0, the totals would need to
>> > >>>> survive reboot, I would want to reset on the first of each month and
>> > >>>> maintain a history.  For extra credit... be able to identify high
>> > >>>> users on my internal network(s).
>> > >>>> 
>> > >>>> Any ideas?  Have any other gateways (like OpenWRT) tackled this?
>> > >>>> 
>> > >>>> Thanks
>> > >>>> David
>> > >>> 
>> > >>> Hi David,
>> > >>> 
>> > >>> most applications that I know use RRDtool (a Round-Robin-database to store data/measurements) as its basis, like Munin, Cacti, MRTG etc.
>> > >>> 
>> > >>> https://en.wikipedia.org/wiki/RRDtool
>> > >>> 
>> > >>> It is also available in BR2.
>> > >>> Years ago I had hacked myself a Munin node (client) for AstLinux, so data could fetched from a Munin server on Debian in my network from my AstLinux boxes. But it does not work anymore or I forgot about it. But it created nice progress graphicss for some parameters (CPU load, traffic, Asterisk calls, etc.).
>> > >>> 
>> > >>> Now since we're using SSDs instead CF cards it would be nice to have such application.
>> > >>> My 2 cts.
>> > >>> 
>> > >>> Michael
>> > >> 
>> > >> If we are mostly interesting in network info:
>> > >> 
>> > >> ip -s link show dev eth0
>> > >> --or--
>> > >> ifconfig eth0
>> > >> 
>> > >> provides network interface usage.  On shutdown and/or regular cron this info would need to be saved to persistent storage along with the sample date.
>> > >> 
>> > >> Though corner cases when the eth0 link goes down or a PPPoE ppp0 interface comes and goes can make pure interface monitoring less accurate.
>> > >> 
>> > >> An AIF plugin could be added to do something similar, which would be required if forwarded LAN -> WAN traffic was to be recorded.  Though the matching WAN -> LAN traffic might be a little tricky.
>> > >> 
>> > >> Then the little matter of what the ISP says the data is vs. your actual data.
>> > >> 
>> > >> 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....
>> 
>> 
>> 
>> _______________________________________________
>> 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....

Re: [Astlinux-users] Metering all traffic

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

Lonnie,
  That is very interesting, I would love to have that as part of astlinux.
We may be missing some dependencies, it says it needs libgd for the
graphs.  But I would find the data it collects and shows more useful than
what we have with Netstat/darkstat today.

David.

On Tue, Jan 26, 2021 at 9:56 PM Lonnie Abelbeck <li...@lo...>
wrote:

> Hi David,
>
> In upstream Buildroot there is a "vnStat" package.
>
> Seems like exactly what you are after, uses sqlite for storage.
>
> https://humdi.net/vnstat/
>
> Might be a good addition to AstLinux.
>
> Lonnie
>
>
>
> > On Jan 26, 2021, at 4:26 PM, David Kerr <da...@ke...> wrote:
> >
> > Here is what I have done so far. In the network init script I have added
> the following...
> >
> > echo $(date +%s.%3N; cat /sys/class/net/$EXTIF/statistics/rx_bytes; cat
> /sys/class/net/$EXTIF/statistics/tx_bytes) "stop" >>
> /var/log/$EXTIF-meter.txt
> >
> > right before the ip link set dev $EXTIF down.  I did the same for EXT2IF
> and a "start" log immediately after every place the EXTIF/EXT2IF is brought
> up.
> >
> > Then I added the following to crontabs...
> >
> > 59 * * * * echo $(date +%s.%3N; cat
> /sys/class/net/eth0/statistics/rx_bytes; cat
> /sys/class/net/eth0/statistics/tx_bytes) "cron" >> /var/log/eth0-meter.txt
> > 59 * * * * echo $(date +%s.%3N; cat
> /sys/class/net/eth2/statistics/rx_bytes; cat
> /sys/class/net/eth2/statistics/tx_bytes) "cron" >> /var/log/eth2-meter.txt
> >
> > Is there a way to get $EXTxx variables in crontabs?
> >
> > After rebooting and waiting for the big hand to point at the number 12,
> here is my eth0 log...
> >
> > pbx kd # cat log/eth0-meter.txt
> > 1611696594.726 41916587023 8211080131 stop
> > 1611696625.644 0 0 start
> > 1611698340.940 832008278 51755144 cron
> >
> > So now I think I can just gather all the data and I should be able to
> create a script to read and sum things up... last hour, last day, last
> week, last month, whatever.  Could probably import to excel for fancy
> graphs.  But patience required, will have to wait a while before I have
> enough data to play with.
> >
> > I suppose I could do this for INTIF's as well.
> >
> > David
> >
> >
> > On Tue, Jan 26, 2021 at 12:42 PM Lonnie Abelbeck <
> li...@lo...> wrote:
> > David,
> >
> > If you are happy with Netstat/darkstat there is a way to save and reload
> that data to persistent storage.  Years ago this caused issues, but may
> work today, and with a rc.conf variable option to enable it.
> >
> > Without looking, basically the darkstat.init needs to be tweaked.
> >
> > Lonnie
> >
> >
> >
> >
> > > On Jan 26, 2021, at 10:45 AM, David Kerr <da...@ke...> wrote:
> > >
> > > ifconfig/ip -s probably reports closest to what the ISP is metering.
> > > And I assume that is what Netstat/darkstat is measuring.  But the data
> > > on that tab is reset every reboot. I assume the interface RX/TX bytes
> > > are reset to zero on boot (and/or on taking the interface down/up).  I
> > > would need to make sure to capture the values on shutdown... and maybe
> > > at regular intervals.  Any suggestions on how to capture final values
> > > as an interface is shutdown?
> > >
> > > Measuring in iptables might provide more granularity, but may not map
> > > as closely to the raw data comcast measure.
> > >
> > > David
> > >
> > > On Tue, Jan 26, 2021 at 10:57 AM Lonnie Abelbeck
> > > <li...@lo...> wrote:
> > >>
> > >>
> > >>
> > >>> On Jan 26, 2021, at 8:29 AM, Michael Keuter <li...@mk...>
> wrote:
> > >>>
> > >>>
> > >>>
> > >>>> Am 26.01.2021 um 15:08 schrieb David Kerr <da...@ke...>:
> > >>>>
> > >>>> As some of you may be aware, Comcast / Xfinity are starting to
> impose
> > >>>> monthly data caps on internet usage.  Where I live it is 1.2TB a
> > >>>> month.  So I just received the dreaded "You have used 75% of your
> > >>>> allowance" email.  Fortunately only 5 days from the end of the
> month,
> > >>>> but looking back there are months that I have exceeded the cap.
> > >>>>
> > >>>> Can I do anything in Astlinux to meter usage myself?  I would want
> to
> > >>>> monitor raw traffic in and out on eth0, the totals would need to
> > >>>> survive reboot, I would want to reset on the first of each month and
> > >>>> maintain a history.  For extra credit... be able to identify high
> > >>>> users on my internal network(s).
> > >>>>
> > >>>> Any ideas?  Have any other gateways (like OpenWRT) tackled this?
> > >>>>
> > >>>> Thanks
> > >>>> David
> > >>>
> > >>> Hi David,
> > >>>
> > >>> most applications that I know use RRDtool (a Round-Robin-database to
> store data/measurements) as its basis, like Munin, Cacti, MRTG etc.
> > >>>
> > >>> https://en.wikipedia.org/wiki/RRDtool
> > >>>
> > >>> It is also available in BR2.
> > >>> Years ago I had hacked myself a Munin node (client) for AstLinux, so
> data could fetched from a Munin server on Debian in my network from my
> AstLinux boxes. But it does not work anymore or I forgot about it. But it
> created nice progress graphicss for some parameters (CPU load, traffic,
> Asterisk calls, etc.).
> > >>>
> > >>> Now since we're using SSDs instead CF cards it would be nice to have
> such application.
> > >>> My 2 cts.
> > >>>
> > >>> Michael
> > >>
> > >> If we are mostly interesting in network info:
> > >>
> > >> ip -s link show dev eth0
> > >> --or--
> > >> ifconfig eth0
> > >>
> > >> provides network interface usage.  On shutdown and/or regular cron
> this info would need to be saved to persistent storage along with the
> sample date.
> > >>
> > >> Though corner cases when the eth0 link goes down or a PPPoE ppp0
> interface comes and goes can make pure interface monitoring less accurate.
> > >>
> > >> An AIF plugin could be added to do something similar, which would be
> required if forwarded LAN -> WAN traffic was to be recorded.  Though the
> matching WAN -> LAN traffic might be a little tricky.
> > >>
> > >> Then the little matter of what the ISP says the data is vs. your
> actual data.
> > >>
> > >> 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....
>
>
>
> _______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to
> pa...@kr....
>

Re: [Astlinux-users] Metering all traffic

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

Hi David,

In upstream Buildroot there is a "vnStat" package.

Seems like exactly what you are after, uses sqlite for storage.

https://humdi.net/vnstat/

Might be a good addition to AstLinux.

Lonnie



> On Jan 26, 2021, at 4:26 PM, David Kerr <da...@ke...> wrote:
> 
> Here is what I have done so far. In the network init script I have added the following...
> 
> echo $(date +%s.%3N; cat /sys/class/net/$EXTIF/statistics/rx_bytes; cat /sys/class/net/$EXTIF/statistics/tx_bytes) "stop" >> /var/log/$EXTIF-meter.txt
> 
> right before the ip link set dev $EXTIF down.  I did the same for EXT2IF and a "start" log immediately after every place the EXTIF/EXT2IF is brought up.
> 
> Then I added the following to crontabs...
> 
> 59 * * * * echo $(date +%s.%3N; cat /sys/class/net/eth0/statistics/rx_bytes; cat /sys/class/net/eth0/statistics/tx_bytes) "cron" >> /var/log/eth0-meter.txt
> 59 * * * * echo $(date +%s.%3N; cat /sys/class/net/eth2/statistics/rx_bytes; cat /sys/class/net/eth2/statistics/tx_bytes) "cron" >> /var/log/eth2-meter.txt
> 
> Is there a way to get $EXTxx variables in crontabs?
> 
> After rebooting and waiting for the big hand to point at the number 12, here is my eth0 log...
> 
> pbx kd # cat log/eth0-meter.txt
> 1611696594.726 41916587023 8211080131 stop
> 1611696625.644 0 0 start
> 1611698340.940 832008278 51755144 cron
> 
> So now I think I can just gather all the data and I should be able to create a script to read and sum things up... last hour, last day, last week, last month, whatever.  Could probably import to excel for fancy graphs.  But patience required, will have to wait a while before I have enough data to play with.
> 
> I suppose I could do this for INTIF's as well.
> 
> David
> 
> 
> On Tue, Jan 26, 2021 at 12:42 PM Lonnie Abelbeck <li...@lo...> wrote:
> David,
> 
> If you are happy with Netstat/darkstat there is a way to save and reload that data to persistent storage.  Years ago this caused issues, but may work today, and with a rc.conf variable option to enable it.
> 
> Without looking, basically the darkstat.init needs to be tweaked.
> 
> Lonnie
> 
> 
> 
> 
> > On Jan 26, 2021, at 10:45 AM, David Kerr <da...@ke...> wrote:
> > 
> > ifconfig/ip -s probably reports closest to what the ISP is metering.
> > And I assume that is what Netstat/darkstat is measuring.  But the data
> > on that tab is reset every reboot. I assume the interface RX/TX bytes
> > are reset to zero on boot (and/or on taking the interface down/up).  I
> > would need to make sure to capture the values on shutdown... and maybe
> > at regular intervals.  Any suggestions on how to capture final values
> > as an interface is shutdown?
> > 
> > Measuring in iptables might provide more granularity, but may not map
> > as closely to the raw data comcast measure.
> > 
> > David
> > 
> > On Tue, Jan 26, 2021 at 10:57 AM Lonnie Abelbeck
> > <li...@lo...> wrote:
> >> 
> >> 
> >> 
> >>> On Jan 26, 2021, at 8:29 AM, Michael Keuter <li...@mk...> wrote:
> >>> 
> >>> 
> >>> 
> >>>> Am 26.01.2021 um 15:08 schrieb David Kerr <da...@ke...>:
> >>>> 
> >>>> As some of you may be aware, Comcast / Xfinity are starting to impose
> >>>> monthly data caps on internet usage.  Where I live it is 1.2TB a
> >>>> month.  So I just received the dreaded "You have used 75% of your
> >>>> allowance" email.  Fortunately only 5 days from the end of the month,
> >>>> but looking back there are months that I have exceeded the cap.
> >>>> 
> >>>> Can I do anything in Astlinux to meter usage myself?  I would want to
> >>>> monitor raw traffic in and out on eth0, the totals would need to
> >>>> survive reboot, I would want to reset on the first of each month and
> >>>> maintain a history.  For extra credit... be able to identify high
> >>>> users on my internal network(s).
> >>>> 
> >>>> Any ideas?  Have any other gateways (like OpenWRT) tackled this?
> >>>> 
> >>>> Thanks
> >>>> David
> >>> 
> >>> Hi David,
> >>> 
> >>> most applications that I know use RRDtool (a Round-Robin-database to store data/measurements) as its basis, like Munin, Cacti, MRTG etc.
> >>> 
> >>> https://en.wikipedia.org/wiki/RRDtool
> >>> 
> >>> It is also available in BR2.
> >>> Years ago I had hacked myself a Munin node (client) for AstLinux, so data could fetched from a Munin server on Debian in my network from my AstLinux boxes. But it does not work anymore or I forgot about it. But it created nice progress graphicss for some parameters (CPU load, traffic, Asterisk calls, etc.).
> >>> 
> >>> Now since we're using SSDs instead CF cards it would be nice to have such application.
> >>> My 2 cts.
> >>> 
> >>> Michael
> >> 
> >> If we are mostly interesting in network info:
> >> 
> >> ip -s link show dev eth0
> >> --or--
> >> ifconfig eth0
> >> 
> >> provides network interface usage.  On shutdown and/or regular cron this info would need to be saved to persistent storage along with the sample date.
> >> 
> >> Though corner cases when the eth0 link goes down or a PPPoE ppp0 interface comes and goes can make pure interface monitoring less accurate.
> >> 
> >> An AIF plugin could be added to do something similar, which would be required if forwarded LAN -> WAN traffic was to be recorded.  Though the matching WAN -> LAN traffic might be a little tricky.
> >> 
> >> Then the little matter of what the ISP says the data is vs. your actual data.
> >> 
> >> 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....

Re: [Astlinux-users] Metering all traffic

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

Here is what I have done so far. In the network init script I have added
the following...

echo $(date +%s.%3N; cat /sys/class/net/$EXTIF/statistics/rx_bytes; cat
/sys/class/net/$EXTIF/statistics/tx_bytes) "stop" >>
/var/log/$EXTIF-meter.txt

right before the ip link set dev $EXTIF down.  I did the same for EXT2IF
and a "start" log immediately after every place the EXTIF/EXT2IF is brought
up.

Then I added the following to crontabs...

59 * * * * echo $(date +%s.%3N; cat
/sys/class/net/eth0/statistics/rx_bytes; cat
/sys/class/net/eth0/statistics/tx_bytes) "cron" >> /var/log/eth0-meter.txt
59 * * * * echo $(date +%s.%3N; cat
/sys/class/net/eth2/statistics/rx_bytes; cat
/sys/class/net/eth2/statistics/tx_bytes) "cron" >> /var/log/eth2-meter.txt

Is there a way to get $EXTxx variables in crontabs?

After rebooting and waiting for the big hand to point at the number 12,
here is my eth0 log...

pbx kd # cat log/eth0-meter.txt
1611696594.726 41916587023 8211080131 stop
1611696625.644 0 0 start
1611698340.940 832008278 51755144 cron

So now I think I can just gather all the data and I should be able to
create a script to read and sum things up... last hour, last day, last
week, last month, whatever.  Could probably import to excel for fancy
graphs.  But patience required, will have to wait a while before I have
enough data to play with.

I suppose I could do this for INTIF's as well.

David


On Tue, Jan 26, 2021 at 12:42 PM Lonnie Abelbeck <li...@lo...>
wrote:

> David,
>
> If you are happy with Netstat/darkstat there is a way to save and reload
> that data to persistent storage.  Years ago this caused issues, but may
> work today, and with a rc.conf variable option to enable it.
>
> Without looking, basically the darkstat.init needs to be tweaked.
>
> Lonnie
>
>
>
>
> > On Jan 26, 2021, at 10:45 AM, David Kerr <da...@ke...> wrote:
> >
> > ifconfig/ip -s probably reports closest to what the ISP is metering.
> > And I assume that is what Netstat/darkstat is measuring.  But the data
> > on that tab is reset every reboot. I assume the interface RX/TX bytes
> > are reset to zero on boot (and/or on taking the interface down/up).  I
> > would need to make sure to capture the values on shutdown... and maybe
> > at regular intervals.  Any suggestions on how to capture final values
> > as an interface is shutdown?
> >
> > Measuring in iptables might provide more granularity, but may not map
> > as closely to the raw data comcast measure.
> >
> > David
> >
> > On Tue, Jan 26, 2021 at 10:57 AM Lonnie Abelbeck
> > <li...@lo...> wrote:
> >>
> >>
> >>
> >>> On Jan 26, 2021, at 8:29 AM, Michael Keuter <li...@mk...>
> wrote:
> >>>
> >>>
> >>>
> >>>> Am 26.01.2021 um 15:08 schrieb David Kerr <da...@ke...>:
> >>>>
> >>>> As some of you may be aware, Comcast / Xfinity are starting to impose
> >>>> monthly data caps on internet usage.  Where I live it is 1.2TB a
> >>>> month.  So I just received the dreaded "You have used 75% of your
> >>>> allowance" email.  Fortunately only 5 days from the end of the month,
> >>>> but looking back there are months that I have exceeded the cap.
> >>>>
> >>>> Can I do anything in Astlinux to meter usage myself?  I would want to
> >>>> monitor raw traffic in and out on eth0, the totals would need to
> >>>> survive reboot, I would want to reset on the first of each month and
> >>>> maintain a history.  For extra credit... be able to identify high
> >>>> users on my internal network(s).
> >>>>
> >>>> Any ideas?  Have any other gateways (like OpenWRT) tackled this?
> >>>>
> >>>> Thanks
> >>>> David
> >>>
> >>> Hi David,
> >>>
> >>> most applications that I know use RRDtool (a Round-Robin-database to
> store data/measurements) as its basis, like Munin, Cacti, MRTG etc.
> >>>
> >>> https://en.wikipedia.org/wiki/RRDtool
> >>>
> >>> It is also available in BR2.
> >>> Years ago I had hacked myself a Munin node (client) for AstLinux, so
> data could fetched from a Munin server on Debian in my network from my
> AstLinux boxes. But it does not work anymore or I forgot about it. But it
> created nice progress graphicss for some parameters (CPU load, traffic,
> Asterisk calls, etc.).
> >>>
> >>> Now since we're using SSDs instead CF cards it would be nice to have
> such application.
> >>> My 2 cts.
> >>>
> >>> Michael
> >>
> >> If we are mostly interesting in network info:
> >>
> >> ip -s link show dev eth0
> >> --or--
> >> ifconfig eth0
> >>
> >> provides network interface usage.  On shutdown and/or regular cron this
> info would need to be saved to persistent storage along with the sample
> date.
> >>
> >> Though corner cases when the eth0 link goes down or a PPPoE ppp0
> interface comes and goes can make pure interface monitoring less accurate.
> >>
> >> An AIF plugin could be added to do something similar, which would be
> required if forwarded LAN -> WAN traffic was to be recorded.  Though the
> matching WAN -> LAN traffic might be a little tricky.
> >>
> >> Then the little matter of what the ISP says the data is vs. your actual
> data.
> >>
> >> 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] AstLinux Pre-Release: astlinux-1.4-5001-4341d2 (Release Candidate1 pre-1.4.1)

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

Release Candidate1 pre-1.4.1, please report any issues, ASAP.

The next AstLinux version will be 1.4.1, most notably switching to the Linux kernel 4.19.x LTS series.

** IMPORTANT NOTICE

-- The ipsec-tools (racoon) support in AstLinux is deprecated, and will be removed in the near future.
	The development of ipsec-tools has been ABANDONED.
	The Network tab -> VPN Type: "IPsec Peers" and "IPsec Mobile" is the web interface configuration for ipsec-tools.
	The AstLinux Team suggests using either WireGuard or OpenVPN for your VPN needs, but if IPsec is required for
	compatibility reasons the Network tab -> VPN Type: "IPsec strongSwan" should be able to do what you want,
	albeit in a less than ideal text based configuration.
	More info: https://doc.astlinux-project.org/userdoc:tt_ipsec_vpn_strongswan

** 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.167 (version bump), security and bug fixes

-- RUNNIX, version bump to runnix-0.6.3, with Linux Kernel 4.19.167, kexec 2.0.21

-- OpenSSL, version bump to 1.1.1i, security fix: CVE-2020-1971

-- WireGuard VPN, module 1.0.20210124 (version bump), tools 1.0.20200827 (no change)

-- libcurl (curl) version bump to 7.74.0, security fixes: CVE-2020-8284, CVE-2020-8285, CVE-2020-8286

-- dnsmasq, version bump to 2.84, security fixes: CVE-2020-25684, CVE-2020-25685, CVE-2020-25686

-- getdns/stubby, remove package, replace getdns/stubby with unbound for DNS-over-TLS

-- unbound, version bump to 1.13.0

-- PPPoE client, reimplement using the latest pppd 2.4.9 pppoe kernel driver and our custom scripts

-- rng-tools, jitterentropy version bump to 3.0.1 (2x improved performance on APU systems)

-- miniupnpd, version 2.1, add Debian security fixes: CVE-2019-12107, CVE-2019-12108
	CVE-2019-12109, CVE-2019-12110, CVE-2019-12111

-- sngrep, version bump to 1.4.8

-- Monit, version bump to 5.27.2

-- zabbix, version bump to 4.0.27

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

-- Asterisk 13.38.1 (version bump) and 16.15.1 (version bump)

-- Add support for directory /var/spool/asterisk/outgoing_tmp for call file staging.

-- Add support for persistent /mnt/kd/call-file/ directory for certain tmpfs spool directories.
	If the directory /mnt/kd/call-file/ exists, the following symlinks will automatically occur:
	== /var/spool/asterisk/outgoing -> /mnt/kd/call-file/outgoing
	== /var/spool/asterisk/outgoing_tmp -> /mnt/kd/call-file/outgoing_tmp
	== /var/spool/asterisk/outgoing_done -> /mnt/kd/call-file/outgoing_done

-- 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

Re: [Astlinux-users] Metering all traffic

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

David,

If you are happy with Netstat/darkstat there is a way to save and reload that data to persistent storage.  Years ago this caused issues, but may work today, and with a rc.conf variable option to enable it.

Without looking, basically the darkstat.init needs to be tweaked.

Lonnie




> On Jan 26, 2021, at 10:45 AM, David Kerr <da...@ke...> wrote:
> 
> ifconfig/ip -s probably reports closest to what the ISP is metering.
> And I assume that is what Netstat/darkstat is measuring.  But the data
> on that tab is reset every reboot. I assume the interface RX/TX bytes
> are reset to zero on boot (and/or on taking the interface down/up).  I
> would need to make sure to capture the values on shutdown... and maybe
> at regular intervals.  Any suggestions on how to capture final values
> as an interface is shutdown?
> 
> Measuring in iptables might provide more granularity, but may not map
> as closely to the raw data comcast measure.
> 
> David
> 
> On Tue, Jan 26, 2021 at 10:57 AM Lonnie Abelbeck
> <li...@lo...> wrote:
>> 
>> 
>> 
>>> On Jan 26, 2021, at 8:29 AM, Michael Keuter <li...@mk...> wrote:
>>> 
>>> 
>>> 
>>>> Am 26.01.2021 um 15:08 schrieb David Kerr <da...@ke...>:
>>>> 
>>>> As some of you may be aware, Comcast / Xfinity are starting to impose
>>>> monthly data caps on internet usage.  Where I live it is 1.2TB a
>>>> month.  So I just received the dreaded "You have used 75% of your
>>>> allowance" email.  Fortunately only 5 days from the end of the month,
>>>> but looking back there are months that I have exceeded the cap.
>>>> 
>>>> Can I do anything in Astlinux to meter usage myself?  I would want to
>>>> monitor raw traffic in and out on eth0, the totals would need to
>>>> survive reboot, I would want to reset on the first of each month and
>>>> maintain a history.  For extra credit... be able to identify high
>>>> users on my internal network(s).
>>>> 
>>>> Any ideas?  Have any other gateways (like OpenWRT) tackled this?
>>>> 
>>>> Thanks
>>>> David
>>> 
>>> Hi David,
>>> 
>>> most applications that I know use RRDtool (a Round-Robin-database to store data/measurements) as its basis, like Munin, Cacti, MRTG etc.
>>> 
>>> https://en.wikipedia.org/wiki/RRDtool
>>> 
>>> It is also available in BR2.
>>> Years ago I had hacked myself a Munin node (client) for AstLinux, so data could fetched from a Munin server on Debian in my network from my AstLinux boxes. But it does not work anymore or I forgot about it. But it created nice progress graphicss for some parameters (CPU load, traffic, Asterisk calls, etc.).
>>> 
>>> Now since we're using SSDs instead CF cards it would be nice to have such application.
>>> My 2 cts.
>>> 
>>> Michael
>> 
>> If we are mostly interesting in network info:
>> 
>> ip -s link show dev eth0
>> --or--
>> ifconfig eth0
>> 
>> provides network interface usage.  On shutdown and/or regular cron this info would need to be saved to persistent storage along with the sample date.
>> 
>> Though corner cases when the eth0 link goes down or a PPPoE ppp0 interface comes and goes can make pure interface monitoring less accurate.
>> 
>> An AIF plugin could be added to do something similar, which would be required if forwarded LAN -> WAN traffic was to be recorded.  Though the matching WAN -> LAN traffic might be a little tricky.
>> 
>> Then the little matter of what the ISP says the data is vs. your actual data.
>> 
>> 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....
> 
>