Documentation

documentation@lists.ipfire.org

226 discussions

Re: IPTraf-ng problem with version 1.1.4
by Erik K. 29 Aug '13

29 Aug '13

The patch seems to solve it. Fwd: [PATCH] BUGFIX: fix "Floating point exception" in tcplog_flowrate_msg() > make sure interval is at least 1 (bug was made in > "tcplog_flowrate_msg(): cleanup and fix") > > Reported-by: Erik K. <ummeegge(a)ipfire.org> > Signed-off-by: Vitezslav Samel <vitezslav(a)samel.cz> > --- > src/tcptable.c | 2 ++ > 1 files changed, 2 insertions(+), 0 deletions(-) > > diff --git a/src/tcptable.c b/src/tcptable.c > index a4133d9..e217b19 100644 > --- a/src/tcptable.c > +++ b/src/tcptable.c > @@ -437,6 +437,8 @@ static char *tcplog_flowrate_msg(struct tcptableent *entry, char *buf, > size_t bufsize) > { > time_t interval = time(NULL) - entry->conn_starttime; > + if (interval < 1) > + interval = 1; > > char rbuf[64]; > rate_print(entry->bcount / interval, rbuf, sizeof(rbuf)); > -- > 1.7.8.4 i will go for some further tests and bring it also to IPFires bugzilla for eventual news and/or other fixes. Greetings Erik Am 28.08.2013 um 20:03 schrieb Erik K.: > Hi Michael, > > Am 28.08.2013 um 13:26 schrieb Michael Tremer: > >> Hi Erik, >> >> On Wed, 2013-08-28 at 13:13 +0200, Erik K. wrote: >>> Hi all, >>> i want to report a problem with the unreleased, updated version of IPTraf-ng-1.1.4 . The problem occurs if i turn on the IPTraf logging, after a while i get an "Floating point exception" under the "Packets catured:" line and IPTraf-ng quits. Until now i couldn´t localize the problem, but it seems like a bug in the new version. >>> The IPTraf-ng version 1.1.3 works without this problem. >> >> This is most certainly a division by zero. If you do that, the floating >> point unit of the CPU throws a floating point exception. >> It is best to report that to the iptraf-ng developers and open a bug >> report about this on our own bugtracker as well, so that we can update >> as soon as a fix is available. > > i have sent an mail to IPTraf mailinglist and i´am currently compile the patched iptraf-ng source with some fixes from the community. Hope this solves the problem, will let you know this after some testing results. > >> >>> Beside info: >>> I have added an IPTraf-ng configuration for the logrotate.conf. In here --> http://git.ipfire.org/?p=people/ummeegge/ipfire-2.x.git;a=commit;h=16bcdaeb… the diff can be found. >> >> Should this be merged? Why is iptraf-ng writing log files any way? > > I think version 1.1.3 is also pretty much up to date (on my Fedora 16 system version 1.1.1 works) and a good possibility to use IPTraf-ng nevertheless in IPFire, i don´t know how much time it takes that the above mentioned patch will be provided in the official source code and also if it solves the problem. > > The logging of IPTraf-ng is very nice i think, especially with the ability of the filter usage the output can be very clear and applicable for different needs also easy to use for further processing with shell scripting. The configuration window allows to activate or deactivate the logging, so i thought it might be a good idea to add it also in logrotate.conf. > >> >> -Michael >> >> _______________________________________________ >> Development mailing list >> Development(a)lists.ipfire.org >> http://lists.ipfire.org/mailman/listinfo/development >

1 0

New things to translate: Tor, DNS Forwarding GUI, Wireless Client GUI
by Michael Tremer 21 Aug '13

21 Aug '13

Hello translators, I just wanted to shout out, that the documentation team has finished these three articles: * http://wiki.ipfire.org/en/configuration/network/dnsforward * http://wiki.ipfire.org/en/configuration/system/wlanclient * http://wiki.ipfire.org/en/addons/tor/start You may now translate them to your respective languages. Have fun, -Michael Please make that if you reply to this email and your answer is translation-related, to not post to the documentation mailing list, which is for documentation discussions only.

1 0

DNS Forwarding + Wireless Client + Tor [week two]
by Michael Tremer 21 Aug '13

21 Aug '13

Hey, so, this is the first try to get things down by the rules of the new wiki workflow [1]. As far as I can see you guys have been working on the DNS forwarding docs and wireless client docs. I would also like to add the documentation about the new Tor addon, which will be released to testers very shortly. All three of those are pretty advanced as far as I can see, so that we can skip the first week of the schedule where we write things from scratch. This is already done. Let's directly move on to week number two, were we review what has been done. What I want you to do now is to check if there is everything on the pages you definitely need to know. Is a novice user able to set up the add-on with the information that is provided on the pages? Set up a clean installation of IPFire and work through the guide step by step and check if it works. If so, great! If not, please add the required information and leaves us a note. If you have some bigger chances, please discuss them with the other guys first. Please only use the lists for discussions that nobody is left out. It would be great if the native speakers could check the spelling and grammar. Getting all three guides done until the end of the week would make me really happy. If you have some spare time, please have a look at the new TODO list I set up in the international area of the wiki [5]. There is a section where you can add pages that need to be improved. There is also one entry by me. This is the list of features we will work on in the next week. We also don't care about the translation of these pages, yet. Now, let's start! -Michael P.S. The Tor add-on is not available in the testing tree, yet. You will be able to install it by the end of the weekend. So if you need that to review the Tor documentation, please be patient and start with one of the others first. [1] http://wiki.ipfire.org/projects/docs/workflow [2] http://wiki.ipfire.org/en/configuration/network/dnsforward [3] http://wiki.ipfire.org/en/configuration/system/wlanclient [4] http://wiki.ipfire.org/en/addons/tor/start [5] http://wiki.ipfire.org/todo

4 11

Fwd: Translating rsync backup to usb-hard drive
by Luke Lawry 14 Aug '13

14 Aug '13

I noticed this in the script "locale=de_DE.utf8" which sets the language to German. It should be changed to an english variant. Luke -----

2 1

Translating rsync backup to usb-hard drive
by t.berthel＠gmx.net 14 Aug '13

14 Aug '13

Hi, here the next document of German "Backup auf USB-Festplatte" -> http://wiki.ipfire.org/de/optimization/usb-festplatte/start into English here -> http://wiki.ipfire.org/de/optimization/usb-harddisk/start Can someone check this times? Thanks. Thomas

3 4

Re: Translate VLAN with IPFire
by SCHUH Karl, SCHUH-TV 13 Aug '13

13 Aug '13

Hi, following Bernhards posting, I read through the wiki-page "VLAN with IPfire" and noticed one little thing, that may be unclear for new users. When you use VLANS, all VLANs must have an ID. So it would be fine to add the green network and its ID on the picture. From your code-snippet of the file vlans I suppose that green has ID=20. Best, Karl ----- Ursprüngliche Mail ----- > As usual, I've corrected the english text. > For the german version, I let it as is. This should be fixed by a > further step english-->german, when the english version is checked and > proved to be correct. > > Bernhard > > > Gesendet: Freitag, 09. August 2013 um 11:07 Uhr > > Von: "Thomas Berthel" <t.berthel(a)gmx.net> > > An: "Mailingliste IPFire" <documentation(a)lists.ipfire.org> > > Betreff: Translate VLAN with IPFire > > > > Hi, > > > > i have translate the documentation on "VLAN", here: > > in German -> http://wiki.ipfire.org/de/optimization/vlan/start > > > > to english here -> > > http://wiki.ipfire.org/en/optimization/vlan/start > > > > Can someone check this times? Thanks. > > > > greetings, Thomas > > _______________________________________________ > > Documentation mailing list > > Documentation(a)lists.ipfire.org > > http://lists.ipfire.org/mailman/listinfo/documentation > > > _______________________________________________ > Documentation mailing list > Documentation(a)lists.ipfire.org > http://lists.ipfire.org/mailman/listinfo/documentation -- Ing. Karl SCHUH Hauptstraße 23a A-7434 Bernstein +43(664)38 06 107 -- Ing. Karl SCHUH Hauptstraße 23a A-7434 Bernstein +43(664)38 06 107

4 3

New Translation Mailing Lists
by Michael Tremer 13 Aug '13

13 Aug '13

Hello, as promised I created some translation mailing list, so that all translation-related discussion can move from the documentation mailing list to those. The first one is for all kinds of translations and the coordination of those. I recommend to subscribe to that to all of you who are working on translations, because I will posts announcements and other important things on there. I also created a German translation list, which is for ... yeah, you know. I didn't know of there are any more people working actively on other languages, so I didn't create any more lists. If you need an extra list for your language, just contact me. Best, -Michael P.S. For those who I accidentally subscribed to one of those lists, I meant to invite you, but hit the wrong button. Sorry. Feel free to unsubscribe if you want to.

1 0

Not only wiki
by info＠drcomputer.nl 12 Aug '13

12 Aug '13

Hi there, I'm reading a lot regarding the wiki and it's translations. But I was wondering if the website could be translated in the same way. In this way, if people refer to IPFire website they can read it. For now everything looks so english! For example, if I surf to nl.ipfire.org I get the Dutch (NOT German!) language. Would this be an idea? I'm willing to translate it to dutch. Kind regards, drcomputer.nl

2 1

Aw: Translate VLAN with IPFire
by Bernhard Bitsch 10 Aug '13

10 Aug '13

1 0

Hey guys...
by Michael Tremer 10 Aug '13

10 Aug '13

Hey guys, on Thursday, Erik sent an email to the Core Developers which said that he won't have the time to work on the project, because of personal reasons and that his job requires him to travel a lot in the near future. He was the Wiki Coordinator [1] and we have currently been working on organizing the people who work on the documentation in a better way. The goal was to raise everybody's awareness about what there is to do, so that we work together as best as possible. As more and more volunteers have shown up in the last weeks and month, (which I am very happy about, by the way) I think that it is becoming more and more important that the documentation team will finally become a real "team", which more than just one person. As long as we don't have a coordinator, I wouldn't like seeing things going down, so that I am going to take the role for a little while, until we found solutions for the problems we need to sort out. This is not intended to go on for more than one or two weeks. What are those problems? * We started working on a so called "workflow" [2], which should help to keep us all on the "same page" - almost literally. * We are planning to build translation teams, so that the documentation team and the group of translations are completely independent. This only makes sense, because they always work independently and status of the translations also varies a lot. I am still undecided on how we should handle this, so please feel free to send me ideas or opinions on this list. * We have got a whole bunch of things to do at the moment. A lot of new functionality has been added to the distribution and for parts of that there is no documentation at all. So, there is a lot of chaos going on here right now. Now you know the reasons and I would be happy if we could solve this all together very soon. -Michael [1] http://wiki.ipfire.org/projects/docs/start [2] http://wiki.ipfire.org/projects/docs/workflow

2 3

← Newer
1
...
6
7
8
9
10
11
12
...
23
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Documentation