Development July 2012

development@lists.ipfire.org

2 participants
3 discussions

[Development] Benutzer Feedback
by Michael Liekmeier 01 Aug '12

01 Aug '12

Hallo, ich habe auf der Homepage gelesen, das ihr von Nutzern ein Feedback wünscht. Ich habe einige Dinge die ich Euch mitteilen möchte. Aber erstmals an alle Entwickler ein reisen Dankeschön. *Asterisk / MISDN / LCR * Bei der Version die zur Zeit zur Verfügung steht, hatte ich sporadisch abstürze. Nach langem hin und her habe ich den Fehler bei dem LCR Addon gefunden mit Hilfe von Google. Leider habe ich den genauen Fehler nicht mehr gespeichert. Dann hat mir ein Freund LCR 1.10 erstellt und seit dem stürzt Asterisk nicht mehr ab. *VDR* VDR läuft super, allerdings wäre es schön, wenn es ein Update auf die Version 1.7 geben würde. Denn die Streaming-Clients (EasyVDR / VDR vib1710) sind nicht abwärtskompatibel. *Samba* Samba läuft auch super, bloß SMB2 mit Win7 geht nicht, aber ich glaube das sollte bekannt sein. Um das Problem zu beseitigen, ist ein Update Samba 3.6 erforderlich. Ich hoffe, ich konnte ein wenig helfen mit meinem Feedback. Gruß Michael

2 1

[Development] Dynamic DNS Client for IPFire 3
by Michael Tremer 20 Jul '12

20 Jul '12

Hi, I pushed the first version of a dynamic DNS client for IPFire, yesterday: http://git.ipfire.org/?p=oddments/ddns.git;a=summary git://git.ipfire.org/oddments/ddns.git It is written entirely in Python and offers a class modem for the providers. Every provider gets an own class which updates the specified account. The configuration file syntax is unified and extensible, to support an easy way to add new accounts have the option to add some more configuration variables when needed. A lot of important stuff is already done like support for an upstream proxy server, a generic provider class and a basic command line tool. There are currently two providers supported: No-IP.com and selfhost.de IMPORTANT: I am not planning to add any more providers by myself. But I think there might be interest in having more providers and some more features, so this is an open request for a new maintainer of the tool. If you are a Python programmer and have interest in maintaining this little piece of software, write new features and fix bugs, please mail me. Michael P.S. I will eventually add some licensing information which is missing for now.

1 0

[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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Development July 2012