Done: http://openwrt.glowingmonkey.org/trunk/
It’s junk a simple wget --mirror job, and the main index page still points to openwrt.wk.cz, but the lower links should work.
Does anybody know possible way just change asterisk default configuration files of the image (.gz file), without rebuilding it? I tried to use 7-ZIP. It allow me to change files of the image without extracting it. But when I upgraded asterisk configuration files of the image, image become unable to import into metarouter. Metarouter says “Archive is too short”
Second thin is, yesterday I had power issue and router rebooted. But /etc/asterisk/users.conf file has broken. Just became blank file. All other files “/etc/asterisk/extensions.conf, /etc/asterisk/extconfig.conf” are OK. How can I automate process “backup users.conf file every day and replace original users.conf by this backup file after every reboot occurs”
Well, it’s not just a .gz (gzip) file, it’s a .tgz / .tar.gz file, so it’s a compressed “tarball”. I have no familiarity with 7-ZIP, but a quick Google reveals it to be a Windows-based multiformat compressed archive utility. If you are modifying the tarball with 7-ZIP, and RouterOS can no longer import it after that, then it seems clear that 7-ZIP is doing something wrong, and is corrupting the file when you try to use 7-ZIP to modify the file. So…moral of the story is, don’t use 7-ZIP, I guess. Something must be buggy either with its TAR support, or its GZIP support.
I have never bothered to try to modify the MetaROUTER tarball images directly, because I’ve had no need to. If I want to make a change, I always make it in the OpenWRT build environment. However, in theory, making your own tarball without recompiling everything should be possible. Rather than using 7-ZIP, why don’t you use the actual tools that made the file in the first place? tar and gzip. Decompress the file somewhere, make the changes that you want to the directory tree you unpacked from the tarball, and then recompress the entire directory tree again into a new compressed tarball.
Long term, if you are going to be making many changes, it would serve you best to teach yourself how to perform an OpenWRT build.
Sounds like an issue similar to what others were seeing with http.conf corruption after not shutting down the system cleanly. You might look back through this thread for other posts on the subject. I think some people may be creating cron jobs to schedule config backups, and then adding their own shell scripts to /etc/init.d that restore the latest backup during bootup. I haven’t looked into it myself.
Quite honestly, if you are unfamiliar with basic UNIX system administration concepts (such as using tar and/or gzip, cron, shell scripts, and the init bootup process), you’re probably going to have a tough time maintaining an Asterisk system. I am trying to make my MetaROUTER image as plug-and-play and “turnkey” as possible, but obviously it isn’t there yet. It’s a project I’ve been working on in my spare time and that I’ve voluntarily given back to the community. But I cannot reasonably be expected to support every single person that uses it, and help them make their own custom changes to it; I don’t have the time to train people how to use it correctly, much less do things with it or to it that it doesn’t do already. I am offering it freely “as-is”, so if it serves your purposes as-is, then great! And although I welcome feedback when things don’t work, as that will help make it better, if you need something other than what I’ve provided, you should be willing to take the time to teach yourself how to make it, and then get your hands dirty, or find someone you can pay to do what you need.
Finally I got my own Asterisk OWRT image. Just modified after extracted and re-archived it to tgz using Tarball. Works great on RB450G, RB2011, RB1100AH.
Not sure why this wasn’t done before or what I’ve broken in the process;
I’ve taken the latest OpenWRT Backfire snapshot (r33081). I then applied the metarouter patches to the longterm 2.6.32 kernel which is 2.6.32.61 at the time of writing. This is the 2.6.x with the latest projected EOL, somewhere Mid-2014 probably. I build a rootfs, it boots, but that’s as far as I’ve tested it.
I’m a bit unsure how to proceed now, do I try and get ‘Attitude Adjustment’ to run a 2.6.32 kernel? Or do I try to get the metarouter patches to work for the 3.x kernel?
I’m well aware where and when Backfire was branched from the trunk I also never mentioned 3.2, I’m aware that has been removed too. What I said was that I had a working 2.6.32.61 kernel, and then asked how to proceed Do I try and get the current OpenWRT trunk to work with my 2.6.32.61 kernel or do I try and get some 3.x kernel to boot on MetaRouter?
Fact of the matter is that I’m working on patches to get 3.x working, the bare kernel which would then compile both in buildroot and OpenWRT. Current state is that I have it compiling, booting and I even hacked a debug console in there so I can see where it hangs (because it does before hvc0 can come up). I guess it’s a matter of debugging now
liquidcz, can you add to your repository 2 packages: redsocks and srelay, please. I cannot compile this sources for mr-mips arch. But this packages very need for me
I used to have a lot of options (all in this thread and many other) for the images they reboot the router at boot OpenWRT. Can you show what specific image will work with RB OmniTIK U-5HnD?
If I want to build my image, that is the question:
Necessarily need a Mikrotik patch?
When building OpenWRT which target platform must be chosen without the patch for RB OmniTIK U-5HnD?
Building openwrt patching it and so forth is a bit beyond my scope.
I want to run openwrt and openl2tp, but I cant find a build package for it. (I’m just looking for a lt2p client that I can run inside mikrotik metarouter that support shared secret without ipsec).
Mainly this post is addressed to Nathan and liquidcz
Is there a possibility to add to Nathan’s openwrt asterisk the firewall fail2ban ?
The reason is that we are getting lots of attack attempts from the internet, with fail2ban firewall we could subscribe (freely) to networksystemssolution.info
all attacks will be registered and therefore added to the blacklist.
Having this added to the image will make everyone’s life simple.
I am sure someone have noticed that due to the large amount of attacks the “/var/log/asterisk/messages.log” is getting very large hence rendering the asterisk unstable, slow and sometimes dead until next reboot.
If someone wondered why the asterisk (that is on public IP) becoming dead or slow the answer is the “messages.log” became too big.
Thank you for letting me know if that is possible.