20 Commits

Author SHA1 Message Date
Vincent Li
d30518a04a README: update the build url link
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2025-06-30 19:54:22 +00:00
Vincent Li
0879d828a7 README: use TLS url for bpfire.net 2025-05-21 15:53:12 +00:00
Vincent Li
8af09f38e0 README: update README
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2025-05-09 20:19:35 +00:00
Vincent Li
db7b863fa4 README: add image download link and discord
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2024-11-27 18:32:04 +00:00
Vincent Li
eadd074122 README: add Suricata multi XDP attachment support
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2024-10-18 20:04:35 +00:00
Vincent Li
f204528cf4 README: Add XDP GeoIP/Country blocklist
Vincent Li <vincent.mc.li@gmail.com>
2024-10-12 18:58:01 +00:00
Vincent Li
17d5413bc2 README: update TLS/SSL SNI blocklist to XDP
Lunatik sni filter currently does not work
for BPFire when chrome browser is used due to
clienthello > 1500 bytes, XDP TLS/SSL has
the same issue, to block domain access, it
appears XDP DNS domain blocking works more
reliable than SNI, so if there is need to block
chrome browser for some domain, use XDP DNS
domain blocking as mitigation.

see https://github.com/vincentmli/BPFire/issues/40

Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2024-10-01 00:28:37 +00:00
Vincent Li
e5464739c9 README: update XDP DNS and SNI blocklist feature
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2024-09-17 23:33:31 +00:00
Vincent Li
a6f4f1dc2e README: update BPFire project README
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2024-09-09 00:32:24 +00:00
Vincent Li
c946e2d263 README: update load balancer screen shot
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2024-06-01 14:15:48 +00:00
Vincent Li
01b41130e5 Update README.md
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2024-05-17 03:57:24 +00:00
Vincent Li
4d35e1845b update README build
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2024-05-01 20:51:17 +00:00
Vincent Li
c463d1d203 Add DPDK Pktgen 10G SYN flood test throughput 2024-04-28 22:16:45 +00:00
Vincent Li
1aac7c1a4c Add BPFire runnig in Microsoft HyperV pictures
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2024-04-24 16:27:35 +00:00
Vincent Li
1cd908092b Add XDP DDoS README UI screenshot
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2024-04-24 00:47:52 +00:00
Vincent Li
8b50f8d07c Rename FireBeeOS to BPFire
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2024-04-17 00:18:34 +00:00
Vincent Li
0c908cf913 Update README with demo link and download link
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2024-04-06 18:43:08 +00:00
Vincent Li
11d2901fc7 Update README with FireBeeOS
Signed-off-by: Vincent Li <vincent.mc.li@gmail.com>
2024-03-01 04:08:02 +00:00
Peter Müller
e6cbe7563f Improve README and CONTRIBUTING
- Strip tailing whitespaces
- Use shorter line length to make reading the files with editors or
  terminals without automatic line break easier
- Slightly improve the content of these files

Signed-off-by: Peter Müller <peter.mueller@ipfire.org>
2022-03-21 13:47:58 +00:00
Jonatan Schlag
a5a5857865 Add Readme and Contributing guidelines.
For people which just have found our source code especially over GitHub
sometimes seem to have problems finding out how to contribute. This is
sad as it prevents us building a bigger community. While we have a wiki
which conatins a lot informations, this seems to get overlooked. I guess
a contributing fact is that most software today has these informations
contained in the repository itself. While I am not going to duplicate
the wiki to have these informations in our repository I still think it
is a good idea to have a short guide to lead new contributers into the
right direction.

Someone now could argue that new people just a too * to look at the
right place and that's why we do not need these documents. I do not
think so because of several points:

First people get used to look for information at a readme. I guees that
is because of the fact both GitHub and Gitlab place the readme so
prominently.

Second starting in a new project is hard. Finding the right place where
to start is also not easy as every project is different. Giving people a
short introduction what the first steps could be is definitely needed.

Signed-off-by: Jonatan Schlag <jonatan.schlag@ipfire.org>
2022-03-21 13:39:02 +00:00