RazWall 1.0 Beta Build

[razwall]

Here is just a quick update on the fork of EndianCFW to RazWall.

A lot of things are still in the works. I will be cleaning up the files and structures to create the first github upload very soon. I hope people will arrive and assist in this process as things begin to pick up.
Here is the done list:

Dev Unit 1:
Remove EMI and related proprietary code. (remnants remain but are not used)
Replace efw-console I have implemented a very crude Perl based replacement
updated dashboard & overall theme
Added websocket service on Port 4000 on 127.0.0.1
Updated httpd configs and templates for proxy_wstunnel - Web socket gets proxy pass from wss://IP:10443/ws -> ws://127.0.0.1:4000
Step through code and remove all usage and mention of color zones (GREEN,BLUE,ORANGE,RED)
Step through code and replace colored zones with dynamic naming convention
Step through code and convert colored zone rules to named rules (GREEN,BLUE,ORANGE,RED) -> (LAN,WIFI,DMZ,WAN)

Dev unit 2:
Re organize all of the files structures to work primarily out of the /razwall directory
remove all path and mentions of Endian

Here is the to-do list:
Consolidate all the changes from Dev unit 1 and Dev unit 2
Re-work code to expand the DHCP scopes per naming zones
Add a section to create new rule sets so instead of just LAN,WIFI,DMZ,WAN we can add custom rulesets
Figure out a packaging routine
Figure out how to rework the ISO/USB packer routine/build environment
Figure out new setup/installer scripts/programs

I hope to get some volunteers to work on some of these projects, but i know I need to publish the code first!

Here are a few screenshots of my progress:

Dashboard/Theme, Console (simple for now), Zone Setup

[techdevel]

Hi,
Wonderful work. Thanks for sharing the details of development work. I am not good in the development side however i have used different open source firewall even recent dynfirewall as well.
I am also waiting to test and use the razwall and share my experience with you. I have following suggestions if seems okay to you.
1. It would be good if you share the folloiwng details in the github issues or documents on the main page.
2. IPfire is supporting very good feature list and if you allow me i can make a list of all those feature set which can be incorporated into your fork with some efforts.
3. please have a look on this project page [https://github.com/FoobarOy/foomuuri] because it is using nftables instead of iptables and it will be helpful.

I am sorry for suggestions at this stage of the project.

[razwall]

Welcome and thanks for posting! Any suggestions are welcome. I have added a your feature request for future development board of the forum. I do plan to add everything to Github I just haven't had the time and nothing is stable (everything is changing daily). once I have went through all of the code i will be posting everything.

[razwall]

I created a fork of the Foomuuri project for future reference. Thanks!

[razwall]

Quick update. Still stepping through the code, beginning to consolidate /var/efw/ config files into JSON so it can be called over the web socket. I have also been working at cleaning up the shell scripts. A lot of them are used to call system data for the emi that has been removed. The replacement scripts are in perl for consistentcy. I have created a developer board that shows the new filesystem layout (work in progress).