RFC: ip_nat|conntrack_h323.c on 2.6, first preview
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest5 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | update kernel requiresh323-conntrack-nat/ | +1 | 0 replies | |
| 2/5 | author update | +0 | 1 reply | |
| 3/5 | whitespace and indentationh323-conntrack-nat/ h323-conntrack-nat/ | +51 | 0 replies | |
| 4/5 | use c99 initializersh323-conntrack-nat/ h323-conntrack-nat/ | +46 | 0 replies | |
| 5/5 | port the module to Linux 2.6h323-conntrack-nat/ h323-conntrack-nat/ h323-conntrack-nat/ | +146 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH pom-ng 0/5] RFC: ip_nat|conntrack_h323.c on 2.6, first preview
Hi,
I have worked a bit on porting the H.323 conntrack module to Linux 2.6. Here is my first preview. Both connection tracking and NAT work well in my home network (gnomemeeting and ohphone, tunneling disabled).
It's still the old brute force method, no real protocol evaluation is performed. I will implement that the "right" way after the port to the Linux 2.6 API is finished and tested. The current algorithm is not recommended for production environments, because it is insecure, sometimes buggy and horribly inefficient.
The patches apply to patch-o-matic-ng from svn. Due to recent API changes, you need kernel 2.6.10-mm2 or later. I am currently using 2.6.11-rc1.
Using the module is easy: patch your kernel as usual with patch-o-matic-ng, enable H.323 connection tracking and NAT in the kernel configuration, boot the new kernel. Now the module should see all incoming, outgoing and forwarded TCP connections on port 1720, and lets the state module know about them.
I would appreciate comments and discussion about my patches and the H.323 module.
Max