freeacs/freeacs-next

(WIP) A project to revitalize the FreeACS project

ARCHIVED!

Due to inactivity for several years and because no one wanted to maintain it, this project and all other projects in this org is archived.

FreeACS Next

The goal of this project is to combine that which has previously been developed and deployed individually in the FreeACS project.

This project will serve the following purposes:

1. Provisioning server
2. Administration gui
3. Scheduler
4. ++

The project is built with a minimal version of the Play framework which in turn is built on top of Akka HTTP. Its using Slick for asynchronous data access, Play Cache for caching things like unit type, groups, jobs etc (the cache can be easily distributed with hazelcast), and uses plain and core Scala to do the stuff that needs to be coded. For an object oriented programmer there is no big jumps needed to understand this code base. Another reason to avoid using advanced scala libraries is to be ready for Scala 3 aka Dotty in 2020.

Send an inform

1. Change the digest.secret in application.conf
2. Start the application either with sbt run or from your preferred IDE
3. Send an Inform to the acs like the curl below:

curl -v -d '<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:cwmp="urn:dslforum-org:cwmp-1-2"><SOAP-ENV:Header><cwmp:ID SOAP-ENV:mustUnderstand="1">1</cwmp:ID></SOAP-ENV:Header><SOAP-ENV:Body><cwmp:Inform><DeviceId><Manufacturer>FakeManufacturer</Manufacturer><OUI>000000</OUI><ProductClass>FakeProductClass</ProductClass><SerialNumber>FakeSerialNumber</SerialNumber></DeviceId><Event SOAP-ENC:arrayType="cwmp:EventStruct[3]"><EventStruct><EventCode>0 BOOTSTRAP</EventCode><CommandKey>TR069_FakeManufacturer_HOMEGATEWAY</CommandKey></EventStruct><EventStruct><EventCode>1 BOOT</EventCode><CommandKey></CommandKey></EventStruct><EventStruct><EventCode>4 VALUE CHANGE</EventCode><CommandKey></CommandKey></EventStruct></Event><MaxEnvelopes>1</MaxEnvelopes><CurrentTime>1970-01-02T00:08:34</CurrentTime><RetryCount>0</RetryCount><ParameterList SOAP-ENC:arrayType="cwmp:ParameterValueStruct[10]"><ParameterValueStruct><Name>InternetGatewayDevice.DeviceSummary</Name><Value xsi:type="xsd:string">InternetGatewayDevice:1.0[](Baseline:1, EthernetLAN:4,GE:4,WiFi:1,PONWAN:1, Voip:0, Time:1, IPPing:1)</Value></ParameterValueStruct><ParameterValueStruct><Name>InternetGatewayDevice.DeviceInfo.SpecVersion</Name><Value xsi:type="xsd:string">1.0</Value></ParameterValueStruct><ParameterValueStruct><Name>InternetGatewayDevice.DeviceInfo.HardwareVersion</Name><Value xsi:type="xsd:string">V5.2</Value></ParameterValueStruct><ParameterValueStruct><Name>InternetGatewayDevice.DeviceInfo.SoftwareVersion</Name><Value xsi:type="xsd:string">V5.2.10P4T26</Value></ParameterValueStruct></ParameterList></cwmp:Inform></SOAP-ENV:Body></SOAP-ENV:Envelope>' \
    -H "Content-Type: text/xml"  \
    --digest -u test:test \
    -X POST http://localhost:9000/tr069

freeacs-next's Issues

Find out what the heck is wrong with get parameter names trying to recreate existing params

Re-Implement first and last connect timestamp

I need to always update/insert LastConnectTimestamp and insert FirstConnectTimestamp if not exists.

Re-Implement Kick functionality

Kick is inherently extremely simple. Either we do have connectionrequest params or we dont. If we do. Use them to kick device with a http request with basic header. Done. No fuzz

Re-implement TR-069 Basic Provisioning

Following things must be implemented:

1. IN -> INr, including auto discovery of unit, authentication etc.
   DONE
2. IN -> INr -> EM -> [GPN -> GPNr ->] GPV -> GPVr -> SPV -> SPVr -> EM
   Partially done, tr069 controller will automatically answer EM with dummy GPV and onwards.
   Done:

• If Discover param is 1, or if discovery mode is true, or if deviceParameters.length == 0 (meaning only system params)
  • GPN: Ask CPE for parameter names in <Keyroot>.ManagementServer. (or be explicit)
  • GPNr: Store all parameters in unit type that does not already exist
• GPV/GPVr: Ask CPE for all values to parameters with Read Always flag
• SPV/SPVr: Ask CPE to set new values for parameters that has different values in ACS (for initial provisioning this is obviously none). Always set new semi random PII.

What about Shell scripts, is it possible?

Re-implement auto generating new semirandom PeriodInformInterval