Router & Proxys

IPCOP

Documentationen (via www.ipcop.org)

IPCop Schnellstartanleitung (v1.x)

Installation Manual (v1.x)

Administration Manual (v1.x)

Netzwerkskizzen

Addon

URL-Filter (via urlfilter.net)

Advanced Proxy (via advproxy.net)

Net-Traffic (via blockouttraffic.de)

Installation von Addons

  • Nach dem Herunterladen des Addons muss es auf den IPCop kopiert werden
  • Kopieren Sie die Datei " Addon_VERSION.tar.gz " auf Ihren IPCop (mit Hilfe von SCP oder WinSCP bzw. FileZilla) nach " /tmp/ "
  • Entpacken des Archivs mit " tar zxvf Addon_VERSION.tar.gz "
  • Wechseln in den Ordner: " cd Addon_VERSION "
  • Installieren mit "./install" bzw. "./setup. (Readme lesen)
  • Nach erfolgreicher Installation kann der Ordner wieder gelöscht werden

IPCop Konfiguration in der internetLOUNGE

Hardware
Fujitsu Siemens
Pentium III
933 MHz
Software
IPCop Version: 1.4.21
Advanced Proxy
URL Filter
Net-Traffic

sonstige

IPCop Hardware Compatibility List (via rkaehler.de)

IPFIRE

IPFire 2.21 - Core Update 126 is available for testing

The next update is available for testing! This update comes with a new kernel and security enhancements and will hopefully be released as the last maintenance update for this year. This change log is rather short, but the changes are very important.

Linux 4.14.86

The kernel has been updated to the latest version of the Linux 4.14.x branch which brings various improvements around stability, enhances performance and fixes some security vulnerabilities. This kernel also has major updates for the Spectre and Meltdown vulnerabilities that remove previously existent performance penalties in some use-cases.

The kernel's modules are now compressed with the XZ algorithm which will save some space on disk as the kernel is one of the largest components of IPFire.

Misc.

  • openssl has been updated to 1.1.0j and 1.0.2q which fixes some minor security issues and has various bug fixes
  • The bind package has now changed to ship shared libraries which it did not before. Those allow that commands like dig and host use those shared libraries and are no longer statically linked. This makes the files a lot smaller.
  • Stéphane Pautrel has substancially improved the French translation of IPFire. Thank you very much for that!

Add-ons

  • Updated packages: bird 2.0.2, nano 3.2,
  • New packages: shairport-sync

Contributing Companies

I have recently talked about how to contribute to the project. As an Open Source project, we always appeal to individuals and ask them for their contributions to make IPFire better - whether that is code or donations.

But today, I would like to talk to the companies that use IPFire and point out a common habit that I have noticed:

There are forks of IPFire

I know for a fact, that many companies out there are maintaining their own fork of IPFire. That is not a full-fledged fork of IPFire with their own website or community. It is rather, that they make a couple of changes to the IPFire system every time they are deploying it.

Those changes can be small. Maybe it is a script that makes monitoring work a little bit easier. Maybe it fixes a couple of minor bugs that we did not find yet. I think these changes technically make their version of IPFire a fork.

But forks are bad. They take away something from a community that should be about giving back instead of everyone working on their own. They immensely create overhead for those companies because work needs to be done over and over again. Not only in the community when a certain bug is found and a fix is being developed although one already exists somewhere out there. It also comes at a high cost for the company that has to adjust their changes and rewrite their patches over and over again when something changes in IPFire. I think everyone can agree on that this is a waste of everybody's time and difficult and painful, too.

Stopped installing updates?

A common recipe against that is that people stop applying updates. I cannot warn strongly enough what a bad idea that is. On fireinfo, we can see that there are many systems running today that have not received latest updates and one often-heard reason for that is that the update "will break our changes" or "the system didn't come back up any more and we had to roll back" and then the system just stays in that state.

Get your changes into IPFire and you will never have to worry about this again.

Come on and contribute back!

Therefore, I would like to invite all the companies out there who are doing this to become a contributor to the Open Source project. Bring in you bug fixes, bring in your smaller features and scripts where you think that only you need them. This is giving something back to the community and you will see very quickly how soon you will benefit from this again, too.

If you think that your code needs to be a little bit polished before it is ready for production, talk to us and get feedback. IPFire developers are available for hire and can help you out.

IPFire will become a lot better through these small contributions and they will make it work in even more environments out there. Tested and approved by you, the community.


FLI4L

Release der stabilen fli4l Version 3.10.15

Nach gut drei Monaten Entwicklung stellt das fli4l-Team das nächste stabile Release der...

Release der stabilen fli4l Version 3.10.14

Nach gut drei Monaten Entwicklung stellt das fli4l-Team das nächste stabile Release der...

Release der stabilen fli4l Version 3.10.13

Nach gut drei Monaten Entwicklung stellt das fli4l-Team das nächste stabile Release der...

Release der stabilen fli4l Version 3.10.12

Nach etwas mehr als drei Monaten Entwicklungsphase stellt das fli4l-Team das nächste stabile...

Aktualisierung des wöchentlichen Tarballs verfügbar

Nachdem nun die neue Entwicklungsserver installiert und konfiguriert sind, nochmals vielen Dank an...

Release der stabilen fli4l Version 3.10.11

Nach knapp dreimonatiger Entwicklungsphase stellt das fli4l-Team das nächste stabile Release der...

Release der stabilen fli4l Version 3.10.10

Nach knapp dreimonatiger Entwicklungsphase stellt das fli4l-Team das nächste stabile Release der...

Build von fli4l-Archiven bricht unter Windows 10 (1703) mit Fehler ab

Bei Tests mit dem ab dem 11. April durch Microsoft ausgerollten Update für Windows 10 auf die...

Release der stabilen fli4l Version 3.10.9

Nach knapp dreimonatiger Entwicklungsphase stellt das fli4l-Team das nächstestabile Release der...

Release der stabilen fli4l Version 3.10.8

Nach knapp dreimonatiger Entwicklungsphase stellt das fli4l-Team das nächste stabile Release der...

LEG LOS! Anlaufstelle für Jugendmedienarbeit Berlin-Lichtenberg 2006-2017