Development June 2012

development@lists.ipfire.org

3 participants
2 discussions

[Development] Recent networking changes
by Michael Tremer 01 Jul '12

01 Jul '12

Good morning, I would like to update you about the recent changes on the networking code. I reckon nobody already noticed. Right at the beginning I would like to say, that I really need help to test my patches. I have done as much as I could possibly do, but this kind of code should be running very well and it's a pain in the ass when you have a box without any network connectivity. ---- * Support for DHCP, which has been requested several times at the summit, has been added and is currently working for me. I'll probably need more testers to verify the functionality, so please join. You'll need to checkout the network git and make sure you have installed the dhcp package from unstable: http://git.ipfire.org/?p=network.git;a=summary dhcp-4.2.2-3.ip3: https://pakfire.ipfire.org/build/df9a43e6-8d99-4ac7-973a-239a9120211b To enable the DHCP client on a zone type: network zone upl0 config create ipv4-dhcp ---- * Basic (!) firewalling support, which has no option to be configured, yet has been added. That means that I have been porting some of my old testing code I have written in 2009 to the network package. It can be enabled by running "firewall start" and disabled by typing "firewall stop". Don't expect to reach the internet anymore. The interesting part here is the structure of the chains. Have a look at "iptables -L -n -v". ---- * Hotplugging for USB devices. There has been some code, but due changes in udev and systemd it was not working anymore. This has been fixed and there has been support added for wireless devices. Example #1: If you now plug in a USB-LAN adapter, you will automatically create a port configuration for that device which is called p0, p1, ..., pN. If you unplug the adapter, the device will disappear automatically and will be removed from the zone where it has been in. If you plug it in again and there is a zone configuration for that port, the port will automatically added to the zone (if the zone is already running). Example #2: A wireless device is treated somewhat differently. When plugged in, there won't show up any interface (like wlan0). The reason for that is, that wireless devices can have multiple interfaces at the same time (think of multiple SSID access points). Those interfaces will be created when they are needed and automatically created when the USB device is plugged in. When you are building a wireless access point please make sure you have at least hostapd-0.7.3-2.ip3 and iw installed: https://pakfire.ipfire.org/build/08e1b509-2198-459f-9de2-2a9c8aa5a38e Please set up some testing hardware and check if this is working on your box as well. ---- * systemd is controlling the zones. Which enables us to them in parallel and access their status via dbus. ---- To not ask too much from you in a single email, I will stop here and we will see in about a week with what I am coming up then :D Again my request: Please test and file bug reports against: https://bugzilla.ipfire.org/enter_bug.cgi?product=IPFire&component=network Michael

2 5

[Development] New repository for current IPFire content
by Michael Tremer 21 Jun '12

21 Jun '12

Hello mirror admins, some people from Indonesia asked me if we could try to decrease the size of the data we have on the mirrors and therefore I created a new repository that is called "current". "current" contains the latest two releases from each series that is currently maintained (this is IPFire 2 at the moment) and all the other releases won't be up. Supposedly they don't get downloaded that often anyway, it is okay for us to have them mirrored only on a couple of servers. "current" also holds the complete package tree of the current stable release (which is IPFire 2 only right now). We need to mirror that too. If we didn't the whole mirror thing would not make very much sense. So these are the current repositories: full : 24G current: 3.3GB So, we would like you to switch to the current repository if you are still using the older "pakfire2" repository that comes only with the packages for IPFire 2. If you have the possibility to mirror the whole content, please choose that one. Thank for mirroring our small project. We appreciate it very much. Michael

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Development June 2012