Development

development@lists.ipfire.org

2 participants
6279 discussions

AW: today an IPfire Developer Meeting?
by Alexander Marx 15 Nov '12

15 Nov '12

Will be there at 20:15 Alex Daniel Weismüller <whytea(a)ipfire.org> hat geschrieben:Hi there In case of the latest activities here on the mailing list there are few things I would like to talk about. I think it would be helpful to talk to each other directly so I suggest that we meet us today at 19:30 hours in the IRC developer channel. Please let me know who will participate. - Daniel __________________________________________ You need a firewall? Easy to use? Powerful? Modular? For free? www.ipfire.org An Open Source Firewall Solution _______________________________________________ Development mailing list Development(a)lists.ipfire.org http://lists.ipfire.org/mailman/listinfo/development

1 0

today an IPfire Developer Meeting?
by Daniel Weismüller 15 Nov '12

15 Nov '12

Hi there In case of the latest activities here on the mailing list there are few things I would like to talk about. I think it would be helpful to talk to each other directly so I suggest that we meet us today at 19:30 hours in the IRC developer channel. Please let me know who will participate. - Daniel __________________________________________ You need a firewall? Easy to use? Powerful? Modular? For free? www.ipfire.org An Open Source Firewall Solution

2 1

CCD 15-11-2012
by Alexander Marx 15 Nov '12

15 Nov '12

Dear List! I made the latest modifications and tested mostly all possibilities. Tested: Roadwarrior with dynamic/static ip works Roadwarrior changed network static->dynamic, dynamic->static, static->static works Roadwarrior IROUTE (Network behind client) works Roadwarrior ROUTE (Network behind IPFIRE) works Converting old clients to new ccd files works Please test this Version. Files go to: Directoy "Tools" - all files in this directory go to /usr/bin/ (make them executable with: chmod +x ccd.pl lang.sh) de.pl, en.pl -> /var/ipfire/langs general-functions.pl -> /var/ipfire/ ovpnmain.cgi -> /srv/web/ipfire/cgi-bin Then make Languagefiles with new tool "lang.sh" ! (no need to search for the long command in lang.pl anymore ;-)) After that, just execute ccd.pl and your old clients will be converted. Now TEST,TEST,TEST! -- Alexander Marx Fachinformatiker Systemintegration

2 3

Re: CCD 8.11.2012
by Michael Tremer 15 Nov '12

15 Nov '12

On Thu, 2012-11-15 at 13:17 +0100, Alexander Marx wrote: > > I will answer the original here: > > > > > Am 13.11.2012 16:08, schrieb Michael Tremer: > > Why is it necessary to stop the roadwarrior server to manage the IP > > address pools? I guess a note that all changes require a restart would > > be sufficient. > The Button is clickable when server is stopped. That makes sense > because when you can edit the static networks, they will be written in > the server.conf and so the ovpn server needs a restart. > Other Question: WHY AM I NOT ABLE TO EDIT ADVANCED SERVER OPTIONS, > WHEN SERVER IS RUNNING?!!! Right, that is exactly the same problem here. I know that you cannot edit the settings, but the user should still be able to view them. > > The legend below the table it somewhat messy and unaligned. Don't know > > if that was already the case before. > Was the case before, didn't touch that! Okay. Using the German translation of the WUI does not show this error. > > The name field accepts values with a comma. Try it out to see the > > damage. > > It is also possible to add subnets twice or to add overlapping subnets. > Fixed. Well, I cannot have a space in the description, which is not cool. > > Client configuration page: > > > > There is again "net" all over the page. Again "Net name" -> "Name", "IP > > address pool" -> "Network", "Host address" -> "Assigned IP address". > > The table is missing a headline. > Fixed, except Headline. Don#t know if that makes sense here. I can fix > that, too. I think so. But it's not a must for me. Let it be as it is right now, then. > > "Dynamic OpenVPN server addresspool" -> "Dynamic OpenVPN IP address > > pool". One could also add the network, just to be sure. > Fixed. Could you please add the network to that line? > > "Net to route" does not really explain what those boxes to. "Behind > > Client" is not a possible explanation because it depends on the point of > > view. > We phoned on that one and agreed to name it "Network behind client" > And "Network behind IPFIRE". > If you don't like it now, tell me how to name it! It's not fine. Indeed it is hard to find a better label for those boxes, but these are bogus. > > The select box below is really cool. However, "Green" is spelled mixed > > case, the other options "BLUE" and "ORANGE" are all upper case. Why is > > that? > Fixed. Was in the language file en.pl green was "Green" orange "ORANGE > and blue BLUE That's bad. > > Code review: > > > > I see that the entire web user interface is a mess and I see that nobody > > likes to touch it. But we need to make sure that we don't introduce new > > problems, because IPFire 2 needs to be maintained for many years and I > > don't want to make this a hell to ourselves. > > > > So. Don't comment in German. Comments in English are a requirement. > > In case a function replaces an other one, remove the old (and buggy?) > > function. Make sure that it is clear what arguments a function expects > > and what the return value is. Use meaningful names for variables. I see > > that "$a, $b, $c, $d" is much more easy to type, but I find "$byte1, > > $byte2, ..." better. > Fixed. Didn't check that. > > Also code in a way that is easy to understand. Perl > > let's users to write many things in one line, but that code does not > > execute faster. Make clear what you do. > > > > Remove the tags which say which lines have been added for the CCD > > functionality. We use git to track those things. > Also phoned on that one and agreed to kick the last comments when code > gets mainstream. Yeah, that was today :D > SO: WHICH HALF OF THE MAIL DID I MISS?! See above.

