I have been working with Shorewall on Openwrt and as most know it uses BusyBox for a majority of its tools. I have run into a problem using 4.05 when creating TC rules that will fail on with the built in sed of BusyBox.
I have seen that there has been some compatibility created in the past for Openwrt to resolve some of these types of problems. I was wondering what the chances are that sed in the shell scripts could be modified to use a variable that could be configured in the shorewall.conf file? I have created gnu sed packages that I am using on the system. The default scripts in Openwrt expect the responses from BusyBoxe's sed. So I just named the new sed package to sed-gnu. In doing this I can get the advance use of gnu sed that Shorewall needs and the BusyBox sed that Openwrt needs. I have then modified all of the shell scripts and libraries to use the sed-gnu binary instead. I know this may not be the best fix, but at least it would give some flexibility for some of the embedded systems. I am willing to create a diff that would have this already done and I could submit this if the Shorewall crew would accept it. I don't like to have to maintain my own versions of this type of thing, it makes upgrading and management a nightmare. Please let me know what everyone thinks. Philip ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
