are there any one who knows if the TR-069 issupported by openWRT ?
thanks for your help

I to think this is important to some of the commercial deployments it appears OpenWRT is being used in. Wither TR-069 or CWMP - I'm not sure which would be better of OpenWRT

Since there isn't an mature OS TR-069 solution, prob need to look at the larger community. Here are two OS CPE projects:
http://code.google.com/p/tr069/
http://sourceforge.net/projects/cpe/
Got to check out wikipedia http://en.wikipedia.org/wiki/TR-069

I think the route for the service providers to go would be to bundle one of the proprietary stacks for now while helping dev one of the OS projects.

TR-069 Prob isnt going to cover everything OpenWRT user want. Perhaps a better solution would be a cgi interface or a ssh interface to update a master xml file that could parsed. When settings and locations change the update infrastructure can stay the same and the parser is changed. Heck Funambol's device management may even be used??? Or a we could do like IP phones and just check for updated config xml from http/tftp address.

-Tom

(Last edited by tomdavidson on 19 Oct 2008, 10:25)

Hi kallel ,
I am also having the same requirement for tr069 support in openwrt.
Please let me know, how did you proceed further?

Thanks!

TR-069 to me is clearly a massive intrusion into a system's integrity and a potential break of the end user's privacy.
Such a "feature" is only requested by commercial ISP or major vendors. And if they really need it they should contribute to the community by providing a free, open and reliable implementation of it.

Knox:

TR69 is not a massive intrusion on system integrity. It is a management, configuration and support feature essential to large Service Providers to support mass updates of firmware in the field and to do preventative troubleshooting. In contrast to something like VNC, SNMP or even just plain old telnet or SSH, if some change occurs on the CPE side, the device sends a notice (an INFORM) to the Service Provider's auto configuration server (e.g., the ACS), and based on a stored profile of the customer's account, the change is logged, allowed or disallowed, and if disallowed, the ACS responds with a set of commands to reset the change. This happens based on rules in the ACS without manual intervention. Very slick and very scalable, and no support calls that cost them $40 per ticket.

Essentially, it's a remote control app for configuration, management and support. While not the lightest weight protocol around, it has proven very scalable and secure, which is one reason almost all the consumer ADSL service providers use it.

It is true, however, that the concept of TR69 goes against the grain of a lot of OpenWRT (and general) users. For example, many Service Providers charge the user for the CPE, so the customer thinks they own it. In the terms of service, it usually states otherwise. This managed CPE belongs to the Service Provider-- and the customer paid for it, which is a benefit to the Service Provider, not the customer. Ouch.

I can see a TR69 CPE client integrated into OpenWRT quite nicely using UCI commands. This actually solves the biggest issue with commercial Linux offerings... the lack of a consistent management interface to system internals. But some commercial Linux offerings support add on commercial TR69 clients out of the box, but for a hefty cost. For example, Jungo charges NRE ~$50K and a per unit license fee of $5-$20 depending on features and volume.

marc.

No offence. But from my point of view, a "remote control app" remains an intrusion into the system. Especially if it acts without the device owner's interaction or even knowledge. It might claim to fullfill support and maintenance tasks but in fact it opens a back door to full remote control over a system. One could also call it trojan horse, not?

As i said before: if one desperatly needs it (for example an ISP or a hardware vendor) it is highly appreciated to contribute a free and open implementation to the community.

May the source be with you :-)

I have made GPLv2 TR-069 client - freecwmp. You can get it here:

http://www.freecwmp.org/

It's working with several ACS servers.

Questions, info, etc. on the mailing list freecwmp #at# linux-mips.org or on the IRC freenode channel #freecwmp

I developed a cwmp client under the GPLv2 (open source). It's complete and fully conform with the TR069 standard. you can get it from http://www.easycwmp.org

you are so greate ! like you!

you are so greate ,like you!

I have tried your code,but i failed.I compiled it with the openwrt_SDK .the info as following,can you give me a hand,thanks ahead!
../src/cwmp.h:63: error: field 'list' has incomplete type
../src/cwmp.h:80: error: field 'list' has incomplete type
../src/cwmp.h:86: error: field 'list' has incomplete type
../src/cwmp.h:99: error: field 'list' has incomplete type
../src/cwmp.h:114: error: field 'events' has incomplete type
../src/cwmp.h:115: error: field 'notifications' has incomplete type
../src/cwmp.h:116: error: field 'downloads' has incomplete type
../src/cwmp.h:117: error: field 'scheduled_informs' has incomplete type
make[5]: *** [easycwmpd-backup.o] Error 1
make[5]: Leaving directory `/home/nickli/openwrt/backfire/build_dir/target-i386_uClibc-0.9.30.1/easycwmp/easycwmp-1.1.2/bin'
make[4]: *** [all-recursive] Error 1
make[3]: *** [/home/nickli/openwrt/backfire/build_dir/target-i386_uClibc-0.9.30.1/easycwmp/easycwmp-1.1.2/.built] Error 2
make[2]: *** [package/easycwmp/compile] Error 2
make[4]: Leaving directory `/home/nickli/openwrt/backfire/build_dir/target-i386_uClibc-0.9.30.1/easycwmp/easycwmp-1.1.2'
make[3]: Leaving directory `/home/nickli/openwrt/backfire/package/easycwmp'
make[2]: Leaving directory `/home/nickli/openwrt/backfire'
make[1]: *** [/home/nickli/openwrt/backfire/staging_dir/target-i386_uClibc-0.9.30.1/stamp/.package_compile] Error 2
make[1]: Leaving directory `/home/nickli/openwrt/backfire'
make: *** [world] 错误 2

yeah,I have download your source code into openwrt-sdk  on my local compiling envirenment （Ubuntu 14.04） ,but i can't compile it successfully, as a chinese please forgive  my bad english . thanks

Please post your question http://support.easycwmp.org

Hi, Has anyone any information on either:
1) How to FreeCWMP to connect to an ACS (I have installed GenieACS to test but it refuses to connect)
2) An actual easy to install version of EasyCWMP, from what I can see it needs to be compiled and the developer has not provided a package which can be automatically installed.

Thanks in Advance

Jerome