1 0

CCD Extension 14-11-2012
by Alexander Marx 14 Nov '12

14 Nov '12

Dear List! I hope this is the final package ;-) All points from michaels Mail are changed, also a few additional checks where implemented. Please test the package and give feedback! files go to: de.pl -> /var/ipfire/langs/ en.pl -> /var/ipfire/langs/ general-functions.pl -> /var/ipfire/ ovpnmain.cgi -> /srv/web/ipfire/cgi-bin/ after that, create languagefiles. For this, i appended a file i use myself. just copy lang.sh to /usr/bin/ of your ipfire and make it executable with chmod +x /usr/bin/lang.sh After that you just have to type lang.sh and languagefiles will be build! -- Alexander Marx Fachinformatiker Systemintegration

1 1

Firewall Groups 2
by Alexander Marx 13 Nov '12

13 Nov '12

Dear List, Please take this version. I gave you wrong information: The directory needed must be /var/ipfire/fwhosts Sorry ;-) -- Alexander Marx Fachinformatiker Systemintegration

3 3

CCD 8.11.2012
by Alexander Marx 13 Nov '12

13 Nov '12

Dear List! Just talked to Michael. He would like to see the standard networks in the routingbox (Green,Orange and Blue if they exist). So i coded it! I deleted the standard route line in the server config, and therefore i put GREEN in the routingbox as Default. As always, comments are welcome. -- Alexander Marx Fachinformatiker Systemintegration

2 1

Firewall Groups
by Alexander Marx 12 Nov '12

12 Nov '12

Dear List, I reviewed the code for the firewall groups and found out that ii is mostly unusable. Besides the look it lacks some functionality. So if you edit a group, it is edited, but the firewallrules are not updated! That seems to be a bug. I want to develop a firewall gui for the forwarding firewalll (VPN and so on) Therefor i need some extensions. So i wrote them. First extension is the ccd extension, which should be tested by everyone. The next extension is a group-management extension which can be used by the outgoing firewall and the forward firewall (Which i start later) Right now, the group extension is completely seperated from other code and i want to use it for my project. Please install it and test it. Therefor you have to create a directory /var/ipfire/forward for nobody. Then test the extension. It just creates 3 Textfiles (hosts, Net and Groups) If you like it and it finds the way into the distribution, i will go on developing a gui for the forward firewall. Any comments are welcome. This is early code! -- Alexander Marx Fachinformatiker Systemintegration

1 0

CCD 6.11.2012
by Alexander Marx 07 Nov '12

07 Nov '12

Dear List! Again a new package. changes: The Routing box is no longer a textarea. It is now a multiselectbox, which has only the options to select already defined routes from ipfire, which makes sense. So you are only able to push routes to networks which are existent! Therefor i read the /var/ipfire/main/routing file. Also i don't know if that is correct, because if i enter some routes in the ipfire, i can't see them when doing a route on the console. Another point: Can someone please tell me how i get my local git repo synchronised with the one on git.ipfire.org? I put my files in my local repo but i don't know how to sync my local branch "ccd" to the public server. maybe someone can give me some sample commands. my repo should be git://git.ipfire.org/people/amarx/ipfire-2.x.git Thank you -- -- sign Alexander Marx Fachinformatiker Systemintegration

2 6

CCD 7-11-2012
by Alexander Marx 07 Nov '12

07 Nov '12

Dear list another package with these improovements: routes behind client is a multiselectbox. Here the first entry is "Keine" or "None" which resets the route settings for the specific client. Alexander Marx Fachinformatiker Systemintegration

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

Development