Red Bear OS
aa6bf0f2ea
CRITICAL BUG FIX: is_echo_request() and track_icmp() were reading ctx.packet[0] thinking it was the ICMP type byte. But ctx.packet is the IP packet, so offset 0 is the IP version/IHL byte (0x45 for IPv4). Result: ICMP echo detection NEVER matched Type 8 packets. - ICMP rate limiting (R32) was a no-op — wrong byte read - ICMP echo tracking in track_icmp() was checking IP version vs 8/128 Fixed: read ICMP type from offset for IPv4, or offset 40 for IPv6. ALSO: separate TCP SYN and ICMP echo rate limit maps. Previously both shared one BTreeMap, so a host doing 100 TCP SYNs + 1 ICMP echo would be over-limit. Now each has its own budget. NEW TESTS (4 conntrack + 5 filter table = 9 total, all passing): - syn_limit_triggers_after_threshold - icmp_limit_triggers_after_threshold - syn_and_icmp_have_independent_budgets - non_syn_tcp_does_not_count_against_syn_limit These tests caught the ICMP type bug — failed before fix, pass after.
Base
Repository containing various system daemons, that are considered fundamental for the OS.
You can see what each component does in the following list:
- audiod : Daemon used to process the sound drivers audio
- bootstrap : First code that the kernel executes, responsible for spawning the init daemon
- daemon : Redox daemon library
- drivers
- init : Daemon used to start most system components and programs
- initfs : Filesystem with the necessary system components to run RedoxFS
- ipcd : Daemon used for inter-process communication
- logd : Daemon used to log system components and daemons
- netstack : Daemon used for networking
- ptyd : Daemon used for pseudo-terminal
- ramfs : RAM filesystem
- randd : Daemon used for random number generation
- zerod : Daemon used to discard all writes and fill read buffers with zero
How To Contribute
To learn how to contribute you need to read the following document:
If you want to contribute to drivers read its README
Development
To learn how to do development with these system components inside the Redox build system you need to read the Build System and Coding and Building pages.
How To Build
It is recommended to build this system component via the Redox build system, you can learn how to do it on the Building Redox page.
To build and test outside the build system, install redoxer then use check.sh script to build or test:
./check.sh- Check build for x86_64./check.sh --arch=ARCH- Check build for specific ARCH (aarch64,i586,riscv64gc)./check.sh --all- Check build for all ARCH./check.sh --test- Check the base system boots up on x86_64
You can also use make install to inspect the content on ./sysroot, or make test-gui to test booting with orbital interactively.