| 1 |
IPTState Bugs |
| 2 |
|
| 3 |
KNOWN BUGS |
| 4 |
We keep track of bugs in our bugtracker on our Sourceforge page. However, before |
| 5 |
filing bugs, be aware of bugs in these other pieces of software that may affect |
| 6 |
your iptstate experience: |
| 7 |
|
| 8 |
- libnetfilter_conntrack 0.0.50 has a bug that prevents iptstate from |
| 9 |
deleting ICMP states. I wrote the following patch which the netfilter folks |
| 10 |
have already applied to their SVN tree: |
| 11 |
http://www.phildev.net/linux/patches/libnetfilter_conntrack-0.0.50_icmp_id.patch |
| 12 |
You can use it if this affects you. |
| 13 |
|
| 14 |
- There seems to be a small memory leak somewhere in ncurses. See |
| 15 |
http://www.phildev.net/iptstate/memleak.html |
| 16 |
for details. This won't effect most users much, but you want to be weary of |
| 17 |
leaving iptstate running on very busy firewalls for very long periods of time |
| 18 |
(a day or more). This bug has been reported to ncurses, see above URL. |
| 19 |
|
| 20 |
ABOUT BUGS |
| 21 |
If you find a bug in IPTState you should file a bug at our bugtracker: |
| 22 |
https://sourceforge.net/tracker/?group_id=52748&atid=467897 |
| 23 |
OR mail our -devel list: |
| 24 |
https://lists.sourceforge.net/lists/listinfo/iptstate-devel |
| 25 |
|
| 26 |
If you are unsure if it's a bug or need support, please use the -devel mailing |
| 27 |
list. |
| 28 |
|
| 29 |
Sending a bug to your distro or some public forum is not going to let me know. |
| 30 |
I can't fix things I don't know about. So make sure I know! |
| 31 |
|
| 32 |
ABOUT MY RESPONSE |
| 33 |
If your bug is serious - i.e. compilation errors, a major a functionality is |
| 34 |
broken, or a security problem I'll usually give you pretty immediate attention. |
| 35 |
If it's a very minor bug, or a feature request, I'll respond as I have time. |
| 36 |
|
| 37 |
ABOUT PATCHES |
| 38 |
Patches are welcome but not necessary. I will fix bugs, don't worry. If you |
| 39 |
would like to contribute code, PLEASE use consistent style to the rest of the |
| 40 |
code. If you send a patch, it should be accompanied with a good explanation of |
| 41 |
what it does and why. If it fixes a bug, it should also be accompanied by a |
| 42 |
bug report in our bug tracker. |
| 43 |
|
| 44 |
ABOUT BUG REPORTS |
| 45 |
Please be sure to include these things in bug reports: |
| 46 |
- your iptstate version |
| 47 |
- your distribution and distribution version |
| 48 |
- your kernel version |
| 49 |
- your g++ version (if you built it yourself) |
| 50 |
- your make version (if you built it yourself) |
| 51 |
- your glibc version (if you built it yourself) |
| 52 |
- your ncurses version |
| 53 |
- your libnetfilter_conntrack version |
| 54 |
- any relevant output and/or errors |
| 55 |
|
| 56 |
Once again, distributions don't always forward bug reports upstream, so |
| 57 |
please send bug reports to me if you want bugs fixed. |
| 58 |
|
| 59 |
Thanks! |
| 60 |
|
| 61 |
Phil Dibowitz |
| 62 |
phil AT ipom DOT com |