What's new

Entware-ng for arm, mipsel ....

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

A lot of nice package updates now.... particularly pleased about this
Code:
Upgrading syslog-ng on root from 2.1.4-1 to 3.8.1-3...
loads more functionality...
did the upgrade and collected some clashes?
Code:
Collected errors:
 * check_data_file_clashes: Package libeventlog wants to install file /opt/lib/libevtlog.so
    But that file is already provided by package  * eventlog
 * check_data_file_clashes: Package libeventlog wants to install file /opt/lib/libevtlog.so.0
    But that file is already provided by package  * eventlog
 * check_data_file_clashes: Package libeventlog wants to install file /opt/lib/libevtlog.so.0.0.0
    But that file is already provided by package  * eventlog

Anything i need to fix on my end?
 
Last edited:
Code:
opkg --autoremove remove syslog-ng
opkg install syslog-ng
opkg is too simple to resolve such kind of clashes, sorry.
Done!... thanks and no need to apologise... what you guys do for the community is awesome.
Really appreciate the fast response too :)

Note: /opt/etc/init.d/S01syslog-ng and /opt/etc/syslog-ng.conf are over written when you do this... don't forget to back up
 
Last edited:
Small observation: Transmission was also updated, but the About Dialog shows only "Transmission 2.92 (0)" - revision 0 is less as it was before the update... :rolleyes:
 
@joegreat, there's a good news. Some of unnamed infamous torrent search engine is back online, so we can automatically add appropriate trackers for new torrents. again:)
Done. Very helpful to get my 350 GByte download finished faster... :eek:
Code:
Processing torrent #90...
No additional trackers found, sorry.
Processing torrent #93...
No additional trackers found, sorry.
Processing torrent #94...
adding trackers for a69d91052a142ac91430facfb57e9c617260a063...
* udp://tracker.coppersurfer.tk:6969/announce... done.
* udp://tracker.leechers-paradise.org:6969/announce... done.
* udp://tracker.zer0day.to:1337/announce... failed.
* udp://tracker1.wasabii.com.tw:6969/scrape... done.
* http://mgtracker.org:6881/announce... done.
Processing torrent #95...
No additional trackers found, sorry.
Processing torrent #96...
No additional trackers found, sorry.
Processing torrent #97...
adding trackers for 849b91e3cd810c5f3a5aa497fc46da90b33b23bd...
* udp://tracker.sktorrent.net:6969/announce... done.
* udp://tracker.coppersurfer.tk:6969/announce... failed.
* udp://tracker.leechers-paradise.org:6969/announce... done.
* http://91.218.230.81:6969/announce... done.
* udp://tracker1.wasabii.com.tw:6969/scrape... done.
 
Last edited:
@joegreat, there's a good news. Some of unnamed infamous torrent search engine is back online, so we can automatically add appropriate trackers for new torrents. again:)

Hi ryzhov, followed the instrucctions from your link and got this error trying to run the update script, could you help trying to figure out where the error is coming from?

Unexpected response: <h1>401: Unauthorized</h1>Unauthorized User9091
Authorization: Basic #####################
User-Agent: transmission-remote/2.92 (0)
Accept: */*
Accept-Encoding: deflate, gzip

thanks in advance
 
Hi, Syslog-ng/entware question..... I'm trying to use encryption for loggly with syslog-ng... their community page says:

Quick TLS setup
There are going to be times when you're going to want your logs encrypted during transport. This is where TLS comes in. The quick setup will ensure that your logs go to Loggly encrypted, but it will skip the step where Loggly validates you (which prevents man-in-the-middle attacks). The configuration is similar to above, but for a couple changes within the destination.
template LogglyFormat { template("<${PRI}>1 ${ISODATE} ${HOST} ${PROGRAM} ${PID} ${MSGID} [026308d8-2b63-4225-8fe9-e01294b6e472@41058] $MSG\n");};

destination d_loggly {
tcp("logs-01.loggly.com" port(6514)
tls(peer-verify(required-untrusted) ca_dir('/opt/syslog-ng/keys/ca.d/'))
template(LogglyFormat));
};

log {
source(s_loggly);
destination(d_loggly);
};
### END Syslog Logging Directives for Loggly (myaccount.loggly.com) ###

You'll need to download Loggly's SSL certificate and the intermediate certificate from Starfield, called sf_bundle.crt. The certificates can be obtained by:
$ wget https://logdog.loggly.com/media/loggly.com.crt
$ wget https://certs.starfieldtech.com/repository/sf_bundle.crt

To verify, go ahead and double check the sha1sum or md5:
$ sha1sum sf_bundle.crt
9f4b50011bdeabda276c9dd08f32f545218ea1b7 sf_bundle.crt
$ md5sum sf_bundle.crt
f742e64a892167bb5b4a10da5a380425 sf_bundle.crt

The sha1 hash is displayed on the Starfield web page where you can also obtain the intermediary cert via the browser. You then need to concatenate both and put it into syslog-ng's CA directory:
$ cat {sf_bundle.crt,loggly.com.crt} > loggly_full.crt
$ mv loggly_full.crt /opt/syslog-ng/keys/ca.d/

Of course, you'll need to restart syslog-ng to see your changes take effect. You may want to start syslog-ng with the -d flag (for debug) so you can get an idea of what's happening. TLS can be a little tricky to get just right.

Anyone have an idea where is the CA directory on the entware version of syslog-ng or where to create it??

opkg file syslog-ng gives:
Code:
Package syslog-ng (3.8.1-3) is installed on root and has the following files:
/opt/lib/syslog-ng/libsyslogformat.so
/opt/lib/syslog-ng/libdbparser.so
/opt/etc/init.d/S01syslog-ng
/opt/lib/syslog-ng/libafsocket.so
/opt/lib/syslog-ng/libdisk-buffer.so
/opt/lib/syslog-ng/libdate.so
/opt/lib/syslog-ng/libkvformat.so
/opt/lib/syslog-ng/libgraphite.so
/opt/lib/syslog-ng/libafamqp.so
/opt/lib/libsyslog-ng-3.8.so.0
/opt/lib/syslog-ng/libafstomp.so
/opt/etc/syslog-ng.conf
/opt/lib/syslog-ng/libsdjournal.so
/opt/lib/syslog-ng/libadd-contextual-data.so
/opt/lib/libsyslog-ng-3.8.so.0.0.0
/opt/lib/syslog-ng/libcurl.so
/opt/lib/syslog-ng/liblinux-kmsg-format.so
/opt/lib/syslog-ng/libafuser.so
/opt/lib/libsyslog-ng.so
/opt/lib/syslog-ng/libpseudofile.so
/opt/lib/syslog-ng/libcsvparser.so
/opt/lib/syslog-ng/libcef.so
/opt/lib/syslog-ng/libcryptofuncs.so
/opt/lib/syslog-ng/libafprog.so
/opt/lib/syslog-ng/libbasicfuncs.so
/opt/lib/syslog-ng/libsystem-source.so
/opt/sbin/syslog-ng-ctl
/opt/lib/syslog-ng/libaffile.so
/opt/lib/syslog-ng/libconfgen.so
/opt/sbin/syslog-ng

Appreciate any insight...thanks
 
@joegreat, there's a good news. Some of unnamed infamous torrent search engine is back online, so we can automatically add appropriate trackers for new torrents. again:)
Hi,

Thank you. Could you please help?
It is any possibility to schedule the add_trackers.sh script to run automatically after new torrent addition?

PS: I got it. In settings.json from transmission I found:
Code:
"script-torrent-added-enabled": false,
"script-torrent-added-filename": "",


Many thanks!
 
Last edited:
Anyone have an idea where is the CA directory on the entware version of syslog-ng or where to create it??
If you install ca-certificates or ca-bundle
Code:
opkg install ca-certificates
you'll find out, that certificates are installed in /opt/etc/ssl/certs in entware
 
Thanks Zyxmon
If you install ca-certificates or ca-bundle
Code:
opkg install ca-certificates
you'll find out, that certificates are installed in /opt/etc/ssl/certs in entware
So i can just put the loggly_full.cert in the same directory and point the directive at it then?
Code:
destination d_loggly {
tcp("logs-01.loggly.com" port(6514)
tls(peer-verify(required-untrusted) ca_dir('/opt/etc/ssl/certs/'))
template(LogglyFormat));
};

whats the difference between ca-certificates and ca-bundle?
 
Last edited:
Please, fix transmission login credentials at 4-th line of /opt/bin/add_trackers.sh
Script is working only if the transmissionbt username & password are the same as router ui credentials, "unfortunately" password from settings.json file is hex encrypted and can't be pull out by the script.
Maybe someone else has any ideea?
 
@joegreat, there's a good news. Some of unnamed infamous torrent search engine is back online, so we can automatically add appropriate trackers for new torrents. again:)
Hi,

I am using your add_trackers script but today I recognized that it did not work anymore: all torrents failed to be found. :confused:

After looking on the homepage I found out that https://torrentz2.eu switched to HTTPS only...

By updating the command line for wget with --no-check-certificate it works again!
Maybe you find the time to add this option to the script on github. :rolleyes:

With kind regards
Joe
 
I raised a issue (request) in upstream 15 days ago so that we get an updated binary in entware-ng when it is released next. Is there anything more I need to do?
 
Hi,

I am using your add_trackers script but today I recognized that it did not work anymore: all torrents failed to be found. :confused:

After looking on the homepage I found out that https://torrentz2.eu switched to HTTPS only...

By updating the command line for wget with --no-check-certificate it works again!
Maybe you find the time to add this option to the script on github. :rolleyes:

With kind regards
Joe
Thanks. Or use mirror of https://torrentz2.eu: http://torrentz2.me which is still http.

BR.
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top